Configure federated documents

Overview

To retrieve metadata information for documents on remote content management systems, configure the federated documents feature with information about the remote system.

Because federated documents use AJAX proxies, you can use the global AJAX proxy configuration to customize the outgoing HTTP traffic, such as...

• Applying specific HTTP timeout values
• Configuring an outbound HTTP proxy server

Procedure

Set content management servers as allowed request targets in the AJAX proxy configuration, and enable LTPA cookie forwarding for those requests, by mappping URL patterns for the content management server to federated_documents_policy using WP_ConfigService...

1. Log in to the administrative console and go to...
   Resources | Resource Environment | Resource Environment Providers | WP_ConfigService | Additional Properties | Custom Properties | New

2. Enter the property name...
   wp.proxy.config.urlreplacement.federated_documents_policy.suffix

3. Set the string value to the URL pattern of the content management server.

   For example, to enable federated documents to access information from ecm.example.com on port 10038 over HTTP, add...

   wp.proxy.config.urlreplacement.federated_documents_policy.1=http://ecm.example.com:10038/*

   The value of the property key suffix can be any value as long as it is unique within the set of keys mapping to the federated_documents_policy dynamic policy.

4. Create additional properties as needed for any other content management servers that access through the federated documents feature.

5. Optional: The federated documents feature can also consume arbitrary ATOM feeds. To enable this, you can map the URL prefix of the ATOM feed to the default_policy dynamic policy.

   1. Click New, and enter the property name...
      wp.proxy.config.urlreplacement.default_policy.suffix

      ...and set the string value to the URL pattern of the server providing the ATOM feed.

      For example, to enable federated documents to access ATOM feeds from server www.example.com, add...

      wp.proxy.config.urlreplacement.default_policy.1=http://www.example.com/*

      The value of the property key suffix can be any value as long as it is unique within the set of keys mapping to the default_policy dynamic policy.

      To prevent security token forwarding to untrusted servers, be sure that you do not use the federated_documents_policy dynamic policy for those servers.

   2. Create additional properties as needed for any other ATOM feed servers that access through the federated documents feature.

6. Save changes, and restart the portal server.

Parent topic:

Set up support for federated documents

---