Users with correct permissions can unload (undeploy) previously deployed decision tables from a running BusinessEvents system.The procedure for performing the unload using Decision Manager Worklist view is provided in the section Undeploying (Unloading) Decision Tables. Before you can perform the procedure, however, you must perform configuration described in this section.
● Using a JMX-based unload operation If you have configured JMX to hot-deploy classes, you can also unload classes using JMX, with no additional configuration. See Configuring for Unloading of Decision Table Classes.
● By selecting the Unload action in the Worklist view This is a remote operation and requires RMI settings to be configured as explained below.When you select the Unload action in the Worklist view, Decision Manager sends the request to RMS, which relays it to the RMI server in the running BusinessEvents system, and the class (that is the decision table) is unloaded.
RMI is a Java standard that enables remote communication between Java programs. For an introduction to RMI, see the following:
●
● The BE_HOME/be/bin/be-engine.tra file in all BusinessEvents nodes (except those running only query agents).
1. In each file listed above, add or uncomment and configure the RMI properties as needed. For example:
Specifies if RMI functionality is enabled or not. Set to true to enable. Specifies the host name of the RMI host, that is, the name or IP address of a machine hosting one or more BusinessEvents nodes. An RMI server will be started on this machine.Note: Do not use nodes that contain only query agents.Default is localhost. If a machine has two BusinessEvents nodes, and you want to start two RMI servers, one for each node, specify a different port for each node.
Copyright © TIBCO Software Inc. All Rights Reserved.