Using the BEA Tuxedo ATMI (API) 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 Tuxedo application programming interface (API) is called the Application to Transaction Monitor interface or ATMI. BEA Tuxedo client and server programs use ATMI functions to communicate with BEA TOP END client and server programs through the TOP END Domain Gateway (TEDG).

To a great extent, the way in which ATMI functions are used to communicate with BEA TOP END applications is identical to how ATMI functions are used to communicate with other BEA Tuxedo programs or applications through other domain gateways. The primary difference is that the TEDG does not support the same functions and features as other domain gateways. Because the TEDG connects two similar but not identical client/server environments, only features common to both environments can be supported when these environments are interoperating. This set of features common to both the BEA Tuxedo and BEA TOP END systems is provided by the TEDG through configuration, feature mapping, and exposing supported features at the ATMI programming interface in a way that closely matches the standard use of the ATMI.

As with other domain gateways, the TEDG is viewed by the BEA Tuxedo client as a BEA Tuxedo server; it maps requests from BEA Tuxedo client programs to BEA TOP END servers. When a BEA TOP END client makes a request, the TEDG maps the request and sends it to a BEA Tuxedo server. For this reason, the TEDG is viewed as a BEA Tuxedo client by the BEA Tuxedo server.

From a programming perspective, the TEDG is transparent to BEA Tuxedo applications; it looks like a BEA Tuxedo application and is accessed through the same ATMI functions used to access any BEA Tuxedo application. As with all applications that communicate, a BEA Tuxedo application and a BEA TOP END 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.

Characteristics of the BEA Tuxedo ATMI lists the supported and unsupported features of the BEA Tuxedo ATMI.

Limitations of Supported ATMI Features

Some of the supported ATMI features have limitations and special requirements when used for communication 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 is limited to the following format:
- One process sends a single message and then releases control of the conversation.
- Another process responds with a single message and then releases control of the conversation.
Because the features provided by BEA TOP END RTQ and BEA Tuxedo queuing are not identical, several options in each API are unavailable.
The BEA Tuxedo system supports embedded FML32 buffers; the BEA TOP END system does not. These buffers are ignored by the TEDG and allowed to go through the gateway. If embedded FML32 buffers are used in a BEA Tuxedo application that is accessed by BEA TOP END clients, however, a failure may occur on the BEA TOP END node.
Public/private key encryption of application messages is supported between the BEA Tuxedo application and the TEDG but does not apply to messages between the TEDG and a BEA TOP END application. BEA Tuxedo configuration options that require the use of encryption are enforced. The ability to auto-encrypt messages from a BEA TOP END application is provided. Public/private key encryption for the TEDG is handled the same way that this type of encryption is handled for other non-TDomains BEA Tuxedo gateways.
Digital signatures are supported for application messages sent between the BEA Tuxedo application and the TEDG but are not supported for messages between the TEDG and a BEA TOP END application. BEA Tuxedo configuration options that require use of encryption are enforced. The ability to auto-sign messages from a BEA TOP END application is provided. Digital signatures for the TEDG are handled the same way that digital signatures are handled for other non-TDomains BEA Tuxedo gateways.