Increasing the Java Heap size

If it is intended that network resources will have large configuration sizes being processed on the Worker server, an increase in the Java heap size might be required.

About this task

The default Netcool Configuration Manager Java heap size will fail if used for the processing of large configurations. The maximum this may be increased to on 32-bit systems is 2048 MB, while for 64-bit systems there is no limit. A 64-bit JRE is highly recommended.
Restriction: You are restricted by the resources of your server.
Note: If you have a distributed setup, you need to modify the server memory settings on each server.

To increase the Java heap size, you need to locate and edit the Memory Environment script.

Procedure

To set the heap space for a presentation server

  1. Open
    /<ncm install path>/bin/utils/support/setEnv.sh
  2. Edit the following WebSphere parameters as required:
    • WEBSPHERE_INITIALHEAP_SIZE
    • WEBSPHERE_MAXIMUMHEAP_SIZE
    • WEBSPHERE_MAXPERM_SIZE
  3. Execute /<ncm install path>/bin/utils/support/setWSMem.sh to set the memory variables updated within 'setEnv.sh'.

For worker servers (including linked and standalone), and on the presentation server

  1. Open
    /<ncm install path>/bin/utils/support/setEnv.sh
  2. Edit WORKER_MEM_ARGS as required.
    Note: Do NOT run setWSMem.sh.

For IDT servers

  1. Open
    /<ncm install path>/bin/utils/support/setEnv.sh
  2. Edit IDT_MEM_ARGS as required.
    Important: Do NOT run setWSMem.sh.

What to do next

After making any of these changes, restart Netcool Configuration Manager.

Configuring the Java Heap size for immediate execution (Native Command Set workflow)

In order not to overstress the system, the safest approach is for you to reduce the normal execution thread count by the number of the new immediate execution threads that you have configured.

About this task

If you choose to add the new thread pool as additional threads, then you must increase the resources for the server in question.

Procedure

If you are adding Immediate Execution threads, add (or allow) a further 200MB of RAM per thread.

Example

For example if you currently have a 4GB Heap configured for running 20 normal execution threads on the Worker Server, and wish to add a further 2 Immediate execution threads, then the JVM Heap allocation should be increased to 4.4GB.
Note: The server should have enough physical or virtual RAM available to accommodate JVM Memory increases, including any memory requirements for the operating system, other applications or utilities that are run on the server.