Using Oracle Tuxedo Version-Based Routing (Outbound)

1.1.3.3 Using Oracle Tuxedo Version-Based Routing (Outbound)

When using Oracle Tuxedo version-based routing with External Web services imported into Tuxedo using SALT, please note:

Since one GWWS instance cannot advertise more than one service with same name, that same service has to be in a different instance.
Based on the above, the existing mechanism can simply be used; configure multiple GWWS instances with VERSION_RANGE in its *GROUPsettings accordingly.

Following is an example where Oracle Tuxedo programs (client or server) call an external Web service exposed by both GWWS in groups GROUP2 and GROUP3. Programs using version 1 or 2 are routed to the service exposed by GWWS in GROUP2 which may connect to endpoint 1, and programs using version 3 or 4 are routed to the service exposed by GWWS in GROUP3 which may connect to a different endpoint than GWWS in GROUP2.

Example 1-9 Oracle Tuxedo Version-Based Routing with External Web Services

...
GROUP2
LMID=L1 GRPNO=2 VERSION_RANGE="1-2"
GROUP3
LMID=L1 GRPNO=3 REQUEST_VERSION=1 VERSION_RANGE="3-4"
...
GWWS SRVGRP=GROUP2 SRVID=30
...
GWWS SRVGRP=GROUP3 SRVID=30
...

Parent topic: Configuring External Web Services