Performing Hot Deployment Outside a TIBCO Administrator Domain
You can perform hot deployment when the TIBCO BusinessEvents project has not been deployed to a TIBCO Administrator domain only if the deployed application was enabled for hot deployment before it was deployed. You need to modify the project as needed and build the EAR file.
- Procedure
- In TIBCO BusinessEvents Studio, modify the TIBCO BusinessEvents project according to your needs. See
Modifications Allowed in Hot DeploymentYou can make only certain changes during a hot deployment. Also, supported modifications for Cache OM are more limited than those for In Memory OM.
Hot Deployment Supported ModificationsResource
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*
Concept Property***
Yes
* 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 alter space feature used only when the cache is enabled. You can add new concepts and properties to the existing concepts and it is supported only for the concept types that are cache-only.
The new concept and properties work 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, select the
Store Properties As Individual Fields check box in the CDD file under
Cluster > Object Management: [Cache] configuration. This property is selected by default when using shared nothing persistence.
Adding a concept and concept property is only supported for concept types that are cache-only. Adding a concept property of the type
Contained Concept with the contained concept type set to an existing concept is not supported. When adding a concept, it takes the default domain object settings.
for a list of modifications you can make.
Then rebuild the project EAR file.
- Verify that the new EAR file have the same name as the existing one.
- Replace the EAR File that was used to start the engine with the modified EAR file.
- Ensure that the modified EAR file has the same name and is placed in the same directory as the EAR file that was used to start the engine. The engine notices the changed file and performs the hot deployment at the next RTC cycle.