Message Routing

Both the BEA TOP END and BEA Tuxedo systems support routing based on message content. However, the two facilities differ in the granularity of routing provided through the TEDG. You can use the data-dependent routing (DDR) feature of the BEA Tuxedo system and the message sensitive routing (MSR) feature of the BEA TOP END system to direct message traffic, at a low level, between both systems.These facilities are not mutually exclusive and can be used together to control message traffic between systems.

BEA Tuxedo Data-Dependent Routing (DDR)

Specify routing criteria for the TEDG, as you do for other Domains components, in the DM_ROUTING section of the DMCONFIG file. The criteria you specify allow messages to be routed to specific remote domains depending upon the content of the messages. For the TEDG, a remote domain maps to a specific NI (BEA TOP END system node).

BEA TOP END Message Sensitive Routing (MSR)

BEA TOP END clients can use MSR facilities or explicitly specify an MSR target as part of their service request. Because BEA Tuxedo services are mapped to BEA TOP END service parameters that include the optional MSR target (TARGET parameter in the DM_LOCAL_SERVICES section of the DMCONFIG file), it is possible to route messages from the BEA TOP END system to specific services provided by the BEA Tuxedo system (as long as the BEA Tuxedo services are mapped uniquely).

Formats and Message Content Conversion (MCC)

The TOP END Domain Gateway supports BEA TOP END clients and servers using either raw data buffers or FML32. The BEA TOP END formats facility, which is used primarily to describe screen formats, is not supported.

The Message Content Conversion (MCC) feature, which provides hooks for message translation and relies on formats, is also not supported. When a message is sent to the TEDG with a format specified, the format information is ignored and a message about this occurrence is recorded in the userlog.