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
Transaction Capabilities Supported by the TEDG
The following transaction capabilities are supported:
Transactions may span both BEA TOP END and BEA Tuxedo applications. Transactions may be started by either the BEA TOP END or BEA Tuxedo application. Transactions are supported for request/response and conversational message passing. Transactions are supported for enqueuing messages to queues. Because dequeuing does not involve the TEDG, the transactional characteristics for dequeuing messages are unchanged; they are specific to each system. Transactions may involve one or more local components and have one or more transaction branches into the remote system through the TEDG. Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions may be started by either the BEA TOP END or BEA Tuxedo application. Transactions are supported for request/response and conversational message passing. Transactions are supported for enqueuing messages to queues. Because dequeuing does not involve the TEDG, the transactional characteristics for dequeuing messages are unchanged; they are specific to each system. Transactions may involve one or more local components and have one or more transaction branches into the remote system through the TEDG. Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions are supported for request/response and conversational message passing. Transactions are supported for enqueuing messages to queues. Because dequeuing does not involve the TEDG, the transactional characteristics for dequeuing messages are unchanged; they are specific to each system. Transactions may involve one or more local components and have one or more transaction branches into the remote system through the TEDG. Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions are supported for enqueuing messages to queues. Because dequeuing does not involve the TEDG, the transactional characteristics for dequeuing messages are unchanged; they are specific to each system. Transactions may involve one or more local components and have one or more transaction branches into the remote system through the TEDG. Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions may involve one or more local components and have one or more transaction branches into the remote system through the TEDG. Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions abide by local system conventions with respect to abort/rollback due to message passing or queuing errors before the application issues a commit or abort/rollback. Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Transactions may infect a remote system and then reinfect the original system. For example, a BEA Tuxedo client may send a transactional request to a BEA TOP END server, which then sends a transactional request to a BEA Tuxedo server.
Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.