Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 9 Hot Deployment : Modifications Allowed in Hot Deployment

Modifications Allowed in Hot Deployment
You can make only certain changes during a hot deployment. Supported changes are listed in Table 31, Hot Deployment Supported Modifications. Supported modifications for Cache OM are more limited than those for In Memory OM.
*  Cache object management  When Cache object management is used, hot deployment is available only for rules, rule functions, global variables, event timeout actions, and the following state machine components: transitions, entry and exit actions, timeout expressions and actions.
**  For state machine hot deployment  You can only hot deploy new state machines (and state machine states) that are associated with new concepts, that is, concepts added in the same hot deployment. Adding a state machine or state machine component that is associated with an existing concept modifies that concept, and concept modification is not allowed. Also see notes for Cache object management above.
***  Used only when cache is enabled    This is an alternate space feature used only when cache is nabled. It allows you to add new concepts as well properties to the existing concepts and is supported only for the concept types that are cache-only.
The new concept property works in rule conditions and actions and in rule functions, which should be properly saved to cache and backing store if any. It is supported for Cache OM with shared-nothing backing store or no backing store.
With no backing store, the default be.engine.cluster.as.tuple.explicit=true is required in the CDD.
Adding a concept property of the type Contained Concept with the contained concept type set to an existing concept is not supported.
Enabling Hot Deployment
As a safety measure hot deployment is disabled by default. You must enable hot deployment for specific processing units and then deploy those processing units and start them. You can then perform hot deployment to the running engines (processing units) that are enabled for hot deployment.
To Enable Hot Deployment
1.
2.
3.
See Chapter 29, Agent and Processing Unit Configuration in TIBCO BusinessEvents Developer’s Guide for more details.
4.
For details on performing a hot deployment, see Performing Hot Deployment in a TIBCO Administrator Domain and Performing Hot Deployment Outside a TIBCO Administrator Domain.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved