This issue only applies to the SOA Gateway running on Linux, AIX or Solaris. If your license does not have any Adabas or Natural drivers enabled, this issue does not apply.
If the sagenv file is not available during the SOA Gateway install, Adabas or Natural drivers may not work correctly until this file is made available. For example, you have installed the SOA Gateway before installing Adabas.
Follow these steps to enable a new sagenv file in an existing SOA Gateway installation.
Edit the [INSTALL_HOME]/xmiddleEnv.sh
Append the following to the end of this file (assuming sagenv file is /opt/softwareAg/sagenv.new) :
if test -e "/opt/softwareAg/sagenv.new"; then
source /opt/softwareAg/sagenv.new &> /dev/null
fi
Save and close this file.
Stop and then Start the SOA Gateway server. See here for more information.
Modify the [INSTALL_HOME]/apache2/conf/adabas_soa_gw.conf and change the User directive to use the "sag" user.
Change the file permissions of the SOA Gateway files and directories
chown -R sag [INSTALL_HOME]
Review the error_log for errors/warnings.
Adabas or Natural drivers should now be added successfully. See here for more info.
During the FTP of the SOA Gateway to z/OS, the machine identifier will be set to the hostnam or IP address of the FTP server. This text will be displayed on messages appearing in the JESMSGLG. To change this, modify the SYSPARM member of the CONF dataset and set this as required. It is recommended that this is set to the hostname or IP address of the z/OS machine.
