IBM Tivoli Monitoring, Version 6.3

Setting the TEPS/e maximum heap size

When the dashboard data provider has been enabled on the Tivoli® Enterprise Portal Server, you can use monitoring dashboards in the Dashboard Application Services Hub console. In larger environments, it is possible for the Tivoli Enterprise Portal Server extended services (TEPS/e) Java process to run out of memory when large amounts of data are passed to the Dashboard Application Services Hub. You can increase the maximum heap size of the TEPS/e JRE to improve server response time and better accommodate a larger monitored environment.

Before you begin

The memory required by the TEPS/e depends on the size of the monitoring environment and on the Java heap size parameters. The default maximum Java heap size is 1500 MB, which is appropriate for 32-bit systems. On 64-bit systems, if you encounter "out of memory" exceptions, you can increase the maximum heap size of the TEPS/e JRE to values greater than 1500 MB to allow more memory usage and accommodate a larger monitored environment.

About this task

Complete the following steps on the computer where the portal server is installed to adjust the TEPS/e maximum heap size.

Procedure

  1. At the command prompt, change to the bin directory of your Tivoli Monitoring installation:
    • Windows install_dir\cnpsj\profiles\ITMProfile\bin
    • Linux or operating systems such as UNIX install_dir/platform/iw/profiles/ITMProfile/bin
  2. Enter the following command to start the eWAS console:
    • Windows wsadmin.bat
    • Linux or operating systems such as UNIX wsadmin.sh
  3. At the wsadmin prompt, enter the following command: $AdminConfig modify [$AdminConfig list JavaVirtualMachine] "{maximumHeapSize 2000}"
  4. Enter the following command to save your changes: $AdminConfig save
  5. Enter the following command to exit: quit

What to do next

Restart the portal server. If you continue to encounter "out of memory" exceptions, try increasing the maximum heap size again.


Feedback