2. Deployment and Performance Considerations for Quickr Domino Services
Mark Curran / System Test Engineer / IBM
Bruce Roberts / Quickr Architect / IBM

3. Agenda (very) Quickr Overview of Quickr on Domino
Typical Quickr-Domino deployment topologies
IBM's experience deploying, managing and testing Quickr internally
Configuring and Tuning your Quickr Deployment
Administering your deployment
New for 8.1: Admin Console and Web Cache improvements
Q&A

4. Help Organizations Share Information4 4
What is ...
Help Organizations Share Information
Mergers & Acquisitions
Innovation Place
and ... subscribing to key sites to keep a “finger on the pulse”
Finance / Accounting
Sales
Human Resources
Marketing
R&D
What is Lotus Quickr ? Let’s first answer from a business perspective
Budget planning
Annual report preparation
Bid mgmt.
Shared sites with vendors
Competitive “Win room”
RFP response
Event planning
Employee benefits
New employee resource center
New Content tracking
Product launch
Budget planning
Competition room
Project mgmt.
R&D Place
Best Practices

5. Lotus Quickr Places can be created simply

7. Lotus Quickr Install
Web application installed on an existing Lotus Domino server tied into the server's HTTP task
Lotus Quickr 8.1 installs over Lotus Domino 8.0.1
If installing in a cluster customer have to install on all nodes in the cluster 7

8. Lotus Quickr Functional Topology8
Lotus Quickr Functional Topology
Corporate LDAP Directory:
IBM Tivoli Directory Server 6 & 6.1
IBM Lotus Domino , 8.0+
Microsoft Active Directory 2003
Sun Java™ System Directory Server 5.2®
Browser:
Microsoft® Internet Explorer 6.0 SP2 & 7.0
Mozilla Firefox 2.0 on Windows, Linux,
Apple Safari 3.0 on Mac OS X version 10.4
Rich Clients:
IBM Lotus Notes or later
IBM Lotus Sametime or later
Microsoft Office XP, Microsoft Office 2003, or Microsoft Office 2007
Windows Explorer - Microsoft Windows XP or Microsoft Windows Vista
Feed Support :
Atom based Readers
The most basic deployment of a Connections service requires a WAS 6.1 app server, an LDAP directory and a relational database. Multiple clients are supported – although only a web browser is required.

9. Lotus Quickr Services for Domino - Clustering
Lotus Quickr Clusters behave the same as Lotus Domino Clusters
The servers in a cluster contain replicas of databases that you want to be readily available to users at all times
Data updated on one server is virtually immediately available to all other Lotus Quickr servers in the cluster through replication
The Lotus Domino server continuously synchronizes databases so that whichever replica a user opens, the information is always identical. 9

10. Load Balancing on a Cluster
With load balancing, a virtual server is used to distribute HTTP requests so that the physical servers share the user load.
Each physical server and place has an entry in the Place Catalog.
Recommended: Set up a Place Catalog server, which is a server with a Place Catalog that multiple servers share.
All servers in a cluster should use the same qpconfig.xml settings. 10

11. Lotus Quickr Enterprise Topology
1111
Lotus Quickr Enterprise Topology
Corporate LDAP
Directory
Clients
The most basic deployment of a Connections service requires a WAS 6.1 app server, an LDAP directory and a relational database. Multiple clients are supported – although only a web browser is required.

12. Lotus Quickr Auxiliary Deployment Options
IBM Lotus Quickr services for Domino supports a number of Third Party such as:
Netegrity SiteMinder 5.5 and 6.0
Tivoli Access Manager (TAM) 5.1 and 6.0
HTTP server included with Lotus Domino and we support Forward and reverse proxy servers via:
Apache HTTP Server
WebSphere Edge Server 6.0
IBM Lotus Quickr services for Domino supports integration capabilities with other offerings within the Lotus Portfolio - such as Sametime and Connections
Online Awareness within Quickr Web UI via Sametime
People Card within Quickr Web UI via Connections Profiles
Support added in hotfix for using Native Domino Directory for deployment with Quickr and Sametime

13. Reliability & Performance Test Evaluations
Pick meaningful subset of the configurations tested, cross platform concerns
Define meaningful set of operational profiles to drive workload
Realistic transaction rates per user
Realistic overall transaction rate, max 75% of product capacity
System Verification Test (SVT) workloads target 5 day durations
Performance workloads typically last less than 6 hours

14. SVT Data Population and Content Attrition Decisions for Domino Quickr
High Level
Standard Places, Wiki Place, Blog Place
25% of content
Average Level
Standard Places, Wiki Place, Blog Place
50% of content
Low Level
Standard Places, Wiki Place, Blog Place
25% of content 14

15. Reliability & Performance Test Conclusions
Summary of Quickr 8.1 Base Population Levels
SVT tested 5 day runs on Windows, AIX & i5/OS platforms using a variety of hardware types and levels
SVT initial database size starting our reliability runs is 35GB and after our 5 day run this database has grown to around 50GB in size
Our best results for overall health, stability and transaction response times were seen on systems running in a clustered configuration, with multi-cpu and FAStT Storage Server

