After you upgrade the Application Engine server
from version 3.5, you must configure JBoss Application Server to work with Application Engine. You can also configure
changes for optional modes like SSO.
Important: In a highly available
environment, you must configure
Application Engine upgrades
on the application server on all nodes.
To configure JBoss Application Server for Application Engine:
- Stop JBoss Application Server if
it is running.
- Make a backup copy of the run.conf file
and the startup script, depending on your platform:
Option |
Description |
UNIX® |
run.sh |
Windows® |
run.bat |
- Edit the run.conf file Java settings.
- Add a line to specify the path to the JDK provided by JBoss Application Server, as shown in the following
example (Windows): set JAVA_HOME=C:\Program Files\Java\jdk1.5.0_06
Important: If your JDK is different from version 1.5.0,
substitute your version for the one listed above.
- Update the JAVA_OPTS memory settings.
Adjusting
this setting prevents the application server from running out of memory,
a condition in which users would not be able to log in to Workplace.
In the JAVA_OPTS line,
change the -Xms and -Xmx values for your configuration.
Example
(Windows): set JAVA_OPTS=%JAVA_OPTS% -Xms 128m -Xmx 512
m
See your application server vendor's recommendation
for Initial and Maximum heap size values. For IBM specific recommendations,
see the IBM® FileNet® P8 Performance Tuning
Guide.
- (Sun JVM users only) Set the value of
MaxPermSize in JAVA_OPTS to 128m, as follows:
UNIX
JAVA_OPTS=%JAVA_OPTS%
-Xms128m -Xmx512m -XX:MaxPermSize=128m
Windows
set JAVA_OPTS=%JAVA_OPTS%
-Xms128m -Xmx512m -XX:MaxPermSize=128m
This increased
value prevents out of memory errors that can stop JBoss Application Server.
- If your application server uses the IBM
JVM, edit the JAVA_OPTS variable in the run.conf file
immediately after the line in the previous sub-step. This JAVA_OPTS
edit improves performance.
- UNIX
- Find the following line in the run.conf file:
JAVA_OPTS="$JAVA_OPTS
and
change it to this (without a carriage return):
JAVA_OPTS="$JAVA_OPTS
-Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
- Windows
- Find the following line in the run.conf file:
set
JAVA_OPTS=%JAVA_OPTS%
and change it to this (without
a carriage return):
set JAVA_OPTS=%JAVA_OPTS% -Dfilenet.pe.peorb.pool.min=2
-Dfilenet.pe.peorb.pool.max=5
- Save your edits.
- Configure JAAS login.
Add
one of the following right after the "$JAVA" $JAVA_OPTS (UNIX) or
"%JAVA%" %JAVA_OPTS (Windows) entry in the run.sh file
for UNIX or the run.bat for Windows.
Important: Enter the jaas_login entry as a single line without
line breaks. Do not copy and paste the text from this guide because
hidden formatting can cause problems with the entry. Instead, type
the entry into the script.
Tip: Your
path might be slightly different depending on the version of your
client installations, or whether you have chosen a custom path for
installation. Verify the location of the file before you enter the
path.
- UNIX
"$JAVA" $JAVA_OPTS
-Djava.security.auth.login.config=
"/opt/FileNet/AE/CE_API/config/jaas.conf.JBoss"
"-Djava.endorsed.dirs=$JBOSS_ENDORSED_DIRS" -classpath
"$JBOSS_CLASSPATH" org.jboss.Main $@
- Windows
"%JAVA%" %JAVA_OPTS%
"-Djava.security.auth.login.config=C:\Program
Files\FileNet\AE\CE_API\config\jaas.conf.JBoss"
"-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%" -classpath
"%JBOSS_CLASSPATH%" org.jboss.Main %*
- Save and close the run.sh file
or the run.bat file.
- Configure LDAP settings on Application Engine to exactly match the Content Engine settings.
- On the Application Engine server,
open login-config.xml , located in JBoss_home/server/server_name/conf,
for editing.
- Set the <application-policy name="FileNet"> entry
identical to the corresponding entry in the login-config.xml file
on the Content Engine server.
- Set the <application-policy name="FileNetP8Engine"> entry
identical to the corresponding entry in the login-config.xml file
on the Content Engine server.
- Copy the new <application-policy name="FileNetP8Engine"> entry,
and paste the copied entry directly above entry you copied (<application-policy
name="FileNetP8Engine">).
- Change the first instance of the <application-policy
name="FileNetP8Engine"> to <application-policy
name="FileNetP8">.
- Save changes to the login-config.xml file
on the Application Engine server.
- Restart JBoss Application Server.
- Set permissions for the user running the application server.
On Windows, the following is only
required for NTFS formatted partitions.
If the user that
will be running the application server is different from the user
that installed Application Engine,
you must give the user read and write permissions on the folder where
you installed Application Engine (AE_install_path).
- (Optional) Disable JBoss Application Server logging.
In development mode, JBoss Application Server creates
a large number of HTTP Access, "INFO", "DEBUG" and "TRACE" log messages.
This can cause unexpected behavior in the deployed IBM FileNet software.
Using the following procedure, you can limit this type of excessive JBoss Application Server logging.
When
logging is disabled, error messages will still be displayed in the JBoss Application Server console.
- Open the log4j.xml file (JBOSS_home/server/server_name/conf/log4j.xml)
for editing.
- Change all threshold values and priority values from
"INFO", "DEBUG", or "TRACE" to "ERROR".
- Delete or comment out the "Preserve messages in a local
file" to turn off the server log.
- To turn off HTTP access logging, open jboss-service.xml with
a text editor and delete or comment out the "Access logger" section.
Location of jboss-service.xml:
JBoss_Home/server/server_name/deploy/jbossweb-tomcat55.sar/META-INF
- Open web.xml for editing and change
the logVerbosityLevel to "FATAL".
Location of web.xml:
JBoss_Home/server/server_name/deploy/jbossweb-tomcat55.sar/conf
- Restart the JBoss Application Server server.