1.1.9.2 Configuring the GWWS Servers in the *SERVERS Section
To boot GWWS instances defined in the SALTDEPLOY
file, the GWWS servers must be defined in the *SERVERS
section of the UBBCONFIG file. You can define one or more GWWS
server instances concurrently in the UBBCONFIG file. Each GWWS
server must be assigned with a unique instance id with the option
“-i
” within the Oracle Tuxedo domain. The
instance id must be present in the XML version
SALTDEPLOY
file and the generated binary version
SALTCONFIG file.
The following is an example of a segment of the UBBCONFIG file that shows how to define GWWS servers in an Oracle Tuxedo application:
Example 1-32 GWWS Servers Defined In the UBBCONFIG File *SERVERS Section
......
*SERVERS
GWWS SRVGRP=GROUP1 SRVID=10
CLOPT="-A -- –i GW1"
GWWS SRVGRP=GROUP1 SRVID=11
CLOPT="-A -- –i GW2"
GWWS SRVGRP=GROUP2 SRVID=20
CLOPT="-A -- -c saltconf_2.xml –i GW3"
......
Note:
Be sure that the TMMETADATA system server is set up in the UBBCONFIG file to start before the GWWS server boots. Because the GWWS server calls services provided by TMMETADATA, it must boot after TMMETADATA.To ensure TMMETADATA
is started prior to being called by the GWWS
server, put TMMETADATA
before GWWS
in the UBBCONFIG file or use SEQUENCE
parameters in *SERVERS
definition in the UBBCONFIG file.
SALT configuration information is pre-compiled with wsloadcf
to generate theSALTCONFIG
file binary. GWWS
server reads the SALTCONFIG
file at start up.The SALTCONFIG
environment variable must be set correctly with the SALTCONFIG
file entity before booting GWWS
servers.
Option “-c
” is deprecated in the current version SALT. In SALT 1.1 release, option “-c
” is used to specify SALT 1.1 configuration file for the GWWS
server. In SALT 2.0, GWWS
server reads SALTCONFIG
file at start up. GWWS
server specified with this option can be booted with a warning message to indicate this deprecation. The specified file can be arbitrary and is not read by the GWWS
server.
Parent topic: Configuring the UBBCONFIG File for SALT