NonStop SOAP User's Manual

NonStop SOAP Features and Functions

NonStop SOAP User’s Manual—520501-012

4-58

Pathmon Mapping

Pathmon mapping allows you to override the PATHMON name defined in the SDL with

a different PATHMON name during the SOAP server’s runtime execution.

A typical example might be a situation where you have multiple SOAP servers

deployed under the iTP WebServer supplying the same functionality but using services

located in different Pathmons.

For example, consider a company with operations in these regions: America, Asia

Pacific, Europe and Middle East. A simple NonStop SOAP based catalog Web service

provided by this company runs in a ServerClass under a certain Pathmon. For all the

regions, only the database that is accessed differs and as a result the company has

the same code running under different Pathmons (one each for every region).

As a result, for the NonStop SOAP server deployed you would have to create different

SDLs, each containing one of the Pathmons. Notice that this is the only difference in

the SDLs, as the company wants to keep the different parameters of the Web service

unchanged.

With the introduction of the Pathmon mapping feature you have the option to define

just one SDL file and then configure each of the NonStop SOAP server deployments to

map the Pathmon defined in the SDL to another Pathmon. This mapping would be

done using the SOAP configuration file (referred to as

nssoap.config

Config File Changes

The config file contains changes for Pathmon mapping. Continuing with the scenario

presented earlier, the two Pathmon names defined in the SDL are "$CATLG" and

"$PRCNG". These examples show how to enter the Pathmon mappings in the config

file.

Config File # 1 (For AMERICAS Region)

<SoapEnvironment

SOAP_SDLDB_LOC="$VOL.SUBVOL"

.........>

.........

</SoapEnvironment>