The Oracle Commerce Platform’s startup behavior is affected by its CLASSPATH, the Java arguments passed to the Java Virtual Machine, and any custom environment variables you define. You can modify the startup behavior of these parameters as follows:

To customize the CLASSPATH and JAVA_ARGS settings, as well as define custom environment variables, see your application server documentation.

The following table lists some common values for JAVA_ARGS:

Java Argument

Description

-Djava.rmi.server.hostname=
IP_Address

Configures Java Remote Method Invocation (RMI) to export RMI objects on a particular IP address; for more information, see Starting the ATG Control Center in the Running Nucleus-Based Applications chapter

-Djava.compiler=NONE

Turns off the just-in-time compiler so that stack traces include full line number information

-Xmssize

Minimum size of memory heap for Java Virtual Machine on startup

-Xmxsize

Maximum size of memory heap for Java Virtual Machine

-Xnoclassgc

Prevents garbage collection of classes

-verbose[:class|gc|jni]

Enables verbose output about each class loaded, garbage collection, or Java Native Interface (JNI) messages

-Duser.country=country
-Duser.language=
language
–Duser.region=
region

This allows you to set the Java Virtual Machine locale, which is used by the Locale.getDefault method to set the region. This setting allows you to configure your installation for localization by specifying the region and language used by the JVM. The following example sets the JVM locale to Russian:
-Duser.country=RU –Duser.language=ru
–Duser.region=RU

For more information about arguments you can use with the java command, enter the command java -help.

Note: When setting CLASSPATH be careful to append or prepend your values onto the original value of the environment variable rather than replace it, or you will omit directories that the Oracle Commerce Platform needs to start properly.


Copyright © 1997, 2015 Oracle and/or its affiliates. All rights reserved. Legal Notices