Before you can use the Workplace XT Web application, you must first configure the application to work with JBoss Application Server.
<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.
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.
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.
JBoss_home/server/server_name/deploy/jbossweb.sar/jsf-libs
<!--
<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>
-->
JBoss_home/server/server_name/tmp/deploy
JBoss_home/server/server_name/work/jboss.web/localhost
When logging is disabled, error messages will still be displayed in the JBoss Application Server console.
<!-- 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"/>
INFO
DEBUG
TRACE
to
ERROR
<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"/>
<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.
<!-- ======================= -->
<!-- Setup the Root category -->
<!-- ======================= -->
<root>
<priority value="ERROR"/>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
</root>
Option | Description |
---|---|
UNIX | ./run.sh |
Windows | run.bat |