| Bookmark Name | Actions |
|---|
Flows
SWIFT Interface camel flow implementation provides connectivity channels between swift Interface endpoint and Temenos Transact queues. The flows are classified as inward flow and outward flow.
Inward Flow
Inward flow consumes message from Swift Interface. The message comes from configurable queue or file director and is sent to Temenos Transact queue. The message can be MT or MX.
Non-XML messages are considered as MT Message. Consumed MT message is prefixed with DECARRIER=SWIFT,, wrapped in inflow XML and sent to Temenos Transact inflow queue.
Any well-formed XML are considered as MX message and the consumed message is sent to configurable Temenos Transact queue without modification.
Both the above flows are a part of the Camel flows and the working of the same is explained in the Launching Swift Interface Camel Application section.
Outward Flow
Outward flow consumes message from Temenos Transact and sends the consumed message to swift interface configurable queue or file directory. The message can be MT or MX.
This flow is not a part of CAMEL package. Outward MT flow is a part of TSA Service SWIFT.OUT and explained in the Swift Outward (MT) section.
Outward flow consumes message from configurable Temenos Transact queue and sends the consumed message to swift interface configurable queue or file directory. This is a part of the Camel flows and the working of the same is explained in the Launching Swift Interface Camel Application section.
Add Bookmark
save your best linksView Bookmarks
Visit your best linksIn this topic
Are you sure you want to log-off?