Abstract: An installation package may have metadata concerning optional parameters for a software package to be installed. The metadata may be read by an installation system, and a user interface presented to a user for input on the parameters values. The installation system may store the parameters for later replication of the installation. The installation system may perform the installation on a local device or a remote device, and may further be capable of presenting the user interface on another device. In some embodiments, the metadata may be available to the installation system without having to open the installation package.

Abstract: A system and method for managing application version changes on a network server. A backup is made of a deployed application version. When an update version of the application is to be deployed, a backup of the current application, including dynamic data, is performed. The update version is deployed and automatically monitored. If the update version is determined to be healthy, it is backed up. If it is determined to not be healthy, the previous version is automatically retrieved and deployed. An application skeleton may be automatically generated to facilitate comparison and backups of the application.

Abstract: Described is a technology in which a non-administrator computer/web user is allowed to perform an administrative-level task within a certain context and/or scope. An authorization store is queried based on information (e.g., a provider, a username, and a path) provided with an authorization request, e.g., from an application via an API. The information in the authorization store, set up by an administrator, determines the administrative action is allowed. If so, a credential store provides credentials that allow the action to be runs before reverting the user to the prior set of credentials. Also described is a pluggable provider model through which the authorization store and/or delegation store are accessed, whereby the data maintained therein can be any format and/or at any location known to the associated provider.

Abstract: A system and method for managing application version changes on a network server. A backup is made of a deployed application version. When an update version of the application is to be deployed, a backup of the current application, including dynamic data, is performed. The update version is deployed and automatically monitored. If the update version is determined to be healthy, it is backed up. If it is determined to not be healthy, the previous version is automatically retrieved and deployed. An application skeleton may be automatically generated to facilitate comparison and backups of the application.

Abstract: An installation package may have metadata concerning optional parameters for a software package to be installed. The metadata may be read by an installation system, and a user interface presented to a user for input on the parameters values. The installation system may store the parameters for later replication of the installation. The installation system may perform the installation on a local device or a remote device, and may further be capable of presenting the user interface on another device. In some embodiments, the metadata may be available to the installation system without having to open the installation package.

Abstract: Described is a technology in which a non-administrator computer/web user is allowed to perform an administrative-level task within a certain context and/or scope. An authorization store is queried based on information (e.g., a provider, a username, and a path) provided with an authorization request, e.g., from an application via an API. The information in the authorization store, set up by an administrator, determines the administrative action is allowed. If so, a credential store provides credentials that allow the action to be runs before reverting the user to the prior set of credentials. Also described is a pluggable provider model through which the authorization store and/or delegation store are accessed, whereby the data maintained therein can be any format and/or at any location known to the associated provider.