Configuring remote server access for links | HCL Digital Experience
Before you can add links to files and documents that are stored in remote content management systems into web content elements, you must configure your server 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 Enterprise Content Manager
server.
For example, to enable the server to access information from the Enterprise Content Manager 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
. - Create additional properties as needed for any other Enterprise Content Manager servers that you need to access through the server.
- Save your changes, and restart the portal server.
What to do next
If a user tries to access a server (for example,
www.example.com
) that has not been added to the list of allowed domains, the
following message is
displayed:Access to remote server www.example.com has not been granted. Please contact your system administrator.