This section describes Activities integration with Quickr Domino.
After you have finished collaborating with your team on a file in an activity, you can publish the finished product to an IBM Lotus Quickr library to share it with a larger group or to store the file.
For this integration to work you need to:
1. Enable SSO between Connections and Quickr
2. Edit the configuration file to enable publishing a file attachment to a Quickr library
3. Define a list of Quickr servers so all necessary cookies are sent from Activities to the Quickr server.
Enable SSO between Connections and Quickr
To enable single sign-on between Connections and Quickr, follow the steps in 5. Implement and test single sign-on
Enabling users to publish file attachments to Lotus Quickr
To enable users to publish file attachments to Lotus Quickr:
1, Open a command prompt to the dmgr bin directory (E:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin).
2 Run the following command:
wsadmin -lang jython -user wasadmin -password password -port 8879
3. At the wsadmin prompt, run the following commands:
Where e:/temp is a temp directory on the local machine and connectionsCell01 is the cell for the Connections environment.
: to verify the cell name, run the following command at the wsadmin prompt: print AdminControl.getCell()
4, Leave the wsadmin prompt and window open.
5, Open oa-config.xml file from the temp directory in a text editor, we used notepad; search in the file and look for the following section.
Updated it to match your environment. We used the following:
6. Save and close the file.
7. Back in the wsadmin command window, enter the following command:
8, Type exit
to exit out of the wsadmin console.
You will need to restart the Connections server for these changes to take effect, but we will first define this server in WebSphere so all necessary cookies are sent from Activities to the Quickr server.
Add Quickr server to list of supported servers in WebSphere
: If you configured Communities with this Quickr server, you have already completed this step. In which case, skip to step 10 to restart Connections and test that it works in your environment.
1, Open a browser to the WebSphere® Application Server Integrated Solutions Console for the Deployment Manager and sign in (https://connections.demos.ibm.com:9043/ibm/console
wasadmin : password).
2, Expand Resources
-> Resource Environment
-> Resource Environment Providers
3. Click QuickrWhitelistProvider from the list, and then click Custom properties.
4, Click New.
5, Enter a name that starts with allow (e.g. "allow" and the hostname of the server -- allowquickr.demos.ibm.com) and the value should be the host name of the Quickr server.
6, Click OK.
7, Click Save
to save the changes to the master configuration.
8, Once the change is automatically synchronized with the nodes, click OK.
9, Log out of the Integrated Solutions Console.
10, Restart the Connections server:
a, Open a browser to the WebSphere® Application Server Integrated Solutions Console for the Deployment Manager and sign in (https://connections.demos.ibm.com:9043/ibm/console
wasadmin : password).
b, Click Servers
-> Server Types
-> WebSphere application servers.
c, Select the Connections server (LC301_server1) and click Restart.
Test publishing a file from Activities to a Quickr library
To test, publishing a file from Activities to a Quickr library:
1. Open your browser to activities. If you do not have an activity create a new one and upload a file to an entry.
2. Click More next to the entry.
3. Next to where you can download the attachment, click Publish to Lotus Quickr,
: If you do not see publish to Lotus Quickr, make sure the oa-config.xml has been updated on the node (E:\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\connectionsCell01\LotusConnections-config) on the node where you are testing, as we did in step 2 above.
4. Select the server
, open the place you want to publish this to to the Library, and click Publish.
5. The document should now show it is stored on the Quickr server: