Home

 

Define a list of supported Lotus Quickr servers


Overview

After you configure the Activities server to allow file attachments to be published to IBM Lotus Quickr, provide a list of the supported Lotus Quickr servers to the proxy server, so that it honors any requests made for access to one of the supported Lotus Quickr servers.

You must have Lotus Quickr deployed in your enterprise before you can perform this procedure. You must have administrative access to the WebSphere Application Server to which Activities is installed.

This is an optional task. Perform this task if you want users to be able to publish files that have been attached to activity entries from Activities to a Lotus Quickr library.

  1. Go to the WAS admin console for the server hosting the Activities feature if you have a stand-alone deployment or hosting the deployment manager if you have a network deployment.

  2. Expand...

      Resources | Resource Environment | Resource Environment Providers

  3. Click the down arrow beside the scope field, and then select the node scope. For example:

      Node=acmeNode01

  4. Click QuickrWhitelistProvider from the list, and then click Custom properties.

  5. Create one custom property for each Lotus Quickr server that you want to enable users to publish documents to...

      name Create a property name that begins with the term allow. For example:

        allowQuickrPrimary.acme.com
      value Fully qualified domain name of the Lotus Quickr server or its IP address. Do not specify the protocol, nor any port numbers.

      To enable users to publish files to several servers within a specific domain, specify the parent domain in this field. You must start the string with a period (.). For example, if you were to specify .acme.com, the proxy would allow the file to be published to all of the servers that are available from subdomains of acme.com. If you want users to be able to type in a server that is hosted within this domain, set the allowCustomServers attribute of the <PublishFile> element to true in the oa-config.xml file.

      The provider does not convert IP addresses to domain names nor the other way around. If the server is requested using both identifiers, create two properties: one property that specifies the domain name in the value field and one that specifies the IP address in the value field.

    If you upgraded a stand-alone deployment which was already configured to integrate with Lotus Quickr to a network deployment, recreate these custom properties for the provider on the cluster's cell. The custom properties must be redefined because they are lost when you federate the node into a cluster.

  6. Repeat Step 5 multiple times to add every server defined in the oa-config.xml file.

  7. Repeat Steps 3 through 6 for each node in the cluster.

  8. Synchronize nodes


Integrate Activities with IBM Lotus Quickr


Previous topic:

Enable users to publish file attachments to Lotus Quickr

+

Search Tips   |   Advanced Search