Executing ODM business rules by using an ODMRules node

You can use an ODMRules node to execute IBM Operational Decision Manager (ODM) business rules.

1. Create a message flow containing an ODMRules node. For more information, see Creating a message flow.
2. Create an ODM Server policy that contains details of either a remote Operational Decision Manager (ODM) Rule Execution Server or a ruleset archive that has been downloaded and stored in the local file system.
   For more information, see Creating policies with the IBM App Connect Enterprise Toolkit and Using a local ruleset archive.
3. Configure the ODMRules node to use the ODM Server policy that you created in step 2, either by specifying the policy name in the Policy field (in the form policyProject}:policyName), or by clicking Browse and selecting the required policy from the displayed list.
4. Configure the ruleset path in the ODMRules node, as described in Configuring the ruleset path.
   When the ruleset path configuration wizard has completed, it populates the parameters table.
5. Configure a Data location XPath for each of the parameters listed in the table. Validation of the node cannot complete until this step has been completed.

   You can either enter the XPath manually or click the ellipsis (...) button to open the standard XPath editor, as described in ODMRules node. For each parameter, the location is identified in the message tree. For IN and INOUT parameters, the location specifies where the required parameter data can be found in the input message tree, and that part of the message tree is serialized as XML. The resulting XML is then set as the parameter value when the ruleset is evaluated. For the IN and INOUT parameters, the location must exist so that it can be serialized. For the INOUT and OUT parameters, after executing the ruleset, the XPath location is used to inflate the XML that is obtained from the ruleset execution into the message tree.

6. When the Data location for has been configured for each parameter, save the changes.