Interoperability and Coexistence

The following sections describe how Oracle Tuxedo 11g Release 1 (11.1.1.1.0) interoperates with older releases of the Oracle Tuxedo software, Oracle WebLogic Enterprise, and third-party products:

•	Interoperability Defined

•	Intradomain Interoperability

•	Interdomain Interoperability

•	Client-Server Interoperability

•	Interoperability with Third-Party ORBs

•	Product Upgrades

•	Upward Application Compatibility

Interoperability Defined

Interoperability permits the current Oracle Tuxedo release to communicate over a network connection with Oracle Tuxedo 11g Release 1 (11.1.1.1.0) or earlier software or with Oracle WebLogic Enterprise release 5.1 software. Oracle Tuxedo supports intradomain interoperability and interdomain interoperability. Note the following:

•	Intradomain interoperability

Involves one machine in a multiple-machine Oracle Tuxedo domain (application) running Oracle Tuxedo 11g Release 1 (11.1.1.1.0) software, and another machine in the same domain running Oracle Tuxedo 10gR3. Machines in a multiple-machine domain configuration communicate via Oracle Tuxedo Bridge processes.

•

In a multiple-machine Oracle Tuxedo domain running Oracle Tuxedo10gR3 or earlier system software, the master machine (and master backup machine if so configured) must run the highest release of the Tuxedo system software in the domain. Accordingly, the Tuxedo domain just described qualifies as an “Oracle Tuxedo domain running Oracle Tuxedo release 11g Release 1 (11.1.1.1.0) software.”

•	Interdomain interoperability

Involves one Oracle Tuxedo domain running Oracle Tuxedo release 11g Release 1 (11.1.1.1.0) software, and another domain running Oracle Tuxedo release 10gR3 software. Domains involved in a multiple-domain (Domains) configuration communicate via Oracle Tuxedo domain gateway processes.

Intradomain Interoperability

Message exchange and protocol compatibility exist in the Intradomain Coexistence Group as shown in Figure 1‑1:

Figure 1‑1 Intradomain Groups

Oracle Tuxedo 11g Release 1 (11.1.1.1.0) can coexist in the same domain with Oracle Tuxedo 10gR3, 10.0, 9.1, 9.0, 8.1, and 6.5. In this environment, the propagation of transaction context (transactional state information) and security context (user identity) between application clients and servers is fully supported. Administration is fully supported in this environment.

In the current Oracle Tuxedo release, service name length is increased from 15 to 127. Resource name and remote service name length have also increased from 15 to 127 in domain configuration (for TDomain only). You can also configure a locale resource locator or a remote service with a name less than or equal to 127 characters for TDOMAIN. Note the following:

•	Long service names are not permitted when Oracle Tuxedo 10gR3 or earlier coexists in, and joins the same Oracle Tuxedo 11gR1 domain.

•

In the UBBCONFIG file, the value of the AUTHSVC keyword in the *RESOURCE section and the SVCNM keyword in the *SERVICES section are not allowed to use long service names when Oracle Tuxedo 10gR3 or earlier software coexists in the same Oracle Tuxedo 11gR1 domain. If long service names are used, the earlier Oracle Tuxedo release site will not boot.

•	Oracle Tuxedo 11g Release 1(11.1.1.1.0) application servers with one or more services using long service names will not boot when Oracle Tuxedo 10gR3 or earlier coexists in same the Oracle Tuxedo domain.

•	Any dynamic addition of services with long names fail when Oracle Tuxedo 10gR3 or earlier coexists in the same Oracle Tuxedo domain.

•	Oracle Tuxedo 10gR3 or earlier software is not allowed join a domain if one or more services with long names has already booted in the current Oracle Tuxedo domain.

•	You cannot configure a long local resource and remote service name for TDOMAIN gateway servers that are deployed in running Oracle Tuxedo 10gR3 or earlier in the same Oracle Tuxedo domain.

Interdomain Interoperability

Message exchange and protocol compatibility exist in each of the following three interdomain scenarios as shown in Figure 1‑2,Figure 1‑3 and Figure 1‑4:

