Interoperability and Coexistence

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 Defined

•	Intradomain Interoperability

•	Interdomain Interoperability

•	Client-Server Interoperability

•	Interoperability with Third-Party ORBs

Interoperability Defined

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:

•	Intradomain interoperability

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.”

•	Interdomain interoperability

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.

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 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.

From Oracle Tuxedo 11g Release 1 (11.1.1.1.0), 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 local service name 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 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.

•	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.

•	If users specify XPath in ROUTING section, the earlier Oracle Tuxedo release sites will not be booted.

•	In MP mode, when the following features are enabled, the slave node fails to be booted up if its Tuxedo version is lower than Tuxedo 12gR1 or if the slave node is running on the platforms that those features do not support.

•	XA Affinity

•	Common XID

•	Single Group Multiple Branches (SGMB)

•	FAN Integration

•	Direct Cross Domain Communication Leveraging RDMA

The following features are enabled for Tuxedo12gR1 RP073 or later if the slave node is running on IBM AIX (64-bit), HP-UX (64-bit), Oracle Solaris(64-bit) on SPARC, Linux x86-64 and Linux x86.

•	XA Affinity

•	Common XID

•	Single Group Multiple Branches (SGMB)

•	FAN Integration

In MP mode, when these features want to be enabled on the slave node which Tuxedo version is Tuxedo12gR1 RP073 or later. The Tuxedo version on the master node should be Tuxedo12cR2 RP065 or later.

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.

Interdomain Interoperability

Message exchange and protocol compatibility exist in each of the following interdomain scenarios as shown in Figure 1‑2.

Figure 1‑2 Interdomain Scenario 1

In 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

A TDomain process in any of these releases . . .		Can communicate with a TDomain process in any of these releases . . .
Oracle Tuxedo 12c Release 2 (12.2.2)	Connection Matrix	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 11gR1 Release 1		Oracle Tuxedo 11g Release 1 (11.1.1.3.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

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.

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.

Client-Server Interoperability

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

This component . . .	Can interoperate with . . .
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) • Workstation clients running in Oracle Tuxedo 6.5, 9.1, 10gR3, 11gR1, 12cR1, 12cR2 (12.1.3), 12cR2 (12.1.3), and 12cR2 (12.2.2) • Jolt clients running in Jolt 9.0, 9.1, 10.0 , 10gR3, and 11gR1, 12cR1 , 12cR2 (12.1.3), and 12cR2 (12.2.2) (via Jolt server 12c Release 2 (12.2.2))
Oracle Tuxedo 12c Release 2 (12.1.3) ATMI server	• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3) • Workstation clients running in Oracle Tuxedo 6.5, 9.1, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3) • Jolt clients running in Jolt 9.0, 9.1, 10.0 , 10gR3, and 11gR1, 12cR1, and 12cR2 (12.1.3) (via Jolt server 12c Release 2 (12.1.3))
Oracle Tuxedo 12c Release 1 ATMI server	• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1 • Workstation clients running in Oracle Tuxedo 6.5, 9.1, 10gR3, 11gR1, and 12cR1 • Jolt clients running in Jolt 9.0, 9.1, 10.0 , 10gR3, and 11gR1, and 12cR1 (via Jolt server 12c Release 1)
Oracle Tuxedo 11g Release 1 (11.1.1.1.0, 11.1.1.2.0, and 11.1.1.3.0) ATMI server	• ATMI clients running in Oracle Tuxedo 9.0, 9.1, 10.0 and 10gR3 • Jolt clients running in Jolt 9.0, 9.1, 10.0 and 10gR3 (via Jolt server 11g Release 1)
Oracle Tuxedo 10gR3 ATMI server	• ATMI clients running in Oracle Tuxedo 9.0, 9.1 and 10.0 • Jolt clients running in Jolt 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 Oracle Tuxedo 9.0, and 9.1 • Jolt clients running in Jolt 9.0 and 9.1(via Jolt server 10.0)
Oracle Tuxedo 9.1 ATMI server	• ATMI clients running in Tuxedo 9.0 • Jolt clients running in Jolt 9.0 (via Jolt server 9.1)
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)
Oracle Tuxedo 12g Release 2 (12.1.3) CORBA server	• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
Oracle Tuxedo 12g Release 1 CORBA server	• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0, 11.1.1.2.0, and 11.1.1.3.0) CORBA server	• CORBA clients running in Oracle Tuxedo 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10g Release 3 (10.3) CORBA server	• CORBA clients running in Oracle Tuxedo 9.0, 9.1, and 10.0
Oracle Tuxedo 10.0 CORBA server	• CORBA clients running in Oracle Tuxedo 9.0 and 9.1
Oracle Tuxedo 9.1 CORBA server	• CORBA clients running in Oracle Tuxedo 9.0
Oracle Tuxedo 12c Release 2 (12.2.2) ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, 12cR2 (12.1.3), and 12cR2 (12.2.2)
Oracle Tuxedo 12g Release 2 (12.1.3) ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
Oracle Tuxedo 12g Release 1 ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0, 11.1.1.2.0, and 11.1.1.3.0) ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10gR3 ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, and 10.0
Oracle Tuxedo 10.0 ATMI client	• ATMI servers running in Oracle Tuxedo 9.0, and 9.1
Oracle Tuxedo 9.1 ATMI client	• ATMI servers running in Oracle Tuxedo 9.0
Oracle Tuxedo 12c Release 2 (12.2.2) .NET client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, 12cR2 (12.1.3), and 12cR2 (12.2.2)
Oracle Tuxedo 12g Release 2 (12.1.3) .NET client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
Oracle Tuxedo 12g Release 1 .NET client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, and 12cR1
Oracle Tuxedo 11g Release 1 (11.1.1.1.0 and 11.1.1.2.0) .NET client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1, 10.0 and 10gR3
Oracle Tuxedo 10g Release 3(10.3) .NET client	• ATMI servers running in Oracle Tuxedo 9.0, 9.1 and 10.0
Oracle Tuxedo 10.0 .NET client	• ATMI servers running in Oracle Tuxedo 9.0 and 9.1
Oracle Tuxedo 9.1 .NET client	• ATMI servers running in Oracle Tuxedo 9.0
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.	• CORBA servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, 12cR2 (2.1.3), 12cR2 (12.2.2)
Oracle Tuxedo 12g Release 2 (12.1.3) CORBA client	• CORBA servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2 (12.1.3)
Oracle Tuxedo 12g Release 1 CORBA client	• CORBA servers running in Oracle Tuxedo 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1,
Oracle Tuxedo 11g Release 1 (11.1.1.1.0, 11.1.1.2.0, and 11.1.1.3.0) CORBA client	• CORBA servers running in Oracle Tuxedo 9.0, 9.1 and 10.0, and 10gR3
Oracle Tuxedo 10gR3 CORBA client	• CORBA servers running in Oracle Tuxedo 9.0, 9.1 and 10.0
Oracle Tuxedo 10.0 CORBA client	• CORBA servers running in Oracle Tuxedo 9.0, and 9.1
Oracle Tuxedo 9.1 CORBA client	• CORBA servers running in Oracle Tuxedo 9.0
Oracle Jolt 12c Release 2 (12.2.2) client	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Oracle Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Oracle Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in Oracle Tuxedo 10gR3 (via Jolt server 10gR3) • ATMI servers running in Oracle Tuxedo 11gR1 (via Jolt server 11gR1) • ATMI servers running in Oracle Tuxedo 12cR1 (via Jolt server 12cR1) • ATMI servers running in Oracle Tuxedo 12cR2 (12.1.3) (via Jolt server 12cR2 (12.1.3)) • ATMI servers running in Oracle Tuxedo 12cR2 (12.2.2) (via Jolt server 12cR2 (12.2.2))
Oracle Jolt 12c Release 2 (12.1.3)	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Oracle Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Oracle Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in Oracle Tuxedo 10gR3 (via Jolt server 10gR3) • ATMI servers running in Oracle Tuxedo 11gR1 (via Jolt server 11gR1) • ATMI servers running in Oracle Tuxedo 12cR1 (via Jolt server 12cR1) • ATMI servers running in Oracle Tuxedo 12cR2 (12.1.3) (via Jolt server 12cR2 (12.1.3))
Oracle Jolt 12c Release 1	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Oracle Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Oracle Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in Oracle Tuxedo 10gR3 (via Jolt server 10gR3) • ATMI servers running in Oracle Tuxedo 11gR1 (via Jolt server 11gR1) • ATMI servers running in Oracle Tuxedo 12cR1 (via Jolt server 12cR1)
Oracle Jolt 11g Release 1 (11.1.1.1.0, 11.1.1.2.0, and 11.1.1.3.0) client	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Oracle Tuxedo 9.1 (via Jolt server 9.1) • ATMI servers running in Oracle Tuxedo 10.0 (via Jolt server 10.0) • ATMI servers running in Oracle Tuxedo 10gR3 (via Jolt server 10gR3)
Oracle Jolt 10.0 client	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0) • ATMI servers running in Oracle Tuxedo 9.1 (via Jolt server 9.1)
Oracle Jolt 9.1 client	• ATMI servers running in Oracle Tuxedo 9.0 (via Jolt server 9.0)

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.

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 12cR2.

