Upon approval of a checkin request, RMS copies approved decision table files into the RMS project decisiondata directory. However, you can’t just manually copy decision tables into that directory. Either you must follow the commit and approval process, or you can perform an explicit check-in using JMX. Only if you do one of these procedures are decision tables available for Decision Manager users to check out.
● The checkinExtEntity option checks in the named decision project artifact.
● The checkinExtEntities option checks in all decision project artifacts (such as decision tables and domain model files) that are not yet checked in.
This procedure makes decision tables available for Decision Manager users. It does not create the class files required for deployment. See Deploying Decision Tables for more details.Ensure that the following properties are present in the BE_HOME/rms/bin/be-rms.tra file and restart the server:
1. Open a command window in the bin directory of your JDK installation and type jconsole. You see a dialog box similar to the following:
2. Select the connection corresponding to the node that you want to view. (Each node runs in one JVM.) Click Connect.
3.
4. In the right panel, select the Operations tab.
a. For the first parameter, specify the name of the RMS project. It must be in the correctly configured location (see Configuring RMS Server Properties). For example, if you were working with the example credit card application RMS project, you would enter CreditCardApplication.C:\tibco\be\3.0\rms\examples\CreditCardApplication\decisiondata\_Virtual_RF_BankUser_VirtualRuleFunction_bankUser.rulefunctionimpl
c. Click checkinExtEntity.
a. Specify the name of the RMS project. It must be in the correctly configured location (see Configuring RMS Server Properties). For example, if you were working with the example credit card application RMS project, you would enter CreditCardApplication.
b. Click checkinExtEntities.
Copyright © TIBCO Software Inc. All Rights Reserved.