Defining Processing Rules to Process the Incoming Data
Define a processing rule that will execute when the incoming data is sent to Trading Networks. For example, you might set the criteria in the processing rule to match the TN document type you defined for the incoming data.
The processing action for the processing rule should put the incoming data into ACH format. To do so, use the Execute a Service processing action to invoke a service you create. This service should:
2. In a loop, go through the incoming data for that corresponds to an ACH entry and create an ACH entry and add the entry to the batch.
a. Create logic to map the incoming data to ACH format. This mapping is referred to as outbound mapping. To help you with the outbound mapping, ACH Module provides IS document types that define the structure of the ACH entries. The IS document types reside in the wm.ach.record folder within the WmACH package.
3. After all entries have been added to the batch, add the batch to the queue with the
wm.ach.queue:queueBatch service. At this point the batch is queued in the persistence medium. For an example of a flow service that creates and populates a batch, see the wm.ach.tn.sample.maps.outbound:mapPaymentXMLToCCD service in Developer. 4. Use the
wm.ach.tn.trp:send service to send the ACH file. Note that ACH Module does not implement a transport service. Rather, the user must implement this service. You can use the
wm.ach.tn.trp:send in one of the following two ways: Directly send the ACH file by specifying the transport service in the
sendSvc parameter of the
wm.ach.tn.trp:send service.
The
wm.ach.tn.trp:send service first submits the ACH file to
Trading Networks. So you can set up a TN document type for an outbound ACH file and create an associated processing rule that uses the Execute a Service processing action to invoked the transport service.
5. For information about defining processing rules, see the webMethods Trading Networks User’s Guide.