![]() |
![]() |
![]() |
![]() |
![]() |
The following sections describe how Oracle Tuxedo 12c Release 2 (12.2.2) 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 12c Release 2 (12.2.2) or earlier 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 12c Release 2 (12.2.2) 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 Oracle Tuxedo system software in the domain. Accordingly, the Oracle Tuxedo domain just described qualifies as an “Oracle Tuxedo domain running Oracle Tuxedo release 12c Release 2 (12.2.2) software.”Involves one Oracle Tuxedo domain running Oracle Tuxedo release 12c Release 2 (12.2.2) 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 12c Release 2 (12.2.2) can coexist in the same domain with Oracle Tuxedo 12cR2 (2.1.3), 12cR1, 11gR1, 10gR3, 10.0, 9.1, and 9.0. 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.
Note: Tuxedo 12cR2 (12.2.2) takes TLSv1.2 by default if SSL is enabled. If a Tuxedo 12cR2 (12.2.2) master connects to an earlier release slave in MP mode, tlisten must be started on the master before running the tmboot command.
• 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 12cR2 domain. If long service names are used, the earlier Oracle Tuxedo release site will not boot.
• Oracle Tuxedo 12c Release 2 (12.2.2) 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.
Note: When the option EECS (in OPTIONS of UBBCONFIG *RESOURCES section) is specified, the folowing four features (XA Affinity, Common XID, Single Group Multiple Branches, and FAN Integration) are enabled by default.Message exchange and protocol compatibility exist in each of the following interdomain scenarios as shown in Figure 1‑2.Figure 1‑2 Interdomain Scenario 1In this scenario, 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.
Note: Tuxedo 12.2.2 takes TLSv1.2 by default if SSL is enabled. You must explicitly specify specify TLSversion = {TLSv1.2|TLSv1.1|TLSv1.0} in the DMCONFIG file *DM_TDOMAIN section (see DMCONGIG(5)) for every GWTDOMAIN connection.
Table 1‑1 Communicating TDomain Gateway Processes Oracle Tuxedo 12c Release 2 (12.2.2) Oracle Tuxedo 12c Release 2 (12.2.2) Oracle Tuxedo 12c Release 2 (12.1.3) Oracle Tuxedo 12c Release 2 (12.1.3) Oracle Tuxedo 12c Release 1 Oracle Tuxedo 12c Release 1 Oracle Tuxedo 12c Release 2 (12.2.2) supports interdomain interoperability with Tuxedo 12c Release 2 (12.1.3), 12cR1, 11gR1, 10gR3, 10.0, 9.1, 9.0 CORBA domains. This capability includes the ability to advertise CORBA C++ factories across domain boundaries.To support customer migration, the following client-server interoperability shown in Table 1‑2 is supported for Oracle Tuxedo 12c Release 2 (12.2.2).
Table 1‑2 Client-Server Interoperability Oracle Tuxedo 12c Release 2 (12.2.2) ATMI server
• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, 12cR2 (12.1.3), and 12cR2 (12.2.2)
• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1
• Jolt clients running in Jolt 9.0, 9.1, 10.0 and 10gR3 (via Jolt server 11g Release 1) Oracle Tuxedo 10gR3 ATMI server Oracle Tuxedo 12c Release 2 (12.2.2) CORBA server
• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, 12cR2 (12.1.3), and 12cR2 (12.2.2)
• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1 Oracle Tuxedo 12c Release 2 (12.2.2) ATMI client Oracle Tuxedo 10gR3 ATMI client Oracle Tuxedo 12c Release 2 (12.2.2) .NET client Oracle Tuxedo 12c Release 2 (12.2.2) CORBA client
Note: Tuxedo 12.2.2 takes TLSv1.2 by default if SSL is enabled. You must explicitly specify TLS1.0 on the COBRA client side for the connection to a Tuxedo 12.1.3 or earlier release server. Oracle Tuxedo 10gR3 CORBA client Oracle Jolt 12c Release 2 (12.2.2) client Oracle Jolt 12c Release 2 (12.1.3) Oracle Jolt 12c Release 1 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 12c Release 2 (12.2.2) ATMI client interoperating with an Oracle Tuxedo 9.1 server application, only Oracle Tuxedo 9.1 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 12cR2.
• 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 12cR2 or later are affected.The Oracle Tuxedo 12c Release 2 (12.2.2) feature-specific interoperability is supported as follows:Earlier Tuxedo releases only supported TLSv1.0. Tuxedo 12.2.2 supports TLS1.2/1.1/1.0 and takes TLSv1.2 by default. Tuxedo 12.2.2 either self-adapts or uses TLS1.2 on the SSL client side to inter-operate with a component that acts as an SSL server on top of earlier Tuxedo release(s). You must explicitly specify TLS1.0 on the SSL client side (including GWTDOMAIN, COBRA client, GWWS outbound HTTPS), for connection to a Tuxedo 12.1.3 or earlier release.To use the XML based DDR, all the machines in one domain must use Oracle Tuxedo 12c Release 2 (12.2.2). If any one of them uses a lower version, tmboot prints an error message "Invalid release".If an MP deployment environment is configured with millisecond SCANUNIT, all the nodes in this domain should use Oracle Tuxedo 12c Release 2 (12.2.2).End-to-end ECID propagation can only be guaranteed for machines/domains running Oracle Tuxedo 12c Release 2 (12.2.2).This feature is supported only when both GWT and EvtBroker are running Oracle Tuxedo 12c Release 2 (12.2.2).Figure 1‑3 shows the interoperability with third-party ORBs.Figure 1‑3 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.