Interoperability and Coexistence


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

BEA Tuxedo Doc Home \| BEA Tuxedo Product Overview \| Previous Topic \| Next Topic \| Contents \| Index

This topic discusses the following interoperability scenarios:

Intradomain and Interdomain Interoperability and Coexistence

BEA Tuxedo supports intradomain and interdomain interoperability with BEA WebLogic Enterprise and other versions of the BEA Tuxedo software. BEA Tuxedo 8.0 can coexist in the same domain with BEA Tuxedo 6.4, 6.5, and 7.1 and BEA WebLogic Enterprise 4.2, 5.0 and 5.1. Interdomain interoperability is supported for BEA Tuxedo 8.0 and previous releases of BEA WebLogic Enterprise and older versions of BEA Tuxedo (see Figure 4-1).

Figure 4-1 Domain Gateway Interoperability

Note: While BEA Tuxedo 8.0 clients or servers cannot interoperate or coexist with BEA Tuxedo 6.3 servers, BEA Tuxedo 6.3 clients can interoperate with BEA Tuxedo 8.0 servers.

Interoperability and Coexistence Between BEA Tuxedo 8.0 and BEA WebLogic Enterprise T-Engine

Existing WLE T-Engine Java applications can interoperate with BEA Tuxedo 8.0 and take full advantage of BEA Tuxedo 8.0 features. The following scenarios are supported (see Figure 4-2):

BEA Tuxedo 8.0 can interoperate with 4.2, 5.0, and 5.1 releases of BEA WebLogic Enterprise via domain gateways.
BEA Tuxedo 8.0 can coexist and interoperate in the same domain with 4.2, 5.0, and 5.1 releases of BEA WebLogic Enterprise.
BEA Tuxedo 8.0 can support administration of releases 4.2, 5.0, and 5.1 of BEA WebLogic Enterprise in the same domain.
Figure 4-2 Interoperability with BEA WebLogic Enterprise T-Engine

Interoperability with Third-Party ORBs

In release 8.0 support for the CORBA Services Interoperable Naming Service (INS) was added to the BEA Tuxedo system to enhance interoperability with third-party ORB applications. The addition of INS enables third-party ORBs that use INS to interoperable with the BEA Tuxedo CORBA server ORB. Using INS, third-party ORBs can execute the following operations on BEA Tuxedo CORBA servers without requiring the use of the BEA Bootstrap, SecurityCurrent, or TransactionCurrent environmental objects (see Figure 4-3):

Bootstrapping
Authentication
Starting transactions

Note: The BEA Tuxedo CORBA client environmental objects continue to be supported in BEA Tuxedo 8.0 as they were in BEA WebLogic Enterprise 5.1.

Figure 4-3 Interoperability with Third-Party ORBs

Interoperability Between BEA Tuxedo 8.0 CORBA and BEA WebLogic Server 6.0 Using Object-by-Value Types

To enhance the ability of BEA Tuxedo CORBA C++ applications to access BEA WebLogic Servers via RMI/IIOP, support for C++ object-by-value types in the Interface Definition Language (IDL) and C++ client and server applications was added to BEA Tuxedo in release 8.0. Support of object-by-value types enables bidirectional interoperability between BEA Tuxedo CORBA C++ to BEA WebLogic Server 6.0 (and later) RMI/IIOP interoperability (see Figure 4-4):

Note: The BEA WebLogic Enterprise Connector (WLEC) software is still supported for BEA WebLogic Server to BEA Tuxedo CORBA interoperability.

Figure 4-4 Support for C++ Object-by-Value

Interoperability Between BEA WebLogic Server 6.0 and BEA Tuxedo 8.0 ATMI Using Jolt

As in previous releases, using BEA WebLogic Server and Jolt, you can make BEA Tuxedo services accessible on the Web. In release 8.0, the Jolt software includes the following enhancements that improve the integration of BEA WebLogic Server with BEA Tuxedo services (see Figure 4-5):

Propagation of BEA WebLogic Server user authentication
Connection pools reset option
XML buffer type support
Buffer allocation enhancements

For more information on these enhancements, see Enhancements to Jolt to Improve Interoperability Between BEA WebLogic Server BEA Tuxedo ATMI.

Figure 4-5 BEA WebLogic Server Integration Enhancements

Interoperability Between BEA WebLogic Server 6.0 and BEA Tuxedo 8.0 CORBA Using WLEC

The BEA WebLogic Enterprise Connector (WLEC) enables the BEA WebLogic Server connections to BEA Tuxedo 8.0 CORBA applications. WLEC connects over IIOP and supports propagation of security, connection reset and transaction demarcation.

Figure 4-6 WebLogic Enterprise Connector (WLEC)

Interoperability Between BEA WebLogic Server 6.0 and BEA Tuxedo 8.0 Using WTC

The BEA WebLogic Tuxedo Connector (WTC) enables bidirectional interoperability between the BEA WebLogic Server and BEA Tuxedo ATMI and CORBA environments. WTC uses the BEA Tuxedo domain technology and supports the following capabilities Figure 4-7):

BEA WebLogic Server clients can invoke BEA Tuxedo services.
BEA Tuxedo Clients can invoke BEA WebLogic Server Enterprise Java Beans in response to service requests.
BEA WebLogic Server clients can invoke BEA Tuxedo CORBA C++ applications.
BEA Tuxedo CORBA C++ applications can invoke BEA WebLogic Server Enterprise Java Beans.

Notes: The capabilities of WTC are enhanced in subsequent releases.

WTC version 1.0 enables bidirectional interoperability between BEA WebLogic Server and BEA Tuxedo ATMI. This version is compatible with BEA WebLogic Server 6.0 with Service Pack 2 (SP2) and is available as separate software via a download over the Internet.

WTC version 1.1 enables bidirectional interoperability between BEA WebLogic Server and BEA Tuxedo ATMI and CORBA. This version is delivered with BEA WebLogic Server 6.1.

WTC enables bidirectional security context propagation and unidirectional propagation of transaction context from the BEA WebLogic Server to the BEA Tuxedo system.

Figure 4-7 WebLogic Tuxedo Connector