Siebel Business Rules Administration Guide > Configuring and Activating Rule Modules >

Configuring and Activating a Deployed Rules Module

To activate a rules module that you deployed from HaleyAuthority, you must:

• Confirm the following prerequisites:
  • The rules module exists and has been deployed from HaleyAuthority. See Deploying Rule Modules.
  • The Siebel client is logged in to the same datasource that you specified as the runtime datasource to use with Object Importer and to which you deployed rule modules from HaleyAuthority.
• Configure and activate the rules module in the Siebel client's Administration - Business Rules screen.
• Identify the implementation strategy you plan to use to execute the rule module and configure accordingly. For information about various implementation strategies, see About the Business Rule Service Business Service and its subtopics.

To configure and activate a rules module

1. From the site map in your Siebel application, choose Administration - Business Rules > Rule Modules List.
2. In the Rule Modules List view, in the Rule Modules applet, locate the rule module that you want to configure.

   If the module is not listed, it may not yet be deployed from HaleyAuthority or you may be logged in to a different datasource than you ran against when you configured the module in HaleyAuthority.

3. In the Business Object field, pick the business object to which this rules module applies. This is the same business object from which you imported objects for this module.
4. If the Inconsistent (read-only) field has a value of Y, then you must abort this procedure, resolve the rule module's inconsistency in HaleyAuthority, and re-deploy the rule module from HaleyAuthority.

   The Inconsistent flag indicates that this rule module is not consistent with the currently deployed semantic role model. For causes and remedies for this state, see Troubleshooting Rules Configuration and Activation.

5. The value of the Data Assertion Mode field determines whether one input data set to the Business Rule Service business service is asserted (loaded into memory) at a time, or all input data sets are asserted at once. An input data set here is a unit of transaction data consisting of the top-level business component and its child business components and fields, as defined by the BusCompList input property set. Pick one of the following values:
   • For All. Choose this option to assert all input data sets at once. This is the default choice.
   • For Each. Choose this option to assert one input data set at a time. Because only one input data set is in working memory at any time, this option minimizes the footprint of the working memory of the rules engine.

     NOTE:  For each particular collection of data sets that are being processed, performance may improve by choosing For Each instead of For All at a threshold number of data sets in the collection. At or above the threshold, performance improves. Because this threshold can differ depending upon the actual data, you may want to test for the threshold number in your development or test environment before deploying to your production environment.

6. In the detail Rule Module Relations applet, add a new rule module relation for each relation in the rule module that you are deploying. For each rule module relation, click the Business Component field, and pick a listed relation.
   • Your rule module relations list must include the unary relation (the relation with no Parent Business Component entry) for each top level business component in the rule module
   • Your rule module relations list must include all parent-child business component relations for all the business components that are used in the rule module.
   • You can provide an additional search specification on the business components for each relation record you create.
7. Step off of the current rule module relation record to save it.
8. In the Rule Modules applet, with the appropriate rule module selected, click the Activate button.

   After you activate the rule module, you cannot modify the rule module relations.

   NOTE:  The rule module and its associated relations are cached at runtime.

   For information on rule module loading and caching, see About Rule Modules Invocation: Loading, Using, and Caching.