Changing the Java XOM persistence type

If you set Java™ XOM management for a ruleset, you can specify the persistence properties for the XOM repository.

About this task

If you have set up management of the Java XOM for a ruleset, the Java XOM resources are stored in the Rule Execution Server persistence layer. The persistence type of the ruleset is defined first and the XOM persistence is a property of the ruleset persistence type. You can specify different persistence types for your rulesets and for your Java XOM resources. For example, you can set up the persistence type to file for the ruleset repository and to datasource for the XOM repository.

Procedure

To change persistence properties for your managed Java XOMs:

  1. Open the RAR deployment descriptor in any text or XML editor.
  2. Locate the property name <config-property-name>persistenceProperties</config-property-name>.
    <config-property>
       <config-property-name>persistenceProperties</config-property-name>
       <config-property-type>java.lang.String</config-property-type>
       <config-property-value>JNDI_NAME=jdbc/resdatasource,XOM_PERSISTENCE_TYPE=datasource,XOM_PERSISTENCE_JNDI_NAME=jdbc/resdatasource</config-property-value>
    </config-property>

    The <config-property-value> line defines the following parameters:

    • JNDI_NAME=jdbc/resdatasource is the value for the provider of the ruleset persistence type if that persistence type is set to datasource. See Changing the ruleset persistence type in the XU.
    • XOM_PERSISTENCE_TYPE is the persistence type for the XOM repository if you have set up Java XOM management for the ruleset.
      • If the XOM persistence type is set to datasource, the XOM_PERSISTENCE_JNDI_NAME parameter defines jdbc/resdatasource by default.
      • If the XOM persistence type is set to file, the XOM_PERSISTENCE_DIRECTORY parameter defines the res_xom directory by default.
  3. On the <config-property-value> line, change the XOM_PERSISTENCE_TYPE parameter as appropriate, then set up the second XOM_PERSISTENCE parameter accordingly.
  4. Save the deployment descriptor.
  5. Restart the application server.