Request/Response Message Passing

The TEDG supports the request/response mode of passing messages between BEA Tuxedo and BEA TOP END systems. The systems use the TEDG as an intermediary.

BEA Tuxedo Client to BEA TOP END Server

The TEDG uses the service name to locate the SERVICE entry in the DM_REMOTE_SERVICES section to determine the corresponding BEA TOP END product, function, MSR target, and function qualifier. For FML32 buffers, data marshalling is performed, as required, before a message is sent.

BEA TOP END servers respond to client requests using tp_server_send(3T).

BEA TOP END Client to BEA Tuxedo Server

BEA TOP END clients request BEA Tuxedo services using tp_client_send(3T) or tp_client_signon(3T). BEA TOP END client calls are asynchronous. Responses are handled by the tp_client_receive(3T) call.

Message routing is based on three pieces of information advertised by the TEDG: the product, the function and, optionally, the MSR target. Normal BEA TOP END routing and load-balancing rules are used to determine the destination node. When a message is received by the TEDG, the product, function, optional MSR target, and function qualifier specified in the message are used to determine the corresponding BEA Tuxedo service as specified by the SERVICE entries in the DM_LOCAL_SERVICES section of the DMCONFIG file. The message is sent to the appropriate BEA Tuxedo service after any required data unmarshalling is performed.

See Also