Project Walkthrough

Figure 1 displays the Project’s Connectivity Map, which represents the flow of the Project as follows:

• The Business Process (see Figure 2) begins with a File.read() operation. This operation subscribes to an external “input” directory and picks up a file that contains a valid SWIFT MT 541 message.

• The File.read() operation publishes the message to the input of the mt_541.unmarshal() operation. This operation basically unmarshals the MT 541 message into a Java data structure that represents the message. This structure is the output of the mt_541.unmarshal() operation.

• The Business Process continues by publishing this output to the input of the mt_541.marshal() operation. The mt_541.marshal() operation transforms the OTD data structure back into a String.

• Finally, this String is published as input to the File.write() operation, which writes out the String to an external directory.

The Business Process itself is relatively simple, but it identifies how the operations of the SWIFT OTDs can be used in a Business Process.

Configuration of the Connectivity Map is simply the configuration of the Inbound and Outbound File eWay (see Figure 1). The configuration of the Inbound File eWay determines where the SWIFT MT 541 message is located. The configuration of the Outbound File eWay states where the output of the Business Process goes.

You must have the eInsight.sar file installed to use the features available with this Project. See the Sun Java Composite Application Platform Suite Installation Guide for complete installation procedures.