Creating routes

Routes are created according to the type of thread.

  1. In Network Configurator, select a protocol and drag it onto the layout panel.
  2. Right-click the new thread and select Create Route or Create Reply Route.
  3. Move the mouse to the destination thread and click. This creates a route line between the two threads, and a Create Message dialog box opens for configuring route details.
    Before the target thread is selected, during the dragging you can interrupt the route creation by pressing the ESC key. You can also click in an open space.
  4. In the Name field, specify a transaction ID name.

    The existing route names from the same source thread are listed on the menu. If there is no existing route name, then you can select New Id or use a new name.

    The transaction ID indicates the type of message. This is the type of transaction that is represented by the record. The route name must match the Trx ID in the record, including case.

    For message-type record formats, specify the name of the message type.

    For fixed-length record layouts, specify the exact characters that display in the transaction ID field of the inbound data message.

  5. If you do not select a name, then you must select Static Route or Static else route. If you select an existing route name, then the current route belongs to the selected route name.
    A static route processes all messages the same way, regardless of their transaction ID. Use a static route to apply a common action to all transactions. For example, sending a copy of all messages to an archival site.

    A Static Else Route is similar to a Static Route. This option creates the _HCI_static_else_route_ .

  6. Select additional parameters, as required.
    • Wild Card Route routes a set of messages to one destination. For example, all ADT messages to one destination would use a wildcard: ADT.*.

      This setting can be shared by multiple routes. If the shared setting is changed, then a warning message opens after you click OK: The changed Wild Card Route is shared by the routes: raw1, raw2. This change will be applied to all of them.

      Name behaves as a regular expression. For a message to be considered a match, its transaction ID has to be a complete match to this expression.

      For example, the wildcard ADT_A0\d is the equivalent of the Tcl regexp {^ADT_A0\d$} $transactionID. This wildcard matches a message whose transaction ID is ADT_A01, but does not match a message whose transaction ID is ADT_A17 or ADT_A01a.

      If negative lookahead is used in the wildcard route, then the expression should be written properly. For example, to match a route started with ADT_A and it is not ended in 17 with negative lookahead expression, ADT_A(?!17)\d\d should be used. ADT_A(?!17) does not work.

      To use regular expression shorthand in wildcard route, use double slashes. For example, to make the above negative lookahead expression work as wildcard route, the correct Name value is ADT_A(?!17)\\d\\d.

    • Select Remove all messages when any route detail fails to define route or reply actions when an error happens in a route detail. When this is selected, all messages are dropped. Otherwise, only the error route detail is dropped.
    • Selecting Store original message in metadata for downstream processing caches the pre-xlate message in Route Details and is used in the Database-Outbound Protocol Properties dialog box and Database-Outbound protocol engine thread.

      When this is selected, the engine thread caches the pre-xlate message at runtime. By default, this is cleared.

    • Enabled enables/disables the route.
  7. Configure the Detail Properties parameters. For these properties, see the individual types: