Resolving performance problems

IBM® z/OS® Connect runs as a Liberty application so performance problems are analyzed by using the tools that are provided by Liberty.

To analyze performance problems in Liberty, see A launch icon to indicate a link opens a new tab or window. Troubleshooting performance issues in the WebSphere Application Server for z/OS Liberty documentation.

More performance-related resources

For information about configuring z/OS Connect for best performance, see Performance considerations in the z/OS Connect documentation.
Supportpac CP02: IBM z/OS Connect Performance Reports
Monitoring with z/OS Connect section of the z/OS Connect product documentation.

z/OS Connect processing hangs or waits

Started task Applies to z/OS Connect Servers run by using a z/OS started task procedure.

When the z/OS Connect zFS data set is quiesced during a DFSMShsm backup, z/OS Connect appears to hang or wait, and the SMF data shows that no requests received.

To prevent this from happening, exclude the zFS data set containing the z/OS Connect log files from the backup.

Configuration parameters

To accommodate varied workloads and deployments of z/OS Connect, the default configuration parameters might need to be changed. To avoid impacting the performance of your z/OS Connect Server, be aware of the following configuration:

allowCustomCacheKey setting in openidConnectClient configuration

allowCustomCacheKey specifies whether a custom cache key is used to store users in an authentication cache. If this property is set to true and the cache key for a user is not found in the authentication cache, the user is required to log in again. Set this property to false when you use the jwtSso feature to allow the security subject to be constructed directly from the jwtSso cookie.

Set allowCustomCacheKey="false" in the openidConnectClient configuration if you notice high CPU usage in releases after 3.0.55. For more information, see A launch icon to indicate a link opens a new tab or window. WebSphere Liberty openidConnectClient configuration may cause high CPU in releases after 20.0.0.6.

More performance-related resources

SupportPac CP02: IBM z/OS Connect Enterprise Edition Performance Reports

Known issues

For more information about known performance issues and the suggested minimum levels, see Performance considerations.

Collecting (MustGather) data for z/OS Connect performance problems

For details on how to get MustGather information that you need to collect when you are diagnosing a performance problem, see MustGather data for IBM z/OS Connect performance problems.