How To
Summary
IBM Content Collector 4.0.1 fix pack 12 (4.0.1.12) supports Business Automation Content Services on Cloud (BACSoC) as a repository for IBM Content Collector for Email and SMTP (Simple Mail Transfer Protocol). This document provides the steps for setting up a new server to use this feature.
Steps
IBM Content Collector (ICC) uses Business Automation Content Services on Cloud (BACSoC) application program interface (API) to archive full-text index, Email, and SMTP documents on the cloud.
Setting up ICC Server to use BACSoC APIs with Email and SMTP
- Download the Content Platform Engine (CPE) API package from the BACSoC user portal.
- Install Web Services Enhancements (WSE).
- Install CPE 5.5.8 .Net API (FileNetApiSetup.msi) and confirm the version in the control panel.
- Create a directory structure and copy all the files from cpeapilib (downloaded in Step 1) to this path:
C:\Program Files\IBM\FileNet\CEClient\lib - Take a backup of the version.txt file from cpeapilib (downloaded in Step 1) and place it in this location:
C:\Program Files\IBM\FileNet\CEClient- Rename the file to ce_version.txt.
- Install Content Collector 4.0.1 and fix pack 12 with Email or SMTP as Source and FileNet P8 as Repository.
Ignore the prerequisites missing error for IBM FileNet P8 Content Engine Client during the installation. - Add the following environment variable and reboot the system:
Variable name: IBMAFUFNCEROOT
Value: C:\Program Files\IBM\FileNet\CEClient - Set the following variable in the startInitialConfig.bat file located under:
<IBM_installation_folder>\Configuration
@set IBMAFUFNCEROOT= C:\Program Files\IBM\FileNet\CEClient - Set the following variable in AfuEnv.bat file located under:
<IBM_installation_folder>AFUWEB
@set FNCEPATH= C:\Program Files\IBM\FileNet\CEClient - Launch Initial Configuration Wizard and follow the steps.
Ensure that you remove the slash appended in the P8 URL field in the initial configuration wizard for successful CEAdministrator user validation. - If the initial configuration fails, refer to IBM FileNet P8 validation fails using HTTPS connection in Initial Configuration or Setup Tools.
- After the initial configuration, open the newly created catalog and navigate to the P8 Connector.
- Ensure that the status of the P8 Connection Set is not in the 'error' state. If it is in an error state, verify that all the previous steps are performed correctly.
- Establish a trust relationship between the Content Collector Web Application Server and BACSoC as given below:
- Obtain Business Automation Content Services on Cloud certificate:
- Open Business Automation Content Services on Cloud URL in a browser.
- Click the lock icon on the address bar and view the certificate.
- Export the certificate to a File.
- While exporting, select the Cryptographic message syntax standard-PKCS #7 certificate (. P7B) option and check Include all certificates in the certification path if possible.
- Provide certificate name, click Next, and then click Finish.
- For the remaining steps, refer to the Establishing a trust relationship with IBM FileNet P8 section in Migration of IBM Embedded WebSphere Application Server to IBM WebSphere Liberty Application Server.
- Obtain Business Automation Content Services on Cloud certificate:
- Open the browser to check if the following link opens successfully:
https://<SERVER_NAME>:<port>/AFUWeb/isAlive.jsp
In case of an error, verify that all the previous steps are performed correctly.
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAE9L","label":"Content Collector"},"ARM Category":[{"code":"a8m50000000L3CCAA0","label":"Usage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.1"}]
Was this topic helpful?
Document Information
Modified date:
01 February 2022
UID
ibm16519482