![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
1. Navigate to the Server Overview Page, or any properties page for an EMS server.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.
4.
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.
5. To view the full log, click Full server deployment log available here. The full log includes all details about the deployment, including:
If this occurs, you can view the differences between the base configuration stored in Central Administration and the one held by the running EMS server, as well as between the base configuration and the configuration with the latest edits saved in the lock file that resulted in a rejected deployment. From there, you can choose which configuration to keep. This functionality is available through the Actions drop-down menu on the server deployment log page. Note that this menu is available only for deployments that have been rejected due to local changes.
See Refreshing the Server Configuration for more information on updating Central Administration with changes made to an EMS server using the Administration Tool, API calls, or by directly editing the configuration file.
4.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |