1. Lotus Domino 7.0 New Administration & Server Features
David Stephens
SSR-BP, Portal Evangelist
San Clemente, CA

2. Agenda Why upgrade to Domino 7? What’s the upgrade sequence?
New Domino Features
New Domino Admin Features
Tuning for Peak Performance

3. The Lotus Domino 7 Ecosystem
Mail Archiving
DB2 Commonstore
Legato, IXOS
Records Mgt
DB2 Content Manager + Carefree eRecords Bridge
Anti Spam/Virus
Symantec, McAfee,
Trend, Tumbleweed,
Ironport, Group, Granite
Backup & Restore
Tivoli (TSM)
Veritas, EMC/Legato
BMC, Commvault
Network Appliance
Domino is not just a product, its an entire Ecosystem – 3rd parties and IBM products – some listed here
We are working very closely with our ISVs with the 7.0 beta code to make sure their products are ready when 7.0 ships or soon thereafter.
This is critical to our success - customers need to be able to plan their migrations to 7.0 in the knowledge that all the 3rd party solutions they depend on will also be ready.
So far we are hearing that 7.0 just runs with most of these solutions with no changes.
However many other vendors (especially Backup suppliers) and are planning to exploit DB2 integration.
Directory Integration, SSO, Monitoring
Tivoli Directory Integrator
Tivoli Identity Manager
Netegrity

4. Why Notes/Domino 7

5. The Value of Upgrading
Extract more value from collaborative applications
Continue to extend the reach of messaging and collaboration
Notes, browser, Outlook, mobile, applications
Reduce TCO
Support additional platforms and updated OS versions
Performance improvements for better scalability
Reduce administration costs
Simplify the client - usability and productivity
Extend Domino’s capabilities
IBM Software Group products: Sametime, WebSphere Portal, DB2, Tivoli
3rd party solutions
Leverage client productivity enhancements
Notes client improvements
Domino Web Access improvements
Integrate Domino into SOA initiatives
Via new Web Services capabilities
Notes/Domino Release 5 Support Ending
Major incentive for many customer still on Version 5 to upgrade

6. Notes 7 New Features Autosave option for selected documents
New calendar options
e.g. Auto-processing of calendar events despite conflicts (requires a Domino 7 server)
Calendar cleanup
Calendar filtering
Save state on close
Confirm close of Note
Mail user interface enhancements
Attention icons (the blue dots)
mail threads (great for coming back from vacation and jumping to middle of thread...can see whole thing)
Smart tags support for MS Office (good for desktop integration story)
Chat transcripts view (and automatically saved) - chats can be securely save in rather than plain text on disk ... and searchable!
Extended Sametime integration
Designer, Admin client, Domino Web Access, and Domino Access for Microsoft Outlook improvements

7. Domino 7 and Domino Designer 7 New Features
Performance improvements (reduced TCO)
New enterprise mail workload for benchmarking and server.load.
Significant administration improvements
Domino Domain Monitor (DDM)
Client Policy Lockdown
Smart Upgrade improvements
New mail & calendar settings policy type
DB2 as optional Domino data store
SQL access to Domino data
Domino access to DB2 via SQL
Functional Improvements, including
Web Services support
Messaging improvements
Security enhancements
Improved LDAP support
Expanded Platform Support

8. Upgrading

9. Upgrade Sequence Administration clients
Domino directory/administration server
Hub servers
Spoke servers
Mail servers
Application servers
Other servers
Notes clients
Mail design (template)
Applications and databases
On-disk structure (if upgrading from R5 or before)
New features

10. Upgrade Sequence

11. What’s New in IBM Lotus Domino 7.0?

12. Domino 7.0 Themes Improved TCO New Application Platform Capabilities
Dramatic performance and scalability gains
Major Administration improvements
New Application Platform Capabilities
Web Services support
DB2 database integration
Many Other Valuable Enhancements
Messaging management
Security
Domino Web Access

13. Domino 7 CPU reduction results
Enterprise mail workload (R6Mail.ntf)
Windows, Solaris, AIX, zSeries, zLinux
Up to 25% less CPU utilization than 6.5.1
Domino Web Access (R6iNotes)
Windows, Solaris
% lower CPU utilization than 6.5.1

14. Domino 7.0 - 35% CPU reduction in IBM production
Abnormally high antivirus scan task increased CPU utilization
Domino 7 Beta 3
Domino 7 Beta 4
Domino 6.5.1

