S2: Installing the Lotus Connections Connector for Quickr

To enable communities integration between Communities and Quickr places, you must install the Lotus^® Connections Connector for Lotus Quickr on all nodes. For more information, see the Lotus Connections Information Center at:

http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp?topic=/com.ibm.connections.25.help/c_install_quickr.html

Run the setuplinux.bin file from the plug-ins installation files and follow these steps:

Select the language that you want to use in the wizard.
In the Welcome panel, click Next to continue.
Review and accept the license agreement by selecting I accept the terms in the license agreement and click Next.
Select the type of Quickr system to which you are connecting. Specify Quickr Portal.
Select which integration to enable. Select both Quickr Portal Wiki and Quickr Portal Teamspace.
Complete settings for the Quickr server. The J2C authentication user name is an LDAP user who is an administrator of the Quickr server. This can be any user that has administrator rights on the Lotus Quickr server. In this case, wpsadmin has these rights.
Make sure that the installation locations are accurate. By default, this should be set correctly.
The next panel is a summary window. Click Next to begin installation. Note that the installation takes approximately ten minutes or less.
After installation is complete, a results panel is displayed. Verify that no errors occurred and end the installation wizard.
Repeat this process for all nodes.
On the deployment manager machine, open the administrative console. Create a J2C authentication alias to be used from Lotus Connections when creating Quickr places. You must create this user on the deployment manager since the connector is not installed on this machine. To create this alias, follow these steps:

a. In the WebSphere^® Application Server console, select Security > Secure, Administration, applications and infrastructure and expand the Java™ Authentication and Authorization Service section.

b. Select JAAS > J2C Authentication Data and click New. Provide an alias, user ID, and password in the form as shown and then click OK to save changes.
The configuration files installed during the connector installation do not currently exist on the deployment manager machine. You must copy these manually. To do so, on node 1, locate the following files in the LotusConnections-config directory at:

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/node1cell01/LotusConnections-config

Files:

communities-quickr-config.xml
communities-quickr-config.xsd
Copy these files from this location to the same location on the deployment manager machine:

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/dmgrCell01/LotusConnections-config
On the deployment manager, open the communities-quickr-config.xml with a text editor and do the following:

a. Replace the @nowiki@1comm:authentry> property with the alias name created in step 11. For example:
```
<comm:authentry>dmgrCellManager01/quickradmin</comm:authentry> 
```
b. Locate the section at the bottom of the config file relating to the QuickrDelayedSync task and add the @nowiki@2comm:serverToRun> property. This task ensures that community changes made while the Quickr server is unavailable are propagated to Quickr at a later time. This task can run on only one server, which you must specify here. The property takes the form cellname\nodename\servername. For example:
```
dmgrCell01\\node1Node01\\communitiesServer 
```
c. Save the .xml file.
Follow instructions in the information center to allow authenticated feeds from Lotus Quickr on the community welcome page:

http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp?topic=/com.ibm.connections.25.help/t_admin_communities_support_quickr_feeds.html
Perform a full resynchronization between the DM and all nodes. You must fully restart the Communities feature cluster to reflect this change. To synchronize the nodes do the following on the deployment manager:

Select System administration > Nodes, select the check box next to the node name, and click Full Resynchronize.