How the Decision Service Node Capability works

The Decision Service capability is provided as an IBM® App Connect Enterprise flow action that can be used within an IBM App Connect Enterprise flow (Decision Service)

The execution of a rule set starts when a message enters the Decision Service Node. The IBM App Connect Enterprise creates and caches a J2SE Decision Server in the execution group of the flow. The execution group is the flow container of the IBM App Connect Enterprise. If it's the first invocation of a specific rule set, the J2SE Decision Server requests the rule set from the shared rule persistence layer one time and caches it locally. Any subsequent rule set execution call only runs it within the JVM.

The rule set will run all the rules within it and return the result back to the IBM App Connect Enterprise flow.

If the J2SE Decision Server is enabled for rule set listening, the execution group starts a rule set listener. The listener connects the J2EE engine and registers for update events by the MBean Interface of the application server.

If a rule is updated by a user using the Eclipse Rule Designer or Decision Center and deployed as a RuleApp to the central Decision Server persistence layer, the execution group receives an event and forces the execution group to retrieve the updated rule set from the RuleApp.