After installing JBoss, modify the JVM arguments. Go to <JBdir>/bin/run.conf|bat and edit the JAVA_OPTS line. The following are recommended settings:

JAVA_OPTS="-server -Xms2048m -Xmx3072m -XX:MaxPermSize=768m
-XX:MaxNewSize=768m -Dsun.rmi.dgc.server.gcInterval=3600000 –
Dsun.rmi.client.gcInterval=3600000"

If you are setting up a JBoss instance that is dedicated to lock management, you can run that instance with a smaller heap size, since the lock manager does not serve pages. To do this, create a new run.bat|sh file referring to a new run.conf file.

Duplicate the run.bat|sh and run.conf files and rename the duplicates (for example, runLockMan.sh and runLockMan.conf). In the runLockMan.bat|sh file, change the following section to point to the new configuration file:

# Read an optional running configuration file
if [ "x$RUN_CONF" = "x" ]; then
    RUN_CONF="$DIRNAME/runLockMan.conf"
fi
if [ -r "$RUN_CONF" ]; then
    . "$RUN_CONF"
fi

The runLockMan.conf file should include the following settings:

JAVA_OPTS="-server –Xms512m –Xmx512m -XX:MaxPermSize=128m
-XX:MaxNewSize=128m
-Dsun.rmi.dgc.server.gcInterval=3600000"

Note: The Configuration and Installation Manager (CIM) utility makes these configurations for you. See Configuration and Installation Manager (CIM).

Using ACC Scenarios in JBoss

In order to create scenarios in the ATG Control Center (ACC), you must add the following three JAR files to your class path:

<JBdir>/common/lib/jboss-javaee.jar
<JBdir>/common/lib/jsp-api.jar
<JBdir>/common/lib/servlet-api.jar

To do this, copy the files into the /lib directory of your standalone ACC installation, then modify the bin/startClient.bat file to include the three JARs in the class path.

Disabling Session ID Checking in JBoss

If you are using JBoss on UNIX and expect to run multiple Oracle ATG Web Commerce servers within a single JBoss instance (as may be the case during development or demonstrations), edit the JBoss run.conf script by adding the following line to the end of the file:

JAVA_OPTS="${JAVA_OPTS} -Dorg.apache.catalina.connector.Request
.SESSION_ID_CHECK=false"

This allows your browser to use a single jsessionid cookie for both instances, avoiding unnecessary errors.


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