Troubleshooting SOA Gateway Server issues

Apache 2.0.48-9 reports "Cannot load /usr/local/asg/libs/mod_xmiddle.so into server: libadalnkx.so: cannot open shared object file: No such file or directory"

See the Envvars Problem below

Envvars Problem

Some versions of Apache will report ( using RPM ) /usr/sbin/envvars as the envvars file, but the apache2ctl script uses /usr/bin/envvars. The ASG Install will use whichever file is reported by the RPM program. The install script will attempt to handle this problem by checking the apache2ctl script to see which envvars file it uses. If these differ, then the install script will attempt the symbolically link /usr/bin/envvars to /usr/sbin/envvars. The install script will not do this if the non-empty, or is already a symbolic link to somewhere else. When this happens the user doing the install must either

1. Symbolically link the file by hand

2. Add the source of "xmiddleEnv.sh" to this file by hand. See "/usr/sbin/envvars"

Could not open /etc/apache2/sysconfig.d/include.conf

Some vanilla Apache installations will reference the above file, which is used for Apache directives that are outside the scope of the default Apache installation. To get Apache to ignore this file, "touch" it ( see man 1 touch ), thus creating an empty file.

Cannot load mod_xmiddle.so into server: failed to map segment from shared object: Permission denied.

This error can occur on Red Hat when SELinux is enabled. To disable it do the following:

• As root, run system-config-securitylevel

• Select SELinux Tab.

• In the "Modify SELinux Policy" box, expand "HTTPD Service"

• Tick the box "Disable SELinux protection for httpd daemon"

• Click [ OK ]

• Click [ YES ]

API module structure `xmiddle_module' in file XXX is garbled - perhaps this is not an Apache module DSO?

Ensure that you have chosen the correct installation for your system. For example, this error can occur when SLES 9 files are installed on a SLES 10.

Ensure that the version of Apache you are installing on is either v2.0 or v2.2. Other versions are not supported.

SSLCertificateFile file /etc/httpd/conf/ssl.crt/server.crt does not exist or is empty. RHEL Only

Disable / Enable SSL in the Apache server. Enabling SSL is outside the scope of this document, see Apache Documentation. To disable, rename the /etc/httpd/conf.d/ssl.conf to /etc/httpd/conf/ssl.conf.disable, or delete it.

Failed to bind to <port number>, port already in use

The port specified on the Listen directive in Apache's configuration file is already being used by another application. Change this to a port number not being used.

No error on command line, but Apache is not responding.

Check Apache's error_log file for error messages from the SOA Gateway server.

The default location of the Apache error_log is

• SuSE: /var/log/apache2/error_log

• RedHat: /etc/httpd/logs/error_log

A SOAP Fault is generated

Check the associated message in the <soap:faultString> element for error explanation. There may also be further messages available in the Apache's error_log

See

• SuSE: /var/log/apache2/error_log

• RedHat: /etc/httpd/logs/error_log

Abend S0C1 in module SAFASG

When the SOA Gateway server is running with Security Level = User or Password and is protected by Adabas SAF this abend indicates that SAFASG has not been linked correctly, please revisit the Security Section and relink SAFASG accordingly.

Command 'LF' for dbid=212, fnr=9, Rsp 17 (Invalid file number)

This error indicates you are accessing a file (number 9) that does not exist on the Adabas database (ID=212). For example, you may be running a installation verfication test, and the standard demo files ("Employees" and "Vehicles") delivered with Adabas have not been installed, or have not been installed in the standard locations.

Could not load natural ni library! Failed to open DLL, error 126: The specified module could not be found.

See setup instructions here.

Unicode char 0xF1 is not representable in encoding ASCII.

See information about i18n here