Copyright © Cloud Software Group, Inc. All Rights Reserved

Hot Deployment Overview

You can make certain changes to a set of TIBCO API Exchange Gateway configuration without shutting down the Core Engine. This is known as hot deployment.

Hot deployment process suspends north inbound channels and checks for any pending transactions to complete in memory. If there are any pending transactions, the Core Engine waits for the specified delay time before hot deploying the configuration. If there are no transactions in memory, the configuration is reloaded immediately..

Because a hot deployment might cause unexpected results with transactions currently in progress, we strongly recommend that you perform hot deployment only in a development and testing environment.

Enabling Hot Deployment

By default, hot deployment is not enabled. To enable the hot deployment feature, follow these steps:

1.	Navigate to the ASG_CONFIG_HOME/asg directory.

2.	Edit the asg.properties file to change the value of the following property to true:

tibco.clientVar.ASG/Deployments/AllowHotUpdate=true

3.	Deploy and restart the Core Engines that need to be hot deployed engines. For example, asg_core or asg_caching_core.

Invoking Hot Deployment

Hot deployment can be invoked from an MBean client by invoking the refreshConfig method in com.tibco.asg domain for the appropriate Core Engine.

refreshConfig method uses following parameters:

•	The first parameter is the location of the configuration directory used by the Core Engine.

•	The second parameter is the delay in milliseconds. If the delay value is -1, the Core Engine does not shutdown on any error during hot deployment. Otherwise, the Core Engine shuts down on error.

Copyright © Cloud Software Group, Inc. All Rights Reserved