Chapter 2 RMS and Decision Manager Configuration : Configuring Project Tester Options

Configuring Project Tester Options
When you test a decision project in Decision Manager, you can run the project in a restricted manner, or you can configure to more closely approximate the production system in action. Certain options require project-specific configuration. This section describes the options and explains how to configure for each option.
Project Tester Options
This section describes the options. Each option is selected using the property bui.tester.engine.feature.level (see Configuring Decision Manager Properties).
You must use local or full to test projects for which entries are added to the classpath.
For example, use local or full if the project uses custom functions, or is a BusinessEvents-ActiveMatrix BusinessWorks integration project running with a BusinessEvents container. (Decision Manager does not work with integration projects where ActiveMatrix BusinessWorks is the container.)
Minimal
The bui.extended.classpath property is not processed, and any JAR files listed are not available to the test engine.
This is the default option, and requires no additional configuration. If the project does not run successfully with this option, try using the local option.
Local
Makes all classes in the bui.extended.classpath available to the test engine.
Most projects can run in this mode. It can be slower to run than the minimal option. Configuration may be required to make properties set in the BusinessEvents property file, be-engine.tra, available to the tester. See Configuring for Local or Full Tester Options.
Full (Expert mode)
Makes all classes in the bui.extended.classpath available to the test engine.
This option runs the project in the tester engine as closely as possible to the way it runs in the BusinessEvents engine.
Configuration is required to make properties set in the BusinessEvents property file, be-engine.tra, available to the tester. Only expert users should attempt this mode. See Configuring for Local or Full Tester Options.
Configuring for Local or Full Tester Options
To configure for the local or full tester options, various properties set in the be-engine.tra file must also be added to the bui-config.tra file or DecisionManager.ini file, as explained in this section.
For the local option, you only need to define the bui.extended.classpath (see Classpath Configuration). For the full option you need to add more properties, to more fully reflect the configuration in the be.engine.tra file.
Where and how you add a property from the be-engine.tra file depends on whether it is a BusinessEvents engine property or not:
Copy BusinessEvents engine properties to the bui-config.tra file. (For example, be.engine.cluster.hasBackingStore, is an engine property.)
Add all other required properties as vmargs in the DecisionManager.ini file:
If the property begins with java.property, also remove java.property. For example java.property.tangosol.coherence.cluster becomes -Dtangosol.coherence.cluster.
Classpath Configuration
If you have to add entries to the classpath of the tester engine such as custom function JAR files, add them to the bui.extended.classpath property in the bui-config.tra file (see Configuring Decision Manager Properties).
Also ensure that all environment variables in the bui.extended.classpath are defined as vmargs in the DecisionManager.ini file.
As explained earlier in this section, you add all non-engine environment variables to the DecisionManager.ini file. For example, when configuring to test integrated decision projects where BusinessEvents is the container, you may need to provide ActiveMatrix BusinessWorks classpath information. Suppose a such a project requires this property in the be-engine.tra file:
java.property.palettePath=%BW_HOME%/lib/palettes%PSP%%BW_PLUGINS_HOME%/lib/palettes%PSP%%TRA_HOME%/lib/palettes
You would add the information to the DecisionManager.ini file as follows:

 
-DBW_HOME=c:/tibco/bw/5.4
-DBW_plugins_home=c:/tibco/bw/plugins
-DpalettePath=%BW_HOME%/lib/palettes;%BW_PLUGINS_HOME%/lib/palettes;%TRA_HOME%/lib/palettes

 
 
In BusinessEvents-ActiveMatrix BusinessWorks in process integration projects, the container application manages state and other aspects of the project.
You can use Decision Manager with such integration projects only where BusinessEvents is the container. When ActiveMatrix BusinessWorks is the container, BusinessEvents can’t use cache object management, which is required in order to work with decision tables from Decision Manager.