Lotus Domino/Lotus Notes/LotusNotes
IBM® Lotus® Domino® software
provides world-class collaboration capabilities that can be deployed as a core
e-mail and enterprise scheduling infrastructure, as a business application
platform, or both.
Lotus Domino software and its client software options deliver a
reliable, security-rich messaging and collaboration environment that helps
companies enhance the productivity of people, streamline business processes and
improve overall business responsiveness.
IBM Domino products
· IBM Domino
· Collaboration Express
· Enterprise Server (on premises, or via cloud in IBM SmartCloud Enterprise)
· Messaging Express
· Messaging Server (on premises, or via cloud in IBM SmartCloud Notes)
· Utility Express
· Utility Server (on premises, or via cloud in IBM SmartCloud Enterprise)
· IBM Domino Administrator Client
· IBM Domino Designer Client
· IBM iNotes (IBM Lotus Domino Web Access before 2008)
· Lite Mode (for slow connections, available since 8.0.1)
· Ultralite Mode (for Safari browser on Apple iPhone, available since 8.0.2)
· IBM Notes Traveler
existing Domino infrastructure, there are some additional areas to be reviewed and
evaluated. You should evaluate your current Domino environment thoroughly when planning
your upgrade. Some things you should consider include:
_ Domain and directory configuration
– The number of domains you have
– The types of domains you have
– The types of directories in use
Planning the Notes and Domino 8 Deployment
_ Mail routing topology
_ Replication topology
_ Application topology
_ User and server registration process used in your organization
– Naming standards for users and servers
– Domino certificates for organization and organizational units
_ Domino software upgrade procedures currently used in your organization
_ Hardware age and capacity
_ Usage patterns on each server
_ Template customization
_ Third-party software
– Virus scanning
– Spam scanning
– Backup
– Monitoring
– Mobile device support
The goal of the review of your existing Domino environment is to understand whether it is
meeting your needs and how close to capacity your environment is. Typically, older
enterprise deployments have grown organically and incrementally, as the needs of the
organization have changed. Growth in the size and maturity of an organization, mergers,
acquisitions, and divestitures all have an effect on deployments, with changes typically being
tactical and incremental, rather than strategic.
When reviewing your Domino environment, you may find a need for some new hardware or
added capacity. You may also see an opportunity for server consolidation.
For many organizations, e-mail is considered a mission-critical application. For this reason,
special attention should be given to the evaluation of your mail infrastructure. When
assessing your Domino mail servers, you should consider each of the following areas:
_ General server performance
– Responsiveness
– Average and peak CPU utilization
– Average and peak memory utilization
– Average and peak transactions per minute
– Average and peak disk utilization
_ Total disk usage for mail files
_ Average mail file size
_ Largest mail files
_ Current quota practices
_ Current archiving practices
_ Average number of messages processed each day
IBM Lotus Notes and Domino 8 Deployment Guide
_ Average number of concurrent users
_ Peak usage times
_ Usage of local replica model
_ Inbox size
_ Attachment compression
_ Standard settings and configurations
_ Use of Web-based mail
– HTTP
– IMAP
– SSL
– RSS
You are probably already monitoring many of these things, and you may have historical data
to show you how disk space usage and CPU utilization has increased over time. You may
also track your top 10 largest mail files, and track the overall disk footprint of mail files on your
servers. You may even have implemented an archiving and quota strategy to keep your mail
files at or below a specified size, as well as a local replica model to improve user experience
and decrease user impact in the event of network or server issues.
Wherever you are today, understanding the work that your mail servers do is a very important
part of assessing your overall Domino environment.
Considerations for application servers
From a similar perspective, you should consider your application servers carefully. In some
ways, your application servers are more difficult to assess than your mail servers because of
different usage patterns and differences in application design. However, many of the same
things should be assessed in your review.
Information to collect while assessing your application environment includes:
_ List of all application servers in your environment
_ List of any mixed-use servers (mail and application)
_ Locations of critical and enterprise-wide applications
_ List of servers dedicated to a specific application
_ Inventory of all non-mail applications
_ Usage patterns
– Critical and enterprise-wide applications
– Application servers
_ Use of Web applications
– HTTP
– SSL
– RSS
_ Replication topology
_ Attachment handling
_ Any specialized functions or features used by applications
_ Backup methodology
_ Dependencies between databases in complex applications (such as lookups)
_ Use of applications to send mail
Using the database catalog on your application servers, or on any server on which you allow
users to create databases, is a good way to develop your application inventory. The catalog
also provides information such as ACL listings and information about reads and writes on the
database. Additionally, you can redirect the output of a directory list command on the
operating system to develop a list of all databases and applications on your servers.
Chapter 2. Planning the Notes and Domino 8 Deployment 27
Because of the varied nature of applications, there may well be other concerns as well. It is
important to work closely with your development teams to gain a full understanding of your
application environment.
Third-party applications
Like many organizations, you may have third-party applications in place in your environment,
such as anti-spam, anti-virus, backup, and monitoring. When reviewing your Domino
environment, it is important to fully understand the third-party applications you have in your
environment.
Things to consider while assessing the use of third-party applications in your environment
include:
_ Which third-party applications you have in place
_ Versions of each third-party application
_ Dependencies for each third-party application
_ Interaction between Domino and third-party applications
There may well be other concerns, depending on the nature of the third-party applications
you have in place. Because of the variety of applications and vendors, it is important to work
closely with the teams supporting these applications to fully understand their usage in your
environment.
Template customization
When evaluating your environment, you should also consider any customizations that you
have made to templates. It is possible that customizations have been made to mail templates,
directory templates, and application templates that ship with Notes and Domino, such as
teamroom and discussion. You need to consider any customizations that have been made,
and determine whether any customizations need to be carried forward into the templates that
ship with Notes and Domino 8.
If you do have template customizations, best practices suggest that you create a new custom
template based on the template that ships with the version of code you deploy. This may
involve re-coding certain changes to ensure full compatibility.
Table 2-1 provides a checklist of things to consider based on the areas listed in this section.
Table 2-1 Existing Domino environment evaluation questionnaire
Area of concern Things to consider
Stakeholders
CTO/CIO
Users
Client/desktop software team
Deployment team
Domino admin/operations team
Help desk/support team
Network admin
Storage admin
Other admins (Portal, WAS, DB2, Web servers)
Organizational
concerns
Countries in which you do business
Number of locations/facilities
Number of users
Domino environment -
general
Domain and directory configurations
The number of domains you have
The types of domains you have
The types of directories in use
Replication topology
Naming standards
Domino certificates in use (O, OUs)
User registration process used in your organization
Domino software upgrade procedures currently used in your
Hardware age and capacity
Template customization
Domino environment -
mail
Locations of key mail files (executives)
Average mail file size per server
Largest mail files per server
Archive strategy
Quota strategy
Mail routing topology
Usage patterns on each server
Average number of messages processed each day
Average concurrency rate
Peak usage times
Usage of local replica model
Inbox size
Attachment compression
Standard settings and configurations
Use of IMAP/HTTP/SSL/RSS for mail
Domino environment -
applications
Location of critical applications
Location of enterprise-wide applications
Usage patterns on each server
Any servers dedicated to a specific application
Use of HTTP/SSL/RSS for applications
Replication topology
Attachment handling
Specialized functions or features used by applications
Backup methodology
Dependencies between databases in complex applications (such as
lookups)
Use of applications to send mail
User types Executives
Desktop
Laptop
Kiosk: DWA
Kiosk: Notes multi-user
Roaming users
Telecommuters
Mobile device users
process is essentially the same as for an existing Domino infrastructure upgrade. The
additional concerns include:
_ Designing your Domino architecture
– Planning your hierarchy
– Determining your organizational structure
_ Setting your naming standards
_ Defining your topologies
– Mail routing
– Replication
_ Planning your administration strategy
– Centralized or regional
– User management
– Server management
– Application management
Network/Infrastructure Geographic distribution of users and servers
Network topology
Current network bandwidth usage in each geographic location and
between locations
Network bandwidth availability and cost for each geographic location
Storage subsystems
Documentation Infrastructure diagrams
Standard configurations (client and server)
Lists of customizations
Procedure documents
Organizational best practices
Other concern Governmental regulations
Business pressures
Other data stores you may want to utilize
Future needs Planned mergers, acquisitions, divestitures
Planned or expected hiring
Increased usage of products due to new features
Increased traffic on network/servers
Increases in mail file or application size
Planned changes in corporate strategy
Third-party applications
(such as backup,
anti-virus, anti-spam,
monitoring, mobile)
Third-party applications you have in place
Versions of each third-party application
Dependencies for each third-party application
Interaction between Domino and third-party applications
Area of concern Things to consider
Environment evaluation questionnaire: new Domino deployment
Area of concern Things to consider
Stakeholders CTO/CIO
Users
Client/desktop software team
Deployment team
Domino admin/operations team
Help desk/support team
Network admin
Storage admin
Other admins (Portal, WAS, DB2, Web servers)
Organizational
concerns
Countries in which you do business
Number of locations/facilities
Number of users
User types Executives
Desktop users
Laptop users
Kiosk: DWA
Kiosk: Notes multi-user
Roaming users
Telecommuters
Mobile device users
Network/infrastructure Geographic distribution of users and servers
Network topology
Current network bandwidth usage in each geographic location and
between locations
Network bandwidth availability and cost for each geographic location
Storage subsystems
Documentation Infrastructure diagrams
OS and software versions
Standard configurations (client and server)
Lists of customizations
Procedure documents
Organizational best practices
Other concerns Governmental regulations
Business pressures
Other data stores you may want to utilize
Future needs Planned mergers, acquisitions, divestitures
Planned or expected hiring
Increased usage of products due to new features
Increased traffic on network/servers
Increases in mail file or application size
Planned changes in corporate strategy
Third-party applications Backup
Spam
Virus scanning
Monitoring
Considerations for upgrading an existing Domino infrastructure
In addition to the general areas of concern listed in this section, when you are evaluating anexisting Domino infrastructure, there are some additional areas to be reviewed and
evaluated. You should evaluate your current Domino environment thoroughly when planning
your upgrade. Some things you should consider include:
_ Domain and directory configuration
– The number of domains you have
– The types of domains you have
– The types of directories in use
Planning the Notes and Domino 8 Deployment
_ Mail routing topology
_ Replication topology
_ Application topology
_ User and server registration process used in your organization
– Naming standards for users and servers
– Domino certificates for organization and organizational units
_ Domino software upgrade procedures currently used in your organization
_ Hardware age and capacity
_ Usage patterns on each server
_ Template customization
_ Third-party software
– Virus scanning
– Spam scanning
– Backup
– Monitoring
– Mobile device support
The goal of the review of your existing Domino environment is to understand whether it is
meeting your needs and how close to capacity your environment is. Typically, older
enterprise deployments have grown organically and incrementally, as the needs of the
organization have changed. Growth in the size and maturity of an organization, mergers,
acquisitions, and divestitures all have an effect on deployments, with changes typically being
tactical and incremental, rather than strategic.
When reviewing your Domino environment, you may find a need for some new hardware or
added capacity. You may also see an opportunity for server consolidation.
Considerations for mail servers
For many organizations, e-mail is considered a mission-critical application. For this reason,
special attention should be given to the evaluation of your mail infrastructure. When
assessing your Domino mail servers, you should consider each of the following areas:
_ General server performance
– Responsiveness
– Average and peak CPU utilization
– Average and peak memory utilization
– Average and peak transactions per minute
– Average and peak disk utilization
_ Total disk usage for mail files
_ Average mail file size
_ Largest mail files
_ Current quota practices
_ Current archiving practices
_ Average number of messages processed each day
IBM Lotus Notes and Domino 8 Deployment Guide
_ Average number of concurrent users
_ Peak usage times
_ Usage of local replica model
_ Inbox size
_ Attachment compression
_ Standard settings and configurations
_ Use of Web-based mail
– HTTP
– IMAP
– SSL
– RSS
You are probably already monitoring many of these things, and you may have historical data
to show you how disk space usage and CPU utilization has increased over time. You may
also track your top 10 largest mail files, and track the overall disk footprint of mail files on your
servers. You may even have implemented an archiving and quota strategy to keep your mail
files at or below a specified size, as well as a local replica model to improve user experience
and decrease user impact in the event of network or server issues.
Wherever you are today, understanding the work that your mail servers do is a very important
part of assessing your overall Domino environment.
Considerations for application servers
From a similar perspective, you should consider your application servers carefully. In some
ways, your application servers are more difficult to assess than your mail servers because of
different usage patterns and differences in application design. However, many of the same
things should be assessed in your review.
Information to collect while assessing your application environment includes:
_ List of all application servers in your environment
_ List of any mixed-use servers (mail and application)
_ Locations of critical and enterprise-wide applications
_ List of servers dedicated to a specific application
_ Inventory of all non-mail applications
_ Usage patterns
– Critical and enterprise-wide applications
– Application servers
_ Use of Web applications
– HTTP
– SSL
– RSS
_ Replication topology
_ Attachment handling
_ Any specialized functions or features used by applications
_ Backup methodology
_ Dependencies between databases in complex applications (such as lookups)
_ Use of applications to send mail
Using the database catalog on your application servers, or on any server on which you allow
users to create databases, is a good way to develop your application inventory. The catalog
also provides information such as ACL listings and information about reads and writes on the
database. Additionally, you can redirect the output of a directory list command on the
operating system to develop a list of all databases and applications on your servers.
Chapter 2. Planning the Notes and Domino 8 Deployment 27
Because of the varied nature of applications, there may well be other concerns as well. It is
important to work closely with your development teams to gain a full understanding of your
application environment.
Third-party applications
Like many organizations, you may have third-party applications in place in your environment,
such as anti-spam, anti-virus, backup, and monitoring. When reviewing your Domino
environment, it is important to fully understand the third-party applications you have in your
environment.
Things to consider while assessing the use of third-party applications in your environment
include:
_ Which third-party applications you have in place
_ Versions of each third-party application
_ Dependencies for each third-party application
_ Interaction between Domino and third-party applications
There may well be other concerns, depending on the nature of the third-party applications
you have in place. Because of the variety of applications and vendors, it is important to work
closely with the teams supporting these applications to fully understand their usage in your
environment.
Template customization
When evaluating your environment, you should also consider any customizations that you
have made to templates. It is possible that customizations have been made to mail templates,
directory templates, and application templates that ship with Notes and Domino, such as
teamroom and discussion. You need to consider any customizations that have been made,
and determine whether any customizations need to be carried forward into the templates that
ship with Notes and Domino 8.
If you do have template customizations, best practices suggest that you create a new custom
template based on the template that ships with the version of code you deploy. This may
involve re-coding certain changes to ensure full compatibility.
Evaluation questionnaire: existing Domino environment
Table 2-1 provides a checklist of things to consider based on the areas listed in this section.
Table 2-1 Existing Domino environment evaluation questionnaire
Area of concern Things to consider
Stakeholders
CTO/CIO
Users
Client/desktop software team
Deployment team
Domino admin/operations team
Help desk/support team
Network admin
Storage admin
Other admins (Portal, WAS, DB2, Web servers)
Organizational
concerns
Countries in which you do business
Number of locations/facilities
Number of users
Domino environment -
general
Domain and directory configurations
The number of domains you have
The types of domains you have
The types of directories in use
Replication topology
Naming standards
Domino certificates in use (O, OUs)
User registration process used in your organization
Domino software upgrade procedures currently used in your
Hardware age and capacity
Template customization
Domino environment -
Locations of key mail files (executives)
Average mail file size per server
Largest mail files per server
Archive strategy
Quota strategy
Mail routing topology
Usage patterns on each server
Average number of messages processed each day
Average concurrency rate
Peak usage times
Usage of local replica model
Inbox size
Attachment compression
Standard settings and configurations
Use of IMAP/HTTP/SSL/RSS for mail
Domino environment -
applications
Location of critical applications
Location of enterprise-wide applications
Usage patterns on each server
Any servers dedicated to a specific application
Use of HTTP/SSL/RSS for applications
Replication topology
Attachment handling
Specialized functions or features used by applications
Backup methodology
Dependencies between databases in complex applications (such as
lookups)
Use of applications to send mail
User types Executives
Desktop
Laptop
Kiosk: DWA
Kiosk: Notes multi-user
Roaming users
Telecommuters
Mobile device users
Considerations for a new Domino deployment
When evaluating your existing environment in order to plan a new deployment of Domino, theprocess is essentially the same as for an existing Domino infrastructure upgrade. The
additional concerns include:
_ Designing your Domino architecture
– Planning your hierarchy
– Determining your organizational structure
_ Setting your naming standards
_ Defining your topologies
– Mail routing
– Replication
_ Planning your administration strategy
– Centralized or regional
– User management
– Server management
– Application management
Network/Infrastructure Geographic distribution of users and servers
Network topology
Current network bandwidth usage in each geographic location and
between locations
Network bandwidth availability and cost for each geographic location
Storage subsystems
Documentation Infrastructure diagrams
Standard configurations (client and server)
Lists of customizations
Procedure documents
Organizational best practices
Other concern Governmental regulations
Business pressures
Other data stores you may want to utilize
Future needs Planned mergers, acquisitions, divestitures
Planned or expected hiring
Increased usage of products due to new features
Increased traffic on network/servers
Increases in mail file or application size
Planned changes in corporate strategy
Third-party applications
(such as backup,
anti-virus, anti-spam,
monitoring, mobile)
Third-party applications you have in place
Versions of each third-party application
Dependencies for each third-party application
Interaction between Domino and third-party applications
Area of concern Things to consider
Environment evaluation questionnaire: new Domino deployment
Area of concern Things to consider
Stakeholders CTO/CIO
Users
Client/desktop software team
Deployment team
Domino admin/operations team
Help desk/support team
Network admin
Storage admin
Other admins (Portal, WAS, DB2, Web servers)
Organizational
concerns
Countries in which you do business
Number of locations/facilities
Number of users
User types Executives
Desktop users
Laptop users
Kiosk: DWA
Kiosk: Notes multi-user
Roaming users
Telecommuters
Mobile device users
Network/infrastructure Geographic distribution of users and servers
Network topology
Current network bandwidth usage in each geographic location and
between locations
Network bandwidth availability and cost for each geographic location
Storage subsystems
Documentation Infrastructure diagrams
OS and software versions
Standard configurations (client and server)
Lists of customizations
Procedure documents
Organizational best practices
Other concerns Governmental regulations
Business pressures
Other data stores you may want to utilize
Future needs Planned mergers, acquisitions, divestitures
Planned or expected hiring
Increased usage of products due to new features
Increased traffic on network/servers
Increases in mail file or application size
Planned changes in corporate strategy
Third-party applications Backup
Spam
Virus scanning
Monitoring
No comments:
Post a Comment