15. Domino/DB2 Integration
Leverage DB2 for common storage of data, including IBM Lotus Domino and IBM Lotus Workplace applications.
DB2 provides robust data management capabilities and advanced data integrity.
Designers can build applications that blend Domino collaborative services and relational data using Standard Query Language (SQL).
DB2 Access Views - expose Lotus Domino data to other DB2 apps
DB2 Query Views - SQL based queries as views accessed via Notes 7 client
Point to Lotus open lab for people to learn more.

16. DB2 Considerations Optional, can be enabled at a later time
Not a replacement for NSF
Choose specific applications to DB2 enable
Need a special key file before the feature is enable
Can be downloaded from public beta site
Need DB Enterprise Edition
Evaluation copy available
Use “compact –p” to convert from .nsf to DB2
Planning required to determine proper infrastructure
Do Not put system databases in DB2
Log.nsf (should never be in DB2)
NAB
DDM (testing in progress)
See Oct TechTalk here:
Point to Lotus open lab for people to learn more.

17. What’s New in Domino 7.0 Administration?

18. What’s new in Domino 7.0 Administration highlights
NEW !! Activity Trends
Domino Domain Monitoring (DDM)
Smart Upgrade Improvements
Improved Policy Based Management
Linux/Mozilla Web Admin Client
Improved Management

19. Why DDM in Domino 7.0?
2003 survey results on administrative priorities

20. Why Domino Domain Monitoring (DDM)?
In Jan 2003 survey, Domino Administrators said:
Domino 6.x provided new tools that reduce TCO
Many usability and "polish" improvements
However...
Monitoring/troubleshooting servers takes too much time.
Many problems across servers reported in many places.
Correlation/analysis of lots of diverse data for complex problems is difficult.
Need root cause analysis and corrective action context.

21. DDM Goals
At the highest level, reduce TCO by providing a means to quickly monitor and determine the health of an entire domain at a single UI location and quickly resolve problems -- How?
Automate problem determination/analysis by feature (replication, messaging, directory, security, etc.)
Rollup, prioritize, and resolve problems across servers
Hide details until they are needed
Make DDM checks and reporting configurable and flexible
Be consistent with IBM Autonomic Computing (AC) vision
The DDM Five C’s – Check, Collect, Consolidate, Correlate, Correct

22. 7 Key Points to Take Home
DDM is aimed at TCO reduction and all administrators
One-stop shopping for monitoring and problem resolution
Distills/correlates a huge amount of otherwise indigestible data
Highly usable interface allows systematic approach to server issues
Configurability and flexibility accommodates diverse enterprises
More efficient monitoring and problem resolution leads to:
Server stability and uptime
Focus on business needs, not the mechanics of administration
DDM should become primary monitoring interface, but it’s optional!
DDM architecture facilitates future extensibility and programmability

23. Activity Trends Formerly available with Tivoli Analyzer
A capacity planning and resource/load balancing tool for Domino domains
Gathers and analyzes Domino activity data
Resource balance many Domino servers by moving databases across servers
Provides automated change management with full administration-cycle support

24. Activity Trends -- Why Load Balance?
Domino response varies with load
At high utilization, response is highly variable
Want stable and predictable utilization
Result: improved availability, better response times, and decreased costs

25. Activity Trends -- Capabilities
Balances resources in several dimensions and increases predictability of resource consumption
Over 25 transactions (CPU), space, network, etc.
Manages/minimizes daily fluctuations in server load
Generates solutions that are stable over long periods
Solution is usually stable for 12 months or more
Implements solution by moving databases
Domino Change Manager automates approval process and migration of databases between servers
Provides server decommissioning capability
Allows “what-if” scenarios with ghost servers

26. Getting the Data Activity Logging Activity Trends Collector
Server task writes performance data (binary) to the server log
Activity data stream written to the standard server log (log.nsf)
Activity Trends Collector
Processes performance data once a day
Correlates with other data from different sources
Performs historical analysis to predict future size and consumption rates for resources and “trends” the data
Data is written to Activity Database for use by Activity Trends in the Domino Administrator client

27. Activity Trends Load Balancing

28. Smart Upgrade Improvements in 7.0
Smart Upgrade tracking
Governor - Limit the number of Smart Upgrades per hour (also in 6.5.4)
Smart Upgrade server cluster failover to another server
Smart Upgrade failover from shared drive path kit to Attachment kit.
Smart Upgrade fields added to the desktop policy settings document.

