Dynamo’s startup behavior is affected by Dynamo’s CONFIGPATH and 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:
CONFIGPATH: By including additional directories in the CONFIGPATH, you can add further configuration layers beyond the default Dynamo CONFIGPATH. For more information on configuration layers, see Working with Configuration Layers earlier in this chapter.
CLASSPATH: Dynamo’s CLASSPATH includes a
<ATG2007.3dir>/home/locallibdirectory, which you can use for any Java class files you create. Any classes stored in this directory are picked up by Dynamo automatically. For more information, see the Nucleus: Organizing JavaBean Components chapter of the ATG Programming Guide.Note: Dynamo’s CONFIGPATH behavior is different from Java’s CLASSPATH behavior. With CLASSPATH, class files found earlier in the path replace files found later. With CONFIGPATH, properties files are merged, not replaced, and the order of precedence is the opposite of CLASSPATH. Unlike CLASSPATH, Dynamo doesn’t stop with the first matching property it finds in the CONFIGPATH. Instead, it examines the entire CONFIGPATH and uses the last defined value.
Java Arguments: You can set or add to the arguments passed to the Java Virtual Machine by setting the environment variable
JAVA_ARGS.
You can customize the CONFIGPATH, CLASSPATH, and JAVA_ARGS settings, as well as define custom environment variables, by editing the postEnvironment.sh (on UNIX) or postEnvironment.bat (on Windows) file in your <ATG2006.5dir>/home/localconfig or <ATG2006.5dir>/home/servers/<servername>/localconfig directory. See Modifying the Environment Settings Automatically and Modifying the Environment Settings Manually for details. If you create a custom module, you can use the module’s MANIFEST.MF file to specify paths to the module’s resources. For more information, see Modifying Custom Module Resource Settings.
Modifying the Environment Settings Automatically
You can use the Dynamo Administration UI to configure the CONFIGPATH, CLASSPATH, and JAVA_ARGS environment settings. You can also use it to add your own custom environment variables. Dynamo creates a localconfig/postEnvironment file with the settings you specify. Note that you must recreate and redeploy your EAR for the changes to take effect.
To configure the CONFIGPATH and CLASSPATH environment settings through the Dynamo Administration UI, follow these steps:
Open the Dynamo Administration page (
http://hostname:port, by default) and click Configuration Manager.Click on the name of the server you want to configure. The configuration page for that server appears.
In the Configure Dynamo Services section, click on System Paths.
Configure the desired environment settings as follows:
CLASSPATH: Under the heading “Add your classes to Dynamo’s Java CLASSPATH,” locate the “Extend Dynamo’s CLASSPATH” section. In the New classpath value box, enter the full path to the directories to search for Java class files. Click on the Append to CLASSPATH button.
CONFIGPATH: Locate the heading “Append to the CONFIGPATH used to find component configurations.” In the New configpath value box, enter the full path to the directories to search for Nucleus components. Click on the Append to CONFIGPATH button.
To append a Java argument to the JAVA_ARGS environment variable, follow these steps:
Access the Configuration Manager as described above and click on the name of the server you want to configure. The configuration page for that server appears.
In the Configure Dynamo Services section, click on Java Arguments.
Enter the new argument and click Append to JAVA_ARGS.
To add custom environment variables, follow these steps:
Access the Configuration Manager as described above and click on the name of the server you want to configure. The configuration page for that server appears.
In the Configure Dynamo Services section, click on Environment Variables.
Enter a name and value for the new variable, and then click Add.
Modifying the Environment Settings Manually
To configure the CONFIGPATH, CLASSPATH, and JAVA_ARGS environment settings manually, do the following:
Open the
postEnvironment(.bat|.sh)in your<ATG2007.3dir>/home/localconfigdirectory.Modify the desired environment settings, as follows:
CLASSPATH: Use the following syntax:
On Windows:
set CLASSPATH=%CLASSPATH%;ClassFileDirOn UNIX:
CLASSPATH="${CLASSPATH}:ClassFileDir"export CLASSPATH
ForClassFileDir, enter the full path to the directories to search for Java class files.CONFIGPATH: Use the following syntax:
On Windows:
set CONFIGPATH=%CONFIGPATH%;ComponentDirOn UNIX:
CONFIGPATH="${CONFIGPATH}:ComponentDir"export CONFIGPATHFor
ComponentDir, enter the full path to the directories to search for Nucleus components.Java Arguments: Use the following syntax:
On Windows:
set JAVA_ARGS=%JAVA_ARGS%JavaArgumentOn UNIX:
JAVA_ARGS="${JAVA_ARGS}JavaArgument"export JAVA_ARGSFor
JavaArgument, enter the Java argument to pass to the JVM.
The following table lists some common values for JAVA_ARGS:
Java Argument | Description |
|---|---|
| Gives the path to the Java 2 security policy file ( |
| 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 |
| Turns off the JIT compiler so that stack traces include full line number information |
| Minimum size of memory heap for Java Virtual Machine on startup |
| Maximum size of memory heap for Java Virtual Machine |
| Prevents garbage collection of classes |
| Enables verbose output about each class loaded, garbage collection, or Java Native Interface (JNI) messages |
By default, Dynamo sets the following JAVA_ARGS parameters in dynamoEnv.sh/.bat:
-Xms256m -Xmx384m
If you manually set JAVA_ARGS parameters as system variables, Dynamo does not set any JAVA_ARGS parameters in dynamoEnv.sh/.bat.
For more information about arguments you can use with the java command, enter the command java -help.
Example postEnvironment.bat for Windows:
set CONFIGPATH=%CONFIGPATH%;c:\myConfigDir
set CLASSPATH=%CLASSPATH%;c:\myClassDir
set JAVA_ARGS=%JAVA_ARGS%-Djava.compiler=NONE
Example postEnvironment.sh for UNIX:
CONFIGPATH="${CONFIGPATH}:/myConfigDir"
export CONFIGPATH
CLASSPATH="${CLASSPATH}:/myClassDir"
export CLASSPATH
JAVA_ARGS="${JAVA_ARGS} -Djava.compiler=NONE"
export JAVA_ARGSNote: When setting CONFIGPATH and CLASSPATH, be careful to append or prepend your values onto the original value of the environment variable or you will omit directories that Dynamo needs to start properly.
Modifying Custom Module Resource Settings
If you create a custom module, you can use the module’s MANIFEST.MF file to specify paths to the module’s resources, as follows:
ATG-Class-Path: Specify a space-delimited set of paths to module resources that contain classes required by the module. For example:ATG-Class-Path: lib/resources.jar lib/classes.jarDynamo adds the
ATG-Class-Pathvalue to the beginning of the CLASSPATH as each module is processed.ATG-Config-Path: Specify a space-delimited set of paths to module resources that provide Nucleus configuration files needed by the module’s server application components. For example:ATG-Config-Path: config/config.jar config/oca-ldap.jarDynamo adds the
ATG-Config-Pathvalue to the end of the CONFIGPATH.Note: The path names in a module’s
ATG-Class-PathandATG-Config-Pathsettings are relative to the module’s root, not to the<ATG2006.5dir>install directory.
In the MANIFEST.MF file, the ATG-Required attribute specifies which modules start up. ATG-Required ensures that a given module’s manifest is processed after it processes all the modules that the module depends on. For example, if you want to place the config directory for your custom module after the DPS config directories in the CONFIGPATH, configure the attributes as follows:
ATG-Config-Path: config/
ATG-Required: DPS
