The AFP Viewer plug-in and the Java™ line data viewer allow users to view AFP and line data documents, respectively, from IBM® Content Manager OnDemand™. Note that users cannot download AFP and line data documents directly from Workplace XT. In addition, you can customize the MIME types to allow users to view various documents with different viewers.
You can configure the trace logging settings that are used by the Content Manager OnDemand Java API. Use the logging levels to analyze application activity as well as diagnose and solve problems.
To install the viewers on the Workplace XT server
<listener>
<listener-class>com.filenet.ae.cmodviewer.ViewerServlet</listener-class>
</listener>
<servlet>
<servlet-name>cmodViewer</servlet-name>
<servlet-class>com.filenet.ae.cmodviewer.ViewerServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>cmodViewerCallback</servlet-name>
<servlet-class>com.filenet.ae.cmodviewer.ViewerCallbackServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>cmodViewer</servlet-name>
<url-pattern>/cmodViewer/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>cmodViewerCallback</servlet-name>
<url-pattern>/cmodViewerCallback/*</url-pattern>
</servlet-mapping>
To use the AFP Web Viewer on a Workplace XT client
Before users can view AFP and line data documents from a Content Manager OnDemand server you must specify the name and password of the user account used to authenticate with the server in the IBM Content Manager OnDemand site preference. See General settings for IBM Content Manager OnDemand for more information.
NOTE The user name and password that is defined for the IBM Content Manager OnDemand site preference is stored in a key store. The default path for the key store is located in <XT_install_path>\WorkplaceXT\WEB-INF\cmodKeyStore. You can change the key store location using the keyStorePath context parameter in the Servlet descriptor (web.xml) file.
Users must install the AFP Viewer plug-in on their local machine before they can view AFP documents. The AFP Viewer plug-in installation program is called afpplgin.exe, and is located in the plugins subfolder where you installed ODWEK. For more information about installing the AFP Viewer plug-in, see Installation in the IBM Content Manager OnDemand Information Center.
You can use the OnDemand Web Enablement Kit to map MIME types, where each MIME type corresponds to a document type that users view. Modify and add MIME types to the cmodMimeMappings.properties file. This file is located in the configuration folder that is defined when the Workplace XT application is installed.
When you add new MIME types to the cmodMimeMappings.properties file, you must restart the application server.
Use a text editor to edit the Servlet descriptor (web.xml) file in the folder where the Workplace XT application is installed. You configure the trace logging settings in this file. To change the defaults, open web.xml, modify as necessary, and save the file. Redeploy the application after making your changes. Refer to "Task 7a-c: Deploy IBM FileNet Workplace XT" in the IBM FileNet Workplace XT Installation and Upgrade Guide for more information.
The following lines are examples of the text you would add to web.xml to configure trace logging.
<context-param>
<param-name>traceLevel</param-name>
<param-value>1</param-value>
</context-param>
<context-param>
<param-name>traceDir</param-name>
<param-value>your_path</param-value>
</context-param>
NOTE The variable your_path is the location you define. An example of the format for the location is:
Windows: c:\\tempdir\\your_path
UNIX: c:/temp/your_path
The trace logging level you specify determines the type and amount of information collected. The level you specify determines the amount of information collected. A direct correlation exists between the amount of information collected and the performance impact on the system.
The following table briefly describes the levels.
Level | Description |
---|---|
0 |
No errors are logged. |
1 |
Only ERROR messages are logged. |
2 |
WARNING and ERROR messages are logged. |
3 |
INFO messages are logged along with WARNING and ERROR messages. |
4 |
A FULL TRACE is performed and all messages are logged including the function trace. |