29. IBM Lotus Notes Smart Upgrade
IBM Lotus Notes Smart Upgrade notifies users to update their Notes 6 and more recent clients to later releases.
Lotus Notes Smart Upgrade uses policy and settings documents to help manage updates.
The Smart Upgrade Kits are available in global English only. In a non-English environment, the Notes Client Web Kit can be substituted for the Smart Upgrade Kit.

30. To use Lotus Notes Smart Upgrade
Follow this procedure:
Create a database using the Smart Upgrade Kits template (SMUPGRADE.NTF) to host Notes client update kits.
Update the Configurations Settings document in the Domino Directory with a link to the Lotus Notes Smart Upgrade database.
Download an update kit, also known as an incremental installer, from the Lotus Developer Domain Web site (
Create a Kit document in the Lotus Notes Smart Upgrade database and attach a Notes client kit or All Client kit to the Kit document, or designate a shared network drive in the Kit document.
Create or modify a desktop policy settings document where you specify the updated release to deploy and the date on which the grace period for updating a Notes client ends.
Create or modify a master policy to assign users or groups to the desktop policy settings document.
Depending on the master policy created, edit Person documents to assign users to the master policy and/or set the Lotus Notes Smart Upgrade desktop policy settings document for one or more groups.

31. Smart Upgrade Example

32. Policy Management in 6.5/7.0 In 6.0.x & 6.5.x In 7.0
Notes Client setup
Desktop settings
Security
Registration
Archiving
In 7.0
Client Policy Lock-Down for all settings
New mail and calendar policies

33. Domino 6.X vs 7.0: Policies Compared
ND6
Lock
ND7
Registration policy Y
N/A
Setup policy N
Desktop policy
Security policy
Archive policy
Mail and calendar policy
Note: Additional policy settings have also been added in 7.0
New in Domino 7.0

34. Domino 7.0 Web Admin Client for Linux/Mozilla

35. Web Administrator on Mozilla
The Web Administrator uses the Web Administrator database (WEBADMIN.NSF).
Make sure that the server you want to administer is set up as a Domino Web server and that it is running the HTTP task.
A TASK Tool is added to allow Tell commands to be issued and to issue stop, start and restart replication, router and messaging tasks.
Domino Server Monitoring and performance charting is not available.
You can specify other tasks to be disabled for the Web Administrator.

36. Web Administrator Usage
Most of the Domino Administrator functionality is available on the Web Admin
You can use the Web Administrator to perform the following tasks for Internet or Notes users:
Add an ACL entry
Remove an ACL entry
Rename an ACL entry
Add, remove, or rename a database role
View the ACL change history
Create a new database on the server based on templates
Create a new copy of the database
Delete a database
Compact a database
Create or update a full-text index of a database
Force manual replication of a database with a remote server

38. Mail Management Enhancements
Anti-Spam – Blacklist and Whitelist Support
Complements perimeter Anti Spam solutions
New in Domino 7.0
Added control for exception/override of blacklists
DNS whitelists
Private whitelists
Private blacklists
Works with mail rules to support flexible processing
Message disclaimers
add disclaimers to all messages, including signed and encrypted messages
Disclaimers can be managed via mail policies
Mail rules -- stop processing action to increase control/efficiency
Archiving – by Create Date and usability improvements

39. Autosave
You can have Notes automatically save documents you are working on to a local encrypted database in case you need to recover your work after a power outage or system crash.
Encrypted db is named “as_<shortname>.nsf” in the Notes\data directory.
Not enabled by default.
From the menu, choose File - Preferences - User Preferences.
Choose the AutoSave interval to your preference (1-999 minutes).
Can also be added to the user’s notes.ini or set in a desktop policy.
A new form property is available to allow AutoSave in an application.
More information can be found in this article: “All about AutoSave in Lotus Notes/Domino 7”

40. AutoSave Recover and Delete
If you have set the user preference to automatically save a draft at intervals, a local encrypted database contains your current draft documents.
To open stored drafts
Choose File - AutoSave - Recover AutoSaved Documents.
Select the document you want to open and click Recover, or click Recover All to open all documents in the local database.
To delete stored drafts
Select the document you want to delete and click Remove, or click Remove All to delete all documents in the local database.

41. Using Message Disclaimers in ND7
Message disclaimers are notices -- usually short text blocks -- that are added to messages.
They are often used by organizations in an attempt to protect the organization's legal interests.
Enable or disable the use of message disclaimers from the Domino server, Notes client, or both.
IBM recommends that you enable the Notes client to add the disclaimer because this reduces the overhead on the server.
This client setting is found on the Mail Settings document as a policy.
The server setting is a combination of the server configuration document and the mail policy.
More information can be found in this article: “Tip: Using message disclaimers in Lotus Notes/Domino 7”

42. Additional Administration Features
Open Mail File button accessible from an open Person document and from the People view of the Domino Administrator.
Multiple Notes client users can use the same directory at the same time.
Documentation now contains information about using policies to assign NOTES.INI settings to Notes client users or to Location documents.
Instant messaging setup within the Notes application plug-in can be done using the desktop policy settings document.
New client policy lock down feature
New private whitelists and blacklist feature and DNS whitelist feature
Custom password policies -enables administrators to enforce password requirements that will fit almost any set of corporate or government security requirements.
Room & Resources Manager enhancements prevent overbooking of rooms and resources.

43. Tune E-Mail for Peak Performance
6 Steps you can take to improve performance, conserve system resources and help users get their work done faster.
Taken from Lotus Advisor December 2005 issue
Written by David Yavin and Andrew Wolff, SYS Analytics
People assume that and IM are free – and use them as such.
The result for most organizations is that far too much information is distributed to far too many people.
Traffic surges impact performance for everyone.

44. Who are the culprits?
Not usually the large message sent to another person.
Usually many mid-sized messages sent to distribution lists.
Implementing a maximum size doesn’t fix this problem.
Messages between 500K-5M typically are 5% of the messages, yet they consume % of the resources.
Compounded with “Reply to All”
Suggestion:
Change the default to Reply w/o Attachment.
Remove Reply w/ Attachment.

45. Address habitual volume e-mailers
Less than 1% cause more than 20% of resource consumption.
Two types: habitual mass mailers and large attachment senders
Even small attachments sent to large distributions cause issues.
Mail agents often send to a distribution list, but the recipients create an agent to auto-delete those messages.
Suggestion:
See if large regular distributions can be a Notes application. Then the sender only sends a doclink/hyperlink.
See if large attachments can be placed an a separate db and distributed similar to above.
Use a performance management tool to identify these users.

46. Make best use of the platform
Perhaps regular conversations between two people should use IM instead of .
archiving often isn’t used.
Suggestion:
Use IM for conversations
Use archiving
Strip attachments

47. Place servers where there’s need
This cuts down on WAN traffic.
Hub and spoke vs centralized
Suggestion:
Use IM and analysis tools to determine best location.
Way the costs between an additional server and WAN/performance.

48. Prune large mailboxes Large mailboxes cause issues:
Longer to back up
Longer to index
Corruption more easily
Setting quotas may just “waste” users time managing their mail instead of performing their job.
Suggestion:
Teach the value of deletion.
Use network drives for personal file stores.
Remove or archive “dead accounts”.

49. Monitor for inappropriate personal use
“Although ensuring employee productivity isn’t an admin’s problem, ensuring the infrastructure is being used appropriately is.”
There are many regulations about this.
Suggestion:
Monitor and IM
Have policies regarding how to deal with offending parties.

50. Optimize Internet Settings
Internet domains often are a security risk.
Internet mail also overloads the SMTP gateway.
Suggestion:
Monitor mail sent to internet and discuss alternatives with the sender.
Beware of Out-Of-Office cyclical agents.

51. Summary

52. Domino 7.0 Features & Benefits
Functional Area
Scalability
Administration
Database
Applications
Platforms
Key Features
Performance improvements
DDM, Activity Trends, Policies
DB2 alternative data store
Web Services, DB2
Expanded platform support
Business Benefits
Enable server consolidation
Reduce admin & support cost
Consolidate data management
New integrated applications
Flexible deployment

53. Notes and Domino 7.0 lowers TCO - Again!
Ferris study showed Notes/Domino 6 reduced TCO by 15% overall *
Cost Area
7.0 Potential Savings
User productivity
Notes client features improve user productivity
Server hardware
Server performance gains lead to server hardware savings (more users per server)
Upgrade costs
Smart Upgrade reduce cost of client upgrades
Admin costs
Reduces admin time spent troubleshooting servers. Capture & analysis of server data, better load balancing tools
Support costs
Desktop & mail settings policy enforcement to reduce client support call volume/ fix time
User downtime
Reduced downtime due to better monitoring
Application integration
Mores rapid development of new web services applications leveraging existing Domino skills *

54. Thank you! For more information… IBM home page www.ibm.com
Lotus software home page
Notes client home page
IBM Workplace home page