Figure 1‑2 Interdomain Scenario 1

Figure 1‑3 Interdomain Scenario 2

Figure 1‑4 Interdomain Scenario 3

In each of these scenarios, an Oracle Tuxedo domain (TDomain) gateway process running on a machine in one domain communicates over a network connection with a TDomain gateway process running on a machine in another domain. Table 1‑1 lists the supported TDomain gateway processes.

 

Table 1‑1 Communicating TDomain Gateway Processes

A TDomain process in any of these releases . . .		Can communicate with a TDomain process in any of these releases . . .
Oracle Tuxedo 11g Release 1 (11.1.1.1.0)	Connection Matrix	Oracle Tuxedo 11g Release 1 (11.1.1.1.0)
Oracle Tuxedo 10g Release 3 (10.3)		Oracle Tuxedo 10g Release 3 (10.3)
Oracle Tuxedo 10. 0		Oracle Tuxedo 10.0
Oracle Tuxedo 9.1		Oracle Tuxedo 9.1
Oracle Tuxedo 9.0		Oracle Tuxedo 9.0
Oracle Tuxedo 8.1		Oracle Tuxedo 8.1
Oracle Tuxedo 6.5		Oracle Tuxedo 6.5
Oracle WebLogic Enterprise 5.1		Oracle WebLogic Enterprise 5.1

Interdomain capabilities available through a pair of communicating TDomain processes are limited to the capabilities available to the TDomain process running in the earlier Oracle release.

In all of these scenarios, administration, transaction context propagation, and security context propagation between domains is fully supported except when the master machine in one domain is running Tuxedo 6.5. Administration is supported and transaction context propagation is supported, but security context propagation is not supported.

Oracle Tuxedo 11g Release 1 (11.1.1.1.0) supports interdomain interoperability with Tuxedo10gR3, 10.0, 9.1, 9.0, 8.1 CORBA domains. This capability includes the ability to advertise CORBA C++ factories across domain boundaries.

For interdomain transactional requests between Tuxedo 6.5 and other Other Tuxedo releases (6.5, 8.1, 9.0, 9.1, 10.0, and 10gR3), the following patch level upgrades must be applied:

•	Patch level 446 or higher for Oracle Tuxedo 6.5

•	Patch level 090 or higher for Oracle Tuxedo 8.1

•	Oracle Tuxedo 9.0 General Available version is acceptable

•	Oracle Tuxedo 9.1 General Available version is acceptable

•	Oracle Tuxedo 10.0 General Available version is acceptable

•	Oracle Tuxedo 10gR3 General Available version is acceptable

•	Oracle Tuxedo 11gR1 General Available version is acceptable

This may require simultaneous patch upgrades for all interoperating domains involved. However, this simultaneous upgrade requirement might cause practical problems for applications that do staggered patch upgrades. To mitigate this issue, TM_GWT_OLDSECCHECK (for GWTDOMAIN)must be used until all interoperating domains are at least at the patch levels mentioned previously. Once all interoperating domains are upgraded, this environment variable can be eliminated from all domains.

Client-Server Interoperability

To support customer migration, the following client-server interoperability shown in Table 1‑2 is supported for Oracle Tuxedo 11g Release 1 (11.1.1.1.0).

 

Table 1‑2 Client-Server Interoperability

