Skip to Main Content
Return to Navigation

Tuning Performance and Monitoring Resources

Monitoring the performance of a WebLogic instance is primarily performed in the Administration Console. This section discusses how to:

Managing JVM Heap Size

This section discusses how to:

  • Monitor JVM heap.

  • Change JVM heap size.

Monitoring JVM Heap

The JVM heap size is the amount of memory that a particular JRE (Java Runtime Environment) gives to the JVM (Java Virtual Machine) that it creates. The java.exe command on Windows, java on UNIX and beasvc.exe when running WebLogic as a Windows service is the JRE, and the JVM exists within the JRE’s memory space. The primary sources for monitoring the amount of memory that is in use within a JVM are the Administration Console and the WebLogic logs.

To monitor the amount of the JVM heap size available and in use:

  1. Sign on to the Administration Console by entering the following URL in a browser:

    http://webserver:9999/console

    Where webserver is the hostname of the WebLogic server.

  2. Traverse the following in the navigation tree on the left:

    1. Expand your WebLogic domain (for example, peoplesoft).

    2. Expand Servers.

  3. Click the server you intend to monitor (for example, PIA).

  4. Select the Monitoring tab, and the Performance sub-tab.

Changing the JVM Heap Size

If you need to adjust any of the Java options, most commonly the JVM heap size, you must manually edit that WebLogic domain’s local setEnv script. The parameters, -Xms and -Xmx, control the JVM memory minimum and maximum heap size respectively.

Following are examples of the JVM heap size as specified in setEnv using the JAVA_OPTIONS_OSplatform environment variable. You only need to set the variables that correspond to the operating system where the WebLogic server is running.

See Adjusting the JVM Heap Size.

Note: If you do adjust any of the Java options, most commonly the JVM heap size, you must restart WebLogic for these changes to take effect.

If you're running WebLogic Server as a Windows service you must rerun the installNTservice script to propagate this change into the Windows registry.

The WebLogic Node Manager does not use the Java options set in setEnv, but instead uses Java options set from the WebLogic console.

To modify the Java options for a WebLogic instance started via the WebLogic Node Manager:

  1. Sign on to the WebLogic Server Console by entering the following URL in a browser:

    http://webserver:9999/console

    Where webserver is the hostname of the WebLogic server.

  2. Expand your WebLogic domain (for example, peoplesoft) and click Environment, then Servers.

  3. Select the managed server you intend to modify.

  4. Select the Configuration tab, and the Server Start sub-tab.

  5. Update the Arguments field.

  6. Click Save.

Monitoring HTTP Session Count for PeopleSoft Interaction Hub

In addition to memory and thread usage, it's also possible to monitor the number of established HTTP sessions used in conjunction with the PeopleSoft PORTAL application. This number, although not necessarily directly related to current performance, is an indicator of the following performance factors:

  • JVM memory used to store HTTP session data.

  • Current number of logged on clients.

  • Peak number of logged on clients.

  • Idle time of logged on clients.

To monitor the total number of HTTP sessions:

  1. Sign on to the Administration Console.

  2. In the Domain Structure section, click Deployments and select the check box next to peoplesoft.

  3. Select the Monitoring tab.