Configure your Lotus® Quickr™ server to enable publishing Lotus Quickr documents to an ECM repository.
- Install ECM Services
- Configure Single Sign-On for ECM Services
Lotus Quickr users need to have appropriate access rights to the ECM libraries and folders for publishing documents.
This section provides instructions for configuring your Lotus Quickr server to enable publishing of Lotus Quickr documents to ECM systems, such as IBM FileNet P8 and IBM Content Manager. You cannot use these instructions to publish documents to a document library of an external Lotus Quickr server.
To enable document publishing, specify values for the custom properties of the QuickrPublishConfig resource environment provider. The QuickrPublishConfig resource environment provider enables you to specify the service URL of the server where the ECM services have been installed, the path or the ID of the library and the target folder to publish the Lotus Quickr documents.
To specify the values for the custom properties:
- 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.
- Save the changes to your master configuration and restart Lotus Quickr.
Lotus Quickr must be restarted every time updates are made to this configuration.
Customize the Publish Wizard: qp85
If the publish operations within a team are fairly uniform, you can customize the Publish Wizard to assume values for some of the fields and display minimum data entry screens. This makes adding Lotus Quickr documents to an ECM repository easier.
Parent topic: Configuring Lotus Quickr for ECM Integration: qp85
Publishing documents to an ECM repository: qp85
Set up global credentials using Credential Vault: qp85
Configure linking to ECM documents: qp85
Troubleshooting Unable to publish Lotus Quickr documents to IBM Filenet P8 on Sun ONE http server
Configuring federated documents