This component . . .	Can interoperate with . . .
Oracle Tuxedo 11g Release 1 (11.1.1.1.0) ATMI server	• ATMI clients running in Tuxedo 6.5, 8.1, 9.0, 9.1, 10.0 and 10gR3 • Jolt clients running in Jolt 8.1, 9.0, 9.1, 10.0 and 10gR3 (via Jolt server 11g Release 1 (11.1.1.1.0))
Oracle Tuxedo 10gR3 ATMI server	• ATMI clients running in Tuxedo 6.5, 8.1, 9.0, 9.1 and 10.0 • ATMI clients running in WebLogic Enterprise release 5.1 • Jolt clients running in Jolt 8.1, 9.0, 9.1, and 10.0 (via Jolt server 10g release 3 (10.3))
Oracle Tuxedo 10.0 ATMI server	• ATMI clients running in Tuxedo 6.5, 8.1, 9.0, and 9.1 • ATMI clients running in WebLogic Enterprise release 5.1 • Jolt clients running in Jolt 8.1, 9.0 and 9.1(via Jolt server 10.0)
Oracle Tuxedo 9.1 ATMI server	• ATMI clients running in Tuxedo 6.5, 8.1 and 9.0 • ATMI clients running in WebLogic Enterprise release 5.1 • Jolt clients running in Jolt 8.1 and 9.0 (via Jolt server 9.1)
Oracle Tuxedo 9.0 ATMI server	• ATMI clients running in Tuxedo 6.5 and 8.1 • ATMI clients running in WebLogic Enterprise release 5.1 • Jolt clients running in Jolt 8.1 (via Jolt server 9.0)
Oracle Tuxedo 8.1 ATMI server	• ATMI clients running in Tuxedo 6.5 • ATMI clients running in WebLogic Enterprise release 5.1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0) CORBA server	• CORBA clients running in Tuxedo 8.1, 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10g Release 3 (10.3) CORBA server	• CORBA clients running in Tuxedo 8.1, 9.0, 9.1, and 10.0 • CORBA clients running in WebLogic Enterprise 5.1
Oracle Tuxedo 10.0 CORBA server	• CORBA clients running in Tuxedo 8.1, 9.0 and 9.1 • CORBA clients running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.1 CORBA server	• CORBA clients running in Tuxedo 8.1 and 9.0 • CORBA clients running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.0 CORBA server	• CORBA clients running in Tuxedo 8.1 • CORBA clients running in WebLogic Enterprise 5.1
Oracle Tuxedo 8.1 CORBA server	• CORBA clients running in WebLogic Enterprise 5.1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0) ATMI client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10gR3 ATMI client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0, 9.1, and 10.0 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 10.0 ATMI client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0, and 9.1 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.1 ATMI client	• ATMI servers running in Tuxedo 6.5, 8.1, and 9.0 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.0 ATMI client	• ATMI servers running in Tuxedo 6.5 and 8.1 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 8.1 ATMI client	• ATMI servers running in Tuxedo 6.5 ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 11g Release 1(11.1) .NET client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10g Release 3(10.3) .NET client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0, 9.1 and 10.0 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 10.0 .NET client	• ATMI servers running in Tuxedo 6.5, 8.1, 9.0 and 9.1 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.1 .NET client	• ATMI servers running in Tuxedo 6.5, 8.1, and 9.0 • ATMI servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0) CORBA client	• CORBA servers running in Tuxedo 8.1, 9.0, 9.1 and 10.0, and 10gR3
Oracle Tuxedo 10gR3 CORBA client	• CORBA servers running in Tuxedo 8.1, 9.0, 9.1 and 10.0 • CORBA servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 10.0 CORBA client	• CORBA servers running in Tuxedo 8.1, 9.0, and 9.1 • CORBA servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.1 CORBA client	• CORBA servers running in Tuxedo 8.1 and 9.0 • CORBA servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 9.0 CORBA client	• CORBA servers running in Tuxedo 8.1 • CORBA servers running in WebLogic Enterprise 5.1
Oracle Tuxedo 8.1 CORBA client	• CORBA servers running in WebLogic Enterprise 5.1
Oracle Jolt 11g Release 1 (11.1.1.1.0) client	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in Tuxedo 8.1 (via Jolt server 8.1) • ATMI servers running in Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in Tuxedo 10gR3 (via Jolt server 10gR3) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)
Oracle Jolt 10gR3 client ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2)	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in Tuxedo 8.1 (via Jolt server 8.1) • ATMI servers running in Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)
Oracle Jolt 10.0 client	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in Tuxedo 8.1 (via Jolt server 8.1) • ATMI servers running in Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)
Oracle Jolt 9.1 client	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in Tuxedo 8.1 (via Jolt server 8.1) • ATMI servers running in Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)
Oracle Jolt 9.0 client	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in Tuxedo 8.1 (via Jolt server 8.1) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)
Oracle Jolt 8.1 client	• ATMI servers running in Tuxedo 6.5 (via Jolt server 1.2) • ATMI servers running in WebLogic Enterprise 5.1 (via Jolt server 1.2)

