官术网_书友最值得收藏!

Chapter 3. IBM Lotus Quickr Domino Architecture

The Lotus Quickr Services for the Lotus Domino product has a long standing architecture which has grown over many years of product development. The roots started with the Lotus QuickPlace v1.0 product released during 1999, a product that ran on top of Lotus Domino v5.0. Since those early days many wide range of features have been introduced. With the introduction of Lotus Quickr 8.0 in 2007 a wide range of expanded services were brought to the market. This included a broad expansion into the Web 2.0 space as well as the Desktop Connectors.

The following sections will outline the basic architecture of the Lotus Quickr Services for Lotus Domino product and cover various deployment architectures.

  • Product components
  • Server architecture
  • Browser architecture
  • Desktop connector architecture
  • Deployment topologies

Product components

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.

主站蜘蛛池模板: 鹰潭市| 七台河市| 福清市| 大足县| 明水县| 怀化市| 汾西县| 琼结县| 巴塘县| 宜章县| 湛江市| 常熟市| 乌鲁木齐县| 呼图壁县| 德格县| 沭阳县| 江门市| 霞浦县| 尖扎县| 澎湖县| 全南县| 泽普县| 新巴尔虎右旗| 买车| 宕昌县| 高淳县| 贺州市| 安化县| 温泉县| 方正县| 宝清县| 石渠县| 武宣县| 义马市| 太湖县| 中宁县| 满城县| 阿图什市| 合肥市| 海淀区| 卓资县|