Migrating from an earlier version of the Quickr Library widgetsAdded by IBM on February 11, 2013 | Version 1 (Original)
|Follow these steps to migrate from the 126.96.36.199 version of the Quickr library widget.
Parent topic: IBM Lotus Quickr Library widgets for IBM Connections
- In SiteMinder environments only, perform the follow tasks on the IBM® connections server:
- Copy the US_export_policy.jar and local_policy.jar files from wherever you unpackaged the unrestricted.zip file when configuring SiteMinder. Paste it in the following directory, overwriting the existing versions of those files:
- Copy the sm_jsafe.jar and sm_jsafeJCE.jar files from the Siteminder ASA crypto-libraries installation directory. Paste it in the following directory, overwriting the existing versions of those files:
- Download the 4.0 version of the Lotus® Quickr® Library widget war file from the IBM Lotus and WebSphere Portal Business Solutions Catalog web site.
- Install the widget war file.
- Log in to the WebSphere Administrative Console on the IBM Connections server.
- Navigate to Applications -> Application Types -> WebSphere enterprise applications.
- Click Install.
- Browse and select the comm.communitylibrary.war file, click Next, and then click Next again.
- In Step 1 of the installation wizard, click Next without changing anything.
- In Step 2, select the cluster and web server (if there is one), and then click Next.
- In Step 3 of the installation wizard, in the Target Resource JNDI Name column, click Browse and select communities. Then click Apply. The field is populated with the value jdbc/sncomm. Then check the box and click Next.
- In Step 4, check the box and then click Next without changing anything.
- In Step 5, type /quickr/connector in the Context Root field, and then click Next.
- In Step 6, click Finish.
- Click Save to save all changes.
In clusters you must wait for synchronization to complete before continuing. Check the systemout.log in the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeagent directory (on Linux™ servers) to check for the synchronization completed successfully message.
- In the list of applications, select the Lotus Quickr Library widgets application and then click Start to start it.
- Create a J2C authentication alias for the Lotus Quickr administrator.
- On the IBM Connections server, log into the WebSphere Application Server Integrated Solutions Console, expand Security, and then select Global Security.
- Expand Java Authentication and Authorization Service.
- Select J2C authentication data.
- Click New.
- Type an alias name (for example quickradmin), and specify the user ID and password credentials of a Lotus Quickr administrator.
Note: If the Lotus Quickr administrative user is not available to IBM Connections (meaning not in the LDAP or defaultFileBasedRepository), then you must add them to the defaultFileBasedRepository. Navigate to Users and Groups -> Manage Users, and then create a user with the Lotus Quickr administrator ID and password.
Note: In a Siteminder environment, the Quickr administrative user must be a valid Siteminder user.
The server generates a J2C alias with a cell name and the alias name you provided, for example: cell01\quickradmin. You must use this generated alias, including the cell name.
- If you want to preserve the configuration settings from the 188.8.131.52 deployment, copy the values from \IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config. No additional changes are needed. Otherwise, follow these steps to copy the widget configuration files to the IBM Connections configuration directory.
- Navigate to the widget \resources_config directory:
- Copy the communities-quickr-library-config.xml and communities-quickr-library-config.xsd files to the \LotusConnections-Config directory:
In clustered deployments, copy the files to the \LotusConnections-Config directory on the deployment manager node.
- Follow the steps in this article to add /lotus/mycontenthandler/!ut/ to the list of unprotected URLs.
- If you followed the steps in the Connections 4.0 migration topic Saving your customizations, you can skip the remainder of this step. If not, follow these steps to copy the resource files from the 184.108.40.206 deployment and add the widget resource bundle to the LotusConnections-config.xml file.
- Navigate to the widget resources directory:
In clusters, navigate to the directory on any node.
- Copy the contents of the \resources directory to the IBM\Connections\data\shared\customization\strings directory (in clusters, copy to the deployment manager computer).
- Check out and open the LotusConnections-config.xml file. See Editing configuration files.
- Add the following line of code into the <resources> element block to register the resource bundle for the Quickr Library widget:
<widgetBundle name="com.ibm.quickr.communitylibrary.resources" prefix="quickrCommunityLibrary_res" />
- On the IBM Connections server, open communities-quickr-library-config.xml and update the Lotus Quickr information for your environment, for example:
- <host> is the Lotus Quickr server hostname. If you have IBM Tivoli® Access Manager enabled on Lotus Quickr server, replace yourserver.com with the IBM Tivoli Access Manager sever host name.
- <port> is the http port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
- <sslPort> is the https port number of the Lotus Quickr server. Or if a web server is configured, <port> is the http port number of the web server.
- <useSSL> is whether or not to use http or https in communicating with the Lotus Quickr server. If this is set to "true", the Lotus Quickr server must have a certificate that is trusted by the IBM Connections server. See Secure communications using Secure Sockets Layer in the WebSphere Application Server 6.1 documentation for more information.
- <authentry> is the full name of the J2C authentication alias for the Lotus Quickr administrator that you created in Step 3.
- For <ownersRole>, <membersRole>, and <publicRole> the role names can be either the role title in English or the id field returned for the roles feed. If anonymous access is not allowed, the publicRole element should be omitted or empty. The publicRole is applied in both public and moderated communities, but is not in restricted communities
- In clustered environments, perform a full synchronization of the IBM Connections cluster.
- Restart IBM Connections.
- If you had IBM HTTP Server installed before you installed the Lotus Quickr widget, follow instructions in Mapping applications to IBM HTTP Server to map the Lotus Quickr widget application to the IBM HTTP Server.