IBM Support

IBM Content Collector 4.0.1.10 Interim Fix 5 Knowledge Center update

Product Documentation


Abstract

This document provides the Knowledge Center updates for Content Collector 4.0.1.10 Interim Fix 5.

Content

The Download document for this interim fix is available at the following link:

Sections of this document

  • Updated topics
  • Updated content

Updated topics

The following Knowledge Center topics are updated in this interim fix:
Action Sub-action Topic
Installing Content Collector Installing individual components 1. Configuring web application server
  1. Installing web applications
  2. Establishing trust relationships between web application servers
  3. Updating Web Application settings in Configuration Manager
  4. Verifying the web application server configuration
Developing with Content Collector APIs Developing with the Content Collector Web Application services APIs 2. Enabling security for Web Application services APIs
  1. Setting up APIs for embedded web application server Liberty on Content Collector Server
  2. Setting up APIs for external WebSphere Application Server on Content Collector Server
  3. Setting up APIs for external WebSphere Application Server Liberty on Content Collector Server
Troubleshooting Troubleshooting installation problems

Updated content

The following provides the updated content.

1. Configuring web application server

Navigation: Installing Content Collector>Installing individual components>Configuring web application server
Updated section: Note
Added another note:
Note: IBM Content Collector 4.0.1.10 installs the base version of IBM WebSphere Application Server Liberty v19 on Windows as the embedded web application server. For more details refer to Migration of IBM Embedded WebSphere Application Server to IBM WebSphere Liberty Application Server.

1.1. Working with an external web application server

Navigation: Installing Content Collector>Installing individual components>Configuring web application server>Working with an external web application server
Updated section 1: Before you begin
Added supported version and a note before the prerequisites of the task:
Supported version
  • IBM® WebSphere® Application Server (v8.5.5 / 9) on a Linux, AIX, or 32-bit or 64-bit Windows operating systems.
  • IBM WebSphere Application Server Liberty 19.0.0.3 / 19.0.0.4 / 19.0.0.5 on 32-bit or 64-bit Windows operating systems.
Note: IBM Content Collector 4.0.1.10 uses IBM WebSphere Application Server for Windows as the embedded web application server.
Updated section 2: Added a point and some content in the prerequisites of the task:
  • Ensure that Java is not set in the path for external IBM WebSphere Application Server.
The following prerequisites are applicable only for IBM WebSphere Application Server Liberty:
  • IBM Content Collector API Setup can be configured through Liberty Admin Centre Feature (if installed); however, we need not perform this step for IBM Content Collector Web Application.
  • External IBM WebSphere Application Server Liberty requires javaMail-1.6 feature to view mails archived with IBM Content Collector. For more details on how to install features for IBM WebSphere Application Server Liberty, refer to Installing assets using the installUtility command.
Updated section 3: Procedure
Shifted step 3 to step 4 and added a new step 3:

1.1.a. Installing web applications

Navigation: Installing Content Collector>Installing individual components>Configuring web application server>Working with an external web application server>Installing web applications
Updated section 1: Procedure
Modified the command in step 1 and added its explanation:
afu_ewas_gather_external.bat targetServerRuntime targetOS
The targetServerRuntime parameter specifies the target web application server. It can be one of the following:
  • twas: IBM WebSphere Application Server
  • liberty: IBM WebSphere Application Server Liberty
Updated section 2: Procedure
Added a section for IBM WebSphere Application Server Liberty:
IBM WebSphere Application Server Liberty
For IBM WebSphere Application Server Liberty it can be one of the following:
  • Win-32: Copies all the files that are required for installing the IBM Content Collector web applications on a Windows 32-bit operating system.
  • Win-64: Copies all files that are required for installing the IBM Content Collector web applications on a Windows 64-bit operating system.
  • Unix, AIX: Not supported on IBM WebSphere Application Server Liberty.
