Generating and Deploying Decision Table

You can generate EAR files in the Decision Manager user interface, which can be then deployed to be loaded by the engines.

Deployment of EAR files (including hot deployment) is documented in the TIBCO BusinessEvents Administration guide of the TIBCO BusinessEvents documentation set.

If RMS is used, you can generate individual decision table class files and deploy them. You can deploy them by placing them in a preconfigured directory. Using JMX, you can also hot deploy class files, and unload class files from a running application. Internally the action is to load class files into the cache, where all engines pick them up. You can also undeploy (unload) decision tables from a running application.

Some configuration is required before you can do these tasks.

Note: Deployment and unloading of decision table classes requires Cache object management as well as RMS to be used in the TIBCO BusinessEvents application.
  1. Configuring for Deployment and Unloading of Decision Table Classes
    Before deployment configure the deployment properties in the CDD file for deployment of classes at application startup, and for hot deployment and unloading of classes.
  2. Generating Deployable Files (EAR and Class Files)
    Deployable files are generated using the TIBCO BusinessEvents Studio project files, located in the RMS project’s folder.
  3. Deploying and Unloading Decision Table Class Files
    Advisory events for success and failure are asserted as needed during agent startup, and JMX-based hot deployment.
  4. Generated Files Location
    Location of generated files can be configured using deploy location properties (ws.artifact.deploy.location) in the RMS.cdd file.