This section outlines some suggestions to improve the performance of the SOA Gateway.
This only applies for web services which use the invoke operation, e.g services built from the Natural, Cobol or DLL drivers.
The SOA Gateway will validate the incoming XML against an XSD. This ensures that the contents and structure of the payload are correct, and will catch potential errors early on in processing. But XML validation is a relatively expensive operation, so it is possible to turn this off if required.
You may want to back up your existing XSD files before deletion. Use the "Import Web Service Definition" and ensure the XSD box is checked. See here for more information.
To delete the XSD, use the "Delete Web Service Definition", and ensure the XSD box is checked. The XSD has now been deleted from the server and validation of the payload will not take place.
Each time the SOA Gateway handles a request, it writes some logging information to the access log via Apache. By default, this file is access_log / access.log / DD:ACCESS based on the platform, *nix, Windows, z/OS respectively.
To restrict this logging, see the following Apache directive here
To remove this logging, remove the CustomLog directive from your httpd.conf / HTCONF. This can be accomplished by adding a # in front of the directive.
This only applies on z/OS or z/VSE.
Edit your SYSPARM and ensure caching of the SOA Gateway filesystem has been turned on. The option is CACHESIZE=N option on the CDI_DRIVER directive
E.g
CDI_DRIVER=('pfs,PAANPFS,CONTAINER=CIO://DD:PFS,CHARSET=ASCII,LRECL=4096,CACHESIZE=4096')
The SOA Gateway uses the Apache worker MPM to handle requests. This can be modified to increase server threads, therefore allowing the server to serve more requests. See the Apache documentation for more information.
Important:
Ensure that the ServerLimit of 1 is maintained at all times. The
SOA Gateway will not function correctly if more than server process is
started.
