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 (run.bat on Windows) and edit the JAVA_OPTS line. ATG suggests the following settings:
JAVA_OPTS="-server –Xms512m –Xmx1152m -XX:MaxPermSize=256m
-XX:MaxNewSize=256m
-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 lockManager does not serve pages. To do this, you will need to create a new run.sh file referring to a new run.conf file.
Duplicate the run.sh and run.conf files and rename the duplicates (for example, runLM.sh and LMrun.conf). In the runLM.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/LMrun.conf"
fi
if [ -r "$RUN_CONF" ]; then
. "$RUN_CONF"
fi
The LMrun.conf file should include the following settings:
JAVA_OPTS="-server –Xms512m –Xmx512m -XX:MaxPermSize=128m
-XX:MaxNewSize=128m
-Dsun.rmi.dgc.server.gcInterval=3600000"
In order to create scenarios in the ACC, you must add the <JBossDir>/client/jbossall-client.jar file to your class path. To do this, you can copy jbossall-client.jar into the /lib directory of a Dynamo module, then edit the MANIFEST.MF file of that module to indicate that jbossall-client.jar should be downloaded to the ACC. For example, add the following lines to <ATG2007.3dir>/DAS/lib/MANIFEST.MF:
Name: lib/jbossall-client.jar
Digest-Algorithms: SHA MD5
ATG-Client-Update-File: true
SHA-Digest: LAM3QLj3jBCBryXAFz/FcxfSeDo=
MD5-Digest: 5GT8fI3wZI7n99U0cN4COw==
Another option is to 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.
