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.
For class file deployment, including hot deployment, you configure the following items:
- The location where the deployed application looks for the class files for deployment.
- Which engine or engines can and cannot function as class loaders.
At application startup, the first class loader that starts will load the generated classes from the preconfigured location to the cache, and other engines pick them up from the cache.
For hot deployment, you use JMX (and RMI for remote invocations) to load the class files into the cache, which causes them to be deployed to all engines.
You can also use JMX to unload class files from a running engine.
- Configuring for Loading and Deployment of Decision Table Classes
Generated decision table class files are created in the RMS project directory in the RMS’s shared directory. - Configuring for Hot Deployment and Unloading of Decision Table Classes
JMX is a Java standard for managing and monitoring Java applications and services. All agents expose MBeans that can be used from the JConsole application. - Configuring RMI Properties for Remote Invocation
If you want to invoke MBean operations from a remote client, you must have the RMI registry on the machine that hosts the MBeans. You can host the RMI server on cache servers.
Copyright © Cloud Software Group, Inc. All rights reserved.