Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   TOP END Domain Gateway   |   Topic List   |   Previous   |   Next   |   Contents

   Using the BEA Tuxedo TOP END Domain Gateway

The BEA Tuxedo and BEA TOP END systems support different styles of conversational message passing.

• The BEA TOP END system supports the notion of pseudo-conversations. A BEA TOP END server maintains context (a conversation) with a client when the TP_APPL_CONTEXT flag is set. (See tp_server_send (3T) in BEA TOP END Programmer's Reference Manual for details.)

• BEA Tuxedo conversations are more structured. To be conversational, a server must be configured as such by an administrator. Then a dedicated function (tpconnect(3c)) must be used to establish a connection and maintain the conversation. BEA Tuxedo conversations are half-duplex: one side of a conversation can send multiple messages before relinquishing control of the connection. (See Introduction to the C Language Application-Transaction Monitor Interface in BEA Tuxedo C Function Reference for details.)

The TEDG provides a mapping of BEA TOP END pseudo-conversations to the BEA Tuxedo conversation model. This mapping allows:

• Existing BEA TOP END servers to maintain context with new BEA Tuxedo clients

• Existing BEA TOP END clients to engage in multi-step interactions with new BEA Tuxedo servers

Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.