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

Configuring JBoss Application Server to support user tokens and WebDAV connections for Workplace XT used with other applications

If you are using Workplace XT with other applications, such as Application Integration, eForms, or Records Manager, you must enable support for user tokens and WebDAV connections. You can verify these settings in the Bootstrap Settings in the Site Preferences.

To configure JBoss Application Server to support user tokens and WebDAV connections:
  1. Stop JBoss Application Server, if it is running.
  2. (For installations with Content Engine at 4.5.x) Copy the authentication-utils.jar file from here:

    install_path/IBM/FileNet/WebClient/WorkplaceXT/authenticationFiles

    to here:

    JBoss_home/server/server_name/lib

  3. (For installations with Content Engine at 4.0.x ) Copy the authentication-utils1.1.2.jar file from here:

    install_path/IBM/FileNet/WebClient/WorkplaceXT/authenticationFiles/1.1.2

    to here:

    JBoss_home/server/server_name/lib

  4. Modify the login-config.xml file.
    Tip: Create a backup of the file before making changes.
    1. On the Workplace XT server, open login-config.xml in JBoss_home/server/server_name/conf for editing.
    2. Add the following xml element (bold below) as the first entry in the FileNet® domain section, and set the flag to "optional":
      <application-policy name="FileNet">
      <authentication>
      <login-module code="com.filenet.ae.authentication.
      loginmodule.UserTokenLoginModule" flag="optional">
      <module-option name="wcmApiConfigPath"><install_path>
      /IBM/FileNet/WebClient/WorkplaceXT/WEB-INF/WcmApiConfig.properties
      </module-option>
      <module-option name="multi-threaded">true</module-option>
      </login-module>
      <login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" 
      flag="required">
      <module-option name="java.naming.provider.url">ldap://copenhagen: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=FileNet,DC=Com</module-option>
      <module-option name="bindCredential">MyPassword</module-option>
      <module-option name="baseCtxDN">DC=FileNet,DC=Com</module-option>
      <module-option name="baseFilter">(cn={0})</module-option>
      <module-option name="rolesCtxDN">DC=FileNet,DC=Com</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>

      On Windows, use double back slash (\\) in place of the forward slash in the wcmApiConfigPath entry, as shown in the following example:

      <module-option name="wcmApiConfigPath"> < install_path >\\IBM\\FileNet\\WebClient\\WorkplaceXT\\WEB-INF\\WcmApiConfig.properties</module-option>

      When deploying as an EAR or WAR file, the wcmApiConfigPath value must be a valid folder path, such as the install location. It cannot point to a folder within the EAR or WAR file.

    3. Save changes to login-config.xml.


Feedback

Last updated: March 2013
wxtip032.htm

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