Maintenance Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Java Virtual Machine Configuration

This appendix describes how to adjust JVM memory parameters and turn garbage collection logging on and off. Instructions below cover applications supported by Oracle WebCenter and those standalone Oracle WebCenter products.

The standalone Oracle WebCenter products are:

 


Java Memory Switches

The following are Java memory switches used to tune JVM garbage collection. Use these switches in conjunction with the instructions specific to your application server or Oracle WebCenter product.

 


Application Servers

Tomcat 5.x

To update Java options for Tomcat 5.x on Windows:

  1. Run TOMCAT_HOME\tomcat5w.exe
  2. Click the Java tab.
  3. Update the Java memory switches in the Java Options: box.
  4. Click OK. Restart the Tomcat service.

Tomcat 6.x

To update Java options for Tomcat 6.x on Windows:

  1. Run TOMCAT_HOME\tomcat6w.exe
  2. Click the Java tab.
  3. Update the Java memory switches in the Java Options: box.
  4. Click OK. Restart the Tomcat service.

WebLogic 10.3.0

To update Java options for WebLogic 10.3.0:

  1. Edit setDomainEnv.cmd in BEA_HOME/user/projects/domains/domain_name.
  2. Add arguments to the line:
  3. set MEM_ARGS=-Xms256m -Xmx512m
  4. Run setDomainEnv.cmd.
Note: The MEM_ARGS parameter can also be updated in the startup script for the WebLogic domain.

 


Oracle WebCenter Standalone Products

Oracle WebCenter Analytics

To update Java options for the Oracle WebCenter Analytics JVM:

  1. Edit wrapper.conf in PT_HOME/ptanalytics/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the Analytics service.

Automation Service

To update Java options for the Automation Service JVM:

  1. Edit wrapper.conf in PT_HOME/ptportal/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the Automation service.

Oracle WebCenter Collaboration

To update Java options for the Oracle WebCenter Collaboration JVM:

  1. Edit wrapper.conf in PT_HOME/ptcollab/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.
  4. Restart the Collaboration service.

Document Repository

To update Java options for the Document Repository JVM:

  1. Edit wrapper.conf in PT_HOME/ptdr/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the Document Repository service.

Notification

To update Java options for the Notification JVM:

  1. Edit wrapper.conf in PT_HOME/ptnotification/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the Notification service.

PTUpload

To update Java options for the PTUpload JVM:

  1. Edit wrapper.conf in PT_HOME/ptupload/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the PTUpload service.

Oracle-BEA AquaLogic Interaction Publisher

To update Java options for the Publisher JVM:

  1. Edit service.conf in PT_HOME/ptcs/version/settings/config.
  2. Add a new parameter or modify existing parameters in the section Java Additional Parameters.
  3. For example, locate

    # Java Additional Parameters
    wrapper.java.additional.1=-Dprogram.name=cswfserver
    wrapper.java.additional.2=-Djava.awt.headless=true
    wrapper.java.additional.3=-Dplumtree.container.home=./../../../../../ptcs/6.2/container
    wrapper.java.additional.4=-Dplumtree.container.logs=./../../../../../ptcs/6.2/logs
    wrapper.java.additional.5=-Dorg.jboss.net.protocol.file.decodeFilePaths=true

    and add the garbage collection logging parameter

    # Java Additional Parameters
    wrapper.java.additional.1=-Dprogram.name=cswfserver
    wrapper.java.additional.2=-Djava.awt.headless=true
    wrapper.java.additional.3=-Dplumtree.container.home=./../../../../../ptcs/6.2/container
    wrapper.java.additional.4=-Dplumtree.container.logs=./../../../../../ptcs/6.2/logs
    wrapper.java.additional.5=-Dorg.jboss.net.protocol.file.decodeFilePaths=true
    wrapper.java.additional.6=-Xloggc:c:\publishergclog
  4. Restart the Publisher service.
Note: Oracle-BEA AquaLogic Interaction Publisher and Oracle-BEA AquaLogic Interaction Workflow run on the same JVM. Garbage collection logging and memory tunings are for both services.

Oracle-BEA AquaLogic Interaction Studio

To update Java options for the Oracle-BEA AquaLogic Interaction Studio JVM:

  1. Edit wrapper.conf in PT_HOME/ptstudio/version/settings/config.
  2. Add or modify parameters in the section Additional -D Java Properties.
  3. Note: Java parameter numbers must be continuous and incremental, and are set in both wrapper_base.conf and wrapper.conf. Check both files to ensure added parameters use the next number in sequence.

Restart the Studio service.

Oracle-BEA AquaLogic Interaction Workflow

Oracle-BEA AquaLogic Interaction Workflow runs on the same JVM as Oracle-BEA AquaLogic Interaction Publisher and does not require separate tuning.


  Back to Top       Previous  Next