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

Configuring JBoss Application Server for Workplace XT

Before you can use the Workplace XT Web application, you must first configure the application to work with JBoss Application Server.

To configure JBoss Application Server:
  1. Stop JBoss Application Server, if it is running.
  2. Configure LDAP settings on the Workplace XT server to exactly match the Content Engine settings.
    Tip: Create a backup of the login-config.xml file before making changes.
    1. On the Workplace XT server, open login-config.xml, located in JBoss_home/server/server_name/conf, for editing.
    2. Add an identical <application-policy name="FileNet"> entry to match the corresponding entry in the login-config.xml file on the Content Engine server. This should be added at the end of the file before the final </policy> line.
      <authentication>
      <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" 
      flag="required"/>
      </authentication>
      </application-policy>
      <application-policy name="FileNet">
      <authentication>
      <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" 
      flag="sufficient">
      <module-option name="java.naming.provider.url">ldap://cm-nihuevm9:389
      </module-option>
      <module-option name="java.naming.security.authentication">simple
      </module-option>
      <module-option name="allowEmptyPasswords">false</module-option>
      <module-option name="bindDN">cn=ceadmin,ou=shared,ou=engineering,
      ou=filenet,dc=apple</module-option>
      <module-option name="bindCredential">Password1</module-option>
      <module-option name="baseCtxDN">dc=apple</module-option>
      <module-option name="baseFilter">(cn={0})</module-option>
      <module-option name="rolesCtxDN">dc=apple</module-option>
      <module-option name="roleFilter">(cn={0})</module-option>
      <module-option name="roleAttributeID">memberOf</module-option>
      <module-option name="roleAttributeIsDN">true</module-option>
      <module-option name="roleRecursion">-1</module-option>
      </login-module>
      </authentication>
      </application-policy>
      </policy>

    You can copy this entry from the Content Engine login-config.xml file. If you have no custom entries in the file on your Workplace XT server, you can copy the entire file from the Content Engine, and overwrite the login-config.xml file on the Workplace XT server.

  3. Set permissions for the user running the application server.

    If the user who will be running the application server is different from the user that installed Workplace XT, you must give the user read/write permissions on the following folder:

    install_path/IBM/FileNet/WebClient

    For Windows, this is only required for NTFS formatted partitions.

  4. (JBoss Application Server 5.0.1 only) Remove the JSF 1.2 that is part of the JBoss Application Server 5.0.1 installation.

    Removing the files and the references to the files in the web.xml file enables JBoss Application Server to use the JSF 1.1 provided by Workplace XT.

    1. Delete all jar files found under the jsf-libs folder of the web server, but do not delete the jsf-libs folder:

      JBoss_home/server/server_name/deploy/jbossweb.sar/jsf-libs

    2. Open the web.xml file (JBoss_home/server/default/deployers/jbossweb.deployer/web.xml) for editing.
    3. Modify the web.xml file to comment out the references to the JSF 1.2 implementation, as shown in the following sample.
      <!--
      <context-param>
      <param-name>com.sun.faces.injectionProvider</param-name>
      <param-value>org.jboss.web.jsf.integration.injection.
      JBossDelegatingInjectionProvider</param-value>
      </context-param>
       -->
      <!--
      <listener>
      <listener-class>org.jboss.web.jsf.integration.config.
      JBossJSFConfigureListener</listener-class>
      </listener>
      -->
      
      <!--
      <listener>
      <listener-class>com.sun.faces.application.WebappLifecycleListener
      </listener-class>
      </listener>
       -->
      
       <!--
      <init-param>
      <description>JSF standard tlds</description>
       <param-name>tagLibJar0</param-name>
      <param-value>jsf-libs/jsf-impl.jar</param-value>
      </init-param>
      <init-param>
      <description>JSTL standard tlds</description>
      <param-name>tagLibJar1</param-name>
      <param-value>jstl.jar</param-value>
      </init-param>
       -->
  5. Clear out all files and folders within the following temp directories:

    JBoss_home/server/server_name/tmp/deploy

    JBoss_home/server/server_name/work/jboss.web/localhost

  6. Disable JBoss Application Server logging to prevent unexpected behavior in the deployed IBM® FileNet® software.

    When logging is disabled, error messages will still be displayed in the JBoss Application Server console.

    1. Open the log4j.xml or jboss-log4j.xml file (JBoss_home/server/server_name/conf/log4j.xml) for editing.
    2. Add the following line (in bold) for the FILE appender, under the Preserve messages in a local file section:
      <!-- A time/date based rolling appender -->
      <appender name="FILE" class= "org.jboss.logging.appender.
      DailyRollingFileAppender">
      <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
      <param name="File" value="${jboss.server.log.dir}/server.log"/>
      <param name="Append" value="false"/>
      <param name="Threshold" value="ERROR"/>
    3. Change all threshold values and priority values from

      INFO

      DEBUG

      TRACE

      to

      ERROR

      except for the CONSOLE appender threshold value, which should be set to INFO, as shown in bold below:
      <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
      <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
      <param name="Target" value="System.out"/>
      <param name="Threshold" value="INFO"/>
    4. Add IBM FileNet-specific categories to avoid excessive tracing messages in the console, which can impact performance. Add the following at the end of the Limit categories section, just before the Setup the Root category section:
      <category name="filenet_error.api">
      <priority value="ERROR"/>
      </category>
      <category name="filenet_tracing.api">
      <priority value="OFF"/>
      </category>
      
      <category name="com.filenet.wcm.api">
      <priority value="ERROR"/>
      </category>
      
      <category name="com.filenet-trace">
      <priority value="OFF"/>
      </category>
      
      <category name="com.filenet-debug">
      <priority value="ERROR"/>
      </category>

      If other IBM FileNet-specific tracing message in the command console affect performance, add additional categories for those messages.

    5. Remove the Root category priority value, if any, as shown in bold below:
      <!-- ======================= -->
      <!-- Setup the Root category -->
      <!-- ======================= -->
      <root>
      <priority value="ERROR"/>
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
      </root>
    6. Save and close the log4j.xml file.
  7. Optional: Start JBoss Application Server as follows, to verify that configuration changes were successful:
    Option Description
    UNIX ./run.sh
    Windows run.bat


Feedback

Last updated: March 2013
wxtip031.htm

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