OSM Memory Tuning Guidelines
(Doc ID 2028249.1)
Last updated on NOVEMBER 25, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.0.0 to 22.214.171.124.0 [Release 7.0.0 to 7.4.0]
Information in this document applies to any platform.
This document provides guidelines focused on tuning memory usage and configuring Java Virtual Machine (JVM) parameters for Oracle Communications Order and Service Management (OSM) 7. It is targeted to system integrators and system administrators, who must work together to plan and configure an OSM solution, as well as Oracle support personnel dealing with OSM performance issues.
OSM provides great flexibility in configuring solutions. Because each customer implementation is unique, there is generally not a one-size-fits-all configuration for OSM. For this reason, configuration parameters must be adapted for each deployment. That being said, the sample JVM parameters provided in section 4.8 are recommended for all OSM installations; tuning for a specific solution should be focused on the remaining configuration parameters including order cache size and eviction timeout, connection pool size, and work manager maximum thread constraints.
This document assumes that the reader already has a basic understanding of OSM, WebLogic, Java and UNIX-based operating systems.
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