Message Routing

jhmase: The page contains a lot of information that should not be in an overview page.

Message routing describe queuing and dispatching to different targets of a message from/to IFS Applications. This will be based on the message type and/or the content of the message.

The picture shows IFS Connect with the central Message Router
 

Following points below is a summary of the Message Routing functionality.

• All inbound messages that are received by Connect and outbound messages that are send from Connect go through the Message Routing rules.
• The routing rule determines the destination address(s), transport connector (destination) type, transformers and envelop that use with the message.
• Routing rule may be a Content base routing rule or a Location base routing rule.

Note: In content base routing rules we compare the content of the message header/body with the given values. In location base routing rules we compare the details of the location from where we got the message. eg. name and/or the directory of a file.

• Both Content base routing rules and Location base routing rules can apply for Inbound message routing where as outbound message routing will only handled by using content base routing rules.
• In routing it is vital to match at least one condition.
• If more than one routing rule matches, will that one with the greatest number of conditions, content and location based, be used.
• When there are routing rules with equal numbers of conditions that matches, will the first found routing rule be used.
• You can route a message more than one destination by setting one or more addresses to a rule.
• For asynchronous messages you can define a response address in the same rule.
• Destination types include Business API's and Transport Connectors such as FTP, Mail, File, Http(s) etc.