Decision service node

The FTM Fragmentation sample application provides an example of using decision service node in IBM® App Connect Enterprise to run a J2SE runtime business rules engine, which can process rules based on the business content from messages within the integration bus flows. The runtime rules engine can come from the IBM Operational Decision Manager (ODM). The node receives a standardized input message and runs the rule engine. The result is propagated to the output terminal and can be used for complex routing and decision making.

For more information on Decision Service node and ODM, see Decision Service Node.

  • In the FTM fragmentation sample project, locate the following actions - A_RoutePayInit.msgflow and A_RoutePayInit_ODM.msgflow.
  • Rename A_RoutePayInit.msgflow to A_RoutePayInit_NotDeployed.msgflow.
  • Rename A_RoutePayInit_ODM.msgflow to A_RoutePayInit.msgflow.
  • Rebuild the BAR files containing the action and deploy them to the execution group.
  • On the Configuration Value window, locate Key = 'SIMU'. Change the Configuration Value to N for off and to Y for on. Refer to Figure 3 for an example of the Configuration Value window.
Figure 1. A_RoutePayInit.msgflow
fragA_RoutePayInit.jpg
Figure 2. A_RoutePayInitODM.msgflow
searchfragA_RoutePayInitWODM.jpg
Figure 3. Decision Service simulation configuration values
iLogSimulation.jpg

Copy the following XOM JAR file located in FTM Fragmentation Sample\config\Fragmentation RuleApp\FTMFragmentationSampleRuleAppProject\runtime into your IBM App Connect Enterprise work path directory.

Within Decision service node properties, the ra.xml configuration file is a promoted property. You can configure the path to the ra.xml file at the BAR file level in FTM Fragmentation Sample Bar Files project - EventWrapper.bar - FragmentationSample_Actions - A_RoutePayInit - properties.

Figure 4. Decision service node
DecisionNode_installationDNS