Reply route trxID configuration
On the Route Replies tab, click to open the Route dialog box.
This table shows the available configuration items:
Parameter | Description |
---|---|
Name | The transaction ID indicates the type of message. For example, what type of transaction is represented by the record. The route name must match the Trx ID in the record, including case. Specify a transaction ID name. The existing route names from the same source thread are listed in the . If there is no existing route name, then the is empty. You can specify a new route name or select any existing one. Specify a transaction ID name. The existing route names from the sameFor 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. |
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. When you select an existing route name, the current route belongs to the selected route name. , see |
|
This setting can be shared by multiple routes. If the shared setting is
changed, then a warning message opens after you click Select this option to route a set of messages to one
destination. For example, all ADT messages to one destination would
use a wildcard: The 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 If negative lookahead
is used in the wildcard route, then the expression must be properly
written. For example, to match a route started with To use regular expression shorthand in wildcard
route, double slashes should be given. For example, to make the
above negative lookahead expression work as wildcard route, the
correct Name value is |
: "The changed Wild Card Route is shared by the routes:
raw1, raw2. This change will be applied to all of them." |
Select this to define route or reply actions when an error happens in a route detail. If the check box is selected, then all messages are dropped. Otherwise, only the error route detail is dropped. | |
The pre-xlate message is cached 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. | |
Enables/disables the route. |