Search results

The purpose of this document is to describe when to use the Lotus Domino utilities (Updall, Compact, Fixup) and to explain how to use them for normal and abnormal maintenance.

This document, the final of a series of four, describes the Out of Office feature with respect to the Domino Web Access (formerly iNotes Web Access) client, outlining the basic differences between using the feature when in the Notes client as opposed to a Web browser.

This document, the first in a series of four, describes in detail the design features and behavior of the Lotus Notes/Domino Out of Office functionality, answering these questions: 1. Out of Office terminology: What are some frequently used terms to describe the Out of Office functionality? 2. What does it do (and not do)? 3. Where is the Out of Office functionality located? 4. How does a Hide When formula affect when you see the Out of Office options in the Notes client? 5. How does the Out of Offic

For the Out of Office feature to work properly, certain settings in the Server document and Notes databases must be configured. This document, the third in a series of four, describes in detail all the settings necessary to configure the Lotus Notes/Domino Out of Office, relative to each ACL access level. This document, intended for Domino administrators, is a checklist of all these necessary configuration settings.

The access level that a mail file owner has in the Access Control List (ACL) of his or her mail database impacts the configuration and behavior of the Out of Office functionality in Lotus Notes/Domino. This document, the second in a series of four, describes the Out of Office functionality with respect to each allowable database access level, examining the LotusScript code differences among the following: --Manager access --Designer access --Editor access (available with Notes/Domino version 6.0)

This document serves as a pointer to a white paper addresses the most important and most serious factors affecting IBM® Lotus® Notes® and Domino® application performance.

With Lotus Notes and Domino 8, world class business e-mail and collaboration take an exciting step forward, offering new approaches to enhance efficiency and creativity, while extending the value of current investments. This IBM Redpaper will guide you through all the newly released innovative and open features of Notes and Domino 8. It is a must-read for any existing or potential user of Lotus Notes and Domino, from the casual user to the administrator or application developer to the line of business executive.

IBM Lotus Notes access for SAP solutions can provide even greater business value for companies using both Lotus Notes software and SAP enterprise systems. This feature lets you access SAP information and business processes in your familiar Lotus Notes messaging and collaborative environment, starting with Lotus Notes 7.0.1. The Lotus Notes access for SAP solutions feature builds on proven IBM and SAP integration technology that has been on the market for eight years. The new capabilities extend this integration into calendars and scheduling, contact management, workflow processing, and other common business tasks. This feature leverages Lotus Notes strengths in personal information and workflow management to complement SAP application processes. IT architects, application developers, and business leaders in an organization looking to integrate SAP business applications and workflow into their familiar, security-rich Lotus Notes collaboration client at no additional charge will want to read this Redpaper.

In early 2005, the Scalability Center for Linux on zSeries (SCL) in Poughkeepsie performed a study on IBM Lotus Domino 6.5 for Linux on IBM System z. During that study, capacity planning and performance data was collected using an industry-standard benchmarking tool to drive both NRPC (Notes) and Domino Web Access (HTTP) e-mail users. The results of this benchmark showed two bottlenecks that prevented linear scalability of throughput for Domino 6.5 for Linux on System z. Domino 7.0 and z/VM 5.2, which both became available later in 2005, offer relief for these two bottlenecks. This IBM Redpaper discusses the results of those tests and provides some recommendations.

Performance tuning, or optimization, is the process of modifying a system's configuration in order to improve its efficiency at meeting specified functional goals. The systems in question can be a single application, one Domino server, a collection of servers participating in a common activity, such as mail routing or replication, or an entire Domino infrastructure. Performance tuning is goal-focused, and involves balancing the use of available system resources in order to meet those goals. This usually involves some sort of trade off, where one or more resources are optimized at the expense of others. A classic example of this is caching, which attempts to improve I/O performance by buffering data to memory. The memory allocated to the cache service is unavailable for use by any other programs on the platform, but if overall system performance is improved, the benefits outweigh the cost. This IBM Redpaper discusses a best practices approach to Performance Tuning in Domino 7. It addresses both how to approach the science of performance tuning in a structured, logical manner, while also providing an in-depth discussion of specific configuration parameters to tune in specific situations. After reading this Redpaper, this should further assist Domino Administrators in tuning Domino systems to more effectively: - Improve user or application response time - Improve system stability - Reduce transaction times - Balance the use of system resources