Configuring the Hot Deployment Settings

You cannot perform hot deployment for specific assets in a package. The unit of upgrade is a package. During hot deployment, Integration Server upgrades all the assets in a package and in case of any errors, Integration Server reverts the packages to the previous version.

If any of the assets in the package that is being deployed is being processed, Integration Server waits for the processing to complete or for a specified timeout period, whichever is earlier, before attempting to deploy the package.

If there are any long running tasks that you want to complete before deploying the packages, make sure that you configure the hot deployment timeout value to a value more than the time taken for the task to complete.

Integration Server ensures that processes such as HTTP/HTTPS/FTP/FTPS requests, scheduler tasks, file polling requests, emails, Messaging/JMS requests, and web service requests continue uninterrupted while performing hot deployment of packages.

In case the deployment of a new version of package fails, Integration Server provides the auto recover option using which you can recover the earlier version of the package.

When you install a package for the first time in Integration Server, if there is any error in hot deployment, Integration Server will not be able to automatically recover the package because a working copy of the package does not exist.

You can use the pub.packages.hotdeployment:cancel service to cancel a hot deployment operation. For more information, see webMethods Integration Server Built-In Services Reference.

Hot deployment is not cluster aware. Hot deployment of packages may not happen at the same time on all the server nodes in a cluster. Also, info and debug messages related to hot deployment in one server node will not be shared across the cluster nodes.

In case of scheduled user tasks, Integration Server assesses the dependency of packages that are being deployed and permits the completion of any scheduled user tasks that are already running, and suspends any scheduled user tasks that have not yet started till hot deployment is complete.

1. In Integration Server Administrator, click Settings > Hot Deployment > Edit Hot Deployment Settings.

2. Select Yes to enable hot deployment of packages.

3. In the Timeout field, specify the maximum time in seconds Integration Server should wait for the in-flight processing to continue before attempting to hot deploy the packages. The default is 60 seconds.

4. Select Yes for the Auto Recover option, if you want Integration Server to revert to the previous version of the package in case the deployment of a new version of the package fails. When you select Yes for the Auto Recover option, Integration Server copies the original package to the Integration Server_directory \instances\instance_name\replicate\salvage directory before it deploys the new version. Thus, in case of any error during hot deployment, Integration Server recovers and reverts to the original package.