Using the BEA TOP END CSI with the TEDG


	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 TOP END application programming interface (API) is called the Client/Server Interaction facility, or CSI. BEA TOP END client and server programs use CSI routine calls to communicate with BEA Tuxedo client and server programs through the TOP END Domain Gateway (TEDG). To a great extent, the way in which CSI routine calls are used to communicate with BEA Tuxedo applications is identical to how CSI routines are used to communicate with other CSI applications. The primary difference is the features or options supported for each routine. The TEDG supports a set of features common to both the BEA Tuxedo and BEA TOP END systems through configuration, feature mapping, and exposing supported features at the CSI programming interface in a way that closely matches the standard use of the CSI.

The TEDG is viewed by the BEA TOP END client as a BEA TOP END server and maps requests from BEA TOP END client programs to a BEA Tuxedo server. When a BEA Tuxedo client makes a request, the TEDG maps the request and sends it to a BEA TOP END server. For this reason, the TEDG is viewed as a BEA TOP END client by a BEA TOP END server.

From a programming perspective, the TEDG is transparent to BEA TOP END applications: it functions like a BEA TOP END application and is accessed using the same CSI calls used to access a BEA TOP END application. As with all applications that communicate, both the BEA TOP END application and the BEA Tuxedo application must be designed to work together on requests, responses, and error handling. Because the TEDG configuration and mapping affect this interaction, the application designer must understand the TEDG configuration.

For lists of supported and unsupported features of the BEA TOP END CSI, see Characteristics of the BEA TOP END CSI.

Limitations of Supported CSI Facilities

Some of the supported CSI features and interfaces have limitations and special requirements when used for communicating via the TOP END Domain Gateway. These limitations and requirements ensure that BEA Tuxedo and BEA TOP END applications have a common method of communicating. Some of the limitations are:

Conversational communication with an application context is accomplished by mapping to the BEA Tuxedo conversational paradigm. There are limitations to the use of function qualifiers with the TEDG. A traditional BEA TOP END application may use function qualifiers to indicate the step of the conversational interaction; this is not possible with the TEDG. Successful communication in a conversational manner requires adapting one or both of the applications to the features available through the TEDG mapping of context to conversations.
Because the features provided by BEA TOP END RTQ and BEA Tuxedo queuing are not identical, a number of options in each API are unavailable.