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 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: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.”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.Message exchange and protocol compatibility exist in the Intradomain Coexistence Group as shown in Figure 1‑1:Figure 1‑1 Intradomain GroupsOracle 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 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.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 1Figure 1‑3 Interdomain Scenario 2Figure 1‑4 Interdomain Scenario 3In 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 Oracle Tuxedo 11g Release 1 (11.1.1.1.0) Oracle Tuxedo 11g Release 1 (11.1.1.1.0) 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.
• Oracle Tuxedo 10gR3 General Available version is acceptable
• Oracle Tuxedo 11gR1 General Available version is acceptableThis 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.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 Oracle Tuxedo 11g Release 1 (11.1.1.1.0) ATMI server
• 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 Oracle Tuxedo 11g Release 1 (11.1.1.1.0) CORBA server Oracle Tuxedo 11g Release 1 (11.1.1.1.0) ATMI client Oracle Tuxedo 10gR3 ATMI client Oracle Tuxedo 11g Release 1 (11.1.1.1.0) CORBA client Oracle Tuxedo 10gR3 CORBA client Oracle Jolt 11g Release 1 (11.1.1.1.0) client 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.
• 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.
• 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.Figure 1‑5 shows the interoperability with third-party ORBs.Figure 1‑5 Interoperability with Third-Party ORBs
Note: 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.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 PathsWhen 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.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).