Configure Connections Content Manager with an existing FileNet deployment
To use an existing FileNet deployment with Connections Content Manager, the existing deployment must be configured to use Connections as a directory provider. Changing configuration of the directory or changing JVM arguments used in FileNet directory configuration may only be done during FileNet domain creation or afterward with services for directory migration. Contact IBM services to migrate the directory service provider to use IBM Connections.
OAuth is supported by the Connections WebSphere cell. OAuth is enabled only when FileNet is installed through the Connections installer. OAuth is used for single sign-on with other applications including IBM Notes . Download events are not available in the Connections event SPI and metrics might not include download information when Connections Content Manager uses an existing FileNet deployment.
For an existing FileNet system, ensure that single sign-on has been configured between the FileNet and Connections servers. WebSphere LTPA SSO is recommended. See Configure SSO between IBM FileNet and Connections for more information.
See
- Configure Profile and Community membership lookups for FileNet
- Generate Security identifiers for an existing FileNet deployment
- Prepare an object store to be used by Connections
- Configure WebSphere SSL for Activity Stream
- Set up anonymous access
What to do next
To complete the configuration, make sure to configure collaborative features in FileNet using the Administration Console for Content Platform Engine (ACCE) on the FileNet system.
Parent topic:
Configure IBM Connections Content Manager for Libraries