Note: When you install JBoss, do not use the installer download; using that version results in errors. Instead, use the .zip file download.

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

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

If you are setting up a JBoss instance that will be 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, ATG recommends creating 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, 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
if [ -r "$RUN_CONF" ]; then
    . "$RUN_CONF"

The runLockMan.conf file should include the following settings:

JAVA_OPTS="-server –Xms512m –Xmx512m -XX:MaxPermSize=128m

In order to create scenarios in the ATG Control Center (ACC), you must add the <JBdir>/client/jbossall-client.jar file to your class path. To do this, copy jbossall-client.jar into the /lib directory of your standalone ACC installation, then modify the bin/startClient.bat file to include jbossall-client.jar in the class path.

loading table of contents...