Chapter 2 RMS and Decision Manager Configuration : Configuring for Deployment of Decision Table Classes

Configuring for Deployment of Decision Table Classes
After a decision project is approved, class files for the decision tables are generated in the deployment subdirectory of the RMS project directory. You can selectively deploy them to the production system.
See Deploying Decision Tables for the related administration procedures.
You can also undeploy class files that were earlier deployed. See Configuring for Unloading of Decision Table Classes).
Requires Cache Object Management  Deployment and undeployment of decision table classes requires Cache object management to be used in the BusinessEvents application.
Class Loaders
When classes are being deployed, a BusinessEvents node that has been configured as a class loader loads the generated classes to all the other nodes.
Nodes that contain only query agents cannot function as class loaders. Choose cache server nodes or nodes containing inference agents (or both).
Hot Deployment
You can also configure for hot deployment to a running system. Hot deployment (and one method of undeployment of classes) uses JMX. 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. An MBean is a managed bean, which is a Java object that can represent a manageable resource. For an introduction to JMX, see the following:
http://java.sun.com/developer/technicalArticles/J2SE/jmx.html
To Configure for Deployment of Decision Table Classes
1.
Open the BE_HOME/bin/be-engine.tra file for the node or nodes you will use for loading the classes.
For deployment at startup
2.
   be.engine.cluster.externalClasses.path filepath-to-RMS-classes
   be.engine.cluster.externalClasses.classLoader=true
For hot deployment
3.
For hot deployment, ensure that the following entry is present in the java.extended.properties property in all BusinessEvents nodes:
   -javaagent:%BE_HOME%/lib/cep-instrumentation.jar
The above property is required for hot deployment and is present in the TRA file as shipped.
See Table 6, BusinessEvents Engine Property Settings for Deploying Decision Table Classes for details on property settings.
4.
For hot deployment, also configure the following JMX-related properties in all BusinessEvents nodes. Some typical values are shown. Configure for your environment as needed.

 
# Coherence JMX properties
 
java.property.com.sun.management.jmxremote=true
java.property.com.sun.management.jmxremote.ssl=false
java.property.com.sun.management.jmxremote.port=5558
java.property.com.sun.management.jmxremote.authenticate=false

 
 
Specifies the filepath used by the cluster to load external rule classes created in Decision Manager to all BusinessEvents cluster nodes. Set on one or more nodes as needed.
Set this property in nodes where you also set be.engine.cluster.externalClasses.classLoader to true. Ensure these nodes can access the filepath.
Tip: If the value of this property is set to the value of the RMS property rms.project.deployment then when decision tables are approved, they are automatically available for deployment to BusinessEvents without manual copying.
If true, this node has the ability to load external rule classes to all cluster nodes. Set on one or more nodes as needed.
For related details, see notes for be.engine.cluster.externalClasses.path.
Note: Do not use nodes that contain only query agents.
Possible values: true or false.
Enables secure monitoring via SSL. If false, then SSL is not used.
Possible values: true or false.
Enables monitoring and management from remote systems on the specified port. Specify an unused port.
java.property.com.sun.management.jmxremote.authenticate
If set to false, JMX does not use passwords or access files. Access is available to all users.
Possible values: true or false.