Configure remote server access for links
Before we can add links to files stored in remote content management systems into web content elements, configure the server with information about the remote system. To prevent linking to unsafe servers, specify a list of allowed domains in the AJAX proxy configuration. We can customize the outgoing HTTP traffic, such as applying specific HTTP timeout values, or configuring an outbound HTTP proxy server. To do this, we map the URL patterns for the ECM server to the federated_documents_policy dynamic policy using the WP ConfigService configuration service.
- Log in to the WAS console and go to...
Resources | Resource Environment | Resource Environment Providers | WP ConfigService | Additional Properties | Custom Properties | New
- Enter the property name...
wp.proxy.config.urlreplacement.federated_documents_policy.suffix
...and set the string value to the URL pattern of the ECM server. For example, to enable the server to access information from the ECM server...
ecm.example.com
...on port 10038 over HTTP, add property...
wp.proxy.config.urlreplacement.federated_documents_policy.1=http://ecm.example.com:10038/*
Property key suffix can be any value unique within the set of keys mapping to the federated_documents_policy.
- Create additional properties as needed for any other ECM servers that we need to access through the server.
- Save the changes, and restart the portal server.
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 the system administrator.
Parent Configure a web content authoring environmentRelated tasks:
Set service configuration properties
IBM DB2 Content Manager publication library