Configuring the Client Process

The SOAPam Client Process receives interprocess messages from your application process and relays them to Web services that you have defined in a Client Definition File (CDF). When the Web service completes, its response is returned as a reply to the original interprocess message request. Refer to Creating and Editing the Client Definition File for more information about the CDF.

The SOAPam Client Process is started by running the SOAPAMCP program as a standalone Guardian process or by configuring the program as a Pathway server.

Running the Client Process as a Guardian Process

The general syntax for starting the client process from TACL as a standalone Guardian process is:

CODE

tacl> run SOAPAMCP / run-options / command-line-parameters

Example

The following example starts the Client Process nowaited, with a process name of $WSCP and a home terminal of $VHS, using the configuration options listed in a file named OPTIONS.

CODE

tacl> run SOAPAMCP / name $wscp, nowait, term $vhs / @options

Refer to the SOAPAMCP Command-Line Reference page for complete information about options for configuring the Client Process

Running the Client Process as a Pathway Server

The SOAPam Client Process may also be configured as a Pathway server. Potential advantages of running the Client Process as a Pathway server include process management and load balancing.

The configuration options are the same as those for standalone process configuration, however in the Pathway environment individual options are supplied as server PARAMs. The following is a sample pathway server configuration:

CODE

reset server
set server cpus 0:1
set server createdelay 0 secs
set server deletedelay 60 secs
set server highpin on
set server linkdepth 1
set server maxservers 6
set server maxlinks 20
set server numstatic 0
set server program soapamcp
set server tmf on
set server debug off
set server param cdf "echocdf"
set server param log "$0 event info"
set server param tcpip "$zsam0"
add server echo-service

You may also provide the options in a command file by setting the SERVER STARTUP value to @<command-file>. The following is a sample pathway configuration using this technique.

CODE

reset server
set server cpus 0:1
set server createdelay 0 secs
set server deletedelay 60 secs
set server highpin on
set server linkdepth 1
set server maxservers 6
set server maxlinks 20
set server numstatic 0
set server program soapamcp
set server tmf on
set server debug off
set server startup @config
add server echo-service

Refer to the SOAPAMCP Command-Line Reference page for complete information about options for configuring the Client Process