Abstract: Remote installation of an application program is provided via a configuration of the application program corresponding to a particular user of the local application. The configuration is defined and stored on a remote server. In response to a user request, a determination is made that the stored configuration corresponds to the requesting user, the user is authenticated, and data is downloaded from the remote server according to the stored configuration. This stored configuration is also encrypted and stored in a manifest file which is also downloaded. Responsive to the user authentication, the manifest file is decrypted, and the application program is constructed pursuant to the configuration decrypted from the manifest file.

Abstract: A configuration of an application program corresponding to a particular user of the local application is defined and stored on a remote server. In response to the user requesting the application program, a session is initiated between the local data processing system and the remote data processing system, and the user is authenticated. Responsive to the user authentication, data is downloaded from the remote server to the local data processing system according to the stored configuration. This stored configuration may be encrypted and stored in a manifest file which is decrypted to produce a decrypted configuration in response to the user authentication, and data may be downloaded from the remote data processing system to the local data processing system according to the decrypted configuration. The application program may be constructed pursuant to the configuration file or the decrypted configuration file.

Abstract: An installation of an application program is updated by use of a stored configuration of the application program corresponding to a particular user of the local application. In response to a user request, a determination is made that the stored configuration corresponds to the requesting user. The stored configuration is checked to determine if any items described in the stored configuration have been updated. If an item has been updated, then the updated item is retrieved, and the application program is built with the updated item. This stored configuration may also be encrypted and stored in a manifest file which may be decrypted to produce a decrypted configuration responsive to a user authentication. The decrypted configuration is checked to determine if any items described in the decrypted configuration have been updated. If an item has been updated, then the updated item is retrieved, and the application program is built with the updated item.

Abstract: Accessing a legacy target file with a potentially corrupting development tool, where the target file is characterized by its attributes, and the development tool is characterized by its tool capabilities, including the capability to return the target file with changed attributes. Protecting target file attributes is accomplished by limiting development tool access to the target file if development tool capabilities mismatch target file attributes. This is achieved by determining target file attributes from a source of target file attribute information. The determination of access is done by matching target file attributes to tool capabilities and granting development tool access to the target file if there is a match of target file attributes and tool capabilities, and denying or limiting access if there is a mismatch. A further step is assigning a registration permission key tool to the development tool if the development tool capabilities match the target file attributes.

Abstract: Accessing a legacy target file with a potentially corrupting development tool, where the target file is characterized by its attributes, and the development tool is characterized by its tool capabilities, including the capability to return the target file with changed attributes. Protecting target file attributes is accomplished by limiting development tool access to the target file if development tool capabilities mismatch target file attributes. This is achieved by determining target file attributes from a source of target file attribute information. The determination of access is done by matching target file attributes to tool capabilities and granting development tool access to the target file if there is a match of target file attributes and tool capabilities, and denying or limiting access if there is a mismatch. A further step is assigning a registration permission key tool to the development tool if the development tool capabilities match the target file attributes.