Configuring JBoss Application Server for Content Platform Engine

JBoss Application Server requires some configurations before you install Content Platform Engine.

Note: JBoss Application Server clusters do not use a separate administrative server, and configuration changes are implemented on each cluster node separately in a highly available environment.

To prepare the web application server:

1. Navigate to the configuration file set directory.

   Option	Description
   Standard deployment	jboss_install_dir/server
   Cluster deployment (required for high availability)	jboss_install_dir/all

2. Create a new configuration file set by copying the configuration file set to a new directory. For JBoss Application Server 5.0.0 and higher, the configuration file set is the standard subdirectory. For JBoss Application Server versions less than 5.0.0, the configuration file set is the default directory.

   Option	Description
   Standard deployment	Copy the configuration file set to a new directory within the /server directory. For example, copy the files to jboss_install_dir/server/server1.
   Cluster deployment	Copy the configuration file set to a new directory within the /all directory. For example, copy the files to jboss_install_dir/all/server1.

   jboss_install_dir is the directory where JBoss is installed.
3. 
   Record application server values in your customized Installation and Upgrade Worksheet. To find these properties, use the Autofilter drop-down arrow in Column E, Installation or Configuration Program, to select CM: Create New Installation Profile. Then use the Autofilter drop-down arrow in Column D, ISV Component Vendor, to select JBoss.
4. In the jboss_install_dir/bin directory, edit the configuration file run.conf (AIX®, HPUX, and Linux), run.bat (Windows and JBoss 5.0), or run.conf.bat (Windows and JBoss 5.1):
   1. Add a line to specify the path to the JAVA Development Kit (JDK) on the machine where JBoss Application Server is installed, as shown in the following example:

      JAVA_HOME="path_to_Java_JDK"

   2. In the JAVA_OPTS line, change the -Xms and -Xmx values from -Xms128m -Xmx512m to -Xms512m -Xmx1024m.
   3. Save your edits.
   
5. (JBoss 4.3.0 EAP on Windows) Edit the hotspot line in the startup script file:
   1. Open the startup script file jboss_install_dir\bin\run.bat.
   2. Find the hotspot line in the file:

      "%JAVA%"  -version 2>&1 | findstr /I hotspot > nul

   3. Replace the hotspot line with the following line:

       "%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul

   4. Save your edit.
6. Refer to theIBM FileNet P8 system requirements for information on the JDBC driver file for the database type that you need for the GCD or for an object store you will be creating later.
7. Install JDBC drivers on the JBoss Application Server machine, as follows:
   1. Obtain the JDBC drivers, depending on your database type.

      DB2®

      Find the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the IBM® Web site by searching for JDBC Type 4.

      Microsoft SQL Server

      Find the version of Microsoft JDBC Driver at Microsoft Support that matches the version of the JDK on the JBoss Application Server machine.

      Oracle

      Access the Oracle JDBC Driver Downloads Web site and find the JDBC driver file that matches the version of the JDK on the JBoss Application Server machine.

   2. Place the file JDBC driver file in the CLASSPATH.

      Standard deployment

      Copy the JDBC driver file to the jboss_install_dir/server/server1/lib directory.

      Cluster deployment

      Copy the JDBC driver file to the jboss_install_dir/all/server1/lib directory.

8. If you are deploying multiple instances of Content Platform Engine on the same server, do the following for each additional instance:
   1. Copy the configuration file set that you just created and modified from the jboss_install_dir/server/server1 directory to a new directory. Use a separate directory for each instance. For example, copy the jboss_install_dir/server/server1 directory to jboss_install_dir/server/server2 and jboss_install_dir/server/server3.
   2. Assign unique port numbers to each instance. Refer to your JBoss Application Server documentation for details.
9. If it is not already running, start the web application server as follows, and leave the command window open:

   Option	Description
   AIX, HPUX, Linux, Solaris, and JBoss 5.0 and 5.1	./run.sh -c server1 -b 0.0.0.0
   Windows and JBoss 5.0	run.bat -c server1 -b 0.0.0.0
   Windows and JBoss 5.1	run.conf.bat -c server -b 0.0.0.0