Configuring access to remote systems for federated documents | HCL Digital Experience
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 that are used to handle communication with the system.
About this task
federated_documents_policy
dynamic policy using the WP
ConfigService
configuration service.Procedure
- Log in to the WebSphere® Integrated Solutions Console.
- Click .
- Click WP ConfigService.
- Under Additional Properties, click Custom Properties.
-
Click New, and enter the property name wp.proxy.config.urlreplacement.federated_documents_policy.suffix,
and set the string value to the URL pattern of the content management server.
For example, to enable the federated documents feature to access information from the content management server
ecm.example.com
on port 10038 over HTTP, you would add the following property:wp.proxy.config.urlreplacement.federated_documents_policy.1=http://ecm.example.com:10038/*
Note: The value of the property keysuffix
can be any value as long as it is unique within the set of keys mapping to thefederated_documents_policy
dynamic policy. - Create additional properties as needed for any other content management servers that you need to access through the federated documents feature.
- 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. - Save your changes, and restart the portal server.