•

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 12cR2 or later are affected.

•	Domain mode

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

Feature-Specific Interoperability

The Oracle Tuxedo 12c Release 2 (12.2.2) feature-specific interoperability is supported as follows:

•	TLSv1.2 Support

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.

•	XML Based Data Dependent Routing (DDR)

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".

•	Exalogic Features

•	Oracle Tuxedo 12c Release 2 (12.1.3) can interoperate with Oracle Tuxedo 11gR1 (11.1.1.3.0) or above if any Exalogic feature that is introduced prior to Oracle Tuxedo 12c Release 2 (12.1.3) is enabled in the UBBCONFIG file.

•	Oracle Tuxedo 12c Release 2 (12.1.3) cannot interoperate with Oracle Tuxedo 11gR1 (11.1.1.2.0) or earlier if any Exalogic feature is enabled in the UBBCONFIG file.

•	Oracle Tuxedo 12c Release 2 (12.1.3) cannot interoperate with previous releases if any Exalogic feature that is introduced in Oracle Tuxedo 12c Release 2 (12.1.3) is enabled in the UBBCONFIG file.

•	Oracle Tuxedo 12c Release 2 (12.1.3) cannot interoperate with Oracle Tuxedo 11gR1 (11.1.1.3.0) if Read-Only Optimization for XA feature is enabled.

For more information, see Oracle Tuxedo/Oracle Exalogic Users Guide.

•	Millisecond Granularity for Timeouts

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).

•	ECID Propagation

End-to-end ECID propagation can only be guaranteed for machines/domains running Oracle Tuxedo 12c Release 2 (12.2.2).

•	Cross Domain Event Broker

This feature is supported only when both GWT and EvtBroker are running Oracle Tuxedo 12c Release 2 (12.2.2).

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‑3 shows the interoperability with third-party ORBs.

Figure 1‑3 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 9.0, 9.1, 10.0, 10gR3, 11gR1, 12cR1, and 12cR2.

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.