Front cover
Domino Web Access
ccess 6.5
for Sun Solaris
laris 9
Discover the features and benefits of running
Domino Web Access 6.5 on Solaris 9
Learn about hints and tips for
installation and setup
Gain helpful knowledge about
performance tuning and testing
Wunchon (Indy) Beak
John Bergland
ibm.com/redbooks
Redpaper
International Technical Support Organization
Domino Web Access 6.5 for Sun Solaris 9
March 2004
Note: Before using this information and the product it supports, read the information in
“Notices” on page v.
First Edition (March 2004)
This edition applies to Domino Web Access 6.5 and the Solaris 9 operating system.
This document created or updated on March 5, 2004.
© Copyright International Business Machines Corporation 2004. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9. . . . 1
1.1 Domino Web Access 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 What is Domino Web Access? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 New features and benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.1 General enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2 Mail enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2.3 Calendar and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.4 Template customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.5 Usability enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.6 Print enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.7 Mozilla support for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.8 New administrative features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.9 Domino Web Access 6.5 performance improvements . . . . . . . . . . . 10
1.2.10 More information about Domino Web Access 6.5 . . . . . . . . . . . . . . 11
1.3 Sun Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.1 Highlights of Sun Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.2 System requirements for Sun Solaris 9. . . . . . . . . . . . . . . . . . . . . . . 13
1.3.3 Domino Web Access 6.5 requirements for Solaris 9. . . . . . . . . . . . . 13
1.3.4 For more information about Sun Solaris 9 . . . . . . . . . . . . . . . . . . . . 13
1.4 Structure of this paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 2. Installation hints and tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 Pre-installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.2 Creating group and user account for Domino . . . . . . . . . . . . . . . . . . 17
2.1.3 Checking disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 Installing Domino 6.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Preparing users for Domino Web Access 6.5 . . . . . . . . . . . . . . . . . . . . . . 25
2.3.1 Registering new users for Domino Web Access . . . . . . . . . . . . . . . . 26
2.3.2 Converting users to Domino Web Access. . . . . . . . . . . . . . . . . . . . . 26
2.4 Domino Web Access configuration settings . . . . . . . . . . . . . . . . . . . . . . . 27
© Copyright IBM Corp. 2004. All rights reserved.
iii
2.4.1 Configuration settings and impact on performance. . . . . . . . . . . . . . 28
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9 . . . . . . . . . . . . . 33
3.1 Tuning guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2 Sun Solaris performance monitoring options . . . . . . . . . . . . . . . . . . . . . . 34
3.2.1 Stat commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2.2 SE Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.3 Lotus Domino 6.5 performance monitoring options. . . . . . . . . . . . . . . . . . 41
3.4 Tuning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.4.1 Solaris kernel tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.4.2 Solaris file system tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.4.3 Domino tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4.4 Network tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.5 Further reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 4. Performance testing: Methodology and results. . . . . . . . . . . . 55
4.1 Our test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.1 Hardware and software setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.2 Simulation methodology and our workload . . . . . . . . . . . . . . . . . . . . 56
4.1.3 Performance improvement process . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2 Performance studies and the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.1 Study 1: Is the disk system a bottleneck? . . . . . . . . . . . . . . . . . . . . . 58
4.2.2 Study 2: Can CPU utilization be improved by fsflush tuning? . . . . . . 59
4.2.3 Study 3: Can page-in rates be improved by segmap_percent? . . . . 60
4.2.4 Study4: Network improvement? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.2.5 Study 5: More HTTP threads = faster? . . . . . . . . . . . . . . . . . . . . . . . 63
4.3 Conclusion: Test summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
iv
Domino Web Access 6.5 for Sun Solaris 9
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to IBM for the purposes of
developing, using, marketing, or distributing application programs conforming to IBM's application
programming interfaces.
© Copyright IBM Corp. 2004. All rights reserved.
v
Trademarks
The following terms are trademarks of the International Business Machines Corporation and/or Lotus
Development Corporation in the United States, other countries, or both:
ibm.com®
iNotes™
Domino®
IBM®
Lotus Notes®
Lotus®
Notes®
Redbooks(logo)
Redbooks™
Sametime®
Tivoli®
™
The following terms are trademarks of other companies:
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United
States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.
C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure
Electronic Transaction LLC.
Solaris and SunONE are registered trademarks of Sun Computer Corporation.
Other company, product, and service names may be trademarks or service marks of others.
vi
Domino Web Access 6.5 for Sun Solaris 9
Preface
IBM® Domino® Web Access (iNotes™) is an advanced Web client that delivers
leading Domino messaging, collaboration and Personal Information
Management (PIM) capabilities to Web browsers. It allows users to leverage the
reliability and security features of IBM Lotus Domino server, while benefitting
from the flexibility of access to information through a Web browser. A user may
be at an Internet kiosk or another user's PC, and they may be online or
disconnected from the network. Regardless, that user can achieve ubiquitous,
authenticated access to supported Lotus Domino data, including e-mail,
calendar, to-do list, personal contacts and notebook.
The Solaris 9 Operating Environment (OE) is the foundation for Sun systems,
from smaller departmental servers to massive, clustered servers with more than
100 CPUs. Designed for multiprocessing and 64-bit computing, Solaris software
delivers a consistent computing environment that scales to handle heavy traffic,
huge data sets, and CPU-intensive problems. Solaris 9 OE minimizes planned
and unplanned downtime, reducing administration errors and simplifying
troubleshooting. In doing so, it keeps mission-critical applications available and
ensures high-speed, reliable access to data. The Solaris 9 OE is scalable,
available, manageable, and secure.
This IBM Redpaper provides a technical overview of Domino Web Access 6.5. It
discusses how to install and configure Domino Web Access 6.5 on Solaris 9. It
also discusses performance tuning considerations for both Solaris 9 and Domino
Web Access 6.5.
This Redpaper explains:
򐂰 The new features included with Domino Web Access 6.5 for Solaris 9
򐂰 Basic installation and setup guidelines for Domino Web Access 6.5 on
Solaris 9
򐂰 General Solaris performance monitoring techniques that are appropriate for
Domino Web Access 6.5
򐂰 Performance tuning suggestions for optimizing a Domino Web Access 6.5
install on Solaris 9
򐂰 Results and analysis of basic performance benchmarks that demonstrate the
scalability of Domino Web Access 6.5 on Solaris 9
© Copyright IBM Corp. 2004. All rights reserved.
vii
The team that wrote this Redpaper
This Redpaper was produced by a team of specialists from around the world
working at the International Technical Support Organization (ITSO), Cambridge
Center.
Wunchon (Indy) Beak is a software engineer with Lotus software support
operations, Crash and Performance Team, specializing in the UNIX/Linux
platform. He has been supporting Domino for over three years. Before joining
North American Domino support, he worked in IBM Software Technical Sales
Support Team in Korea, assisting with Lotus Critical Situations. Indy has a
Masters of Science degree in computer science and has experience
programming in Java, C++, C and UNIX shell scripts. Prior to writing this
Redpaper, he was responsible for testing the Domino 6.5 Milestone 2 build on
Solaris.
John Bergland is a project leader at the ITSO, Cambridge Center. He manages
projects that produce Redbooks™ about Lotus Software products. Before joining
the ITSO in 2003, John worked as an Advisory IT Specialist with IBM Software
Services for Lotus (ISSL), specializing in Lotus Notes and Domino messaging
and collaborative solutions.
The authors thank the following people for their contributions to this project:
򐂰 Catherine Stone, IBM Lotus Software
򐂰 The IBM/Lotus Performance Testing Team, Westford, Massachusetts,
especially the contributions and support of:
–
–
–
–
–
–
Louis Bradbard
Rich Buck
Andy Nolet
James Powers
Razeyah Stephen
Nirmala Venkatraman
򐂰 The IBM/Lotus Common Services Team, Westford, Massachusetts,
specifically the contributions and support of:
– Steve Davis
– Bill Hankard
򐂰 The contributions and technical support from Sun Microsystems, particularly
the help from:
– Gopa Kumar
– Eric Sosman
viii
Domino Web Access 6.5 for Sun Solaris 9
򐂰 Bob Sommers, Sun Microsystems
򐂰 Shane Kilmon, member of the Lotus RAS Engineering team, for his efforts in
reviewing the material and contributing to the success of this project
Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook
dealing with specific products or solutions, while getting hands-on experience
with leading-edge technologies. You'll team with IBM technical professionals,
Business Partners, customers, or all three.
Your efforts will help increase product acceptance and client satisfaction. As a
bonus, you'll develop a network of contacts in IBM development labs, and
increase your productivity and marketability.
Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want our papers to be as helpful as possible. Send us your comments about
this Redpaper or other Redbooks in one of the following ways:
򐂰 Use the online Contact us form found at:
ibm.com/redbooks
򐂰 Send your comments in an Internet note to:
redbook@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
1 Rodgers Street
Cambridge, MA 02052
Preface
ix
x
Domino Web Access 6.5 for Sun Solaris 9
1
Chapter 1.
Introduction to Domino Web
Access 6.5 on Sun Solaris 9
IBM® Lotus® Domino® Web Access 6.5 (formerly IBM Lotus iNotes™ Web
Access) is a sophisticated Web client. It gives end users many of the messaging
and collaboration features previously available only with a Lotus Notes® client.
Browser users can take full advantage of Domino services through an
ultra-intuitive, easy-to-use interface, both on and offline, seamlessly. Domino
Web Access was architected using the latest Web application development
technologies and can be centrally administered. This helps organizations to drive
down deployment costs and reduce total cost of ownership.
By combining the improved functionality and performance of IBM Lotus Domino
Web Access 6.5, together with the reliability, performance and scalability of Sun’s
Solaris 9 platform, you can offer your organization an industry leading messaging
and collaborative solution. This chapter introduces you to both Domino Web
Access 6.5 and Sun Solaris 9. But first it begins by presenting an overview of this
Redpaper.
Those of you who are already familiar with both the new features of Domino Web
Access 6.5 and Solaris 9 may want to proceed to Chapter 2, “Installation hints
and tips” on page 15.
© Copyright IBM Corp. 2004. All rights reserved.
1
1.1 Domino Web Access 6.5
Domino Web Access 6.5 delivers Lotus Notes and Lotus Domino capabilities on
the Web. It provides users with fully functional access to corporate messaging
services, collaborative services, and personal information management,
regardless of where or how they may be working.
Figure 1-1 illustrates the Welcome Page from within a Mozilla 1.3.1 browser. By
clicking one of the tabs across the top of the Welcome page, users can access
their mail, calendar, to-do list, contact list, or notebook. See 1.2, “New features
and benefits” on page 4, for an in-depth review of the features and functionality
included in Domino Web Access 6.5.
Figure 1-1 Domino Web Access 6.5 Welcome Page
2
Domino Web Access 6.5 for Sun Solaris 9
The key goals and functional improvements for this release of Domino Web
Access are:
򐂰 Integrated Lotus Sametime® Instant Messaging: Domino Web Access
integrates the Lotus Sametime Instant Messaging function. This provides
presence awareness and enable users to initiate chats and collaborate with
colleagues, without launching a separate application.
򐂰 Performance and scalability improvements: Domino Web Access software
delivers new levels of scalability and support for high numbers of concurrent
users. For example, Domino Web Access 6.5 caches static data, such as
e-mail forms, for greater efficiency. This eliminates the need for Domino Web
Access 6.5 to pull this data from disk for each session, so users should see a
marked improvement in performance. Additionally, when combined with Linux
as a supported platform for Lotus Domino server as the back end for Lotus
Domino Web Access software, this provides several options for increased
flexibility and scalability.
򐂰 Security rich environment: Security is paramount in a browser client.
Domino Web Access 6.5 supports basic authentication, session
authentication, secure logoff, Secure Sockets Layer (SSL) encryption, local
offline file encryption, and active content filtering.
򐂰 Usability and productivity improvements: In addition to overall usability
improvements, specific functionality and tools are improved to help make
users more productive. Some of the highlights include:
– Follow-up flags: Users can mark entries in their mail with a follow-up flag to
indicate that further action is warranted. This maximizes user
responsiveness to incoming requests.
– Mail Rules/Spam Blocking functionality: Block Mail from Sender function
allows users to block future messages from a specified sender from
display in the inbox view and automatically moves them to the Junk Mail
folder.
– Enhanced Calendaring and Scheduling tools: Advanced calendaring and
scheduling capabilities in Lotus Domino Web Access 6.5 software allow
users to perform even more actions from a browser. This further enhances
their productivity.
򐂰 End-to-end Linux solution: Domino Web Access 6.5 lets you access Lotus
Domino on a Linux server, from a Linux desktop. This gives you a leadingedge, end-to-end collaborative solution for Linux. Although Linux is not the
focus of this paper, it is significant to note that Domino Web Access 6.5
represents the first Domino messaging client available for Linux.
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
3
1.1.1 What is Domino Web Access?
Domino Web Access 6.5 is built upon Lotus Domino technology. It requires an
underlying Domino server to provide much of its functionality. It serves as the
latest generation Web-based client solution to Domino messaging and Personal
Information Management (PIM) capabilities such as e-mail, calendar, scheduling,
group calendar and scheduling, to-do items, contact, follow-up, and integrated
notebook.
Domino Web Access exclusively runs within Web browsers and communicates
with Domino server only using Hypertext Transfer Protocol (HTTP). It was built
using extensive Dynamic Hypertext Markup Language (DHTML) technology such
as JavaScript, HTML 4.0, CSS, and the HTML DOM to provide a sophisticated
HTML based user interface. It also can be collaborated with Domino Off-Line
Services (DOLS) and IBM Lotus Sametime Instant Messaging.
Two files contain all of Domino Web Access specific code. One is iNotes6.ntf and
the other is Forms6.nsf. Notes6.ntf is the new Domino Web Access mail
template. All Domino Web Access users are required to replace their mail
template to this to access their mail files using Domino Web Access from Web
browser. When you register new Domino Web Access users, make sure that you
use this new Domino Web Access mail template, iNotes6.ntf. Forms6.nsf
contains graphical user interface (GUI) codes for Domino Web Access. Changing
the mail template does not make any differences to their Notes client use.
To learn more about their use of DHTML, read the Lotus Developer Domain
(LDD) article, “Exploiting dynamic HTML: Lessons from iNotes Web Access”, by
Vinod Seraphin and David Dejean. This article provides valuable insight into the
use of DHTML for Domino Web Access design.
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b380/77d60e9c
1a10909f85256b9d00593986?OpenDocument&Highlight=0,inotes
1.2 New features and benefits
Significant enhancements are introduced in Domino Web Access 6.5 with the
iNotes6.ntf template. Domino Web Access 6.5 provides more Notes-like features.
1.2.1 General enhancements
Several of the most notable enhancements to Domino Web Access are:
򐂰 Lotus Sametime Instant Messaging integration: Domino Web Access now
provides integration with Lotus Sametime Instant Messaging to provide
presence awareness and instant messaging capability directly from within the
4
Domino Web Access 6.5 for Sun Solaris 9
Domino Web Access client. The user can see who is online in the Inbox view,
without launching a separate Instant Messaging client or separate browser
window.
From any name entry, a user can open a chat session with another user by
clicking the green or yellow (online) indicator. They begin a chat by using the
Chat button shown in Figure 1-2.
Figure 1-2 Chat button
With Domino Web Access 6.5, single signon is used to log into both the mail
client and Lotus Sametime Instant Messaging. Additionally, there is a built in
buddy list which is stored on the server and reloaded from the server each
time a user logs on. Figure 1-3 shows an example of the Instant messaging
Chat window.
Figure 1-3 Instant messaging window
򐂰 Domino Web Access Redirect: Domino Web Access Redirect is a new
feature which allows users to access their mail file, without knowing the name
of either their mail file or the name of their mail server. The Webmail Redirect
is a database that resides on the server and processes Uniform Resource
Locators (URLs). With Domino Web Access Redirect, users do not need to
know the name of their mail file or mail server. Instead. They need only to
know the name of the Domino Web Access Redirect server. This can be any
server in their Domino infrastructure. Domino Web Access Redirect uses
Domino authentication methods to access the person document in the public
name and address book (the Domino Directory) to obtain the information on
which server the user’s mail file is stored. It takes this information to redirect a
user's browser to their mail file.
Specific configuration details for Domino Web Access Redirect are outside of
the scope of this paper. However, you may refer the redbook Domino Web
Access 6.5 on Linux, SG24-7060, for more information about how to set up
and customize this new feature.
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
5
򐂰 Archive locally with offline support: Beginning with Lotus Notes and
Domino 5.0.8, users had the ability to create a server-based archive of their
mail file. Domino Web Access 6.5 users (using Internet Explorer) now have
the ability with Domino Web Access 6.5 to create and store an archive locally,
thereby extending offline support. This further allows users to maximize their
productivity while offline. Users can easily access their local or server-based
archive from a link in the Domino Web Access user interface.
1.2.2 Mail enhancements
The latest enhancements to mail are:
򐂰 Copy into Calendar/To Do entries: Domino Web Access users can now
copy the body of a received message into a new To Do item or calendar entry
with a single click. This saves time and allows them to more efficiently
manage their daily tasks. It is important to note that this function even works
with the entire rich-text body field, such as a case with inline images, tables,
and so on.
򐂰 Send and file messages: Similar to Notes client functionality, the Domino
Web Access user can now send and file new messages in a single step.
Clicking the Send & File button (Figure 1-4) sends the document and files it in
a folder all in one step. This saves time and helps users efficiently manage
their inbox and folders.
Figure 1-4 Send & File button
򐂰 Create page breaks in mail messages: While creating new messages,
users can now insert a page break directly into the rich-text body of the mail
message. This ultimately provides them with much greater control over the
pagination and appearance of their message.
򐂰 Add public contacts to a personal contact list: In the Select Addresses
dialog, users now can add anyone from the public Domino Directory to the
personal contact list by simply clicking the Copy button.
򐂰 View only unread mail: In the View menu, a special new function is added
called Show Unread only (see Figure 1-5). Users can select this function in
the View menu, which then displays only the unread mail in the user’s view or
folder.
6
Domino Web Access 6.5 for Sun Solaris 9
Figure 1-5 Show unread only
򐂰 Multiple browser window support: Users can open every functional area of
Domino Web Access in a separate browser window. This includes the
Welcome Page, Mail, Calendar, To Do list, a user’s Personal Address book,
and their Notebook.
򐂰 Encrypt mail messages: Users can send, sign, and verify Domino Web
Access encrypted mail messages with the Sign and Verify Notes Encrypted
Messages feature. These mail messages use the same encryption that is
used in Lotus Notes.
򐂰 Reply with history using Internet-style formatting: When users reply with
history to a mail message, they can select Internet-style formatting that
begins each line of the original message with an angled (>) bracket. After the
message is converted to plain text, the brackets make it easier for users to
distinguish the new response text from the original text.
򐂰 Mark entries for follow up: Users can mark important mail messages and
contact entries with a follow-up flag to indicate that they need to take further
action on that message or with that contact.
Figure 1-6 Follow-up menu and buttons
򐂰 Block mail from sender: Users can add a recipient's name to a block sender
list to prevent future messages from the specified e-mail address from
reaching them. This mail rule denies entries from that e-mail address and
removes messages from the system.
򐂰 Use the phone message form to take a message: Users can use the phone
message form in Domino Web Access to notify another user of a phone
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
7
message. They simply click New and choose Phone Message to create a
message.
1.2.3 Calendar and Scheduling
The following enhancements were made within the functional areas of
Calendering, Scheduling, and To-Do entries:
򐂰 Customize the Welcome page with more Calendar options: These options
allow a user to display their schedule from a one-day or two-day format, up to
10-day format on the Domino Web Access Welcome page.
򐂰 Pencil in meetings: Users can mark a meeting invitation, appointment,
anniversary, event, reminder, and to-do with the Pencil In option. Any one with
access to their calendar can view the details of a penciled in entry. Penciled in
entries appear as free to those who perform a free time search.
򐂰 Specify more than one time zone: Domino Web Access now lets users
show two time zones—a start time zone and an end time zone—in calendar
entries and in the calendar view (Figure 1-7).
Figure 1-7 Multiple time zone support
򐂰 Unaccepted calendar invitations appear on calendar view: When users
receive a calendar invitation, it appears not only in their Inbox view, but also
their calendar view. This gives users one more way in which to manage their
calendar.
򐂰 Delegate your calendar: Users can let others schedule and respond to
meeting invitations by delegating their calendar to them.
򐂰 Create group to do's: Users have the ability to create To-Do items that can
be assigned to another individual or group.
1.2.4 Template customization
Lotus Notes and Domino application developers have additional
customization options with the Domino Web Access template to better suit the
needs of their users. Using the Forms6.ntf file, you can create action buttons
for the Domino Web Access views or dialog boxes, provide more options for
the Domino Web Access Welcome page, and substitute the Domino Web
8
Domino Web Access 6.5 for Sun Solaris 9
Access logo with your corporate logo. The Custom_JS_Extensions,
Custom_WelcomePage, and Custom_Banner forms are available for
modification. In addition, you can modify subforms.
1.2.5 Usability enhancements
Several significant usability enhancements are available in this release. The most
significant ones that Domino Web Access 6.5 offers are:
򐂰 Customize the terms in a dictionary: You can customize your personal
dictionary by adding or removing your own terms.
򐂰 Viewing the database size and properties: You can view your total
database size to see if you are nearing your database quota.
1.2.6 Print enhancements
With Domino Web Access 6.5, users can now:
򐂰 Select multiple documents from a view for printing
򐂰 Select a view and print its contents
򐂰 Select entries in the Contact view and print them in summarized or detailed
form
򐂰 Print a document while in edit mode
򐂰 Print multiple documents from a view
Domino Web Access users now have the ability to select and print multiple
documents in a view. Users are presented with three options to help them
easily print in their preferred format.
1.2.7 Mozilla support for Linux
Domino Web Access supports Mozilla 1.3.1 on Red Hat Linux 7.2, 8, and 9, and
SUSE LINUX 8.0 (including United Linux 1.0).
1.2.8 New administrative features
To make the Domino Web Access server administrator's job easier, this release
includes the following new administrative features and enhancements:
򐂰 Support for name change requests
The Domino Administration Process (AdminP) handles the client interaction
necessary to perform name-change requests.
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
9
򐂰 DOLS replication setting enhancement
DOLS supports replication of truncated documents to determine the size of
attachments replicated to the client. The administrator can also filter
replication to not allow replication of attachments.
1.2.9 Domino Web Access 6.5 performance improvements
Domino Web Access 6.5 performance was a top priority for the Domino
development team. Accordingly, the development team focused on optimizing,
streamlining, and removing bottlenecks in Domino Web Access and in the
underlying Domino 6 code. The summary of improvements includes:
򐂰 Rewriting the HTTP server to enhance performance and scalability: This
benefits Domino Web Access 6.5 and other Web-based applications.
򐂰 Introducing new Notes memory management techniques to allocate memory
faster and to improve memory utilization
򐂰 Enhancing the NSF database core code
򐂰 Optimizing Domino Web Access code, especially Calendar and Scheduling
(C&S)
򐂰 Minimizing semaphore contention in Domino code
򐂰 Optimizing the Formula and Compute engine code
򐂰 Server-side caching and GZIP compression for improved performance.
Internal performance analysis shows that, on the Solaris platform, Domino Web
Access improvements can increase the number of Domino Web Access active
users by 50% with a CPU cost per user saving of 50%, when compared to the
results of Domino R5.0.10 iNotes Web Access. This substantial CPU cost saving
means that an R5 iNotes site can now support more users by upgrading to
Domino 6.5.
HTTP 1.1 persistent connections
The Domino 6 HTTP server includes HTTP 1.1 persistent connections. This
allows for improved session handling, better denial of service attack handling,
and more administrative control over URL length and number of path segments.
Note that the persistent connections are on by default in Domino 6.
With HTTP 1.1 persistent connections, after a client and server open a
connection, it remains open until the client or server specifically requests the
connection to be closed. While the connection is open, the client can send
multiple separate requests and the server can respond to them in the order in
which they are received.
10
Domino Web Access 6.5 for Sun Solaris 9
It can make a noticeable difference in slow networks, such as 56 Kb modems.
However, on fast networks (especially such as a 100 Mb fast Ethernet), it's not as
beneficial. This is because the cost of establishing a connection is low compared
to polling persistent connections. Internal performance analysis of Domino Web
Access server done on a 100 Mb network showed the number of active users
and resources used are about the same with or without persistent connections.
1.2.10 More information about Domino Web Access 6.5
To learn more about Domino Web Access 6.5, refer to the following sources:
򐂰 Lotus Domino Administrator 6 Help for complete information about
administering Domino Web Access
򐂰 iNotes Web Access Deployment and Administration, SG24-6518, for a
complete reference for deploying and administering Domino Web Access
򐂰 Domino Web Access 6.5 on Linux, SG24-7060
򐂰 iNotes Web Access Deployment Guide white paper from LDD:
http://www-10.lotus.com/ldd/notesua.nsf/find/inotes
򐂰 Lotus Software Domino Web Access Web site:
http://www.lotus.com/dominowebaccess
1.3 Sun Solaris 9
As the foundation for Sun systems, the Solaris 9 Operating Environment enables
your IT organization to deliver on the promise of massive scale, continuous
real-time computing, and secure systems. At the same time, it increases service
levels, reduces risk, and decreases costs.
With Solaris 9, you can efficiently manage resources and provide a higher level
of service. It also helps reduce complexity by providing easy-to-use interfaces
and comprehensive administration tools, all designed to help lower your IT risk.
And by optimizing your resources and enabling them to scale to meet demand,
the Solaris 9 Operating Environment helps to minimize costs and lower your total
cost of ownership.
The Solaris platform supports:
򐂰
򐂰
򐂰
򐂰
򐂰
One million simultaneous processes on a single system
Up to 128 CPUs on a single system
More than four billion network connections
32- and 64-bit applications
Two-, four-, and eight-node clusters
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
11
򐂰 IPv4 and IPv6 network addresses
򐂰 Up to 512 CPUs in a clustered environment
1.3.1 Highlights of Sun Solaris 9
The highlights of using Sun Solaris 9 include:
򐂰 The leading UNIX operating environment, combines power, stability, and
predictability with complete backwards compatibility
򐂰 Offers reliability, availability, and serviceability comparable to that of a data
center, but at a fraction of the cost of a mainframe
򐂰 Assures superior availability through a smaller, more stable kernel design and
increased load balancing across multiple processors
򐂰 Scales to handle heavy traffic, huge data sets, and CPU-intensive problems
򐂰 Tightens an already secure environment with increased support for major
security protocols and new technologies
򐂰 Offers a complete global solution with extensive support for 37 languages and
123 locales
򐂰 Provides the premier deployment platform for Java technology
򐂰 Enhances ease of use through simplified software installation and setup, plus
comprehensive integration capabilities
򐂰 Supports the latest networking protocols and adheres to all major industry
standards
Standards supported by Sun Solaris 9
The standards that are supported by Sun Solaris 9 are:
򐂰 Interface: X/Open UNIX 98
򐂰 Graphics: X11, Adobe PostScript, Display PostScript, OpenGL
򐂰 Desktop: CDE, Motif
򐂰 Object: Java IDL
򐂰 Connectivity: ONC, ONC+, NFS, WebNFS, SMB, and optional NetWare
IPX/SPX, SNA, AppleTalk, DECnet, and others
򐂰 Internet: HTTP, FTP, Telnet, DNS, NTP, IMAP4, DHCP, SNMP, SMTP, IPv6,
IPSec, Kerberos, SASL, OCF
򐂰 Protocols: LDAP v3 IETF RFCs 1323, 1510, 1652, 1869, 1870, 1891 to 1894,
1985, 1996, 2018, 2136, 2045, and 2078
12
Domino Web Access 6.5 for Sun Solaris 9
1.3.2 System requirements for Sun Solaris 9
To use Sun Solaris 9, your system must meet these requirements:
򐂰 SPARC 32- and 64-bit platforms
򐂰 Disk space: 600 MB for desktops, 1 GB for servers
򐂰 Memory: 64 MB minimum
1.3.3 Domino Web Access 6.5 requirements for Solaris 9
Domino 6.x does not support Solaris 32-bit kernel mode. Use 64-bit mode to run
Domino 6.x.
The Domino 6.5 Release Notes recommend that you apply the latest Solaris
patches as they become available. You can obtain them from Sun Microsystems
on the Web at:
http://www.sun.com
1.3.4 For more information about Sun Solaris 9
To learn more about new features of Solaris 9, see “What’s New in the Solaris 9
Operating Environment” on the Web at:
http://docs.sun.com/db?p=/doc/806-5202
To learn more about the Solaris Operating System, visit:
http://www.sun.com/solaris
For additional technical and development information, visit the BigAdmin portal
on the Web at:
http://www.sun.com/bigadmin
1.4 Structure of this paper
The remainder of this paper follows this structure:
򐂰 Chapter 2, “Installation hints and tips” on page 15, provides guidance and tips
for installing Domino 6.5 on the Sun Solaris 9 platform. It discusses
improvements in Solaris 9 which are important to note when installing Domino
6.5. Installation steps are discussed in terms of pre-installation tasks, a review
of the steps to install Domino Web Access 6.5 on Solaris 9, and an
Chapter 1. Introduction to Domino Web Access 6.5 on Sun Solaris 9
13
administrative review for preparing and configuring new and existing users for
Domino Web Access.
򐂰 Chapter 3, “Tuning Domino Web Access 6.5 on Solaris 9” on page 33,
describes key tuning parameters in Solaris 9 and in Domino 6.5. It starts by
discussing general tuning guideline and monitoring options that are available
within Solaris and Domino. Then it proceeds to describe these tunable
parameters in greater detail.
򐂰 Chapter 4, “Performance testing: Methodology and results” on page 55,
concludes the paper with an analysis of our performance testing results of
Domino Web Access 6.5 on Solaris 9. This anlysis is based on several of the
tuning methods discussed earlier in the paper. This chapter discusses both
the performance test environment and simulation methodology used for this
Redpaper and presents the actual results of the performance tests. We
believe that this analysis of the performance test results can help you to
understand better the potential impact of performance tuning for Domino Web
Access 6.5 and Sun Solaris 9.
Prior to reading this Redpaper, you must be familiar with Solaris administration
and installation. We do not cover the details about installing the Solaris 9
operating system since it is beyond the scope of this Redpaper.
To review the detailed process of installing Solaris 9, we recommend that you
refer to specific installation and technical documentation provided by Sun. For
example, you may want to refer to the Solaris 9 Installation Roadmap. This
includes the installation guide, the Solaris 9 release notes, and the package list.
You can find it in PDF format on the Web at:
http://docs.sun.com/db/coll/214.12
14
Domino Web Access 6.5 for Sun Solaris 9
2
Chapter 2.
Installation hints and tips
This chapter provides hints and tips for installing Domino 6.5 on the Sun Solaris
9 platform. There are some improvements in Solaris 9 that are important to note
when installing Domino 6.5. We cover those differences.
If you are already familiar with installing Domino 6.5 on Solaris 9, you may want
to proceed to 2.3, “Preparing users for Domino Web Access 6.5” on page 25.
© Copyright IBM Corp. 2004. All rights reserved.
15
2.1 Pre-installation
The following section discusses preliminary requirements and the steps that you
need to verify prior to installing Domino Web Access 6.5 on Solaris 9.
2.1.1 Requirements
Before you install Domino 6.5, you must meet the following requirements:
򐂰 Apply the latest recommended patches for your Sun Solaris 9. You can type
the following command to view the system’s current patch list:
myshell> showrev -p
During Domino installation, checkos validates the required patches before the
actual installation (see Figure 2-1). See Domino 6.5 Release Notes for the
minimum patch requirements.
Figure 2-1 Checking the operating system for the latest patches
򐂰 If you are using the Fault Recovery feature on Solaris, the number of available
messages per message queue must be increased. To accomplish this,
become superuser and add the following line to /etc/system and reboot:
set msgsys:msginfo_msgtql=1024
This needs to be set on Solaris because Fault Recovery uses message
queues. The default for Solaris is 40 messages per queue. Fault Recovery
requires more than 40 messages in this queue. This setting increases it from
40 to the recommended setting of 1024.
򐂰 Make sure your Sun Solaris system is running in 64-bit kernel mode. Domino
6.x does not support Solaris 32-bit kernel mode.
16
Domino Web Access 6.5 for Sun Solaris 9
򐂰 You may want to check “Domino Web Access system requirements” in the
Domino 6.5 Release Notes, which are included in the Domino 6.5 CD. If the
CD is not in a convenient location, you can find the release notes on the Lotus
Developer Domain (LDD) Web site at:
http://www-12.lotus.com/ldd/doc/domino_notes/6.5/readme.nsf
Note: In Solaris 9, Sun increased the default value of rlim_fd_max to 65536.
Therefore, it is unnecessary to set rlim_fd_max as originally recommended in
the Domino R6.5 Release Notes.
2.1.2 Creating group and user account for Domino
After you meet the requirements, you need to create a group and a user account
for Domino setup. The user account is used to operate the Domino server, so you
must have a dedicated user for the Domino server.
In Solaris, you can use admintool to create the group and the user account. To
start admintool, type admintool from the shell prompt:
myshell> admintool &
Note: Most of the command examples begin with myshell>. This is an
example of a shell prompt. In this Redpaper, this simply implies that you must
use a shell prompt.
Now you can create a group and a user as explained in the following steps:
1. Create a group for Domino. In our example, we used notes for the group
name.
a. In admintool, click Browse-> Groups.
b. You should see a listing of groups, similar to the example in Figure 2-2. To
add a group, click Edit-> Add. You are prompted within another window.
Here you can type the group name you want to use.
Chapter 2. Installation hints and tips
17
Figure 2-2 Groups list in admintool
2. Create a user to operate Domino.
a. To switch to the users list, click Browse and select Users.
b. You should see a list of users, similar to the example in Figure 2-3. To add
a user, click Edit-> Add. You are prompted to add a user within a new
window. At this point, you can specify a user name in the window and type
the group name you created in the Primary Group field. You also need to
enter information for the Security and Home directory section for the user
account. Click OK.
You should see the notes account added in the users list in the admintool. In
our example, we also used notes for the user name.
Note: In our test environment for this Redpaper, we used notes for both the
user name and group name. Keep in mind that you can choose any name you
want to use. It is not required to name the user account notes for Domino. For
more details about creating users and groups using Admintool, see “Creating
users and groups” in Lotus Domino R5 for Sun Solaris 8, SG24-5969.
Finally, throughout the remainder of this Redpaper, notes user and notes
group refer to the user account and the group you created in this section for
Domino.
18
Domino Web Access 6.5 for Sun Solaris 9
Figure 2-3 Users list in admintool
You may want to reference the System Administration Guide: Basic
Administration for more information about managing users and groups in Solaris
9. You can find this document on the Web at:
http://docs.sun.com/db/doc/806-4073
2.1.3 Checking disk space
We strongly recommend that you check the disk space of your system. You need
a minimum of 750 MB or more available disk space. Domino data is divided into
four parts:
򐂰 Transactional logging: Allocate a separate physical disk of 4 GB or more for
each Domino server or Domino partition. It is critical that you do not use this
directory for any purpose other than to maintain transactional logs.
򐂰 Domino data directory: Allocate approximately 200 MB to 300 MB per each
Domino server. This directory is used to store all the Domino data, including
the Domino directory (names.nsf). Keep in mind that within a large
organization, it’s not uncommon for a Domino Directory (names.nsf) to
exceed 1 GB of disk space. Therefore, you may need to allocate substantial
space for this directory.
򐂰 User mail files: Allocate disk space based on a calculation of the number of
users multiplied by the average size of the mail file.
򐂰 Application databases: Allocate additional disk space for any application
databases, such as discussion databases, document libraries, workflow
Chapter 2. Installation hints and tips
19
applications, etc. If the server under consideration is solely dedicated as a
messaging or e-mail server, then this consideration may not apply.
For more information about sizing for a Domino Server, see Chapter 2, “Sizing
and configuration of Solaris” in Lotus Domino R5 for Sun Solaris 8, SG24-5969.
Tip: We recommend that, if possible, distribute your databases evenly over
multiple disk devices. This helps to reduce any disk input/output (I/O)
bottleneck.
Checking available disk space in Solaris 9
To check the amount of available disk space, use the df command with the -h
option (see Figure 2-4). This option is new to Solaris 9 and more user-friendly
than other options.
Figure 2-4 df -h output
Alternatively, you can also use a traditional command to check for available disk
space, df -k, if you’re more familiar with this command.
At this point, you are ready to proceed with the installation of the Domino 6.5
server.
2.2 Installing Domino 6.5
Now let’s install Domino 6.5:
1. Log in as a Solaris root user.
Note: If you are working with a Domino 6.5 CD-ROM, proceed to step 2. If
you are working with a tar file, proceed to step 4.
2. Insert the Domino 6.5 CD-ROM.
20
Domino Web Access 6.5 for Sun Solaris 9
3. Change to the sunspa directory by entering the following command:
myshell> cd /cdrom/cdrom0/sunspa
Domino Solaris/Sparc Server CD-ROM directory structure: The
directory structure should be as shown here:
INSTALL.PDF
LICENSE.TXT
README.NSF
README.PDF
START.TXT
SUNSPA
INSTALL
LICENSE
SCRIPT.DAT
SETS
DATA
FGINV
FGROUPS
TOOLS
BIN
SOL
LIB
PERL5
NLS
4. If you downloaded a tar file directly from the Lotus Web site, untar the file
using the following commands. After the file is untarred, you should have the
same directory structure.
To untar the file, enter the following command:
myshell> tar xvf filename.tar
Then enter the following command:
myshell> cd sunspa
5. Run the install program by entering the following command:
myshell>./install
6. Press the Tab key to continue.
7. Follow the instructions and answer the prompts. The following steps provide a
quick reference:
a. Select the Setup type. We used Domino Enterprise Server. Choose the
appropriate one for your organization.
Chapter 2. Installation hints and tips
21
b. Specify the current program directory setting. Specify the location where
the Domino executables are located. By default, this is /opt/lotus.
c. Do you want to run more than one server based on this installation? If you
want to Domino to partition on this server, answer Yes and follow the
instructions. In our example, we selected No.
d. Specify the current data directory setting. Specify the location where all of
your Domino data will be located. The default is /local/notesdata.
e. Specify the user and group you created for Domino.
8. You see the Select Server setup method prompt. The three options are:
– Manual Server Setup: R5 style HTTP setup.
– Local Server Setup: Windows Style setup.
– Remote Server Setup: This allows you to set up a Domino server from
your workstation. You can install the Remote Server Setup tool with the
Domino Administrator Client. Make sure that you include the Remote
Server Setup Utility when you install your Domino and Notes clients.
In our example, we chose Remote Server Setup (see Figure 2-5).
Figure 2-5 Remote Server Setup
9. After you enter information for each prompt, you see a confirmation window to
verify your selections. See Figure 2-6.
22
Domino Web Access 6.5 for Sun Solaris 9
Figure 2-6 Installation settings
10.Press the Tab key to install the Domino server code.
11.The Domino installer validates the operating system patches (see Figure 2-1
on page 16) and starts the installation. When complete, the installer goes into
listen mode automatically to set up the Domino server (see Figure 2-7).
Figure 2-7 Server setup listen mode
12.The actual server code installation is now completed, but the server needs to
be configured prior to its initial start up. The server is in listening mode and
waiting for the Remote Server Setup tool to finish the configuration.
Start Remote Setup from your workstation. When it starts, you see a window
like the example in Figure 2-8. You can ping the server to confirm the server is
listening port 8080. Type the host name (FQDN or IP address) and click OK.
Chapter 2. Installation hints and tips
23
Figure 2-8 Remote Server Setup tool
13.Follow the setup procedure. For example, you need to select whether this is
the first Domino server in the domain or an additional server to an existing
Domino domain. Select all tasks that need to be enabled on the server.
Important: For Domino Web Access, you must select HTTP server. If you
want to allow users offline access to their mail files, you must select DOLS
Domino Off-Line Services. See Figure 2-9.
Figure 2-9 Configuring Domino tasks
24
Domino Web Access 6.5 for Sun Solaris 9
14.On the next window, verify organization, server name, administrator name,
network, and port options. Remember to memorize passwords. You may want
to change default, system-generated passwords to something more
meaningful to you.
15.Click Finish. This completes the configuration the Domino server based on
your input.
16.At the end of the configuration, the server prompts whether you want to stop
the server from listening mode. Click Yes. After listening mode is turned off,
your server is ready.
17.To start the server, change the directory to the Notes data directory:
myshell> cd /notesdata
18.Enter the following command to start the server:
myshell> /opt/lotus/bin/server
Attention: As a best practice, we recommend that you start your Domino
server from a startup script. A basic script for starting Domino on Solaris is
provided Appendix A, “Additional material” on page 69. These startup scripts
provide the basic framework for a startup script, but you need to modify them
for your specific environment.
For the scope of this paper, we assume that you have sufficient administrative
knowledge to modify these scripts to work with your environment. For a
detailed description on how to use such a script, see 3.5.3, “Starting the
Domino Server using a startup script” in Lotus Domino R5 for Sun Solaris 8,
SG24-5969.
2.3 Preparing users for Domino Web Access 6.5
As previously explained, most of the Domino Web Access code is contained
within the mail template. Accordingly, your users’ mail files need to be created
using Domino Web Access 6.5 mail template. The file name is iNotes6.ntf.
Tip: Three iNotes mail templates are supported in Domino 6.5:
򐂰 iNotes6.ntf: Domino Web Access 6. This is the latest, fully featured
template. For the examples in this paper, we use this template.
򐂰 iNotes60.ntf: iNotes Web Access 6: This is the previous R6 iNotes mail
template.
򐂰 iNotes5.ntf: iNotes Web Access 5: This is the R5 iNotes mail template.
Chapter 2. Installation hints and tips
25
2.3.1 Registering new users for Domino Web Access
You can register users either by using the Lotus Domino Administrator client or
by using the Web administrator client (webadmin.nsf). To access the Web
Administrator, type:
http://servername/webadmin.nsf
Follow these steps to register new users:
1. Launch the Administrator Client and make sure that you select the proper
administrative server.
2. Select the People & Group tab.
3. On the far right, click People.
4. Select Register.
5. Select the certifier ID and close the certifier window. Alternatively, you can
use the CA process (Certificate Authority).
6. Ignore the warning message regarding certifier recovery information.
7. You need to complete all necessary fields to register users:
– Note that the Internet password field is required for Domino Web Access.
– Make sure that you specify iNotes.ntf as mail template under the
Advanced tab.
8. Click Add Person.
9. Click Register at the bottom of the page.
10.Click Done.
You have now registered the new users.
2.3.2 Converting users to Domino Web Access
You can allow existing mail users to have access to the features and functions
provided through Domino Web Access 6.5. To do this, you must either
individually replace their mail template to iNotes6.ntf, or use the convert
command through the Administrator.
This process does not completely “convert” a user’s mail file to Domino Web
Access 6.5. To be precise, Domino Web Access 6.5 functionality is added into the
user’s mail template. If a user wants to continue access their mail file through a
browser using the previous version Domino Web mail, this is still possible. To
access the previous Web mail features and browser interface, users must enter
&ui=argument after they convert to the newer iNotes template for Domino Web
Access 6.5.
26
Domino Web Access 6.5 for Sun Solaris 9
For example, to use Web Mail, enter:
http://servername/mail/jdoe.nsf?openDatabase&ui=webmail
Using the convert command
In the case that you need to upgrade many existing mail files to the iNotes6.ntf
template, we recommend that you use the convert command.
The proper syntax for using the convert command to convert users is:
convert [-r] mail filename OldTemplateName NewTemplateName
To convert iNotes5.ntf or iNotes60.ntf to iNotes6.ntf, in the Domino server
console, enter the following command that corresponds to your version:
> load convert mail\*.nsf inotes5 iNotes6.ntf
> load convert mail\*.nsf iNotes60 iNotes6.ntf
To convert all users to iNotes6.ntf regardless of their current mail template, enter:
> load convert mali\*.nsf * iNotes6.ntf
If you want to execute the convert command from Solaris shell prompt, ignore the
load.
Attention: If you execute a convert command while the server is running and
a user accesses their mail file while their mail file design is being updated,
unpredictable results may occur. Accordingly, we recommend strongly that
you run this conversion process during “off” hours, when users are most likely
not accessing their mail files.
2.4 Domino Web Access configuration settings
In the server’s configuration document, you can customize your Domino Web
Access settings. To view these settings, select the configuration view in your
Domino directory, and select the Domino Web Access server. Then you should
see Domino Web Access page (see Figure 2-10). The following sections
describe the specific configuration parameters in greater detail.
Chapter 2. Installation hints and tips
27
Figure 2-10 Domino Web Access Settings
2.4.1 Configuration settings and impact on performance
The Domino Web Access tab on the server’s Configuration document has
several settings that can impact the overall performance and behavior of the
server. Here we highlight several them and describe some notes.ini parameters
that impact Domino Web Access behavior.
The intent of this section is simply to provide a detailed description of the
configuration parameters and comment on how selections may impact overall
server performance.
Chapter 3, “Tuning Domino Web Access 6.5 on Solaris 9” on page 33, and
Chapter 4, “Performance testing: Methodology and results” on page 55,
specifically focus on performance tuning. They discuss specific parameters and
recommend tuning options in much greater detail.
28
Domino Web Access 6.5 for Sun Solaris 9
Alarms
The Alarms section (see Figure 2-11) provides options that allow the
administrator to customize whether Domino Web Access users can choose to be
notified when a meeting, appointment, or other calendar entry is impending. The
default poll time is five minutes.
You can turn off the feature entirely or increase the default length of time that the
Domino Web Access session will poll to see if an alarm is due. A slight
performance gain is seen if the default polling time is increased. Turning off the
feature entirely shows a larger gain, especially in environments with a large
number of Domino Web Access users, since it can reduce the session traffic.
Figure 2-11 Alarms section of Domino Web Access Configuration Settings
Mail
The next section is the Mail section (Figure 2-12). By default, Domino Web
Access sessions poll the server to see if new mail is in the user’s Inbox every five
minutes. By increasing the interval for this poll, the administrator can decrease
session traffic and see a slight gain in performance overall on the server.
In addition to the mail polling interval, this section allows the administrator to
either force users to send mail in plain text format or to allow them to choose that
or a rich text version (HTML). This setting on the Configuration document
corresponds to the notes.ini parameter iNotes_WA_MessageFormat. Setting this
parameter to one forces the use of plain text. The default is zero.
This section also allows the administrator to specify whether users can perform
ambiguous name resolution, which is essentially the same as type-ahead in a
Notes client. The distinction is that, in a Domino Web Access session, the name
does not auto-complete as it can in the Notes client. The user must either press
F9 or click the Check Name(s) icon that appears when you type characters in
one of the recipient fields (To:, CC:, Bcc:).
Chapter 2. Installation hints and tips
29
Figure 2-12 Mail section of Domino Web Access Configuration Settings
Notes.ini parameter iNotes_WA_NameLookupMaxNumMatch impacts the
behavior of this option, but does not have a corresponding field on this tab. This
parameter is used to limit the number of names that are returned when a user
attempts to validate a name. By default, 200 matches can be returned, but this
parameter can be used to change the value.
Other Settings
The following settings in the Other Settings section (see Figure 2-13) can
noticeably impact server performance:
򐂰
򐂰
򐂰
򐂰
Full-text indexing
Archiving on server
Calendar printing
Compress HTTP response data
The Full-text indexing field can allow or prevent users from creating server-side
full-text indexes of their mail files. By default, it is enabled. However, by disabling
it, an administrator can save disk space and improve server performance.
Archiving is also enabled by default. It allows users to create server-side archive
copies of their mail file. This can consume disk space and processing power.
Calendar printing uses an Adobe PDF API on the server to convert calendar
entries to PostScript, and returns it to the browser to print entries. This operation
is lightweight for single calendar entries. Users can request to print multiple
entries or entire calendar views. This can add load to the server if heavily used.
By selecting to enable the Compress HTTP response data setting, you enable
Gzip compression. This is a compression mechanism for HTTP traffic which
allows for potentially a 70 % reduction in bandwidth. Gzip compression also
helps performance on slow networks and low bandwidth lines. For more
information, see 3.4.3, “Domino tuning” on page 48.
30
Domino Web Access 6.5 for Sun Solaris 9
Figure 2-13 Other Settings section of Domino Web Access Configuration Settings
Chapter 2. Installation hints and tips
31
32
Domino Web Access 6.5 for Sun Solaris 9
3
Chapter 3.
Tuning Domino Web Access
6.5 on Solaris 9
This chapter describes key tuning parameters in Solaris 9 and in Domino Web
Access 6.5. It starts by discussing some general tuning guidelines and
monitoring options available within Solaris 9 and Domino. Then it proceeds to
describe these tunable parameters in greater detail.
In addition to the information described in this chapter, you may find additional
information on the Lotus Domino for Sun Solaris Web site at:
http://www.lotus.com/dominosolaris
You can also find valuable information on the Sun and Lotus software site at:
http://www.sun.com/solutions/third-party/global/lotus/
© Copyright IBM Corp. 2004. All rights reserved.
33
3.1 Tuning guidelines
Before describing specific tuning parameters, it is important to emphasize some
best practices and guidelines of performance tuning. You may want to take some
time to think about these before you start making any changes to your system.
Consider the following points as a general set of guidelines:
򐂰 Remember the law of diminishing returns. Your greatest performance
improvements may come from your initial efforts.
򐂰 Do not tune for the sake of tuning. Tune to relieve your identified constraints.
򐂰 Consider the entire system as a whole. Consider how each change to an
individual parameter may affect the entire system.
򐂰 Change one parameter at a time. Do not make more than one change at a
time. Even if you know that all the changes are beneficial, you have no way to
evaluate how much each parameter change is contributing toward better
performance.
򐂰 Check hardware and software problems.
򐂰 Understand the problem before you upgrade your hardware. Take the time to
understand where your system constraints or bottlenecks are.
򐂰 Always have a fallback procedure in place before you start tuning.
3.2 Sun Solaris performance monitoring options
The following section describes useful stat commands which you may use to
monitor the performance of your system.
3.2.1 Stat commands
The easiest way to monitor performance of a system is by using the stat
commands that come with the Solaris Operating Environment. These commands
are located in /usr/bin directory. You can find a full list of the available commands
by typing:
myshell> /usr/bin/*stat
Table 3-1 shows the useful stat commands.
34
Domino Web Access 6.5 for Sun Solaris 9
Table 3-1 Useful stat commands
Commands
Description
prstat
Summary of active processes, simiar to the top utility
vmstat
Virtual memory/paging statistics with CPU/process summaries
mpstat
Per-processor statistics
iostat
Disk input/output (I/O) and Network File System (NFS) statistics
netstat
Network statistics
Collecting these commands and understanding the output should give you a
good idea of the problems that may exist in your current system.
Attention: Do not use the uptime command to monitor or analyze your
system. This command only shows how long the system has been up. The
load average notion in the output is outdated and almost useless in the Solaris
9 Operating Environment. Instead, you may want to use vmstat 5 when a
system becomes sluggish (slow).
The following list examines each of these commands in greater detail:
򐂰 prstat: This command shows what processes are active on the system,
along with how much CPU time they are using. It shows to which processor
the processes are bound, their size in memory, and their priority. This
command works similarly to the freeware tool top.
Here is an example of this command:
myshell> prstat
Unlike other stat commands, prstat is not required to have any argument.
The output is refreshed every 5 seconds by default and appears similar to the
example in Figure 3-1.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
35
Figure 3-1 prstat example
򐂰 vmstat: This command is a simple way to look at memory. You can simply
specify a time interval to vmstat. Then let it run until you press Ctrl+C to stop
it. Here is an example of this command with the output shown in Figure 3-2:
myshell> vmstat 5
Figure 3-2 vmstat 5 example
Tip: Always ignore the first line of any stat command since it is a
summary that shows how long the system has been up. Accordingly, it
doesn’t give you any indication as to the use of the system during the time
period of your interest.
When looking at the vmstat output, you may ignore all the fields about disks
and device interrupts. There are better tools for monitoring these statistics.
We recommend that you focus on the columns shown in Table 3-2.
36
Domino Web Access 6.5 for Sun Solaris 9
Table 3-2 Useful vmstat output columns
Column
Meaning
r
Number of runnable processes (waiting for CPU time)
b
Number of blocked processes (waiting for I/O, paging, etc.)
w
Number of runnable but swapped-out processes (normally 0)
re
Page reclaims (memory pages taken form other processes)
mf
Minor page faults
pi
KB paged in (including process startup and file access)
po
KB paged out (should be close to 0)
sr
Pages scanned by page-out scanner (should be close to 0)
us
Percentage of CPU time spent in user mode
sy
Percentage of CPU time spent in system mode
id
Percentage of CPU time spent idle
A more in-depth examination of the columns and values is as follows:
– Normally the r, b, and w columns are fairly low numbers, if not 0. Larger
numbers in these columns usually indicate a negative performance
implication. The general rule of thumb is that if the run queue (r column) is
greater than four times the number of CPUs in the system, you may have a
CPU constraint. This is explained in the book Sun Performance and
Tuning: Java and the Internet, by Adrian Cockcroft, Richard Pettit, and Sun
Microsystems Press.
– The us, sy, and id columns should give you a good idea of what the system
is doing. For a detailed view of each CPU, use mpstat.
– The sr and po columns should have values close to 0. An increase in the
scanned rate (sr) and a jump in the page-out (po) consistently is evidence
of a memory shortage. The system needs more memory.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
37
Tip: Start by examining memory statistics and memory usage. Repeat this
analysis frequently. When your system has a memory bottleneck, the stats
are unreliable, because the system shows extra delays while managing
memory. It is easy to misdiagnose memory-related issues as CPU or I/O
problems. In reality, the system is slow due to paging or even swapping.
In a Solaris environment, everything is a page of memory, including files.
This is beneficial for the system. However, it makes an accurate analysis
more difficult. Therefore, properly analyzing memory is very important.
򐂰 mpstat: In general, CPU columns of the vmstat output are a good place to
start. Keep in mind, however, that it may often be necessary to look at all of
your CPUs in detail to make sure you are not missing anything.
Like vmstat, start mpstat with a time interval and let it run:
myshell> mpstat 5
Figure 3-3 mpstat 5 example
As you see from Figure 3-3, this command produces a data set displayed in
many columns. In particular, you may want to focus on the columns shown in
Table 3-3.
Table 3-3 Useful mpstat output columns
38
Column
Meaning
xcal
Interprocessor cross-calls
intr
Interrupts
csw
Context switches
icsw
Involuntary context switches
smtx
Spins on mutex locks
Domino Web Access 6.5 for Sun Solaris 9
Column
Meaning
usr
Percent user time
sys
Percent system time
wt
Percent wait time
idl
Percent idle time
򐂰 iostat: This command provides information about disk utilization. The main
column to focus on is svc_t, which describes the average service time (in
milliseconds) required to complete an I/O request. You can also use iostat to
determine if the disks are not load balanced.
Here is an example of this command with the output shown in Figure 3-4:
myshell> iostat -x 5
Figure 3-4 iostat -x 5 example
For more about disk utilization, read the article “What does 100 percent busy
mean?” by Adrian Cockcroft. You can find it on the Web at:
http://www.sun.com/sun-on-net/itworld/UIR990801perf.html
򐂰 netstat: Network analysis can be difficult. In Solaris, there is no solid network
utility that tells you all of the information you need to know. You can get a
general idea about number of packets, but you can’t see such things as
octets, TCP throughput rates, or retransmissions. We usually improve the
network performance by installing additional network interface cards to take
advantage of more bandwidth, even if it is a bit of a “black box” approach.
However, you can use the netstat command to obtain some information
about TCP/IP network information. We are interested in any network buffer
overload errors caused by not allocating enough space to the TCP/IP buffers
of the network. No errors are reported when you allocate too many buffers,.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
39
However, we want to be sure to allocate the minimal amount of memory to
network interfaces to support the sustained load and most of the peak load.
We are specifically interested in any dropped frames from the TCP/IP stack
(tcpTimRetransDrop and tcpListenDrop), as highlighted in Figure 3-5.
Figure 3-5 Sample netstat output
3.2.2 SE Toolkit
The SE Toolkit is a software package developed by Sun performance experts. In
addition to using stat commands, this toolkit can help you to collect more
“intelligent” performance information. You can download the free toolkit and its
documents from the Web at:
http://www.setoolkit.com/
40
Domino Web Access 6.5 for Sun Solaris 9
3.3 Lotus Domino 6.5 performance monitoring options
Domino continuously generates statistics that you can use to monitor system
activity and platform use. It includes many server-monitoring features that work
together to inform you about the processes, networks, and use of the Domino
system.
You can monitor the system using one of three tools: the Domino Administrator,
the Web Administrator, or the server console. For example, from the Domino
Administrator, you can use the Domino server monitor and statistics charts to
view graphical representations of system status. From the server console, you
can view a representation that uses your predefined colors and text attributes to
illustrate the status of a process.
The Domino Administrator includes the following system-monitoring tools that
you use to configure, view, and track the Domino system:
򐂰 Domino server monitor: The Domino server monitor displays real-time
statistics and provides a visual representation of the status of servers and
their tasks. You can view all servers or a subset of servers. Additionally, you
can view the status by state or by timeline.
򐂰 Statistics: Domino gathers statistics that show the status of processes
currently running on the system. You use these statistics along with the
predetermined statistics thresholds to monitor both your Domino system and
platform statistics.
Using the Domino 6.5 platform statistics tool, you can eliminate switching
between Domino and Solaris statistics. Domino platform stats can collect the
same information generated by Solaris stats, such as kstat, iostat, vmstat
and netstat. In addition, the generated information is integrated with
monitoring configuration (Events4.nsf) and reports (Statrep.nsf). These
platform statistics are enabled automatically in Domino 6.5.
The platform stats are grouped into five categories:
–
–
–
–
–
Logical disk stats
Memory stats
Network stats
CPU stats
Miscellaneous system stats
For some stats, average, minimum, and peak values are calculated. There
are sets of Domino console commands to control the platform stats. The
commands are:
– To view platform stats
> show stat platform
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
41
You can also specify an object name that you are interested in:
> show stat platform.<object>.*
– To set a sampling interval
> platform time 15
This means that you are setting the interval to 15 minutes. The default is 1
minute.
– To reset counters
> platform reset
– To pause gathering
> platform pause
– resume gathering
> platform resume
Table 3-4 summarizes a general guideline for some platform statistics that are
especially meaningful to the Solaris platform.
Table 3-4 Healthy statistic range guidelines for Solaris
Platform stat name
Normal value
LogicalDisk.ServiceTime
Single/RAID < 40 msecs
LogicalDisk.PctUtil
< 20%
Memory.RAM.PctUtil
< 5%
Network.PctUtilBandwidth
< 30% of total bandwidth
Network.PctCollisionRate
< 2% of transmitted packets
Process.ActiveDomino.TotalCpuUtil
< 80% of combined CPU util
System.CPUQueueLen
< 1 per processor
System.PctCombinedCpuUtil
< 95%
System.PctTotalUserCpuUtil
< 75% of Total CPU utilization
Memory.PagingFile.PctUtil
< 40%
򐂰 Monitoring server tasks: This tool collects and records information about
the Domino system. The Event Monitor task determines if an Event Handler is
configured for the event. If it is, it routes the event to the specified person,
database, or server-management program for processing. The Statistic
Collector task gathers Domino server statistics and creates statistics reports
in the Monitoring Results database (STATREP.NSF) or to another database
42
Domino Web Access 6.5 for Sun Solaris 9
that you can specify. The ISpy task executes TCP server and mail-routing
event generators.
򐂰 Monitoring configuration documents: This tool defines and configures
what constitutes an event and how the event is handled. It also allows you to
customize the messages that appear on the console when an event occurs.
򐂰 Monitoring databases: This tool stores monitoring documents, information,
and results. The Monitoring Configuration database (EVENTS4.NSF) stores
the documents that you use to set up monitoring. It also includes information
about statistics, statistic thresholds, and event messages. The Monitoring
Results database (STATREP.NSF) stores the gathered statistics reports and
can be configured to store information about logged events. The log file
(LOG.NSF) stores the server's log documents.
Tip: You can customize the appearance of the Domino server console. By
creating a Server Console configuration document for the server you are
monitoring, you can specify the text, background, and color attributes that the
Domino server console uses to display monitoring information. By default, the
Domino Administrator server console uses the same attributes. You can
override the defaults and customize the appearance of the Domino
Administrator server console.
IBM Tivoli Analyzer for Lotus Domino
IBM Tivoli® Analyzer for Domino is a system analysis tool. It includes two
integrated system management tools:
򐂰 Server Health Monitor: This tool offers real-time assessment and
recommendations for server performance
򐂰 Activity Trends: This tool provides data collection, data exploration, and
resource balancing.
Using these tools, you can manage servers and databases to ensure better
server performance and build a baseline for current and future needs.
Note: The IBM Tivoli Analyzer for Lotus Domino requires a separate license.
For more details about IBM Tivoli Analyzer, see the Lotus Developer Domain
(LDD) Today article, “Start using Domino 6 Server Health Monitoring Now”, by
Carol Zimmet. You can find this article on the Web at:
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b380/
453d9e87c12cda0800256bce003f3c6e?OpenDocument&Highlight=0,domino,server
,health,monitoring
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
43
3.4 Tuning considerations
Prior to Solaris 9, many Solaris tuning parameters were recommended to
optimize the performance of Domino. With the introduction of Solaris 9 and
Domino 6.5, far fewer adjustments are needed.
This section reviews the most important tuning parameters in Solaris 9, which
may impact the performance of Domino Web Access 6.5. In addition, see Sun’s
Domino on Solaris: Common Tuning Tips, which covers a broader range topics
and different versions of Solaris. You can find it on the Web at:
http://www.sun.com/solutions/third-party/global/lotus/technical/
index.html
3.4.1 Solaris kernel tuning
When you tune for Solaris kernel parameters, you need to set the parameters in
the /etc/system file.
Tip: Before you make any changes in the /etc/system file, make a backup copy
of the file. You can do this by entering the following command:
myshell> cp /etc/system /etc/system.good
If the change in /etc/system causes the system to become unbootable, you
can recover with following command:
ok boot -a
In addition, you can specify the name of the /etc/system file that you want to
use. You can specify system.good here:
Name of system file [/etc/system]: /etc/system.good
Here is a list of Solaris kernel parameters, their description and a
recommendation for tuning:
򐂰 set msgsys:msginfo_msgtql=1024
This parameter changes the maximum number of messages that can be
created. Domino 6.5 Release Notes recommend this value to be 1024. In
Solaris 9, it’s 40 by default. By issuing this command, you increase the
number of available messages per message queue. This change requires the
system reboot. You may also refer to 2.1.1, “Requirements” on page 16.
44
Domino Web Access 6.5 for Sun Solaris 9
򐂰 set rlim_fd_max=65536
This parameter was recommended in the Domino 6.5 Release Notes. Under
Solaris 9, it is no longer required because the default value of the parameter
has increased to 65536. See 2.1.1, “Requirements” on page 16.
򐂰 Priority_paging and cachefree
Don’t set Priority_paging and cachefree in Solaris 9. They are not
supported in Solaris 9. These parameters are replaced with an enhanced file
system caching architecture that implements paging policies similar to priority
paging. In addition, the new enhanced file system caching architecture is
always enabled.
It is also important to note that the configuration mechanism of the paging
subsystem has changed in Solaris 9. Instead of depending on a set of
predefined values for fastscan, slowscan, and handspreadpages, the system
determines the appropriate settings for these parameters at boot time. Setting
any of these variables in the /etc/system file can cause the system to use less
optimal values.
Attention: Setting Priority_paging or cachefree parameters in the
/etc/system file results in such boot-time warnings as:
sorry, variable 'priority_paging' is not defined in the 'kernel'
sorry, variable 'cachefree' is not defined in the 'kernel'
򐂰 set tune_t_fsflushr=1
set autoup=600
You can tune the system daemon, fsflush, with these two parameters:
– tune_t_fsflushr: This controls how frequently fsflush runs. It specifies
the number of seconds between invocations.
– autoup: This parameter is used in tandem with tune_t_fsflushr. It can
control how much memory is examined at each fsflush execution.
Some experts recommend that you set tune_t_fsflusher to about 4 or 5
instead of 1. You must watch for excessive CPU consumption by the fsflush
process. If fsflush is demanding large amounts of constant CPU utilization,
consider increasing the time interval for tune_t_fsflusher. We recommend
that you do not make it too large. This may result in periodic spikes of CPU
load when the fsflush process runs.
In our internal workload tests, a value ranging from 1 to 4 provided the best
results. Keep in mind that these numbers may not necessarily be optimal for
your case. For each environment, perform your own experiments with your
own real world workload to find the best number for your server.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
45
򐂰 set segmap_percent=48
You may also benefit from increasing the value of segmap_percent if you are
seeing high file system page-in rates. segmap_percent adjusts the percentage
of memory that the kernel will map into its address space for the file system
cache. The default value is 12. This means that the kernel reserves enough
space to map, at most, 12% of memory for the file system cache. For a
heavily loaded system, consider experimenting with this value, starting with
values around 25. This parameter can increase kernel memory requirements
significantly.
In our tests, 48 showed us the best results. Again, we strongly recommend
that you experiment with this parameter and test it in your specific
environment to achieve the best result.
3.4.2 Solaris file system tuning
Several different file system types are supported in Solaris operating system. For
the purposes of this paper, we discuss the default Solaris file system known as
UFS. In UFS, you can use the newfs command to create new file system. The
setting for this command varies, depending on your disk and controller
technology. We also introduce the newfs command and its parameters which may
provide benefit to your Domino Web Access 6.5 server.
Here is an example of the newfs command with its parameters:
myshell> newfs -i nbpi -c cgsize -C maxcontig -m free raw-device
The following lists explains each of the parameters:
򐂰 -i nbpi: This parameter indicates the number of bytes per inode. It specifies
the density of inodes in the file system. The number is divided into the total
size of the file system to determine the fixed number of inodes to create. It
should reflect the expected average size of files in the file system. For fewer
inodes, use a larger number. To create more inodes, use a smaller number.
Table 3-5 shows the default values for nbpi.
Table 3-5 The default nbpi size
46
Disk size
nbpi
~ 1 GB
2048
~ 2 GB
4096
~ 3 GB
6144
3 GB ~
8192
Domino Web Access 6.5 for Sun Solaris 9
򐂰 -c cgsize: This parameter indicates the number of cylinders per cylinder
group. This value ranges from 16 to 256. The default value is calculated by
dividing the number of sectors in the file system by the number of sectors in a
gigabyte, and then multiplying the result by 32.
򐂰 -C maxcontig: This parameter indicates the maximum number of logical
blocks, belonging to one file, that are allocated contiguously before inserting a
rotational delay. The default value is determined from the disk drive’s
maximum transfer rate.
This parameter can be subsequently changed using the tunefs command.
򐂰 -m free: This parameter indicates the minimum percentage of free space to
maintain in the file system. This can be set between 1% to 99%. This space is
off limit to normal users. After the file system is filled to this threshold, only the
super-user can continue writing to the file system.
You can subsequently change this parameter using the tunefs command.
Finally, our general recommendation for the command is:
򐂰 Domino database (Domino data directory) file system:
myshell> newfs -i 200000 -c 200 -C 7 -m 1 /dev/rdsk/<your disk name>
򐂰 Transaction logging file system:
myshell> newfs -i 200000 -c 200 -C 15 /dev/rdsk/<your disk name>
The settings introduced here override the default settings. They usually give you
better performance, but may not be optimal for all disk technology.
We recommend that you mount these file systems with noatime to reduce UFS
housekeeping. Domino does not use data maintained by UFS. You can do this
instead by adding the noatime parameter to the data volume’s mount point in
/etc/vfstab, for example:
/dev/dsk/c4t1d0s6 /dev/rdsk/c4t1d0s6 /notesdata ufs 1 yes noatime
To improve performance and reliability, consider configuring RAID. Generally
speaking, RAID 0+1 is appropriate for Domino data directories. For transaction
logs or a Domino data directory which can be fit onto a single physical disk, RAID
1 is also a good fit.
Note: Follow these simple rules to improve disk performance:
򐂰 The volumes are spread across as many controllers as possible.
򐂰 Use the proper type of volume for your requirements.
򐂰 Use the proper stripe unit size to match your needs.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
47
3.4.3 Domino tuning
In Domino 6.5, a primary goal for the Lotus software development team was to
focus on improving Domino Web Access performance. We summarize these
improvements in 1.2.9, “Domino Web Access 6.5 performance improvements” on
page 10.
This section discusses performance tuning within Domino. Keep in mind that
most of the tuning parameters that are described need to be tuned as you go.
There is no single value or magic number that works for everybody. You must
experiment with each parameter to achieve the peak performance.
The recommended parameters and server settings are:
򐂰 Remove any unused server tasks
Many server tasks are enabled by default. If you don’t need a task, disable it.
It makes more resources available to Domino Web Access.
򐂰 Enable the “Run Web agent concurrently?” setting
To improve concurrency of Web agents, you can enable this setting. To enable
this setting, open the Domino Web Access server document, click Internet
Protocols, and click the Domino Web Engine tab. On this page, you can see
the Web Agents section as shown in Figure 3-6.
Figure 3-6 Web Agents
򐂰 Increase the number of HTTP threads
When Web server response is slow, you may increase the number of threads.
This can help to can help increase the concurrency and performance of the
Web server. The default value provided is 40. This setting is located within the
server document. Click Internet Protocols and click the HTTP tab. On this
page, you can see the Basics section as shown in Figure 3-7.
48
Domino Web Access 6.5 for Sun Solaris 9
Figure 3-7 HTTP page with the Number of active threads parameter
򐂰 Increase Maximum cached users
Domino server stores successfully authenticated users’ information, such as
name, password, and groups in memory. The default value is 64. If your Web
server is accessed by several thousands of users concurrently every day,
consider increasing this number. This setting is also located in server
document. Click Internet Protocols and click the Domino Web Engine tab.
On this page, look for the Memory Cache section as shown in Figure 3-8.
Figure 3-8 Maximum cached users
򐂰 Increase HTTP listenbacklog queue
This setting can help when users experience connection time-outs from a
browser to a Domino Web Access 6.5 server. Increasing this number may
help to alleviate time-out problems. The setting is located in the server
document. Click Internet Protocols and click the HTTP tab. Look for the
Network Settings section as shown in Figure 3-9.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
49
Figure 3-9 Listen queue size
Attention: In addition to setting the Listen queue size, you must increase
the tcp_conn_req_max_q and tcp_conn_req_max_q0 settings. You must
set the value of these to the same value that you specified in the Listen
queue size.
򐂰 Enable Gzip compression
This compression is enabled by default on your Domino 6.5 server. You can
see it in your configuration settings document. Click the Domino Web
Access tab and look for the Other Settings section as shown in Figure 3-10.
By setting Compress HTTP response data to Enable, you enable Gzip
compression.
Figure 3-10 Gzip compression
򐂰 Set NSF_DBCache_MaxEntries
If show stat database shows a lower cache hit ratio than 95%, consider
setting the NSF_DBCache_MaxEntries parameter in the server’s notes.ini file to
slightly higher than the actual number of open databases or concurrent users
you will support on the server.
This parameter adjusts the number of databases that a server can hold in its
database cache at one time. Increasing the cache size may improve the
performance, but requires additional memory. The alternative to increasing
this parameter is increasing physical memory.
50
Domino Web Access 6.5 for Sun Solaris 9
򐂰 Increase the number of Mail boxes
If you can monitor persistent delays (mail waiting) in the mail stats, consider
increasing the number of Mail.boxes. This setting is in the server configuration
document. Click Router/SMTP and the Basics tab. Look for the
Router/SMTP Basics section as shown in Figure 3-11.
Figure 3-11 Number of mailboxes
Tip for Notes_SHARED_DPOOLSIZE: This setting was recommended by
Sun to reduce address space fragmentation for Domino R5 servers. This
setting is not required for Domino R5.08 or later, including all R6 versions.
Finally, in addition to the parameters that are listed, consider such options as
transaction logging, partitioning, and clustering to improve your server’s
performance, availability, and reliability.
Note: Domino Network compression was introduced in Domino R6 to reduce
network utilization. However, it does not benefit Domino Web Access users
because it only benefits Notes Remote Procedure Call (NRPC) traffic.
Network compression is performed by NRPC and can improve the
performance of NRPC traffic such as routing and replicating hub servers. You
may read more details in the LDD Today article, “Network Compression in
Domino 6”, by Mike Gazda. This article is on the Web at:
http://www-10.lotus.com/ldd/today.nsf/0/1c4bc125e871f15300256c070059
9ee9?OpenDocument
3.4.4 Network tuning
The following section discuss options for tuning TCP and other network
parameters.
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
51
TCP parameter tuning
As explained briefly in the discussion about setting the HTTP listen queue size,
you can increase the network queue size when your server is heavily loaded.
Network tuning is performed by means of the ndd command, for example:
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q 2048
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q0 2048
To execute these settings automatically after each system reboot, you can write a
script. Name it something such as “network-tuning”. Then create a link to the file
in /etc/rc2.d, for example:
myshell> ln -s network-tuning /etc/rc2.d/S99network-tuning
TCP slow start and congestion window problem
Due to the differences in TCP implementation of Microsoft Windows operating
system, we recommend that you set tcp_slow_start_initial to 2:
myshell> /usr/sbin/ndd -set /dev/tcp tcp_slow_start_initial 2
This setting synchronizes the way that Solaris acknowledges TCP packets when
communicating with Microsoft operating systems.
Tuning TCP buffering
When you see unpredictable slowdowns in network response from a consistently
loaded server, consider investigating the sq_max_size setting. Sun recommends
that you set it to a value of 512. You can have a following line to the /etc/system
file:
set sq_max_size=512
However, during the residency for this Redpaper, Sun informed us that the
recommended value of this parameter is too high. Sun corrected the value and
now recommends that the range be between 30 and 100. For more detailed
information, on this, we recommend that you read document ID ID71160 on the
SunSolve Web site at:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=finfodoc%2F71160&zone_3
2=sq_max_size
During our performance tests, with a dedicated 100 Mb network, we were not
able to simulate a network slowdown problem like this. The default queue size, 2,
appeared to work well for us. Of course, simulation can never be the same as the
real world workload. Therefore do not neglect this parameter. It helps to
decrease dropping packets during bursty, high-speed network transactions.
52
Domino Web Access 6.5 for Sun Solaris 9
3.5 Further reading
You can find more information from the following sources:
򐂰 Lotus Domino R5 for Sun Solaris 8, SG24-5969
򐂰 Sun’s Domino on Solaris: Common Tuning Tips
http://www.sun.com/solutions/third-party/global/lotus/technical/
index.html
򐂰 Solaris Tunable Parameters Reference Manual in Solaris 9 System Admin
Collection
http://docs.sun.com
򐂰 Sun Performance and Tuning: Java and the Internet by Adrian Cockcroft,
Richard Pettit, and Sun Microsystems Press
Chapter 3. Tuning Domino Web Access 6.5 on Solaris 9
53
54
Domino Web Access 6.5 for Sun Solaris 9
4
Chapter 4.
Performance testing:
Methodology and results
This chapter concludes the paper with an analysis of our performance testing
results of Domino Web Access 6.5 on Solaris 9. They are based on several of the
tuning methods discussed earlier in the paper. We discuss both our performance
test environment and simulation methodology used for this Redpaper. We also
present the actual results of the performance tests. Ultimately, we believe that
our analysis and discussion of the performance testing results will help you to
understand better Domino Web Access 6.5 tuning on Solaris.
It is important to acknowledge that the results in this chapter are from our
simulation tests. Even though we tried to simulate a realistic environment, the
nature of a test environment is always limited in its ability to mimic a real-world
workload.
We recommend that you use our information as a reference upon which to base
performance comparisons. To obtain an accurate understanding of your system
requirements and relevant performance trends, monitor your system frequently
and capture performance data on a regularly scheduled basis.
© Copyright IBM Corp. 2004. All rights reserved.
55
4.1 Our test environment
This section describes the hardware, software, and simulation methodology used
for our performance testing.
4.1.1 Hardware and software setup
The hardware used in our test environment at a high level included one
dedicated domain on a SunFire 6800. This domain consisted of the following
hardware:
򐂰 4 CPUs: UltraSPARC III processors at 1050 MHz, 64-bit SPARC V9 with VIS
Instruction Set Architecture
򐂰 16 GB memory
򐂰 Notes data directory: T3 disk arrays, configured RAID 0
Note: For our performance testing purposes, we configured fast RAID 0.
While this was for testing purposes, we recommend that you do not
configure unreliable RAID 0 for your Domino data directory. Generally
RAID 0 +1 should be a good candidate for your Domino data directory
(see 3.4.2, “Solaris file system tuning” on page 46). RAID 0 +1 should be
as fast as RAID 0 and more reliable.
Here is an overview of the software used in our test environment:
򐂰 Operating system: Sun Solaris 9 with the latest recommended patch cluster
򐂰 Domino Enterprise Server 6.5
4.1.2 Simulation methodology and our workload
For better and extensive performance testing, we set up an internal simulation
environment which is identical to R6iNotes workload of the Server.Load tool.
Since the Server.Load tool can only spawn up to 512 users per driver, the tool
did not provide the flexibility that we needed for our testing approach. For this
reason, we developed our own internal simulation environment for R6iNotes
testing.
R6iNotes workload
This workload is a built-in script in Server.Load tool. It generates the activities
intended to simulate typical user working in Domino Web Access.
An active user sends, retrieves, and deletes mail from a browser. An average
user runs this script four times an hour. Each time the script runs, it checks and
56
Domino Web Access 6.5 for Sun Solaris 9
retrieves mail messages. In addition, on each sixth iteration, the user sends a
mail message to three other users on the server. The user schedules an
appointment, sends invitations to three other users, and responds to one
invitation in the person’s inbox.
For those who already familiar with R5iNotes workload(R5iNotes), Table 4-1
compares the R5iNotes workload with R6iNotes.
Table 4-1 R5iNotes versus R6iNotes
Actions every 90 minutes
R5iNotes
R6iNotes
Open Inbox
6
6
Read Message
30
30
Delete Message
6
12
Add Message to Inbox
None
2 (100 KB average)
Send Message to three recipients
1 (10 KB)
1 (100 KB average)
Send Invitation to three recipients
None
1
Send RSVP
None
1
Close Inbox
6
6
For more information about R6iNotes workload, see the article “The new Domino
6 NotesBench workloads: Heavier by request!” by Razeyah Stephen on the Lotus
Developer Domain (LDD) at:
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b380/
f0c8da415b9112c300256c440027ce70?OpenDocument&Highlight=0,R6iNotes
You can also reference the Lotus Domino Administrator 6.5 Help for more
information about the Server.Load tool.
Simulating large quantities of users
We generated up to 3500 users using the R6iNotes workload in our simulation
environment to measure the performance of our Domino Web Access server.
Our simulation tool starts with 700 users and adds 700 more users every 90
minutes.
4.1.3 Performance improvement process
Before we discuss our actual performance test results, we review information
regarding a general performance improvement process. We hope it helps you to
plan your own performance tuning or improvement plan.
Chapter 4. Performance testing: Methodology and results
57
The performance improvement process requires you to:
1. Establish performance base lines.
2. Define performance objectives.
3. Develop a performance monitoring plan.
4. Carry out the plan.
5. Analyze your measurements to determine if you have met your objectives.
6. Determine the major constraints in your system.
7. Decide where you can afford to make trade-offs and which resources can
handle additional load.
8. Continue monitoring.
4.2 Performance studies and the results
During our performance testing, we focused on demonstrating how a system
responds to each tuning parameter or a group of parameters. The purpose was
not to find the best numbers that will work in your specific environment. In reality,
we simply can’t develop numbers that will work for everyone’s system.
For this reason, we took an approach to show how our system reacts to the
changes of tuning parameters. This allows us to demonstrate the impact of each
tuning parameter or a group of tuning parameters in some situations to help you
understand them better. For a description of what the tuning parameters used do,
see 3.4, “Tuning considerations” on page 44.
The following section presents the five studies from our performance tests.
4.2.1 Study 1: Is the disk system a bottleneck?
First, we looked at the slowest device in the system—disk. Amazingly, our
performance tests showed that the T3 disk array system handles the R6iNotes
workload very well. The only negative thing that we could monitor was sporadic
and frequent bursts or spikes in the disk service time in iostat output. To
improve the service time, we tried to evenly distribute user mail databases in two
separate physical arrays. Later we located mail boxes (mail.box) in a separate
array from all user mail databases to reduce disk input/output (I/O) contentions.
Our approach was successful in reducing the worst cases of bursts or spikes in
service time. However, these improvements didn’t contribute much toward
improving Domino Web Access’s performance.
58
Domino Web Access 6.5 for Sun Solaris 9
From this test, we concluded that the disk system is not a major bottleneck of our
server’s performance. The T3 disk array system was connected over its
dedicated fiber optic channel. This fast connection, together with its own built-in
data distribution algorithm, appear to be doing an excellent job of handing our
workload.
For more information about disk-related tuning, see 3.4.2, “Solaris file system
tuning” on page 46.
4.2.2 Study 2: Can CPU utilization be improved by fsflush tuning?
Next, we looked at our system’s “brain”—the CPU. To improve its utilization, we
studied fsflush tunables to reveal how CPUs react on these parameters. The
values that we examined were:
򐂰 default value: tune_t_fsflushr=5, autoup=30(5/30)
򐂰 tune_t_fsflushr=1, autoup=600(1/600)
򐂰 tune_t_fsflushr=30, autoup=900(30/900)
You can find more information about fsflush tuning in 3.4.1, “Solaris kernel
tuning” on page 44.
Every 90 minutes, our simulation tool added 700 more users to the server. The
results of our test are shown in the graph in Figure 4-1.
By adjusting the values of the fsflush tunables, we could start with about 50%
less CPU consumption. This can also prevent the CPU from spiking during the
low active user sessions, such as those with less than 1400 users. Overall, we
improved CPU utilization, since this tuning enabled the CPUs to become more
reasonably utilized as we expected. Unlike the spiking CPU utilization shown
from the default value (5/30), the other tunings illustrate each CPU becoming
more utilized as we have more users.
We conclude that the second tuning (tune_t_fsflushr=1, autoup=600(1/600)) is
the best fit for our test server since it showed a little better CPU utilization during
the first six hours. Note that the first six-hour period is meaningful because the
Domino Web Access server response time was less than one second during the
time period.
However, we believe the difference between second tuning (1/600) and third
tuning (30/600) is almost negligible. In Sun’s internal benchmark testing, the third
tuning (30/900) actually showed the best result. Keep in mind, however, that
Sun’s hardware configuration is radically different from our test environment.
Therefore, we cannot directly compare their results with ours.
Chapter 4. Performance testing: Methodology and results
59
We highly recommend that you experiment with these parameters to achieve the
best results for your specific environment.
Figure 4-1 CPU utilizations with different fsflush tunables
For more information about Sun’s benchmark, see:
http://www.sun.com/solutions/third-party/global/lotus/collateral/
r6i_benchmark.pdf
4.2.3 Study 3: Can page-in rates be improved by segmap_percent?
Next we looked another important component of system performance—memory.
During our performance tests, we couldn’t detect any major memory problem
such as memory shortage or a high scan rate.
While we did not detect specific memory problems, we can illustrate how you can
improve your page-in rates by having proper segmap_percent value. The values
we examined are:
򐂰 segmap_percent=32
򐂰 segmap_percent=48
򐂰 segmap_percent=64
60
Domino Web Access 6.5 for Sun Solaris 9
For reference information, the default value is 12. We found the default value to
be too low for our R6iNotes workload. A comparison graph is shown in
Figure 4-2. For more information about tuning this parameter, see 3.4.1, “Solaris
kernel tuning” on page 44.
As in previous tests, our tool added 700 more users every 90 minutes.
Figure 4-2 Page-in rates with different Segmap_percent
Table 4-2 summarizes the total number of page-ins during the tests.
Table 4-2 Total number of page-ins
segmap_percent
32%
48%
64%
Total page-ins
38091
35459
43212
To summarize, 48% of segmap_percent showed the least number of page-ins.
Overall it seems to be the best value for our server. The only caveat of this
parameter is that it requires more kernel memory to have a higher percentage.
Accordingly, you must experiment this parameter to find a proper percentage that
the system’s memory can cope with.
Chapter 4. Performance testing: Methodology and results
61
4.2.4 Study4: Network improvement?
Next we looked at the network aspect of performance. People often think that
network performance can be improved by merely increasing bandwidth. Perhaps
buying a Gb network is the easiest solution. Alternatively, we can use an
approach to reduce the number of transmitted packets instead of buying
expensive network equipment. Domino Web Access 6.5 is especially strong in
this regard.
The IBM Lotus Domino Web Access development team added the Gzip
compression feature to Domino Web Access 6.5. This feature helps to
significantly reduce the number of packets transmitted. Our tests showed just
how much Gzip compression can reduce the number of packets in a network.
We also performed network Listen Queue tuning (listenbacklog). However, this
tuning didn’t help much toward improving performance or in reducing the number
of packets. Partially, this result is because our network had almost no packet loss
(negligible amount of packets lost) during testing.
Keep in mind that if your network is heavily loaded and experiencing some or a
rather considerable amount of packet loss, increasing the Listen Queue
(listenbacklog) size helps the server’s performance and to reduce the number of
packets transmitted. Packet loss basically means retransmission of packets. Too
much re-transmission wastes network bandwidth.
For more information of tuning the Listen Queue and other network-related
parameters, see 3.4.4, “Network tuning” on page 51.
As you can see in the graph in Figure 4-3, Gzip compression can reduce the
number of packets almost up to 75%. This is a significant improvement. In
Domino Web Access 6.5, Gzip is enabled on your server by default. To take
advantage of this feature, you need to be certain that your users are using a
browser that is compatible with Gzip compression. All of the browsers listed as
supported for Domino Web Access 6.5 can use Gzip compression.
62
Domino Web Access 6.5 for Sun Solaris 9
Figure 4-3 TotalBytesPerSec
4.2.5 Study 5: More HTTP threads = faster?
Lastly, we experimented with the number of Hypertext Transfer Protocol (HTTP)
threads. Do more worker threads improve either response time or throughput to
improve the server’s performance? To find the answer, we performed specific
sets of tests focused on this parameter and measured the HTTP response time,
CPU utilization, and Domino server transactions per minute. For more
information about how to change the number of HTTP threads, refer to 3.4.3,
“Domino tuning” on page 48.
For a complete analysis, we examined several aspects of server performance.
First, we showed you the response time. Then we compared the results of
response time with CPU utilization, and the number of Domino transactions per
minute. Figure 4-4 illustrates the response time in milliseconds, and how it was
affected as the number of users increased. The three lines indicate the different
results based on the number of HTTP threads allocated.
Chapter 4. Performance testing: Methodology and results
63
To compare the response time more precisely, the graph in Figure 4-4 is scaled
down to between 0 and 1 seconds. As you can see from the graph, having 80
worker threads rather than 40 worker threads is beneficial up to 2300 concurrent
users. But, as more users are added to the server, the response time of 80
worker threads starts to be slower than the response time of 40 worker threads.
Initially, this result may seem counterintuitive. To gain a better understanding of
what is happening, we try to correlate the symptom with CPU utilization.
Figure 4-4 HTTP Response Time
64
Domino Web Access 6.5 for Sun Solaris 9
Figure 4-5 illustrates the percentage of CPU utilization, based on the number of
users and the number of HTTP threads.
Figure 4-5 CPU utilization
HTTP threads and CPU utilization
To correlate the number of HTTP threads to the percentage of CPU utilization,
we want to clarify an important question: How is CPU utilization impacted by
adding 40 more worker threads?
Figure 4-5 can help to find the answer. The CPU utilization of 80 threads
becomes higher after having somewhere between 2200 and 2300 concurrent
users. Why is this happening? We can simply answer that it is because CPUs are
becoming much busier with 40 additional threads. The additional load of 40 more
threads is beginning to translate directly into higher CPU utilization.
From the results, we can understand that more worker threads consume more
system resources. If a server doesn’t have enough worker threads to handle
users’ HTTP requests, the users receive slower response or even time-out
errors. Their requests need to wait until the worker threads currently engaged by
another request become available. Ideally if a server always has enough number
of worker threads available for incoming HTTP requests, the server performs the
best. Therefore, it is a trade-off between your available resources and the
response time.
Chapter 4. Performance testing: Methodology and results
65
The outstanding question is whether more threads do more work? The answer
does not appear to be positive. To gain a better understanding, we compared the
number of Domino server’s transactions. While the number of transactions may
include some other transactions generated by other processes than HTTP, the
number of these “other” transactions generated by other processes should be
minimal. Therefore, we believe these numbers are still meaningful to be
compared. Figure 4-6 shows the results of this test to see if additional threads
result in additional transactions per minute.
Figure 4-6 Transactions per minute
In conclusion, more HTTP threads can help users to have quicker responses as
long as the system is powerful enough to handle additional loads resulting from
additional worker threads. It’s important to have a proper number of worker
threads to help your server’s performance. Remember, however, that having an
excessive number of threads can be rather harmful to your performance if it
causes much higher CPU utilization and eventually reduces the transactions per
minute. Alternatively, too few HTTP threads make some users wait until threads
engaged by other users become free.
We strongly recommend that you experiment with this parameter to find a
suitable value for your server.
66
Domino Web Access 6.5 for Sun Solaris 9
4.3 Conclusion: Test summary
After a series of performance tests, our Domino Web Access 6.5 served up to
about 2800 active concurrent users with less than one second response time.
The DBcache hit ratio always stayed above 97.6% during all of our performance
tests. Overall, our performance tuning allowed us to gain about 700 more users
with less than one second response time. In addition, we increased the number
of transactions per minute.
We conclude this chapter by showing you two comparison graphs that focus on:
򐂰 Response Time (Figure 4-7)
򐂰 Number of Transactions per Minute (Figure 4-8)
Base line represents our initial test with no tuning. After tuning is our best test
result after performing tuning based on the explanations in this chapter and in
Chapter 3, “Tuning Domino Web Access 6.5 on Solaris 9” on page 33. By
following our guidelines for tuning, not the values we used, these tests can help
you to improve your server’s performance.
Figure 4-7 Response time comparison
Chapter 4. Performance testing: Methodology and results
67
Figure 4-8 Transactions per minute comparison
Review of after tuning settings
In our after tuning testing, we made the following changes:
򐂰 We created our file systems as recommended in 3.4.2, “Solaris file system
tuning” on page 46, and mounted them with noatime.
򐂰 In /etc/system, we tuned the following parameters:
–
–
–
–
set msgsys:msginfo_msgtql=1024
set tune_t_fsflushr=1
set autoup=600
set segmap_percent=48
򐂰 In Domino, we tuned the following parameters:
– Enabled “Run agents concurrently”
– Set HTTP worker threads 80
– Set maximum cached users 4000
򐂰 Had one mailbox (mail.box)
As you can see in Figure 4-7 and Figure 4-8, we were successful in gaining
about 700 more users with less than one second response time. We did this
without constraining the number of transactions per minute handled by the
server.
68
Domino Web Access 6.5 for Sun Solaris 9
A
Appendix A.
Additional material
This Redpaper refers to additional material that can be downloaded from the
Internet as described below.
Locating the Web material
The Web material associated with this Redpaper is available in softcopy on the
Internet from the IBM Redbooks Web server. Point your Web browser to:
ftp://www.redbooks.ibm.com/redbooks/REDP3769
Alternatively, you can go to the IBM Redbooks Web site at:
ibm.com/redbooks
Select the Additional materials and open the directory that corresponds with
the Redpaper form number, REDP3769.
© Copyright IBM Corp. 2004. All rights reserved.
69
Using the Web material
The additional Web material that accompanies this Redpaper includes the files:
File name
reference_startstop_script.zip
readme_first.txt
domino
Description
File for download
Readme file
Script for starting or rebooting the Domino
server
How to use the Web material
Create a subdirectory (folder) on your workstation, and unzip the contents of the
Web material zip file into this folder.
70
Domino Web Access 6.5 for Sun Solaris 9
Related publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of some of the topics covered in this Redpaper.
IBM Redbooks
The following IBM Redbooks provide good background reading behind some of
the technologies discussed in this paper:
򐂰 Lotus Domino R5 for Sun Solaris 8, SG24-5969
򐂰 iNotes Web Access Deployment and Administration, SG24-6518
򐂰 Domino Web Access 6.5 on Linux, SG24-7060 (available soon)
Referenced Web sites
These Web sites were referenced within this paper as relevant further
information sources:
Lotus Developer Domain
General Domino Web Access information can be found within the Lotus
Developer Domain:
http://www.ibm.com/software/lotus/products/dominowebaccess/
These specific LDD articles and documents were discussed in this paper:
򐂰 “Exploiting dynamic HTML: Lessons from iNotes Web Access” by Vinod
Seraphin and David Dejean
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b3
80/77d60e9c1a10909f85256b9d00593986?OpenDocument&Highlight=0,inotes
򐂰 iNotes Web Access Deployment Guide
http://www-10.lotus.com/ldd/notesua.nsf/find/inotes
򐂰 “Start Using Domino 6 Server Health Monitoring Now" by Carol Zimmet
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b3
80/453d9e87c12cda0800256bce003f3c6e?OpenDocument&Highlight=0,domino,
server,health,monitoring
© Copyright IBM Corp. 2004. All rights reserved.
71
򐂰 "Network compression in Domino 6" by Mike Gazda”
http://www-10.lotus.com/ldd/today.nsf/0/1c4bc125e871f15300256c070059
9ee9?OpenDocument
򐂰 “The new Domino 6 NotesBench workloads: Heavier by request!” by Razeyah
Stephen
http://www-10.lotus.com/ldd/today.nsf/62f62847467a8f78052568a80055b3
80/f0c8da415b9112c300256c440027ce70?OpenDocument&Highlight=0,
R6iNotes
Solaris Developer Connection
The Solaris Developer Connection is full of technical articles and whitepapers
that will help ensure successful deployment on the Solaris platform. Point your
browser to:
http://soldc.sun.com/
These specific articles and documents were discussed within this paper:
򐂰 Solaris 9 Installation Roadmap
http://docs.sun.com/db/coll/214.12
򐂰 Sun’s Domino on Solaris: Common Tuning Tips
http://www.sun.com/solutions/third-party/global/lotus/technical/
index.html
򐂰 What’s New in the Solaris 9 Operating Environment
http://docs.sun.com/db?p=/doc/806-5202
򐂰 Solaris Tunable Parameters Reference Manual in Solaris 9 System Admin
Collection
http://docs.sun.com
򐂰 “What does 100 percent busy mean?” by Adrian Cockcroft
http://www.sun.com/sun-on-net/itworld/UIR990801perf.html
򐂰 Cockcroft, Adrian; Pettit, Richard; Sun Microsystems Press. Sun Performance
and Tuning: Java and the Internet. Prentice Hall PTR 1998. ISBN
0-13-095249-4.
72
Domino Web Access 6.5 for Sun Solaris 9
How to get IBM Redbooks
You can search for, view, or download Redbooks, Redpapers, Hints and Tips,
draft publications and Additional materials, as well as order hardcopy Redbooks
or CD-ROMs, at this Web site:
ibm.com/redbooks
Help from IBM
IBM Support and downloads
ibm.com/support
IBM Global Services
ibm.com/services
Related publications
73
74
Domino Web Access 6.5 for Sun Solaris 9
Back cover
Domino Web Access 6.5
for Sun Solaris 9
Discover the
features and
benefits of running
Domino Web Access
6.5 on Solaris 9
Learn about hints
and tips for
installation and
setup
Gain helpful
knowledge about
performance tuning
and testing
®
Redpaper
IBM Lotus Domino Web Access 6.5 is a sophisticated Web
client. It gives end users many of the messaging and
collaboration features previously available only with a Lotus
Notes client. The Solaris 9 Operating Environment is the
foundation for Sun systems, from smaller departmental servers
to massive, clustered servers with more than 100 CPUs.
INTERNATIONAL
TECHNICAL
SUPPORT
ORGANIZATION
This IBM Redpaper provides a technical overview of Domino
Web Access 6.5. It discusses how to install and configure
Domino Web Access 6.5 on Solaris 9. It also discusses
performance tuning considerations for both Solaris 9 and
Domino Web Access 6.5. This Redpaper explains:
BUILDING TECHNICAL
INFORMATION BASED ON
PRACTICAL EXPERIENCE
򐂰 The new features included with Domino Web Access 6.5
for Solaris 9
򐂰 Basic installation and setup guidelines for Domino Web
Access 6.5 on Solaris 9
򐂰 General Solaris performance monitoring techniques that
are appropriate for Domino Web Access 6.5
򐂰 Performance tuning suggestions for optimizing a Domino
Web Access 6.5 install on Solaris 9
򐂰 Results and analysis of basic performance benchmarks
that demonstrate the scalability of Domino Web Access
6.5 on Solaris 9
IBM Redbooks are developed by
the IBM International Technical
Support Organization. Experts
from IBM, Customers and
Partners from around the world
create timely technical
information based on realistic
scenarios. Specific
recommendations are provided
to help you implement IT
solutions more effectively in
your environment.
For more information:
ibm.com/redbooks