This section outlines some suggestions to improve the performance of SOA Gateway.

• Turning off Access Logging

  Each time 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.

• Use PFS caching

  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')

• Enable/disable Streaming

  By default, when a user issues a list request, with key data of "*", i.e. listing all records in the database, SOA Gateway will send back records in a "streamed" fashion. For example, as soon as one record is retrieved, it is immediately sent back to the client using the HTTP chunking protocol. It has been found that this is the most effective way of handling large amounts of data, but there is a small performance offset in doing this. There are a number of directives that affect how streaming is applied. These directives must be part of the Apache configuration file.

  SoaGatewayStreaming On : This is the default setting. Responses will be streamed back to the client using the HTTP Chunking protocol when a list is requested that will retrieve every record in the database.
  SoaGatewayStreaming Off : No streaming will ever take place. Use this option if you are concerned about performance, and will be listing every record in the database.
  SoaGatewayStreaming Force : SOA Gateway will always to attempt to stream data back to the client. This is most effective if the SOA Gateway is running on a machine with low resources, and low memory usage is a priority.

• Change MPM settings

  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. SOA Gateway will not function correctly if more than server process is started.