66 Configuring JVM Tuning Parameters

Learn how to tune the JVM parameters in your Oracle Communications Elastic Charging Engine (ECE) system.

Topics in this document:

• Configuring JVM Tuning Parameters

• Configuring Client-Side ECE Request Queues

Configuring JVM Tuning Parameters

Configure JVM tuning parameters for garbage collection and heap size tuning.

Each row in the topology file represents an ECE component that is a running JVM in the cluster. In the topology file, you can specify a JVM tuning profile file for each node defined. This allows you to provide specific tuning settings for each node in the cluster. Multiple nodes can point to the same tuning profile.

To configure JVM tuning parameters:

1. Open the ECE_home/config/defaultTuningProfile.properties file.

   You can create your own JVM tuning file and save it in this directory. You can name the file what you want.

2. Set the parameters as needed.

3. Save the file.

4. In the topology file, ensure your JVM tuning file is associated with the node to which you want the parameters to apply.

   The JVM tuning file is referenced by name in the ECE_home/config/eceTopology.conf file.

Configuring Client-Side ECE Request Queues

You can configure the request queues that your charging clients use to submit requests to ECE.

To configure client-side ECE request queues:

1. Access the ECE configuration MBeans in a JMX editor, such as JConsole. See "Accessing ECE Configuration MBeans".

2. Expand the ECE Configuration node.

3. Expand ChargingClient.

4. Expand BatchRequestService.

5. Set the thread pool size, batch time out, and batch size attributes for the request queues.

   For descriptions of each attribute, see the documentation for the BRSStatMXBean for oracle.communication.brm.charging.brs in ECE Java API Reference.