Originally developed to handle SWIFT incoming messages, this transaction now processes incoming messages of many different channels and formats. A file can contain one or more messages in the respective format.
The processing of partial messages, like in SWIFT MT 700 and MT 701 messages, is supported. This means individual partial messages belonging together are assembled in to one complete message during upload handling for further processing.
Supported Message Formats
The application currently supports many incoming message channels with others being added as they become widely used and adopted by our product team.
The table below summarizes the currently supported channels.
Storage Location of the Files for the Incoming Messages
The messages are usually stored as text files in the subdirectories of the Data partition.
( A sibling transaction MQITSK handles the same messages and services where the MQ messaging service is used instead of flat files. Handling of the actual message contents is the same for both).
Thus, relative path names for defining the output directories are relative to the partition Data. If necessary for organizational reasons, absolute path names can also be defined. In doing so, the usage of the prefix 'db': (files in databases) is also possible. Optionally, incoming messages can be sent in separate directories per entity or in a common directory for the entire installation.
|Message Type||Internal Channel||Subdirectory in Partition 'Data'||Services|
Each channel will have a dedicated panel to configure how it is handled. Common variables would be an activation check box , the file extension expected , the folder to pick these messages up from , and then any channel specific parameters then need to be set.
Typical processing will be as a background batch transaction controlled by the Background Manager (SYSMGR) and Watchdog (SYSWDR).
Using an incoming SWIFT message as an example, as each polling cycle becomes active, SWITSK carries out the following steps:
1.File transferred with extension sco or sf2 should be listed in the transaction panel
2.The next available message is selected, parsed, and processed
3.Once processed , the file will not be available in the placed path. It will move to /arc if the file has been processed successfully or /error folder if process is terminated with an error.
For manual handling , the transaction can be started in the foreground and single messages can be processed in turn by the user, as below.