Add Jvm.cfg For Mac

admin  05.04.2020  No Commentson Add Jvm.cfg For Mac

Configuring the Default JVM and Java Arguments

The directory server provides a means of configuring the Java Virtual Machine (JVM)and Java options for each command-line utility and for the directory server itself.The Java configuration is provided in a properties file, located at instance-dir/OUD/config/java.properties. The configurationspecified in this file is taken into account each time the dsjavapropertiescommand is run. If you do not run the dsjavaproperties command, theproperties file is ignored.

The properties file can be used to specify (among other arguments) whether acommand runs using the JVM in -server mode or -client mode. Bydefault, all client applications run in -client mode, while the directory server andcertain server utilities run in -server mode. Generally, -server mode provides higher throughputthan -client mode, at the expense of slightly longer startup times.

For certain commands (import-ldif, export-ldif, backup, and restore) you can also specifydifferent Java arguments (and a different JVM) depending on whether the command isrun in online or offline mode.

'-XXaltjvm=jvmdir' option, but that too is unsupported. # and may not be available in a future release.server KNOWN.client IGNORE. To add another account, select Tools Accounts. Then select the plus (+) sign New Account. Note: If adding a Gmail, Yahoo, or other IMAP or pop account, see Add.

The Java Properties File Format

The Java properties file has the following format.

  • command-name.java-home=JVM-path

  • command-name.java-args=JVM-arguments

The following table shows three properties present in the java.properties file thatare of particular importance.

Description
If True, the system checks the default.java-args property inthis properties file before the checking the OPENDS_JAVA_ARGS environment variable. If false,the system checks the OPENDS_JAVA_ARGS environment variable first.
Sets the JVM that will beused for the directory server and for all of its command-line utilities, unlessa different JVM is specified for a particular utility.

Configuring JVM Options

The following table summarizes the Java options that can have an impact onserver performance. Note that some of these options apply only to theSun JVM.

Option
Selects server application runtime optimizations. The directory server will take longer to startand “warm up” but will be more aggressively optimized to produce higher throughput.
-d64
For64-bit machines only. By default, the directory server selects a 32-bit JVM regardlessof the architecture. This options should be specified when a large JVM heapis required (greater than 4 Gytes) and the architecture is 64-bit.
-Xms2G -Xmx2G
Selects the initialand maximum memory sizes available to the JVM, respectively. These values are usedfor the JVM heap, which reserves memory for the directory server and itsdatabase (DB) cache (or caches if more than one). Increasing the amount ofmemory available can improve performance, but increasing it to too high a valuecan have a detrimental effect in the form of longer pauses for fullgarbage collection runs. Therefore, the initial and maximum sizes should be set tothe same value. As a general guideline, take a look atthe size of the Oracle Berkeley Java Edition (JE) database folders (instance-dir/OUD/db/userRoot). Basedon the folders' combined size, determine how much memory you want to reservefor the DB cache. After determining this value, tune the local DB back-endproperties, db-cache-percent or db-cache-size and other JVM options appropriately. Be careful to allowadditional memory for the server runtime. For example, if you have a singledatabase of 1 Gbyte, which you want to store entirely in memory, thena 2 Gbyte heap with 60% reserved for the DB cache shouldbe sufficient for efficient directory server performance. You can test this setup by preloadingthe database with the local database back end by using the preload-time-limitproperty.

JVM heaps greater than 4 Gbytes require a 64-bit JVM.

