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:
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.
This switch turns on garbage collection logging for the JVM. Replace <path/filename>
with the location where the garbage collection log should be generated.
-Xms
and -Xmx
These switches set the minimum (-Xms
) and maximum (-Xmx
) heap size for the JVM. The JVM adjusts heap size based on object usage and bounded by these two switches. Setting these switches to the same value increases predictability by removing the ability of the JVM to adjust the heap size.
Caution: | Fixing the heap size to a specific value requires special attention to memory tuning. |
-XX:NewRatio
This switch sets the ration of the young generation to the tenured generation. For example
-XX:NewRatio=3
would mean that the tenured generation is 3x the size of the young generation, or, in other words, the young generation is one quarter of the heap and the tenured generation is three-quarters of the heap.
To update Java options for Tomcat 5.x on Windows:
To update Java options for Tomcat 6.x on Windows:
To update Java options for WebLogic 10.3.0:
Note: | The MEM_ARGS parameter can also be updated in the startup script for the WebLogic domain. |
To update Java options for the Oracle WebCenter Analytics JVM:
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.
To update Java options for the Automation Service JVM:
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.
To update Java options for the Oracle WebCenter Collaboration JVM:
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. |
To update Java options for the Document Repository JVM:
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.
To update Java options for the Notification JVM:
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.
To update Java options for the PTUpload JVM:
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. |
To update Java options for the Publisher JVM:
# 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
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. |
To update Java options for the Oracle-BEA AquaLogic Interaction Studio JVM:
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. |
Oracle-BEA AquaLogic Interaction Workflow runs on the same JVM as Oracle-BEA AquaLogic Interaction Publisher and does not require separate tuning.