Installing IBM Content Collector P8 Content Search Services Support
IBM Content Collector P8 Content Search Services Support is an optional document constructor plug-in in IBM Content Search Services for custom preprocessing of all documents archived by using IBM Content Collector other than file system documents.
Before you begin
- Ensure that IBM FileNet® Content Search Engine Client version 5.1 is installed.
- On all UNIX environments, and on Linux and Linux on System z®, ensure that J2SE 1.4 or greater is installed. IBM Content Collector P8 Content Search Services Support requires that a Java Runtime Environment (JRE) be installed on the server.
- On all UNIX environments, and on Linux and Linux on System z, ensure that the PATH environment variable contains Java (version 1.4 or higher).
- On all UNIX environments, and on Linux and Linux on System z, it is best practice to use the same credentials for installing IBM FileNet Content Engine client, IBM Content Search Services, and IBM Content Collector P8 Content Search Services Support.
- The IBM Content Search Services server uses an SSL connection for communication with the IBM FileNet Content Engine server. Therefore, the Content Engine server certificate must be deployed to the JRE truststore of IBM Content Search Services. For details, see the topic about configuring an SSL connection between these FileNet P8 servers.
About this task
Content Search Services Support can be installed on Windows, UNIX machines, Solaris, Linux, and Linux on System z.
Content Search Services Support must be installed on all IBM Content Search Services instance on the IBM FileNet Content Search Engine server on each IBM FileNet P8 server that is used by IBM Content Collector.
You can install IBM Content Collector P8 Content Search Services Support in GUI mode, console mode, or silent mode. The Content Search Services Support installation installs Content Search Services Support on all of the IBM Content Search Services instances on the IBM FileNet Content Search Engine server.
- Email documents
- Microsoft SharePoint documents
- IBM Connections documents
The source documents that you select when you install Content Search Services Support must be the same as the source documents that you select when you configure the object store for IBM Content Collector using the Content Collector setup tool for repository enablement.
File system documents do not have to be preprocessed by Content Search Services Support before they are sent to the IBM Content Search Services index servers for indexing.
Only Microsoft SharePoint list items that contain attachments, in other words multiple content elements, require preprocessing by Content Search Services Support before they are sent to the IBM Content Search Services servers for indexing.
The way that you configure Content Search Services Support depends on whether the configuration data is stored in the configuration store or is stored entirely in the constructors.xml configuration file which must be maintained manually.
Before Content Collector V3.0, all Content Search Services Support configuration
options were stored directly in the constructors.xml file.
Starting with Content Collector V3.0,
the Content Search Services Support configuration
options that are required for indexing items using IBM Content Search Services are stored in the configuration store,
and can be defined and changed using the IBM Content Collector Configuration Manager.
The constructors.xml file no longer contains
the configuration options; it now contains the link to the configuration store where
the configuration is stored.
If you install Content Search Services Support in an environment with more than one IBM FileNet P8 server, you must store and maintain the Content Search Services Support configuration for all IBM Content Search Services instances on all IBM FileNet Content Search Engine servers in the constructors.xml file. You cannot have a mix of configuration data stored in the configuration store and in constructors.xml configuration files.