Legal Disclaimer
2009 IBM Corporation. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBMs current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBMs sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. All references to Renovations refer to a fictitious company and are used for illustration purposes only.
Quick Intro to Domino cluster
Agenda
Notes related to Quickr in a clustered environment Demo environment deployment topology Creating the Domino cluster Modifications of the scheduled qptool commands on the notes.ini Place catalog configuration on the clustered environment Webpage cache Settings in the notes.ini file Creating replica stubs Domain search configuration Hotfix install in a clustered environment Questions & Wrap-up
Domino Clustering
Domino cluster A Domino cluster can go from 2 to 6 domino servers that provide users constant access to data Balancing the load between servers improve performance Databases that you want accessible by users all the time and in a constant manner are replicated in the cluster With Domino clustering, all the servers in the cluster continually communicate information regarding server availability and continually synchronize the databases replicas.
Using the IBM Lotus Notes or the Domino Administrator to make changes, usually to the Lotus Domino Directory. Making changes using the file system such as modifying the NOTES.INI file or qpconfig.xml file or inspecting HTTP logs.
Changes made through the Site Administration link do not replicate, you must make these changes on each server in a cluster! When you run a qptool command on a server in a cluster, Lotus Quickr applies the command only to the server on which you run it. The results of the command then replicate to the other servers in the cluster.
Example: if you lock a place on one server in a cluster, the place is locked immediately only on that server. The place is locked on the other servers after replication occurs
TDS LDAP
Masterclass03
Masterclass01 Masterclass02
Usual steps to cluster the domino server... From the domino administrator client create the cluster (hands on material) Enable replication between the server members of the cluster
Load balancer
Method for HTTP requests implementation After the install follow the dispatcher configuration to add the IP addresses of the existing Quickr domino web servers.
These commands should run only on the Place Catalog server, to avoid duplication of newsletters and server tasks. So remove them from any other server part of the cluster (in our case they will need to be removed from masterclass11) qptool newsletter -daily -a, from the ServerTasksAt1 parameter qptool remove -cleanup, from the ServerTasksAt2 parameter qptool placecatalog -push and qptool deadmail -cleanup from the ServerTasksAt3 parameter
On the Place Catalog server only (in our case masterclass10), The task updates statistics for the "virtual server" place documents. serverTasksAt6=qptool placecatalog -update
Place catalog
The Place Catalog contains data on the Quickr servers, and the places, rooms, and members on those servers. Each server, place, and room has a separate entry in the Place Catalog. The Place Catalog enables administrators to use the qptool report command, or an XML interface to the Lotus Quickr Java XML API, to report statistics on places and servers. It enables place members to use My Places to see a list of places they belong to and statistics about those places, as well as to search content across places and servers.
Place catalog
Use the same place catalog across the cluster (replication) Delete the place catalog from second and subsequent nodes of the cluster Create replicas of the place catalog on the second and subsequent nodes of the cluster Update the qpconfig.xml with the cluster and place catalog settings
To update PlaceSize, PlaceLastAccessed, and PlaceLastModified statistics load qptool placecatalog -push -a
To account for any place membership changes made during the server downtime load qptool unregister -placecatalog -p place load qptool register -placecatalog -p place
cross-place searching
Configure cross-place searching to enable external place members to use the advanced search feature to search multiple places.
Enable the Domain catalog on the servers From the names.nsf: Server Tasks > Domain Catalog, and in the Domain Catalog field select Enabled Enable the Domain indexer From the names.nsf: Server Tasks > Domain Indexer, and in the Schedule field, click Enabled Make sure that the catalog.nsf database is replicated between the 2 servers on the cluster Enable search_places
From the qpconfig.xml of each node <search_places enabled="true" anonymous="true"> <domain_catalog_server ssl="false"> <port>80</port> <domino_server_name>masterclass01/acme</domino_server_name> <path_prefix></path_prefix> <hostname>masterclass01.mul.ie.ibm.com</hostname> </domain_catalog_server> </search_places>
Upon subsequent requests for the page, the server retrieves and provides the cached copy, as long as it is still valid. If the server is brought down, the existing cache is maintained after the server is brought back up.
Time interval, in minutes, for cache cleaning. If omitted, or if a negative value is specified, then the interval is 60 minutes. QuickPlaceWebCacheUsers=anonymous Enables caching for anonymous users only. If omitted, and by default, caching is enabled for all users. QuickPlaceWebCacheLogging=level Specifies the level (1, 2, 3), for cache logging. Level 1 is the least detailed and 3 is the most detailed. Logging is written to domino_data_root/log.nsf.
qptool replicamaker
qptool replicamaker does the following:
Creates replica stubs for MAIN.NSF and CONTACTS1.NSF on the local server or another server when a place or PlaceType is created. Makes a new copy of SEARCH.NSF on the local server or another server when a place is created. Creates replica stubs on the local server or another server for any new rooms.
Using qptool replicamaker (usage from the main cluster server: masterclass01)
For the new place test on masterclass01, create replica stubs on the server masterclass02/ibm load qptool replicamaker -p test -t masterclass02/ibm For the new place test on masterclass02, create replica stubs on the server masterclass01/ibm load qptool replicamaker -p test -s masterclass02/ibm For all new places, rooms, and PlaceTypes created on the masterclass01, create replica stubs on masterclass02. load qptool replicamaker -t masterclass02/ibm -a For all new places, rooms, and PlaceTypes on masterclass02, create replicate stubs on the masterclass01 server. load qptool replicamaker -s masterclass02/ibm -a
qptool replicamaker
To ensure that replica stubs of new places, rooms and PlaceTypes are created quickly and that replication then populates the places, rooms, and PlaceTypes quickly, do the following: Create Program documents in the Domino Directory that runs the qptool replicamaker command with the -a argument between the servers in a cluster every 10 minutes. If there are more than two servers in the cluster, you must use more than one Program document to run the qptool replicamaker command to ensure that replica stubs are created on all servers in the cluster.
Schedule non-cluster replication between all servers in the cluster to occur at least every 20 minutes, to compensate for any lags in cluster replication.
Run the qptool upgrade commands only on the Main server. Bring the servers back online and enable replication.
Allow the servers to replicate the updated files from the Main server.