Configure your IBM® Lotus® Quickr™ for WebSphere Portal server to enable linking to ECM documents from a Lotus Quickr library or the rich text areas of blogs, wikis, lists, forums, and comments.
- Install ECM Services
- Configure Single Sign-On for ECM Services
Lotus Quickr users can create links to ECM documents in their Lotus Quickr libraries and in the rich text areas of blogs, wikis, lists, forums, and comments. This enables them to always view and download the latest content of the linked ECM documents from Lotus Quickr. Additionally, Lotus Quickr users can copy, move, rename, and delete these ECM document links.
To enable linking to ECM documents, specify values for the custom properties of the QuickrWhitelistProvider and QuickrPublishConfig resource environment providers.
The WP ConfigService resource environment provider enables you to specify a list of allowed domains that can be accessed from your Lotus Quickr environment. Configuring this resource environment provider is important to prevent access to external servers with malicious content. Use this resource environment provider to specify the web address of the ECM system that is to be accessed for creating the document links.
Use the QuickrPublishConfig resource environment provider to enable linking to ECM documents and to specify the name of the credential vault slot that you create if it is impossible to configure Single Sign-On (SSO) between Lotus Quickr and the ECM server.
To specify values for the properties of the two resource environment providers:
- Log in to the WebSphere® Application Server administrative console.
- Click Resources -> Resource Environment -> Resource Environment Providers.
- Click WP ConfigService.
- Click Custom Properties in Additional 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 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.
- 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.
- 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 the federated documents feature to access ATOM feeds from the server www.example.com, you would add the following property: 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.
Important: To prevent security token forwarding to untrusted servers, be sure that you do not use the federated_documents_policy dynamic policy for those servers.
- Create additional properties as needed for any other ATOM feed servers that you need to access through the federated documents feature.
- Navigate back to the list of resource environment providers and click QuickrPublishConfig and then click Custom properties.
- Configure the properties for your system, as per the information provided in the following table.
The names and values of these properties are case-sensitive.
Table 1. QuickrPublishConfig properties
|Property name||Property description||Default value||Recommended value|
|qkrPublishConfig.publishEnabled||Set this property to true to enable creating links to documents in a remote ECM repository from your Lotus Quickr system. ||false||true|
|qkrPublishConfig.targetHost||Specifies the service URL where the ECM services are installed. The value for this property should be of the form http(s)://host(:port). The value of the port depends on the other profiles running on WebSphere Application Server; the default port is usually 9080 if there are no other profiles running on the WebSphere Application Server.|
|qkrPublishConfig.allowHostEdit||Set to true to enable users to edit the Server field of the document picker and specify an ECM server for creating document links. |
If the value of qkrPublishConfig.allowHostEdit is false and a value has been specified for the qkrPublishConfig.targetHost property the Server field of the document picker will be read-only.
|qkrPublishConfig.lookupVaultSlot||The name of the credential vault slot where the credentials for creating links to documents in the remote repository are stored. This property should be used only when configuring Single Sign-on (SSO) is not possible. See the Set up global credentials using Credential Vault topic for steps to add a vault slot and configure credentials.||FilingSlot||If you are using SSO, don't specify any value for this property. |
Important: If you have configured SSO between the Lotus Quickr server and the ECM server and still specify a slot name for this property, the credentials stored in the credential vault slot will override the SSO credentials for linking to the ECM server.
To view the other important custom properties of the QuickrPublishConfig resource environment provider, see Configure document publishing to ECM repositories
- Save the changes to your master configuration, and restart Lotus Quickr.
Note: Lotus Quickr must be restarted every time updates are made to this configuration.
Parent topic: Configuring Lotus Quickr for ECM Integration: qp85
Enterprise Library Viewer: qp85
Configure document publishing to ECM repositories: qp85
Set up global credentials using Credential Vault: qp85
Configuring federated documents