The capabilities available to a client for a particular client-server pair depend on the release of both the application client and the server application. For example, if you have an Oracle Tuxedo 11g Release 1 (11.1.1.1.0) ATMI client interoperating with an Oracle Tuxedo 6.5 server application, only Oracle Tuxedo 6.5 functionality is available to the client.

Client/Server Affinity Interoperability

Oracle Tuxedo Client/Server Affinity interoperability is supported as follows:

•	The Client/Server Affinity feature does not work with Oracle Tuxedo 10gR3 or earlier native clients; however, it does work with older /WS or Jolt client versions connecting to Oracle Tuxedo 11gR1.

•

MP mode

If Client/Server Affinity is configured in the UBBCONFIG file and there are slave nodes that use Oracle Tuxedo 10gR3 or earlier, the master node and only slave nodes installed with Oracle Tuxedo 11gR1 or later are affected.

•	Domain mode

To use Client/Server Affinity in a multiple-domain session, Oracle Tuxedo 11gR1 or later must be installed on all domains involved in the session.

Interoperability with Third-Party ORBs

Bootstrapping an Oracle Tuxedo CORBA domain establishes communication between a CORBA application client and the domain. Two bootstrapping mechanisms are available: (1) the Oracle mechanism using the Bootstrap object and (2) the CORBA Interoperable Naming Service (INS) bootstrapping mechanism specified by the OMG.

Support for INS was added in Oracle Tuxedo release 8.0. With the addition of INS, third-party ORBs that use INS are able to interoperate with the Oracle Tuxedo CORBA server ORB.

Figure 1‑5 shows the interoperability with third-party ORBs.

Figure 1‑5 Interoperability with Third-Party ORBs

 

Note:

The Oracle Tuxedo CORBA client environmental objects continue to be supported in the current Oracle Tuxedo release, just as they were supported in Oracle Tuxedo 8.1, 9.0, 9.1, 10.0, 10gR3 and Oracle WebLogic Enterprise 5.1.

A CORBA application client uses the Oracle Tuxedo Bootstrap object or the INS bootstrapping mechanism to obtain references to the objects in an Oracle Tuxedo CORBA domain. Oracle client ORBs use the Oracle mechanism, and third-party client ORBs use the CORBA INS mechanism. For more information about bootstrapping an Oracle Tuxedo domain, see Oracle Tuxedo CORBA Programming Reference.

Product Upgrades

Figure 1‑6 shows the existing Oracle Tuxedo and Oracle WebLogic Enterprise products that can be upgraded to Oracle Tuxedo 11g Release 1 (11.1.1.1.0).

Figure 1‑6 Upgrade Paths

When you shut down the domain (application) targeted for the upgrade, you must shut down the domain and perform a simple upgrade. If you cannot shut down the domain targeted for the upgrade, perform a hot upgrade, that is, add the Oracle Tuxedo 11g Release 1 (11.1.1.1.0) system software to the existing Oracle Tuxedo or Oracle WebLogic Enterprise domain without shutting down the domain.

For instructions on performing a simple upgrade or a hot upgrade, see “Upgrading the Oracle Tuxedo System to Release 11g Release 1 (11.1.1.1.0)” in Installing the Oracle Tuxedo System.

Upward Application Compatibility

Applications developed with Oracle Tuxedo 8.1, 9.0, 9.1, 10.0 and 10gR3 applications must be recompiled to run on Oracle Tuxedo 11g Release 1 (11.1.1.1.0).

Notes:

For XML-related applications, you must conform to Xerces C++ 2.5 interface requirements.

On Windows platform, the binary must be relinked if FML-related functions are used.