The Lotus Quickr Domino product is based fully on a Lotus Domino platform. It leverages a range of core services for the Lotus Domino server from the security, directory, HTTP, and JVM. The Lotus Quickr components are then built on top of this, providing custom page creation, user security, administration, and place creation/management services to name a few.

Depending on the final configuration, additional components including an LDAP server(s) or load balancers may be required. However, it is possible to build a fully functional Lotus Quickr server that resides on a single server. It should be noted that although a single server deployment is possible, it doesn't provide any form of failover or scalability. There are numerous production customer environments that are built on this type of topology.

As the requirements for service failover and expanded scaling come into play, the Lotus Quickr product supports full clustering support. Similar to most other elements the core Lotus Domino product features are leveraged to provide this support. This means that the Lotus Domino clustering functions provide the foundation of clustering in Lotus Quickr.

The basic design requires first the Lotus Domino server stack to be deployed and configured. If there are no other Lotus Domino servers deployed within your environment then this would mean setting up the user directory, mail routing, and general administration infrastructure.

The Lotus Quickr product is then installed on top with a minimal amount of additional responses requested during this process. Really the only question is for an administrative user for the Lotus Quickr server itself. This user is locally defined and does not exist in the Lotus Domino directory or LDAP server. It is worth noting that if this user does exist outside of the Lotus Quickr server then it can cause problems. For example, if the user exists in the Lotus Domino directory various issues can arise. This includes challenged authentication as well as problems accessing the browser-based administration pages. The key reason this causes problems is because the Quickr application cannot determine which user is the correct one, between the local user and the directory-based user.

After the basic product installation is completed the configuration process starts. This configuration is covered in other sections of this book as well as in the product documentation.