Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Using Central Administration : Deploying Configurations

Deploying Configurations
Central Administration enables users to quickly update all modified servers by deploying all servers for which the user owns the lock with one action. In other words, the deploy action deploys every EMS server locked by the current user.
Permission Requirements
To deploy, the current user must have administrative credentials for each EMS server in the deployment. If you do not have adequate permissions to modify an EMS server, the deployment of that server fails.
If the user who owns the lock does not have the necessary permissions to deploy the changes, another user with administrative permissions can take the lock and deploy. See Take the Lock.
Deployment Errors
Deployment of an EMS server fails if the Central Administration encounters any errors while connecting to and updating the server. Errors include:
Each deployment can affect a number of EMS servers, but there is no dependency between the servers. That is, some EMS servers may deploy correctly while some fail. Those servers that did not deploy can attempt redeployment later. The server lock file remains in its edited state.
Deployment Results
Following a deployment, you can check its status in the deployment log. Review the status of each server:
Because deployment succeeds or fails for each EMS server individually, deployment results may differ for each server. If deployment to an EMS server fails, that server remains locked and editable by the user.
 
Deploy All Locked Servers
To deploy configuration changes made to EMS servers:
1.
Navigate to the Server Overview Page, or any properties page for an EMS server.
2.
3.
By default, the deployment name is the date and time of the deployment: year-month-day-hour-minute-second-milisecond. For example, 2012-09-08-17-11-06-73 indicates a deployment on September 8, 2012 at 5:11:06:73 in the afternoon.
4.
Click Deploy. If you wish to continue editing, click Cancel.
Once Deploy is clicked, the Central Administration server:
5.
If some cases, the EMS server requires a restart before the configuration changes take effect. If such cases, the server deployment log notes this requirement.
6.
Redeploy a Previous Configuration
If a deployment fails, you can easily roll back to a successful earlier deployment.
1.
2.
3.
4.
Click Yes to redeploy this version of the configuration, or No to retain the current configuration.
5.
If some cases, an EMS server requires a restart before the configuration changes take effect. If such cases, the server deployment log notes this requirement.
6.
The Central Administration server reverts all EMS servers deployed in the selected previous deployment.
Review the Deployment Logs
A record of all deployments is maintained on the Deployments Page. A log is kept for each deployment, showing providing useful details about the deployment.
To review a deployment record:
1.
2.
3.
4.
5.
To view the full log, click Full server deployment log available here. The full log includes all details about the deployment, including:
If the deployment was redeployed, each server log for each deployment is separated by a line of hash marks: #######.
 
Delete a Deployment Record
If desired, you can remove a failed or otherwise unwanted deployment from the Recent Deployments list. Once a deployment is deleted, you no longer have access to its logs, and cannot redeploy it.
To delete a deployment record:
1.
2.
3.
4.
Click Yes to the deployment record, or No to cancel and keep the record.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved