Book Image

Domino 7 Application Development

Book Image

Domino 7 Application Development

Overview of this book

Written by Lotus insiders, the book provides a practical guide to developing applications making use of the important features and enhancements introduced in Notes/Domino 7. These experienced experts use their own experiences to map out the benefits you could gain, and the dangers you may face, as you develop Domino applications in your business. Written by specific experts, edited and overseen by Lotus content generator Dick McCarrick, this book is the definitive guide to developing Domino 7 applications. TECHNOLOGY Domino is an application server that can be used as a standalone web server or as the server component of IBM's Lotus Domino product which provides a powerful collaborative platform for development of customized business applications. It also provides enterprise-grade email, messaging, and scheduling capabilities.
Table of Contents (18 chapters)
Domino 7 Application Development
About the Authors
About the Reviewer
Free Chapter
A Short History of Notes and Domino

Appendix A. Vendor Tools

In this appendix, we review several vendor tools that you can use to help upgrade your applications to Lotus Notes/Domino 7. These include:

  • Angkor by Atlantic Decisions

  • PistolStar Password Power 8 Plug-ins by PistolStar, Inc

  • CMT Inspector from Binary Tree

  • FT Search Manager from IONET


Angkor™ is a tool developed by Atlantic Decisions, Inc., to provide a means to analyzing an entire Lotus Domino/Notes enterprise infrastructure in a short period of time. It was built to help Notes managers get a handle on the mass of activity and data that makes up the typical thriving Notes installation. Some of the typical noncritical issues facing today's managers are:

  • The need to cut costs, without affecting essential business services.

  • Upgrading: database compatibility testing.

  • Determining which Notes applications should be migrated.

  • Implementing (or tightening) mail quotas: what are the true costs /opportunities?

In most installations, up to a third of all databases could be eliminated without significant impact on the business. It is not very difficult, given the appropriate data and knowing that it is current and accurate. If you can eliminate all the databases that are not being used effectively, costs will go down. An upgrade would also be easy, but someone has to figure out how much it will cost to test all of the applications, and budget for the development time to fix them. It is better to know these details before the project starts.

How Angkor Works

Angkor searches out every server in the domain, then every database on those servers. A complete inventory is provided with data such as size, number of documents, and template. The data is rolled up to the server and application levels for additional visibility. Views that consolidate replicas are included. Angkor lets you see a complete picture of the Notes infrastructure, allowing you to compare the various parts on a one-to-one basis. The following is an example of an Angkor inventory:

Notes/Domino Inventory === Infrastructure Mapping

Domain verification report

Server discovery

Connection report

Database discovery

Database access report

Mail Inventory === Including for each mail file:


Template version

Mail impact by user


Consolidates size, usage, and # of docs to ID top users

Document count

Mail-enabled applications - cost and impact


Server / Path / Filename

Database Inventory === Including for each database:


Template version

Db sorted by usage, individually, and "rolled up"


Application usage

Document count

Server usage


Template Diversity Report

Replica Report


Identified replica copies

Including locations across all servers

Non-replica copies

Copies of existing databases that do not replicate. Including locations across all servers.

Server Report


Server level "rollups"

Of all database and mail data for each server.

Categorization Reports


All databases by general type

- Mail

- Applications

- 3rd party applications

- Lotus applications

Sorted by

- Server

- Domain

- Database

Graphical depictions

Of server and database statistics.

Docs vs db's vs MB



Notes user listings for all databases

Databases report with primary users for each database ("owners")

In subsequent phases, Angkor extracts the complete usage history and design specifications, in detail, for each database. Reports integrate the data to show which servers, applications, and databases are the most heavily used a critical data point for any decision (see below).

Consolidation Reports

Duplicate file instances report

Lotus Help and Documentation databases report

Standard Lotus databases created at installation rarely used.

Mail file and server consolidation options

Databases by replica ID, all multiples included

Organizational Cost Figures

Departmental or other organizational rollups of mail figures

Departmental or other organizational rollups of application figures

Security Report

Discrepancies across replicas, use of special features (encryption, controlled sections, etc.), default access, manager).

Custom Reporting

AD can build additional Angkor usage/analysis reports according to customer specific requirements.

Application Complexity Report


This report provides an in-depth analysis of every element of all Domino applications, and catalogues them within the application for easy review.


Selected databases

Specific applications as identified


Application rollups (replicas)

Consolidated reports for replicated applications


Code elements

Lotuscripts, etc. within the application


Design elements

Notes structure, views, forms, agents, and ACL



Relative "weights" used to calculate an accurate, level scale to measure complexity


Categories include

- Mail - Databases

- Applications - Domains

- Organization - Cost vs. Usage

- Cost vs. Age

Best Practices/Code Efficiency



Identifies code elements for opportunities to improve efficiency, points to potential problem areas

Resource usage

Identifies known problem areas within Notes design

Custom analysis

Rules-based engine allows flexibility

R7 Migration


R7 compatibility

Identifies potential R6 problems within applications


Direct linking to specific problem code segments

Custom Reporting

The complexity of the individual databases in terms of both design and code is provided, so the true cost of the infrastructure can be accounted for in detail. All of this is built into a set of Notes databases that provide the precise information needed. These databases are left with you, with design elements exposed, for further analysis and review.

A rules-based analysis engine provides custom searches for design elements with potential upgrade issues. Or it can search out elements that are adaptable or problematic for other technologies. Angkor allows for thousands of man-hours of detail analysis on your Notes applications and mail files. It provides useful data to help you make quality decisions now, and not months from now. Most businesses, even if they have the staff to undertake these analyses, don't have the kind of time it takes to wait for a manual effort to be completed.


Angkor compresses a major Notes analysis effort into a matter of days or weeks, giving both an overview and the detail necessary for plans to be made, justifications documented, and actions taken. Information such as Angkor provides should be the first step in any major Notes/Domino project, something that has never been available before.

The detail analysis of code and design elements allows for a wide range of custom reports and analysis, depending upon customer requirements. Certain Notes elements may be sought out by the customer for conversion or support issues. It also allows for differing applications to be compared to one another with a standardized measure of their complexity, providing a valuable tool for users to compare their application base against standards such as the Notes mail file.