FileNet P8 Workplace XT, Version 1.1.5       Application server:  JBOSS Application Server   Operating systems:  Windows

Configuring Java and JAAS settings for Windows

You can use settings in the JBoss Application Server on Windows 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 startup script, run.bat.
  3. Open the run.bat startup script 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:
      set JAVA_HOME=C:\Program
      Files\Java\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.

      set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m

      Refer to 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.bat file immediately after the line in the previous substep. This JAVA_OPTS edit improves performance.

      Find the following line in the run.bat file:

      set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%

      and change it to this (without a carriage return):

      set 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 edits.
  5. Configure JAAS login.

    Add the following JAAS login entry right after the "%JAVA%" %JAVA_OPTS entry in the run.bat file.

    Important: Enter the JAAS login entry (bold below) 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.

    Your path 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, 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.

    "%JAVA%" %JAVA_OPTS% -Djava.security.auth.login.config= install_path \IBM\ FileNet\WebClient\CE_API\config\jaas.conf.JBoss "-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%" -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*

  6. Save and close the run.bat application server startup script.


Feedback

Last updated: March 2013
wxtip030.htm

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