16. IBM Test Recommendations
Clustered configuration is recommended
Load balancing
Fail-over
Redundancy
Hardware Configuration
Fast Disk is recommended, such as a FAStT Storage Server
Quickr can take advantage of multi-cpu systems
Upgrade to 8.1
Significant performance improvements have been made over 8.0 and
Reduced load on directory servers
Improved response times for certain operations
Improved overall throughput
Absolutely recommended if you are going to put Lotus Quickr into production

17. Example Deployment: IBM Internal Site
Part of “Technology Adoption Program” (TAP)
Available to a subset of the IBM population 17

18. More Tuning Microsoft® Windows® Network Resource Tuning
Modify Windows registry entries
Details in Lotus Quickr Tuning Guide and this IBM Redbook®
Change caching parameters in Notes.ini
NSF_DBcache_maxentries=3000
NSF_DBUCACHE_MAX_ENTRIES=3000
Lotus Domino Quickr shares the same best practices as any other nsf
Search the Lotus Domino 8 InfoCenter online under the 'Performance' topic 18

19. Maintenance
Lotus Quickr databases are Lotus Domino databases and benefit from regular Lotus Domino maintenance and upkeep
Rebuilding search indices
Compacting
Etc.
Please refer to the “Administrator Guide for Lotus Domino Server Maintenance” for guidelines. 19

20. Administering a Deployment
Command Line tool
New for 8.1
Admin Console
Improvements in Web Cache

21. Administering Quickr-Domino
Command line
QPTOOL integrated with Domino Console
Support for management tasks like
Update membership across places (e.g. user re-name)
Reset Passwords (e.g. forgotten password)
Send mail to place members/managers
Lock/unlock/archive places
Place Reporting
And more

22. New for 8.1: Admin Console

23. One place to go

24. Take Action – simple, powerful

25. Easily see more place detail

26. Place Detail

27. Policies - **NEW** for Domino

28. Policy “inheritance”

29. Demo

30. Web Cache Improvements in 8.1

31. Web Cache
Web Cache is used to store HTTP pages responses on disk for future retrieval
Can significantly reduce load on server when cache hit rates are high 31

32. Web Cache – Configuration
Notes.ini
QuickPlaceWebCacheEnabled=<0 – disabled, 1 - enabled>
QuickPlaceWebCacheDir= <a directory on a RAID disk system or separate disk from Quickr server code>
QuickPlaceWebCacheLimitInMB=<size in MB of web cache files on disk >
QuickPlaceWebCacheGCIntervalInMIN=<# minutes between cleaning out web cache LRU files to get down to Cache Limit> 32

33. Web Cache – how to check effectiveness
In Lotus Domino Console -
“Show QuickPlace.Cache.RequestFileCache.HitRate” shows % of cache hits for user requested pages.
Want high hit rate
At least 15%, closer to 30% preferred
Less than 10% and cache is probably more of a negative. 33

34. Web Cache – Changes in 8.1 System isn't locked when GC happens.
Garbage Collections much improved
System isn't locked when GC happens.
Prior to 8.1 – GC can cause response times to spike.
Fixed problem with QuickPlaceWebCacheLimitInMB value
Prior to 8.1 – values over 2000 can cause Cache to grow unbounded 34

35. References Developer Works Wiki Best Practices
Best Practices
Deployment tips including two Quickr-Domino deployment scenarios
Lots more.
Lotus Quickr Tuning Guide
Domino Server Maintenance:
Lotus Quickr Guide to Clustering for Lotus Domino 35

36. IBM Lotus Quickr at Lotusphere
Sessions
JMP303: IBM Lotus Quickr in Action
ID306: IBM Lotus Quickr Technical and Architecture Overview
ID307: Deployment and Performance Considerations for IBM Lotus Quickr Domino Services
ID308: Mastering the Collaborative Content Continuum
ID309: Lotus Quickr and Enterprise Content Management: The Complete Content and Collaboration Solution
BP204: Enhancing IBM Lotus Quickr for IBM Lotus Domino with Web 2.0 Integration
BP401: Best Practices for Creating Customized Solutions for IBM Lotus Quickr
AD403: Customizing IBM Lotus Quickr Domino Services
AD404: Customizing IBM Lotus Quickr Portal Services
AD405: Are You REALLY Taking Advantage of an Integrated Lotus Collaboration Experience?
AD409: Build for Success: Getting the Most Out of Lotus Collaboration and Social Software
SHOW202 : Show 'n Tell: Developing for Lotus Quickr Domino Services
Birds-of-a-Feather
Demos
Meet the developers stations
... and more ...

37. Q&A

38. Legal disclaimer © IBM Corporation 2008. 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 IBM’s 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 IBM’s 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.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, 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.