This section describes Communities integration with Quickr Domino.
With the IBM® Connections Connector for Lotus® Quickr™, you can create associated Lotus Quickr team places for IBM Connections communities. A Lotus Quickr team place provides a central location from which a team can organize, share files, and collaborate on documents. Every IBM Connections community owner can optionally choose to create an associated Lotus Quickr team place. Updates made in the Lotus Quickr team place are aggregated in the community overview page, making it easier to stay current with projects and work collaboratively. Access control and membership of the Lotus Quickr place is determined by the often fluctuating IBM Connections community membership; it does not need to be managed separately.
Configure single sign-on between Connections and Quickr Domino
To configure single sign-on between Connections and Quickr Domino, refer to 5. Implement and test single sign-on
Configure admin user in Quickr Domino
During the install and setup of the Connections Connector for Lotus Quickr you have to specify a user that the Connections server will use to authenticate with the Quickr server to create the Quickr place and keep the members of the community and Quickr place synchronized. This user must be an LDAP user that has access to Connections, as well as an Administrator of the Quickr Domino server. The reason the user must exist in LDAP, and the Connections server is because when we make calls to Quickr, the connector will get the username / password of the connector user. call into WebSphere with that name and password. WebSphere will authenticate the user and return an LtpaToken to the connector, then the connector will make the request to Quickr sending the LtpaToken. So the default Quickr admin configured during the Quickr install will not work in this setup as that user is only known by the Quickr server, and not Connections.
Use the following steps to add a user to the Administrator role on the Quickr Domino Server:
1, Open a browser to the Quickr server (http://quickr.demos.ibm.com/lotusquickr
) and sign in as the Quickr Administrator (qpadmin : password).
2, Click Site Administration.
3, Click Security.
4, Under Who can Administer this server, click Add.
5, Click Directory.
6, Search for the user in LDAP you would like to add.
7, Select the user and click Add,
you should see a Successfully Added: username message, Click OK.
8, Click Close
in the Directory Search window.
9, Click Next
on the Server Security: Add Access page.
10, You should see the user in the list (wpsadmin in our example):
11, Log out of Quickr Domino.
Download and install IBM Connections Quickr Connector 3.0.1
To download and install IBM Connections Quickr Connector 3.0.1:
1, Download the IBM Connections Quickr Connector 3.0.1 from the portlet catalog to the Connections Server.
2, Unzip this to a temp directory on the Connections server.
3, Run Lotus_Connections_Connectors_Quickr_3.0.1_win to unzip the install files to the temp directory.
4, Run LC_Connectors_Quickr_Install_IM\IM\windows\install.bat.
5, On the IBM Install Manager page, select IBM Lotus Connectors for Quickr
and Version 126.96.36.199
and click Next
. NOTE: If you see the IBM Install Manager page requested you to click Install, or Properties, you ran install.exe, close the IBM Installation Manager and run install.bat.
6, Review and accept the license agreement by selecting I accept
the terms in the license agreements. Then click Next
7, Specify the location where you want to install the connector in the Installation Directory field (E:\IBM\ConnectorsQuickr), and then click Next.
8, Make sure IBM Lotus Connectors for Quickr
and Version 188.8.131.52
are selected, and then click Next.
9, Specify Quickr type: Quickr Domino:
The templates you want to use from the Quickr Domino server
Hostname and port of the Quickr Domino server
Finally, the J2C authentication user name and password should be the user in LDAP you added as a Quickr administrator earlier.
10, Enter the Lotus Connections install home directory, this should cause the Connector libraries install location and configuration install location to pre-populate, and click Validate.
11, Click Next.
12, Click Install.
13, Once the install completes you will see:
Install results :
14. Click Finish
Synchronize the deployment manager with the nodes
To complete the install of the IBM Connections Quickr Connector you need to synchronize the DMGR with each node.
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, Select System administration
, select the Connections nodes, and then click Full Resynchronize
3, From the main Integrated Solutions Console page, select Servers
-> WebSphere Application Server Clusters.
4, Select the check box beside the cluster containing the nodes that have been updated, and then click Stop
5, Once the cluster is completely Stopped Select the cluster and click Start
Add the Quickr Domino server as a supported server in Connections
We provided the IBM Lotus Quickr server to the ajaxproxy server to ensure that it honors any requests made for access to one of the supported Lotus Quickr servers:
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,
and then click 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 (eg: "allow" and the host name of the server -- allowquickr.demos.ibm.com) and the value should be the hostname of the Quickr server.
6, Click OK.
7, Click Save
to save the changes to the master configuration.
8, Once the change is automatically syncronized with the nodes, click OK.
9, Log out of the Integrated Solutions Console.
Configure Connections ajaxproxy to work with Quickr
Communication between Connections and Quickr goes through the IBM Connections ajaxproxy. By default it is configured to allow cookies, headers or mime types, and all HTTP actions to be exchanged among the IBM Connections applications. However, It also prevents HTTP GET requests from non-IBM Connections services and prevents all cookies or headers from being directed to the applications.
We need to configure the Connections ajaxproxy to allow HTTP GET requests to the Quickr server, and send the LtpaToken for authentication:
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 proxy-config.tpl file from the temp directory in a text editor, we used notepad, scroll down near the bottom of the file and look for the following line:
6, Add the following rules for your Quickr server:
7, Save and close the proxy-config.tpl.
to exit out of the wsadmin console.
2, Sign in as a test user (wpsadmin : password).
3, Click Start a Community.
4, Enter a name, and under Associated Applications, select Include this application in the community: Quickr Teamspace.
6, The Community and Quickr place should be created, after they are created, the community will appear with a Quickr Teamspace widget showing the home page of the place.