Configuring a Branch route detail
On the Route Messages or Route Replies tab, double-clicking the Type opens the Route Details dialog box.
This dialog box shows the properties of the selected node that is the common part of a Branch translation. The common part is a Chain translation but it has no destination. You can add/delete chain items as required.
There must be at least one Chain and Branch detail, otherwise an error message results.
You can view a message when it goes through each chain detail. For example, you can see the message output after it goes through an xlt file in the chain. Then, you can see the message after it goes through another xlt file.
The output that is displayed is each xlate's output in the route testing for the chain or Branch.
Chained details
Click Chained Route Detail Properties dialog box, where you can select a Type and Properties for that type.
to configure Chained details. This opens theIn translation chains:
- The output from a translation is the input to another translation.
- The links in these chains are routing details of the form used for each transaction ID.
- Each link of the chain has the same destination specified for the detail.
- Because a chain with one link is the same as the translation detail in use, chains with a single link are not permitted.
Branch details
Click Branch Route Details dialog box, where you can select a Type and Properties for that type.
to configure Branch details. This opens theThe Branch detail has one common translation and its children which are Branch items.
After a Branch item is selected on the tree, the view updates with the new Branch.
Right-click the Branch node to open a menu of editing choices.
Copy/Paste actions can be made across different levels, so that a sub-Branch can be copied and pasted as its parent’s sibling.
The common/trunk and Branch chains can have a single translation detail as its only link.
Branch chains cover a common problem where a message must be normalized and then passed to several translations by TCP threads:
- The source thread xlate fixes the message for later processing.
- With only one translation per destination the normalized translation is repeated for each outbound destination thread.
- The outbound thread then uses TCP to send the message to another thread where the normalized message is processed.
- Branch chains reduce this overhead.
- The number of protocol threads and their overhead is reduced.
- The chain that does the normalization is the common, or trunk, chain.
Characteristics of a basic Branch chain:
- Consists of one common/trunk translation detail that does the normalization.
- The output of this translation is then passed to one or more translation details that are the Branches.
- Each Branch has a unique protocol thread destination that receives the result of the Branch translation.
- Second level Branches are not supported. There is only one Branch point in a Branch chain.
- Branches are restricted in that they must each have a unique specified destination thread. One of the Branch’s destination must be used for the translation details of the common/trunk chain.
- There is no restriction on the number of single details, chains, or Branch chains that are run under a single TrxID. Each may have from zero to as many as are required.
At this point, you can:
- / / the selected Branch item. After doing a / , you can paste a Branch item to the Route detail level or Branch detail level.
A new Branch item becomes a Branch child to the Branch detail.
Enabling the route
After configuring the Chained and Branch details, select
to enable the route. Clearing the check box disables the route.