This section describes the iWay business components and the processing steps in the basic inbound message flow.
The inbound process converts a TRADACOMS formatted document to an XML document. Inbound processing consists of the following components in the sample message flow:
The iWay Integration Solution for TRADACOMS supports one preparser, XDTRADPreParser (com.ibi.preparsers.XDTRADPreParser), which is provided by iWay Software.
The inbound TRADACOMS document is validated for structure and content. The published TRADACOMS standards and user implementation guides define element types (for example, numeric, alpha, or date) and describe business rules to apply for validation.
For example, the following is a typical date segment in an inbound TRADACOMS document:
FIL=7012+1758+160901+FL RLX'
Note: All TRADACOMS dates use a six digit date format (YYMMDD).
In our sample message flow, the validation report service (TRAD_Validation_rpt) creates a validation report in XML format. This report indicates success or failure transformation and contains the input and output documents. The route directs the document based on this report. You can also apply additional business logic by adding a service to the flow.
For more information on the services available with iSM, see the iWay Service Manager Component Reference Guide.
Outlets define how messages leave a channel at the end of a process. In this example, a Passthrough emitter is used. All the file emits are done in the process flow.
For more information on the emitters available with iSM, see the iWay Service Manager User's Guide.
For more information on deploying and starting the sample channels within the iWay Integration Application (iIA), see Working With TRADACOMS Inbound and Outbound Applications Using iWay Integration Tools.