Route configuration

Route configuration gives you the ability to improve usability for message routes and related configuration.

To enter this mode, select a thread on the Network Graph panel. Then, click Configure Thread Routes. This contains a toolbar, message route graph panel, and properties panel.

Configure Thread Routes toolbar

The toolbar contains buttons for switching back to the Network Configuration panel and buttons for adding nodes to the Message Route Graph panel.

  • Configure Netconfig switches back to the Network Configuration panel.
  • Configure Message Routes switches between the Configure Thread Routes panel for the current thread.
  • Configure Reply Routesd switches between the Reply Route Configuration panel for the current thread.
  • Trx ID adds a transaction ID to the current message flow. To do this, drag and drop this button over a thread node on the Message Route Graph panel, which adds a transaction ID node.

Use these buttons for a route type node after a transaction ID node. To add a route type node, drag and drop a button over a transaction ID node.

  • Raw tells the engine to pass the message data through without translation. Alternately, use one or more Tcl procedures to process the message. In a raw route, other than pre-processors, the message is not interpreted or translated.
  • Xlate is the typical translation mechanism. This translates the message according to the actions in a previously configured translation file. The configuration specifies the name of a translation specification (XLT) file to control the translation process.
  • Generate is similar to raw, except that there is only the Procs option. This controls a message route using a single user-written Tcl procedure.
  • XSLT takes XML messages as inputs and translates them into other formats according to the formats specified in the XSLT files. This is similar to Xlate, except that instead of specifying an Xlate file, you specify a XSLT file. There is also no Elevate warnings to errors option on the XSLT Route Details dialog box. This is because XSLT is only used for XML and there is no elevate warning feature for XML.
  • Chain permits you to mix Raw/Xlate/XSLT route types on one route detail.
  • Branch does one common translation that is a Chain without a destination. Then, it branches to multiple translations which can be Raw, Xlate, XSLT, and Chain. This covers a common problem where a message must be normalized and then passed to several translations by TCP threads.
  • Route Configure Title switches the title bar for each column (Protocol, Inbound Data, and so on).
Note:  Raw, Xlate, XSLT, and Chain can also be dropped over a Branch route type node to create a branch.

Message route graph panel

This panel shows the starting point of route configuration.

The message flow starts with a single circle node in Protocol.

The Inbound Data node specifies the protocol between the inbound thread and the external system.

The thread node is the inbound node.

Note: The above nodes cannot be deleted by the user.

An indicator displays on nodes (inbound, outbound, and xlate) that have UPoCs associated with them (Java or Tcl).

The far right side of the panel lists all available threads which are used for adding destination threads in the message routes.