1.2 Intradomain Interoperability

Message exchange and protocol compatibility exist in the Intradomain Coexistence Group as shown in the following figure :

Figure 1-1 Intradomain Groups

Oracle Tuxedo 22c Release 1 can coexist in the same domain with Oracle Tuxedo 12cR2(12.2.2), 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:

The LLE is disabled by default in Tuxedo 22cR1, and the SECURITY parameter in the UBBCONFIG file is mandatory. Refer to, What’s New and Improved in 22cR1 Release Notes.

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 22c Release 1 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.
• Oracle Tuxedo 22c Release 1 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 following four features (XA Affinity, Common XID, Single Group Multiple Branches, and FAN Integration) are enabled by default.