Updated section 3: Procedure
Modified step 3:
Within the transferDirectory, edit the script that sets the environment for the web applications
On Windows, edit the afuEnv.bat script. On Linux or AIX, edit the afuEnv.sh script. Modify the command script as follows before running the installation scripts:
  1. Set the name of the web application server directory with the WSDir parameter.
  2. Perform this step based on your target Server Runtime:
    Table 1.
    IBM WebSphere Application Server IBM WebSphere Application Server Liberty
    No action required
    • Set JAVA_JRE parameter to <Java_install_dir>/jre (Java 1.8.0.35 or above)
    • Set ANT_BIN parameter to <Ant_install_dir>/bin (Ant 1.10.2 or above)

    You may use the java, ant that is shipped with ICC or they can be downloaded from the official source. Note that the java specified should be the same as that used by Liberty Runtime.

1.1.b. Establishing trust relationships between web application servers

Navigation: Installing Content Collector>Installing individual components>Configuring web application server>Working with an external web application server>Establishing trust relationships between web application servers
Updated section 1: About this task
Added a note and introduced two new hyperlinks:
Note
  • Refer to Using iKeyman section below for detailed steps on opening and importing certificates into keystore.
  • Follow Section I for WebSphere Application Server and Section II for WebSphere Application Server Liberty Server.
  • <ICC_INSTALL_DIR> refers to IBM® Content Collector installation path.
  • <WLP_INSTALL_DIR> refers to External Liberty Location.
Establishing trust relationships with different servers
Updated section 2: Removed the procedure.

1.1.c. Updating Web Application settings in Configuration Manager

Navigation: Installing Content Collector>Installing individual components>Configuring web application server>Working with an external web application server>Updating Web Application settings in Configuration Manager
Updated section: Newly introduced topic.

1.1.d. Verifying the web application server configuration

Navigation: Installing Content Collector>Installing individual components>Configuring web application server>Working with an external web application server>Verifying the web application server configuration
Updated section: Procedure
Added a note:

Note: For WebSphere Application Server, if you get an error about missing libraries in the logs while executing isAlive.jsp, please append the library path in the XML element classpath in the Libraries.xml file. It is located at the following path:

<WebSphere Installation>AppServer\profiles\AFUWeb\config\cells\<cellName>\nodes\<nodeName>\servers\afuServer\libraries.xml

2. Enabling security for Web Application services APIs

Navigation: Developing with Content Collector APIs>Developing with the Content Collector Web Application services APIs>Enabling security for Web Application services APIs
Updated section 1: Removed the procedure.
Updated section 2: Introduced three new hyperlinks.

2.a. Setting up APIs for embedded web application server Liberty on Content Collector Server

Navigation: Developing with Content Collector APIs>Developing with the Content Collector Web Application services APIs>Enabling security for Web Application services APIs>Setting up APIs for embedded web application server Liberty on Content Collector Server
Updated section: Newly introduced topic.

2.b. Setting up APIs for external WebSphere Application Server on Content Collector Server

Navigation: Developing with Content Collector APIs>Developing with the Content Collector Web Application services APIs>Enabling security for Web Application services APIs>Setting up APIs for external WebSphere Application Server on Content Collector Server
Updated section: Newly introduced topic.

2.c. Setting up APIs for external WebSphere Application Server Liberty on Content Collector Server

Navigation: Developing with Content Collector APIs>Developing with the Content Collector Web Application services APIs>Enabling security for Web Application services APIs>Setting up APIs for external WebSphere Application Server Liberty on Content Collector Server
Updated section: Newly introduced topic.

3. Installation of web applications fails

Navigation: Troubleshooting>Troubleshooting installation problems>Installation of web applications fails
Updated section 1: Procedure
Shifted step 3 to step 4 and added a new step 3:
Step 3. Perform this check based on the target Server Runtime.
IBM WebSphere Application Server IBM WebSphere Application Server Liberty
No action required Ensure that JAVA_JRE and ANT_BIN parameters are set and the paths exist.
Updated section 2: Procedure
Shifted step 6 to step 7 and added a new step 6:
Step 6. Check whether the profile directory still exists.
If it still exists, create backup copies of all files that you want to keep. Then,
IBM WebSphere Application Server IBM WebSphere Application Server Liberty
Windows: Delete AFUWeb directory in WASHOME\profiles
or
AIX, Linux: WASHOME/profiles		 Windows: Delete AFUWeb directory in LIBERTYHOME\wlp\usr\servers

Document Location

Worldwide

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSAE9L","label":"Content Collector"},"Component":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.0.1.10","Edition":"Interim Fix 5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 June 2020

UID

ibm11102773

Page Feedback