Project Walkthrough

The flow of the Project is as follows:

• The inbound File eWay subscribes to an external ”input” directory. The eWay accepts an MT_541 message and publishes it to the Service1 Collaboration.

• The CopyCollab1 service (CopyCollaboration) unmarshals the message, copies all of the data fields (to demonstrate how to copy the data fields), marshals the message to a String and publishes the message to a JMS Queue.

• The ValidateMT_541_Modified Collaboration accepts the message from the JMS Queue, validates the messages for MFVR and then for BICPlusIBAN, and publishes it to the ValidMessage Queue if the message is valid, or to the InvalidMessages if the message is not valid.

• The PrintValidMessages Collaboration accepts the valid messages, prints out the message and sends the message to the outbound File eWay.

• The PrintInvalidMessages Collaboration accepts the invalid messages, prints that the message is invalid and lists any errors. It then sends that message to the outbound File eWay.

• The outbound File eWay publishes the messages to an external folder as either Swift2008_JCD_MFVRAndBICPlusIBAN_Valid_output1.dat or Swift2008_JCD_MFVRAndBICPlusIBAN_Invalid_output1.dat.

You must name the source (input) and destination (output) file directories in the setting property settings for the Project’s File eWays. See the File eWay Intelligent Adapter User’s Guide for details.