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

Both the BEA Tuxedo and BEA TOP END application programming interfaces (APIs) follow the X/Open DTP model. The BEA Tuxedo API is called the Application to Transaction Monitor Interface (ATMI). The BEA TOP END API is referred to as the Client/Server Interaction (CSI) facility.

The BEA Tuxedo ATMI provides the interface between the application and the transaction processing system. It provides routines to open and close resources, manage transactions, manage typed buffers, and invoke request/response, conversational, and queuing functions.

The BEA Tuxedo ATMI functions are used by BEA Tuxedo client and server programs 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.

The following ATMI programming features are supported for communication via the TEDG. The functions listed as examples are the primary functions associated with the features from a TEDG perspective. To write a complete application, other interface functions are also required.

• Request/response communication (for example, tpcall(3c), tpacall(3c), tpgetrply(3c), tpreturn(3c), and tpforward(3c))

• Conversational communication (for example, tpconnect(3c), tpsend(3c), tprecv(3c), tpdiscon(3c), and tpreturn(3c))

• Queuing (for example, tpenqueue(3c))

• Transaction management (for example, tpbegin(3c), tpcommit(3c), tpabort(3c), and tx_* equivalents)

• Buffer types FML32, CARRAY, and X_OCTET

• Standard return values and tperrno values (although the meanings of some values may vary, depending on gateway conditions)

• Transactions that involve both a BEA Tuxedo application and a BEA TOP END system

• Security

• Programming and BEA Tuxedo system application features, such as priorities and timeouts, that affect only the behavior of the BEA Tuxedo system and therefore do not require direct support in the remote BEA TOP END system

Unsupported ATMI Features

For several BEA Tuxedo ATMI features there are no corresponding features in the BEA TOP END system. Therefore, these features are not supported by the TEDG, although they are still available in the BEA Tuxedo system. The following ATMI features are not supported by the TEDG:

• Unsolicited notification

• EventBroker

• Dynamic service advertisement

• /Q reply and failure queues

• Conversations with multiple consecutive messages in a single direction

• Administration of BEA TOP END systems through BEA Tuxedo administration interfaces

Characteristics of the BEA TOP END CSI

CSI, the BEA TOP END application programming interface (API), provides a set of routines used by BEA TOP END client and server programs to communicate with BEA Tuxedo client and server programs through the 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 exposure of supported features at the CSI programming interface in a way that closely matches the standard use of the CSI.

BEA TOP END offers several programming interfaces. For the purpose of this document, they can all be considered part of CSI (Client/Server Interaction). The following programming features and routines are supported for communication via the TEDG:

• Request/response and conversational (for example, tp_client_signon, tp_client_send, tp_client_receive, tp_server_receive, and tp_server_send)

• Recoverable Transaction Queuing (RTQ) (for example, tp_rtq_put)

• Transactional (for example, tx_open, tx_begin, tx_commit, tx_rollback, tx_close, tp_begin, tp_commit,and tp_rollback)

• Raw buffers and FML32 buffers (FML32 is supported in BEA TOP END 3.0 systems only)

• Standard status values and extended status values (although the meanings of some values may vary, depending on gateway conditions)

• Transactions that involve both a BEA Tuxedo application and the BEA TOP END system

• Security

• Features unique to the BEA TOP END system that do not require direct support in the BEA Tuxedo system, such as Message Sensitive Routing (MSR)

The routine calls listed as examples are the primary routine calls associated with the features from a TEDG perspective. To write a complete application, other routine calls are also required. In addition, other variations of the calls listed here may be available.

For several BEA TOP END programming facilities there are no corresponding features in the BEA Tuxedo system. Therefore these programming facilities are not supported by the TEDG, although they are still available in the BEA TOP END system.

• Formats and Message Content Conversion (MCC)

• Large Message Architecture (LMA)

• Administration of the BEA Tuxedo system through BEA TOP END administration interfaces (SMAPI)

See Also

• API Programming