Modifications Allowed in Hot Deployment
You can make only certain changes during a hot deployment. Also keep in mind that supported modifications for Cache OM are more limited than those for In Memory OM.
Resource | New | Modify | Delete |
---|---|---|---|
Rules | Yes | Yes | Yes |
Rule Functions | Yes | Yes | Yes |
Concepts* | Yes | ||
Global Variables | Yes | Yes | Yes |
Simple Events* | Yes | ||
Score Cards* | Yes | ||
Time Events* | Yes | ||
State Machines and States** | Yes | ||
State Machine Transitions | Yes | Yes | Yes |
State Machine Timeout Expressions | Yes | Yes | Yes |
State Machine Timeout Actions | Yes | Yes | Yes |
State Machine Entry Actions | Yes | Yes | Yes |
State Machine Exit Actions | Yes | Yes | Yes |
State Machine Event Timeout Actions | Yes | Yes | Yes |
Channels and Destinations* | |||
New Concept Property*** | Yes |
Explanations for Supported Modifications
- * 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.
Copyright © TIBCO Software Inc. All Rights Reserved.