DisableExplicitGC
Prevents externalapplications from forcing expensive garbage collections. If you are using jstatd or otherRMI-based applications to monitor Oracle Unified Directory, you should consider using this optionin order to avoid unexpected pauses.
-XX:NewSize=512M
In heavy throughput environments, you should consider usingthis option to increase the size of the JVM young generation. By default,the young generation is quite small, and high throughput scenarios can result ina large amount of generated garbage. This garbage collection, in turn, causes theJVM to inadvertently promote short-lived objects into the old generation.
-XX:+UseConcMarkSweepGC
Selects the CMSgarbage collector. This garbage collector is set for low pause time. It will resultin a Java application that has a lower average throughput, but much shorterCPU-intensive garbage collections. This option is required in environments that have response timeconstraints.
-XX:CMSInitiatingOccupancyFraction=70
Selects the level at which the collection is started. The default value is68%.
-XX:+UseParallelOldGC
Selects the parallel old generational garbage collector. This garbage collectoris set for high throughput. It will maximize the average throughput of the import-ldifutility at the cost of an occasional stop-the-world garbage collection, which is notas critical to imports.
-XX:+PrintGCDetails
Prints the garbage collection time stampsto help with debugging.
-client
Selects client application run-time optimizations.The application will be faster to start and more responsive due to lowercompilation overheads.
-Xms8m
Selects a low initial JVM heap size for an application.
  1. Edit the Java properties file as follows: command-name.java-home=jvm.

    For example, to specify a particular JDK 1.6 for the offline import, editthe line that starts with import-ldif.offline in the java.properties file, as follows: import-ldif.offline.java-home=/usr/jdk1.6.

  2. Run the dsjavaproperties command to apply the property.
  1. Edit the Java properties file as follows: command-name.java-args=arguments.

    For example, to specify that a maximum heap size of 256 Mbytes beused for the online export, edit the line that starts with export-ldif.onlinein the java.properties file, as follows: export-ldif.online.java-args=-Xms256m -Xmx256m.

  2. Run the dsjavaproperties command to apply the property.

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

The standalone AquaLogic User Interaction products are:

  • AquaLogic Interaction Analytics
  • AquaLogic Interaction Automation Server
  • AquaLogic Interaction Collaboration
  • AquaLogic Interaction Document Repository
  • AquaLogic Interaction Notification
  • AquaLogic Interaction PTUpload
  • AquaLogic Interaction Publisher
  • AquaLogic Interaction Studio
  • AquaLogic Interaction Workflow
Add Jvm.cfg For Mac

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 AquaLogic User Interaction product.

  • -Xloggc:<path/filename>

    • 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

    Torrent microsoft office for mac 2011 home and student edition

    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.

Application Servers

Tomcat 4.1.x

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

  1. Edit setenv.bat in the <TOMCAT_HOME>bin directory.
  2. Update the JVM memory switches in the line
  3. Save setenv.bat. Reinstall the Tomcat service.
    4. Note:The setenv.bat parameters are only loaded into the service settings during service creation.

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.

WebLogic 8.1

To update Java options for WebLogic 8.1:

  1. Edit installservice.cmd in <BEA_HOME>/user/projects/domains/<domain name>.
  2. Add JVM memory switches to the line
  3. Reinstall the WebLogic service.
Note:The MEM_ARGS parameter can also be updated in the startup script for the WebLogic domain.

ALUI Standalone Products

Analytics

To update Java options for the Analytics JVM:

  1. Edit wrapper.conf in <PT_HOME>/ptanalytics/<ver>/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/<ver>/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.

Collaboration

To update Java options for the Collaboration JVM:

  1. Edit wrapper.conf in <PT_HOME>/ptcollab/<ver>/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.
  3. Restart the Collaboration service.

Document Repository

To update Java options for the Document Repository JVM:

  1. Edit wrapper.conf in <PT_HOME>/ptdr/<ver>/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/<ver>/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/<ver>/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.

Publisher

To update Java options for the Publisher JVM:

  1. Edit service.conf in <PT_HOME>/ptcs/<ver>/settings/config.
  2. Add a new parameter or modify existing parameters in the section Java Additional Parameters.

    3. For example, locate

    Best free youtube video to mp3 converter for mac. # 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

  3. Restart the Publisher service.
Note:Publisher and Workflow run on the same JVM. Garbage collection logging and memory tunings are for both services.

Studio

To update Java options for the Studio JVM:

  1. Edit wrapper.conf in <PT_HOME>/ptstudio/<ver>/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.

Workflow

Workflow runs on the same JVM as Publisher and does not require seperate tuning.


© BEA Systems