Use Case 3: Connecting Oracle Tuxedo Domains Using SOAP Protocol

1.4.3 Use Case 3: Connecting Oracle Tuxedo Domains Using SOAP Protocol

SALT also allows you to connect two different Oracle Tuxedo domains using GWWS servers as an alternative to using /T domain. The GWWS server in the calling domain works in an outbound direction, the GWWS server in the receiving domain works in an inbound direction.

The receiving Oracle Tuxedo domain must propagate the Oracle Tuxedo service definition to the calling Oracle Tuxedo domain. This means that the calling domain Oracle Tuxedo Service Metadata Repository must contain the Oracle Tuxedo service definition file that runs in the receiving domain.

Note:

This should be set up manually. The Oracle Tuxedo Service Metadata Repository infrastructure does not currently provide automatic propagation between Oracle Tuxedo domains.

The WSDL document is not required. SALT provides simple configurations to allow two GWWS servers to work together for domain connectivity using SOAP protocol without needing to exchange WSDL documents.

The following figure illustrates how to use SALT to connect two domains.

Figure 1-5 Connecting Two Oracle Tuxedo Domains with SOAP protocol

Two GWWS servers should not be used to create connections within the same Oracle Tuxedo domain, see Figure 6. Also, a single GWWS server cannot connect to itself, see figure below:

In either scenario, the GWWS server advertises the same Oracle Tuxedo services which are already advertised by other application servers. This might result in dead-loop service dispatching.

WARNING:

It is strongly advised that you carefully plan and configure your SALT application to avoid these scenarios.

The following figure illustrates Two GWWS Servers Making a Connection Within the Same Oracle Tuxedo Domain

Figure 1-6 Two GWWS Servers Making a Connection Within the Same Oracle Tuxedo Domain

Figure 1-7 Single GWWS Server Making a Connection to Itself

Parent topic: SALT Use Cases