1.1.2.4 Using Oracle Tuxedo Version-Based Routing (Inbound)

Using Oracle Tuxedo version-based routing with Oracle Tuxedo services exposed as Web services involves the following:

• GWWS gets REQUEST_VERSION and VERSION_RANGE from the UBBCONFIG file.
• Calling service with request version
• If different settings are needed (such as specific traffic from specific gateway to be routed to specific services), another gateway instance can be configured in a group with different REQUEST_VERSION value and started for this.

Following is an example where GWWS inherits a request version "1" from its UBBCONFIG settings, and therefore exposes services that are advertised by Oracle Tuxedo application servers which include "1" in their VERSION_RANGE settings (such as GROUP1 here). If a service exposed by GWWS is actually performed by a server in GROUP2, the result is a TPENOENT error forwarded to the remote Web Services client.

Example 1-8 Using Tuxedo Version Based Routing with Tuxedo Services Exposed as Web Services

...
GROUP1
LMID=L1 GRPNO=2 VERSION_RANGE="1-2"
GROUP2
LMID=L1 GRPNO=2 VERSION_RANGE="3-4"
GWWS_GRP
LMID=L1 GRPNO=3 REQUEST_VERSION=1
...
|mySERVER SRVGRP=GROUP2 SRVID=30
...
GWWS SRVGRP=GWWS_GRP SRVID=30
...