Server Administration Application –
See also: Server Administration Application Home Page, Deployment Overview, Deployment Packages
This page shows all inbound deployments into the server system. These inbound deployments are created by developers and are then deployed to a specific server. A developer can choose to make a deployment in one of two ways:
On this page, deployments are displayed within their parent package. A package is identified by its name or a timestamp if it’s a temporary package. Deployments are identified using a timestamp.
There are no additional security requirements to access the
The Deployments Tab shows all deployments.
Filter criteria can be used to limit the list of packages/deployments shown.
Click the Filter button to refresh the display with the selected filter criteria.
Deployments are shown within their parent package. When a developer has deployed something directly from the studio tree, a temporary package with a timestamp id is created (see first entry in figure 1 above). Packages are shown in order of the most recent action with the latest one shown first. Within each package, deployments are also shown in order of the most recent action. The current deployment within each package is highlighted in yellow. Click the green refresh icon at the top of the panel to refresh the display.
Click on the package name to toggle the display of all deployments for that package.
Transported |
The deployment is held and has not yet been installed. Click the Install action in the right-hand column to install the deployment. Deployments are held when either:
|
Installed |
The deployment has been installed and activated. See install action below under Deployment Actions. |
Reverted |
The deployment has been manually reverted (backed out). The previous versions of all affected files have been activated. See revert install action below under Deployment Actions. |
Error |
An error occurred during deployment. The deployment has been automatically reverted. |
Select an action by clicking on the link in the right-hand column:
Install |
Installs and activates the deployment. This action is only available when either:
After activation:
|
Revert Install |
This action is only available for the most recent deployment within each package. All files that form part of the deployment are backed out and replaced with their previous versions. The activation of these earlier versions is handled in the same way as for the install action. |
This tab shows all deployments with Transported status. The files for these deployments have been transported to the server but have not yet been installed and activated. Click on the install link on the right-hand side to install a deployment.
The details of this display are the same as for the Deployments Tab except that an additional delete action (right-most column) is available – this removes the deployment from the server.
This popup panel shows details of each deployment. It is available by clicking on the Deployment id link for a deployment.
This section contains basic details for the deployment as described above.
This section contains one line for each deployment action. Note that deployment normally consists of two distinct actions – Transport and Install. Additional actions such as Revert may also be shown. Each action has a corresponding log which can be viewed by clicking the View log link to the left.
This section contains details of the package. This is empty for temporary packages.
This section contains a list of all deployed entities and server configuration files. The status of each entity/file is also shown which will be one of:
Unchanged |
The version of the entity/file in the deployment is identical to the previous version. |
New |
The entity/file is new i.e. it did not previously exist on the server. |
Changed |
The entity/file in the deployment already existed on the server but this is a changed version. |