Set up support for federated documents
Before we can access metadata from federated documents, you need to configure access to the remote servers containing the documents and specify information about the feeds or service documents used to retrieve the documents. We can also tune the cache settings used with the federated documents feature.
Authentication requirement: Before we can use the federated documents feature, complete one of the following steps:
- Enable single sign-on (SSO) in IBM WebSphere Application Server between the portal server and the content management system.
- Use a content management system that supports HTTP basic authentication, and enable a credential vault slot that stores the credentials to authenticate with the remote server.
Important: If we are setting up single sign-on between IBM Lotus Quickr and the portal server, export the SSO key from the Lotus Quickr server and import it into the portal server, rather than the other way around.
- Configure access to remote systems for federated documents
To retrieve metadata information for documents on remote content management systems, configure the federated documents feature with information about the remote system and the settings used to handle communication with the system.
- Configure the federated documents feature
Configure the federated documents feature to specify information about the source servers for the documents available to users.
- Cache tuning for federated documents
The federated documents feature uses the document list cache, the document data cache, and the feed type cache to manage information about the list of documents, the document data, and the types of feeds a server provides.