Installing FileNet P8 5.5

In addition, complete these steps:

1. To access Content Engine Client, Collector Server must know the fully qualified paths to specific JAR files. You specify the paths later when you configure the Collector Server instance. The JAR files are installed together with Content Engine Client.
   Collector Server must have access to these JAR files:

   pe.jar
   peResources.jar
   Jace.jar
   log4j-1.2.17.jar
   

   For more information about these JAR files, go to the IBM® FileNet P8 5.5.x product documentation and search for the following strings:

   • “Required Files for Application Development”
   • “Required Java™ Archive (JAR) Files”
   The class path might look as follows:

   • 

     /opt/IBM/FileNet/CEClient/lib/pe.jar:
        /opt/IBM/FileNet/CEClient/lib/peResources.jar:
        /opt/IBM/FileNet/CEClient/lib/Jace.jar:
        /opt/IBM/FileNet/CEClient/lib/log4j-1.2.17.jar:

   • 

     C:\Program Files\IBM\FileNet\CEClient\lib\pe.jar;
        C:\Program Files\IBM\FileNet\CEClient\lib\peResources.jar;
        C:\Program Files\IBM\FileNet\CEClient\lib\Jace.jar;
        C:\Program Files\IBM\FileNet\CEClient\lib\log4j-1.2.17.jar;

   Important: For better readability, the paths are shown on several lines. When you specify them in the server configuration profile, specify the paths on one line.
2. If FileNet P8 uses the DB2® database in Oracle compatibility mode or uses the Oracle database, and if you plan to link archived documents to SAP that are in a P8 queue, you must apply a fix to Content Collector for SAP and a fix to FileNet P8. Starting with Fix Pack 1 of Content Collector for SAP, only the FileNet P8 fix needed.
   Contact IBM Support for the fixes.