Setting the memory for the Java Virtual Machine on the Impact Liberty profile

When you start an instance of the JVM, you can specify a minimum and maximum heap size by using the -Xms and -Xmx flags. The -Xms flag specifies the minimum size of the memory heap and -Xmx specifies the maximum size.

About this task

For Netcool®/Impact, the default value of Xmx is 2400 MB. In JVM, Xmx sets the maximum memory heap size. To improve performance, make the heap size larger than the default setting of 2400 MB. As a guideline, increase the heap setting to 80% of the free memory on your system.

Consider the following factors when you increase the heap size:
  • Event flow volume
  • The number of SQL data types and the amount of data in them
  • Data type caching
  • Internal data types and the size of them
  • The number of event readers and event listeners
  • The number of hibernations

You can use the self-monitoring service to monitor the heap usage. For more information about setup of self-monitoring, see Running self-monitoring using the command line interface and Setting up self-monitoring by using the GUI.

The following procedure shows how to set the maximum heap size for Impact Liberty Profile.

Procedure

  1. Stop a server by using the relevant command:
    • On UNIX use $IMPACT_HOME/bin/stopGUIServer.sh or $IMPACT_HOME/bin/stopImpactServer.sh.
  2. Edit the file $IMPACT_HOME\wlp\usr\servers\<instance>\jvm.options.
    <instance>
    For GUI Server it is ImpactUI.
    For Impact Server it is the name of the Server Instance you provided during install time, the default is NCI.
  3. For your environment, specify the appropriate -Xms or -Xmx.
  4. Start the server by using the relevant command:
    • On UNIX use $IMPACT_HOME/bin/startGUIServer.sh or $IMPACT_HOME/bin/startImpactServer.sh.

Results

When you enable the memory monitoring feature in the self-monitoring service, Netcool/Impact checks the current heap size at intervals and compares it to the maximum size. The severity of the memory monitoring event is calculated based on the heap usage and the available system memory. For more information, see Memory status severity.