![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
The Central Administration server does not automatically update its configration snapshot for an EMS server. If configuration changes were made directly to the EMS server, such as through API calls, you should refresh the server configuration in Central Administration before deploying. See Refreshing the Server Configuration for details.Permission RequirementsTo 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 ErrorsDeployment 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 ResultsFollowing 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.
The deploy action deploys not only the selected server, but all servers for which the current user holds the lock. For example, if you have the lock on five servers, all five servers are updated when the deploy command is issued.
1. Navigate to the Server Overview Page, or any properties page for an EMS server.
3. In the dialog box that appears, enter an identifying name for the deployment. This name is used in the deployment archive, and will help you identify this deployment when you view its log, or should you need to redeploy at a future date.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.
5. To view details about the deployment, including any errors, click the Viewicon next to the deployment name.
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. If required, restart the EMS server. This task cannot be completed using the Central Administration web interface.
Only successful deployments can be redeployed. Any EMS servers that failed in the initial deployment are excluded from a redeployment. If only some of the EMS servers included in a deployment were successfully deployed, only those EMS servers are redeployed. If the initial deployment was wholly unsuccessful—none of the EMS servers deployed—the deployment in unavailable for redeployment.
4.
5. To view details about the deployment, including any errors, click the Viewicon next to the deployment name.
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. If required, restart the EMS servers. This task cannot be completed using the Central Administration web interface.The Central Administration server reverts all EMS servers deployed in the selected previous deployment.
Redeploying updates the EMS server but does not affect the working directory or lock file. As a result, the working copy and lock files in Central Administration are out of sync with the running EMS server.This allows you to retain the configuration changes made prior to the redeploy. To obtain the current configuration, refresh the EMS server configuration. See Refreshing the Server Configuration for details.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.
3.
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: #######.
It is best to regularly review your Recent Deployment list and delete records for deployments that are insignificant and unlikely to be redeployed. This practice ensures that the list is not over-crowded, and that essential deployment records can be easily located.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.
4.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |