This chapter describes the procedure for installing the FileNet Collaboration Services and making it available to IBM Connections. In this chapter, we use an existing FileNet deployment.
For a detailed list of IBM FileNet Collaboration Services Version 2.0 oftware and hardware requirements, visit IBM website at http://www-01.ibm.com/support/docview.wss?uid=swg27021659
IBM FileNet Collaboration Services enables you to directly store and acces content in IBM FileNet P8 by using client application applications such as IBM Connections.
Before you begin
Before you install IBM FileNet Collaboration Services, verify that you have the following applications and their current patches properly installed and configured:
- WebSphere Application Server
- IBM FileNet P8 Platform
IBM Connections CCM integration with FileNet Collaboration Services requires at least 5.2 FP1 version. Make sure Fix Pack 1 is installed on your FileNet 5.2 deployment.
The IBM FileNet Collaboration Services hardware and software requirements technote provides detailed information about the required versions of each product. If there is a conflict between the information that is provided in this information center and the information that is provided in the technote, the information in the technote takes precedence. The prerequisite information in the information center is provided only as a convenience.
System setup constraints and recommendations
Before you deploy your IBM FileNet P8 system, you might consider several constraints and recommendations for your system setup.
Plan your deployment based on the following constraints and recommendations:
- Content Platform Engine must be running on WebSphere Application Server. The same version and patch level of WebSphere Application Server must be used for both Content Platform Engine and FileNet Collaboration Services.
- IBM FileNet Collaboration Services is configured to work with a single FileNet P8 object store. If you want to work with multiple object stores, you must install multiple instances of IBM FileNet Collaboration Services, each on a different port.
- Lotus Quickr and IBM Connections each requires its own application server. The application server instance cannot be used with any other web application.
- FileNet Collaboration Services, Application Engine, Workplace XT, and Content Platform Engine must use the same directory service server for authentication. Lotus Quickr does not have to use the same directory service server. IBM Connections does not need to use the same directory service server to support linked libraries. However, IBM Connections must use the same directory service server to support library integration (that is, a library that is dedicated to a single IBM Connections community and is used to create and manage content in a FileNet P8 object store).
- The application servers hosting the Content Platform Engine and FileNet Collaboration Services must be configured for single sign-on. Single sign-on between FileNet Collaboration Services and IBM Connections or Lotus Quickr is optional.
- FileNet Collaboration Services must have network connectivity to the Content Platform Engine host and port.
- Lotus Quickr and IBM Connections must have network connectivity to the FileNet Collaboration Services host and port.
- End-user computers must have connectivity to Lotus Quickr, IBM Connections, FileNet Collaboration Services, Application Engine, and Workplace XT.
- FileNet Collaboration Services and Content Platform Engine can be collocated on a single application server, but it is recommended that, at a minimum, they be separated into two server instances or profiles for better performance.
- To search FileNet P8 from IBM Connections or Lotus Quickr, the object store must be configured for content-based retrieval.