3. IBM FileNet P8

3.1. Preamble

ARender 4.0 and up uses only a REST API (http) to communicate with its rendition server.

If your Websphere server does not possess the API level 2.0 (minimum) of JAX-RS, follow this procedure:

De-activate the embedded JAX-RS engine by setting a JVM property (com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true). You can set this property using the Websphere Web Admin console on the following path :

Servers > WebSphere Application Servers > yourServerName.

Then, in Server Infrastructure section:

Java and Process Management > Process definition > Java Virtual Machine > Custom properties.

Set com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine for the name, true for the value. Description can be set to your preference.

One final step will be to configure the class loader for the ARender war/ear component in PARENT_LAST, following this procedure:

Go to the deployed ARender application > Manage Modules > ARender war. Class loader order : Classes loaded with local class loader first (parent last). Go to the deployed ARender application > Class loader. Class loader order : Classes loaded with local class loader first (parent last).

Once the configuration is done, restart the web server containing ARender.

3.2. The connectors

Connectors for FileNet P8 4.x and 5.x are provided. However, a unique configuration is required regardless version.

Parameter Description
id Unique id of document version
vsId VersionSeries id allowing to fetch last version of a document
objectStoreName The name of the ObjectStore used to store the document
objectType Document type: document, folder, containerXML, mixedObjects (optional for documents)
  • Examples:

    Open a document stored in FileNet P8

3.3. Define the connector

As detailed below, the connector is composed of two parts. First one is designed for the access of an ObjectStore and its documents. Second one is responsible to manage metadata fetching.

<bean id="fileNetUrlParser" class="com.arondor.viewer.filenetce.FileNetURLParser">
    <property name="objectStoreProvider">
        <ref bean="objectStoreProvider" />
    <property name="documentPropertiesConfiguration">
        <ref bean="documentPropertiesConfiguration" />
  • Définition :

Add following lines to registeredURLParsers property of servletDocumentService bean:

<ref bean=”fileNetURLParser”/>

3.4. Document access

Regarding authentication mode, two provider types can be used to provide document access.

3.4.1. Sharing FileNet session

In the same JVM (or at least in a shared JAAS context) using IIOP protocol:

Parameter Description
ceConnectionUri URI of Content Engine using the IIOP protocol
  • Example

    <bean id="objectStoreProvider" class="com.arondor.viewer.filenetce.helper.impl.JaasObjectStoreProvider">
        <property name="ceConnectionUri" value="iiop://localhost:2809/FileNet/Engine"/>

Nota: It implies that a FileNet session has been previously instanciated.

3.4.2. Technical account

Otherwise, FileNet web services can be consumed using :

Parameter Description
ceConnectionUri URI of Content Engine based on FileNet WS (MTOM ou DIME)
login Username of technical account
password Password of technical account
  • Example

    <bean id="objectStoreProvider" class="com.arondor.viewer.filenetce.helper.impl.LoginPasswordObjectStoreProvider">
     <property name="login" value="{p8_identifiant}"/>
     <property name="password" value="{p8_password}"/>
     <property name="ceConnectionUri" value="http://{content_engine_server}/wsi/FNCEWS40MTOM/"/>

Nota : This access type implies that user is not authenticated at application loading. So, security constraints must be disabled in web.xml configuration file.

3.5. Configuration the annotation format to be saved in FileNet

3.5.1. Save annotations as XML FileNet format

Default configuration, nothing to do here.

3.5.2. Save annotation as XFDF

Simply add the below ligne the the following file: arender-server-custom-filenet.properties (located in WEB-INF\classes)


3.6. Metadata fetching

<bean id="documentPropertiesConfiguration" class="com.arondor.viewer.filenetce.config.DocumentPropertiesConfiguration">

3.6.1. Include system metadata

By default, no system metadata is fetched. In order to force it, you need to add/edit includedSystemProperties property.

  • Example

    <property name="includedSystemProperties">

3.6.2. Exclude custom metadata

By default, all custom metadata are fetched and displayed. In order to force exclusion of some ones, you need to add/edit excludedCustomProperties property


<property name="excludedCustomProperties">

Nota : If the following error appears: No LoginModules configured for FilenetP8WSI, an additional configuration is required:

  • Save the file jaas.conf.WebSphere in a folder on the WAS server

  • Add a parameter to ARender’s JVM:

    • Navigate to the menu Server and select the related server. Then open Java and Process Management and click on Process Definition. In Start command arguments add the following argument: -Djava.security.auth.login.config=[Chemin_vers_fichier_jaas.conf.WebSphere]

3.7. From an user interface

3.7.1. IBM Workplace & Workplace XT

In order to define which document types have to be opened within ARender, you need to edit the configuration file content-redir.properties (for Workplace XT, in folder: C:Program FilesFileNetConfigWebClient) as follow:


3.7.2. IBM Content Navigator

A specific plugin has been implemented to integrate ARender within ICN. Nota: ICN connector uses mixedObjects syntax.

Connect to Content Navigator.

Go to the ‘Administration View’ and click on ‘Plug-ins’


Click on the button “New Plugin-in”.


Enter the JAR file path and click on ‘Load’.

Example: C:\sources\ARenderHMI\arondor-arender-navigator-plugin-2.2.1.jar


Fill ‘ARender context root’ field with ARender’s address (hots + port + context root). Like below:


If you want the plugin to automatically detect the host name and replace it in the configuration when called, use the keyword --arender.hostname--.

Click on the ‘Save’ button.

Click on Edit and check that the plugin is correctly installed.


Map the new viewer. Go to ‘Viewer Maps’


The default map is called ‘Default viewer map’ and is not editable. Click on it and then click on copy.


Click on “New Mapping”. Then select ‘Filenet Context Manager’ for the Repository type. Then select ARenderPluginViewer in the list of viewer available.


You can now choose the MIME Types you want to open with ARender, then click on OK.


To use this Map, you just need to link it to a Desktop (Desktop tab -> Edit the desktop -> Select the Map in the Viewer Map list)