My Oracle Support Banner

Siebel IP17 and above – Application Interface and Clustering Gateway Settings and Recommendations (Doc ID 2591119.1)

Last updated on FEBRUARY 05, 2021

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.






Goal

The goal of this document is to provide insight to general sizing requirements around the deployment of tomcat and Siebel Gateway in Siebel IP17 and above, and recommendations to address or mitigate certain issues surrounding the instability of tomcat prior to 8.5.23 and Gateway memory leak post Siebel 18.5.

We encourage Siebel customers to consider 19.1 or later releases, if possible. Siebel Updates are cumulative; the recommendation is applying the latest update available that contains the fixes for both issues.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 1. Cause and symptoms
 a. Tomcat issues related to Siebel 2017.x and Siebel 2018.x before Siebel 2018 Patch 8
 b. Siebel Gateway Clustering from Siebel 2018 Patch 5 to  Siebel 2018 Patch 12
 2. Settings and Recommendations
 a. Tomcat issues related to Siebel 2017.x and Siebel 2018.x before Siebel 2018 Patch 8
 b. Siebel Gateway Clustering from Siebel 2018 Patch 5 to Siebel 2018 Patch 12
 c. Recommendations for settings for AI/Gateway tomcat heap size and MaxThreads
 d. While the performance issues are under investigation frequent restarts are recommended mitigating performance degradations.
 e. As a safeguard in Siebel 2019 Patch 1, medium settings above could be considered and trim down through monitoring.
 f. For Unix/Linux installations, kernel User Limits (ulimit) is recommended to be set  to -1 (unlimited)
 3. Monitoring
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.