This section outlines the steps required to run multiple instances of the SOA Gateway, either of the same, or different versions, on a single operating system image.
The simplest way for setting up multiple SOA Gateway servers on z/OS is to execute the Deployment Wizard once for every server, specifying distinct HLQs (High Level Qualifiers) for the datasets, TCP/IP port numbers etc., then execute the setup jobs.
This will also create multiple copies of the SOA Gateway load library, which is not required, so the start job / procedure for the various instances of the server can be modified to all use the same loadlib in its STEPLIB.
This step-by-step guide assumes good knowledge of the Apache webserver on a Linux platform.
The following steps outline how to copy the existing SOA Gateway installation, and then bring up both the existing and new installations using the same apache webserver.
If running, stop the soa gateway. See here how to do this.
Make a duplicate of the current installations files and directories. For example, if installed in /home/bre/soaGateway, then
mkdir /home/bre/soaGatewayNew
cp -R /home/bre/soaGateway/* /home/bre/soaGatewayNew
In the new installation, change the Apache Listen directive, specifying a yet unused port number. This directive can be found in the httpd.conf file in the apache2/conf directory.
Again, edit the new httpd.conf file and change the Include directive on the last line to pick up the new installation.
Edit new adabas_soa_gw.conf file in the new installation. Modify required directives to pick up the new files and directories in the new installation.
Add a fully qualified PidFile directive to the new httpd.conf (if one is not already present ). This pid file should point into the new installation.
For example
<IfModule !mpm_netware.c>
PidFile /home/bre/soaGatewayNew/apache2/logs/httpd.pid
</IfModule>Modify the new xmiddleEnv.sh file , updating its contents to use the new installation.
Edit the new envvars file, updating its contents to use the new installation.
In the current installation (not the one you have just created) copy the apachectl control script. For example
cp /home/bre/soaGateway/apache2/bin/apachectl /home/bre/soaGateway/apache2/bin/apachectl_new
Modify the new file to pick up the new httpd.conf and new envvars file.
Note:
You do not need to change the path to the httpd binary.
Note:
Therefore you may remove the new Apache libraries and binaries. For
example, these are located under
/home/bre/soaGateway/apache2/lib and
/home/bre/soaGateway/apache2/bin/. Do not remove the
apache2/bin/envvars file.
Use the 2 apachectls scripts to start your SOA Gateways.
Verify that the SOA Gateway start-up messages (found in the Apache logs) refer to the new SOA Gateway configuration file.