Deployment Choices

You can make changes to a deployed application, and then deploy the changed application. The currently deployed application can continue to run while you make changes. When you deploy the updated application, the current application is automatically undeployed. You can revert to a previously deployed application, if the changes you made need be rolled back.

You can:

  • Select Stop running services before deployment to stop all running services before deploying the service. All services that should be redeployed are stopped. If, however, a service instance is in sync and Force redeployment of all services is not enabled, the running instance is not stopped. This option is disabled if any target machine has a TIBCO Hawk agent version lower than 5.3.

  • Indicate how many seconds can elapse after a stop request before a service is killed, using the Stop command, in Kill services that haven't stopped after (seconds).

  • Select Start successfully deployed services to stop and restart the services in the application after they have been successfully deployed. If you do not select this option, you can explicitly start the services later. See Starting or Stopping a Service Instance or Process Engine for details.

  • Select Force redeployment of all services to redeploy all services even if a service is in a synchronized state. This is useful if you have manually changed deployment files, or if you need to define NT Services to multiple hosts in a Microsoft Cluster.

  • Select Dynamic Symmetric Key to encrypt sensitive application data using a dynamically generated encryption key. See Deploying an Application Using Dynamic Encryption Key for more information.

If the Stop running services before deployment option is cleared, service instances in deployable state are not stopped while they are redeployed. However, they are stopped after a successful deployment. This option has no impact on the services instances that are in a synchronized state unless the Force redeployment of all services option is selected.

If the Start successfully deployed services option is enabled and the Stop running services before deployment option is cleared:

  • Existing service instances in running state are first stopped then restarted after .tra and .cmd files on target machines are updated.

  • Existing service instances not in running state are restarted when they are deployed.

  • Newly added service instances are restarted.

  • Removed service instances are stopped before they are removed.