Node Descriptor

The node descriptor defines a Business Rules node. A node is a callable service which is comprised of a collection of Business Rules tasks. These processing nodes can be customized into a Business Rules workflow or called directly as a service.

The node lists any tasks which comprise the node and any connections between the tasks. For tasks, each connection names the source task, destination task, and whether the connection is made as the result of a success or failure from the source task. For a table task, a success is defined as a table hit and a failure is a table miss. In Figure 1, Node1 consists of two table tasks, account and NewAccount. If the account table task has a failure (did not get a hit), the NewAccount task should be called.
Figure 1. Node1 Descriptor
gpy_izwc_node1descriptor.jpg
The following node descriptor (Figure 2) defines the node, Node1, shown in Figure 1.
Figure 2. Code Node Descriptor for Node1
<?xml version="1.0"?>
<nodeDescriptor name="nodeName" type="ESORT">
  <userExitClass>ESortUserExit</userExitClass>
  <tasks>
    <task name="Account"/>
    <task name="NewAccount"/>
  </tasks>
  <connections>
    <connection srcName="Account" dstName="NewAccount" results="FAILURE"/>
  </connections>
</nodeDescriptor>

The nodeDescriptor element is the root element and holds the remainder of the elements. The name of the node and the type of node to be defined must be specified. The tasks element is a container for the individual task names. Each task element specifies the name of a Business Rules task. The first task in the node should be the first task listed. The connections element is a container for the individual connection elements. Each connection element specifies the source task name, destination task name, and the result from the source task which triggers the move to the destination task. Additionally, the nodeDescriptor element may contain a userExitClass element. The userExitClass element specifies an optional user exit which is invoked before and after the processing of the node. The user exit must implement the defined node user exit interface.