Lotus Quickr Version 8.1 Quick Start

 

+

Search Tips   |   Advanced Search

 

IBM Lotus Quickr is team collaboration software. The software components enable one to deploy services for...

• Lotus Domino
• WebSphere Portal

To install..

1. Download the product. Parts include...
   1. Quick Start CD
   2. Lotus Quickr services for Lotus Domino
   3. Lotus Domino, and Lotus Domino Language Packs
   4. Lotus Quickr services for WebSphere Portal
   5. WAS Network Deployment
   6. IBM DB2 UDB Enterprise Server Edition
   7. IBM Tivoli Directory Server and Fixpack
   8. Edge Components for WAS Network Deployment
   9. WAS Toolkit

2. Evaluate your hardware and system configuration

3. Review Lotus Quickr documentation page

4. To install Lotus Quickr services for Lotus Domino...

   • Install Lotus Domino.

   • Install Lotus Quickr services for Lotus Domino on the same system.

   • (Optional) For greater feature availability and easier place member management, configure Lotus Quickr to connect to a user directory.

5. To install Lotus Quickr services for WebSphere Portal...

   1. Install Lotus Quickr services for WebSphere Portal.

   2. (Optional) To store user information and to authenticate users with an LDAP user registry, install an LDAP directory, and configure it to work with Lotus Quickr.

   3. (Optional) To manage network traffic, particularly in a production environment, install an external Web server and configure it to work with Lotus Quickr.

 

Post-install

Default admin user	quikradm
Default DB2 user	wpdb2ins

If Portal and Quickr are on separate servers, to configure them to use the same external web server, keep the different hosts in a different VirtualHostGroup in the plugin, so the plugin matches them for a different route, which should stop problems with overlapping context roots .

Watch for overlapping context roots such as wps which quickr does use infrequently.

If you get connection refused when trying to connect to Quickr from Portal, port might be blocked or not listening.

Verify that the correct port is being used by the HttpClient session object.

To determine if it is a connection issue between the client and the server, copy code and dependent jars to the server, and run locally on the server.

 

Debug example

Problem: When looking for users in Quickr, none of the LDAP users can be found. The only user that can be found is the *locally-created* one.

• Several users were created in LDAP;
• LDAP users can log-in to the Quickr server using their credentials;
• *One* test user was created *locally*, in Quickr, using the Admin interface;

Solution: In this case, it was a filter problem. We were using:

<supportedLdapEntryTypes> 
               <supportedLdapEntryType name="Person" 
                rdnAttrTypes="cn" 
                objectClassesForRead="inetOrgPerson" 
                objectClassesForWrite="inetOrgPerson" 
                searchBases="ou=WebSphere,o=John"/> 

When we should be using:

<supportedLdapEntryTypes> 
               <supportedLdapEntryType name="Person" 
                rdnAttrTypes="cn" 
                objectClassesForRead="inetOrgPerson" 
                objectClassesForWrite="inetOrgPerson" 
                searchBases="o=John"/>