Modifying the Java virtual machine settings on WebSphere

This section describes how to modify the Java™ virtual machine (JVM) settings through the IBM® WebSphere® Application Server Administrative Console.

Using the IBM WebSphere Administrative Console, in the Generic JVM arguments box, you must type each of the required JVM arguments, which must be separated by a space. Because WebSphere has specific settings for Initial Heap and Max Heap, you should enter the -Xms and -Xmx values in those specific fields. Detailed instructions for setting the JVM parameters can be found at the location in the following table.

Specific settings pertain to allocation of RAM. To prevent attempts to reallocate memory, -Xms and -Xmx must be set to the same value: the minimum and maximum amount of memory to allocate to the Real-time Monitoring server. For a server with 16 GB RAM, the preferred setting is a minimum of 12 GB. Generally, a number that is roughly 3/4 of the total RAM is preferred.

Set -Xmxns and -Xmxnx to the same value. The number should be 1/4 of the size chosen for -Xms.

The following table provides examples of the parameter values to use based on a memory size of 16 GB and 32 GB.

Table 2. JVM parameter values examples
Memory Parameter Value

16 GB





32 GB





You must also specify Garbage Collection settings. The -Xgcthreads8 entry should be the same as the number of processor cores available. For example, if there are two dual-core processors, enter -Xgcthreads4. If there are 4 dual-core processors, or 2 quad-core processors, enter -Xgcthreads8.

The -verbose:sizes and -verbose:gc settings are useful in determining garbage collection issues while running. All should be set. The last setting should point to the log directory, for example:

-xverbosegclog:"c:/program files/ibm/cognos/c10_64/realtime/logs"

If there is a space in the path, you must quote the entire parameter. Use forward slashes instead of backslashes in the path name.


  1. Start the IBM WebSphere Administrative Console.
  2. Include the obiProperties.jar found in the c10_location/realtime/bin64 directory to the classpath of the Java virtual machine.
    • For example, on a server running theWindows operating system, enter:

      c:/program files/ibm/cognos/c10_64/realtime/bin64/obiProperties.jar

    • On a server running the AIX®, Solaris, or Linux operating system, enter:


  3. If you are using either the Network Deployment or Extended Deployment versions of the IBM WebSphere Application Server, add following values to the classpath of the Java virtual machine before creating the web service agents:
    • c10_location/realtime/bin64/wsdl4j.jar
    • c10_location/realtime/bin64/wsif.jar
    • WebSphere_install_location/optionalLibraries/Apache/Struts/1.2.9/commons-logging.jar
  4. Set the JVM parameters for optimum memory and garbage collection (GC). Sample JVM parameters for running Real-time Monitoring on IBM Java for WebSphere are recommended as follows:
    Note: Type the -Xmsentry in the Initial Heap box. Type the -Xmxentry in the Max Heap box. Do not repeat these entries in the Generic JVM Arguments box.
  5. Ensure that the property is set to BOOTPROPS and that the JVM property BOOTPROPS points to the file you edited during your preparation for installation.


    <c10_location> specifies the location of the file that contains the bootstrap properties.

  6. Set the file encoding type to UTF8.


  7. Optionally, set the property anonymousaccessenabled to true to enable anonymous login. Set this property to false to disable anonymous login. When this property is enabled, the log-in screen shows the link Log in as Anonymous user.


    With anonymous login enabled, you can automatically log in to IBM Cognos® Real-time Monitoring Dashboard or IBM Cognos Real-time Monitoring Workbench without specifying a user name and password by using the following URL:


    This enables you to choose the application. If you configured the server to use a port that is different from the default, you may need to specify the port.

  8. Optionally, if outbound http connections such as to web services or geography coding services are required to go through a proxy server from your server environment, add the following JVM property to the start-up script so that the Java connectivity layer uses the proxy server for all outbound calls.

    -Dhttp.proxyHost=<fully qualified server name of http proxy>

    -Dhttp.proxyPort=<http proxy port number>

    -Dhttps.proxyHost=<fully qualified server name of https proxy>

    -Dhttps.proxyPort=<https proxy server port>

    Note: Proxy servers that require authentication are not supported.
  9. Save the new configuration.
  10. Optionally, set the language and locale parameters as described in Setting language and locale parameters for Real-time Monitoring on the WebSphere Application Server.

    You only need to perform this step if you want to initialize the metadata in a locale other than the default server locale.

  11. Save the changes.
  12. Restart the IBM WebSphere Application Server.