2.10. HMI server deployment

2.10.1. Jetty deployment

  • Get “jetty-runner-{VERSION-NUMBER}.jar”
  • Get “arondor-arender-hmi-{VERSION-NUMBER}.war”
  • Move those files to a folder (example : “C:\ARender”)

Once files have been stored:

  • Open the console and type:

    cd C:\ARender

By default, the file to modify is:

  • To launch jetty server, in a console, type the following command:

    java -jar jetty-runner-{VERSION-NUMBER}.jar arondor-arender-hmi-{VERSION-NUMBER}.war

2.10.2. Webpshere deployment Websphere console

  • Go in tab “Applications”, then click on “Enterprise applications”
  • To launch installation, click on “Install”
  • Choose the EAR path to deploy and click on “Next”
  • To accept default parameters, click on “Next”
  • Select webserver(s) and/or server(s) of the Workplace, then click on “Next”
  • To accept the parameters by default (virtual host : default_host), click on “Next”
  • In recap window, click on « Finish » to begin the installation with these parameters after checking them
  • Click on “save” to finish the installation
  • Start “ARender HMI” selecting it and clicking on “Begin”
  • To test if the deployment is OK, load the default document in ARender by typing the following address in your browser:

http://[ARENDER_HOST]:[ARENDER_PORT]/ARender (for example: http://localhost:8080/ARender) Post setup Ordre de chargement des librairies

Websphere must be configured in parent-last which means it has to load its libraries after ARender.

Websphere: version 7.x

  • In the application list click on ARenderHMI
  • Click on “Class loading and update detection”
  • Select “Classes loaded with local class loader first (parent last)”
  • Click on “OK” and save the modifications

Then, for Websphere version above 8:

  • In the application list click on ARenderHMI
  • Click on “Manage Modules”
  • Click on ARender module
  • Select in the drop down list
  • Click on “OK” and save the modifications ARender and IBM Content Navigator (ou encore IBM Content Manager)


IBM prerequisite impose that ICN (or ICM) is deployed in its own JVM. Same for the CPE (source : http://www-01.ibm.com/support/docview.wss?uid=swg27038265&aid=1 ).

ARender HMI also needs to be deployed in its own JVM.

Moreover, ARender JVM LDAP configuration needs to be exactly like the ICN (ou ICM) LDAP configuration

LTPA sharing

Thus, you will need to configure LTPA in order to enable session sharing between IBM Content Navigator and ArenderHMI:

  • Export the LTPA CPE key
  1. In WebSphere Administration Console of the CPE, navigate to Security > Global Security, under Authentication, click LTPA
  1. Specify a password, a filepath, and click “Export keys”
  • Import the LTPA CPE key in the ARender JVM

Copy the key in hte ARenderHMI server.

Then import this key in ARender, like below:

  1. Using the WebSphere Administration Console, navigate to Security > Global Security, under Authentification, click LTPA
  1. Fill in the same password you entered when exporting the keys
  2. Specify the path where you copied the keys
  3. Click Import keys
  4. Save the modifications

ARender cookie name modification

ICN (ou ICM) and ARender are, by default, configured with the same cookie name : JSESSIONID.

So, when a document is opened in ARender the ICN cookie is override by the ARneder cookie and ICN autentication is lost.

Thus, ARender cookie name must be changed:

  1. Using the WebSphere Administration Console, navigate to Enterprise Applications > ARender [VERSION_NUMBER] for FileNet 5.x > Manage Modules > arondor-arender-hmi-filenet-[VERSION_NUMBER].war > Session management > Cookies
  1. Modify default cookie name from JSESSIONID to JESSIONARID
  2. Click on OK and save modifications
  3. Then, navigate to the session management : Applications d’entreprise > ARenderHMI > Gestion des modules > arondor-arender-hmi-filenet-[VERSION ARENDER].war > Gestion de session
  4. And check : Override session management
  1. Click on OK and save modifications.
  2. Restart ARender profile.

2.10.3. Wildfly deployment

To deploy ARender for Filenet in WildFly, you have to configure the Filenet connexion module like below:

  1. Open the WildFly standalone.xml file
  2. Add the security domain: FileNetP8WSI to the existing domains:
<subsystem xmlns="urn:jboss:domain:security:1.2">
       <security-domain name="FileNetP8WSI" cache-type="default">
               <login-module code="com.filenet.api.util.WSILoginModule" flag="required"/>