FileNet P8 Workplace XT, Version 1.1.5       Application server:  JBOSS Application Server   Operating systems:  AIX, HP-UX, Linux, Linux on System z, Solaris

Configuring Java and JAAS settings for UNIX

You can use settings in the JBoss Application Server on UNIX to set up JAVA and memory settings, and JAAS login information for authentication for your Workplace XT Web application.

To configure Java™ and JAAS settings:
  1. Stop JBoss Application Server, if it is running.
  2. Make a backup copy of the JBoss Application Server configuration file run.conf.
  3. Open run.conf for editing.
  4. Edit the Java settings.
    1. Add a line to specify the path to the JDK on the machine where JBoss Application Server is installed, as shown in the following example:
      JAVA_HOME=/export/home/apps/jboss/jdk1.5.0_06

      If your JDK 1.5.0 version is different, substitute your version for the one listed above (_06).

    2. 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 XT.

      In the first JAVA_OPTS entry, as per the examples below, change the -Xms and -Xmx values for your configuration.

      JAVA_OPTS=$JAVA_OPTS -Xms128m -Xmx512m

      See your application server vendor recommendation for Initial and Maximum heap size values. For IBM® specific recommendations, see the IBM FileNet P8 Performance Tuning Guide.

    3. 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 substep. This JAVA_OPTS edit improves performance.
      Find the following line in the run.conf file:
      JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME"
      and change it to this (without a carriage return):
      JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
    4. For high availability environments, configure JNDI lookup to connect to Content Engine and allow failover.
      On each node, edit the run.bat or run.sh file to include the following, entered as a single line:
      -DFileNet.EJB.ContextProperties=java.naming.factory.initial=
      org.jboss.naming.NamingContextFactory
    5. Save your changes.
  5. Configure JAAS login by adding an entry to the run.conf file.

    The path for your entry might be slightly different depending on the version of your client installations, or whether you have chosen a custom path for installation. For example, if your Content Engine Client is at 4.0.x, this path might include a samples directory under the config directory. Verify the location of the jaas.conf.JBoss file before you enter the path.

    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.
    Add this entry to the end of the run.conf file, modifying the path to the jaas.conf.JBoss file for your system if necessary:
     JAVA_OPTS="$JAVA_OPTS -Djava.security.auth.login.config=/opt/IBM/FileNet/WebClient/CE_API/config/jaas.conf.JBoss"
  6. Save and close the run.conf file.


Feedback

Last updated: March 2013
wxtip029.htm

© Copyright IBM Corporation 2013.
This information center is powered by Eclipse technology. (http://www.eclipse.org)