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.

See Generated Files Location for default location for generated class files. The location can be configured using properties in the RMS.cdd file (See TIBCO BusinessEvents WebStudio User’s Guide of the TIBCO BusinessEvents documentation set for more details.)

You place these class files in a preconfigured location for deployment. This could be a network location accessible to all engines. A CDD property references this location. If different engines that act as class loaders point to this location differently, add the property at the PU (engine) level and specify it accordingly.

By default all engines act as class loaders. You can prevent specified engines from acting as class loaders using a CDD property.

Procedure

  1. In TIBCO BusinessEvents Studio, open the project to which you will deploy the decision table classes.
  2. Open the project CDD file in the CDD editor.
  3. As needed, add the following properties at the appropriate level of the CDD. 
    be.engine.cluster.externalClasses.path filepath-to-RMS-classes
be.engine.cluster.externalClasses.classLoader true
be.engine.cluster.externalClasses.packageExclusions

    See the following table for guidelines. The properties are ignored unless there are class files to be deployed, so they are harmless if present and not actually needed. See TIBCO BusinessEvents Configuration Guide for details on CDD configuration.

    Configuration Properties for Deployment of Decision Table Classes
    Property Notes
    be.engine.cluster.externalClasses.path Specifies the file path to the directory where classes are placed for loading. If engines point to this location differently, for example, because a network drive is mounted differently on the machine where they are running, or if you must use more than one location and copy the class files to all such locations, specify this property as needed at the PU level.

    Tip: For single-machine installations such as are used for testing or demonstration purposes, you can set the value of this property to the directory specified by the ws.artifact.deploy.location property (See TIBCO BusinessEvents WebStudio User’s Guide of the TIBCO BusinessEvents documentation set for more details.) When decision tables are generated, they are placed in that directory. The class files would then be automatically available for deployment without manual copying.

    be.engine.cluster.externalClasses.classLoader By default this property is true, so if you want all engines to be able to load classes, do not add the property at all.

    If you want to prevent certain engines from acting as class loaders, add this property to their PU property sheets and set it to false.

    Note: Nodes that contain only query agents do not act as class loaders.

    Possible values:

    • true
    • false

    Default value is true.

    be.engine.cluster.externalClasses.packageExclusions If you will use the core Studio Tools option to generate all class files (see Generating All Project Class Files at the Command Line ), you must prevent all class files except decision table class files from being deployed.

    Add this property to the cluster level property sheet in the project CDD file. Specify the value as a semicolon-delimited list of packages of generated class files to exclude from being deployed.

Related tasks