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.
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 |
|
Size |
Consolidates size, usage, and # of docs to ID top users |
|
Document count |
Mail-enabled applications - cost and impact |
|
Location |
Server / Path / Filename |
|
Database Inventory === Including for each database: | |
|---|---|
|
Template version |
Db sorted by usage, individually, and "rolled up" |
|
Size |
Application usage |
|
Document count |
Server usage |
|
Location |
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 |
- Applications |
- 3rd party applications - Lotus applications |
|
Sorted by |
- Server - Domain |
- Database |
|
Graphical depictions |
Of server and database statistics. Docs vs db's vs MB |
|
Usage |
|---|
|
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 | |
|
Weighting |
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 | |
|---|---|
|
Code |
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 |
|
Code-walker |
Direct linking to specific problem code segments |
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.