Inside Notes: The Architecture of Notes and the Domino Server
Ran across this item the other day... Worth reviewing if you've been doing tihs for awhile... From the KnowledgeBase...
Inside Notes: The Architecture of Notes and the Domino Server
Document Number:
7002793
The database "Inside Notes: The Architecture of Notes and the Domino
Server" is available at
http://www.notes.net/notesua.nsf/0b345eb9d127270b8525665d006bc355/ec73cbf1c6392ba385256856005bd224?OpenDocument&Highlight=0,inside
Inside Notes
In 1989 Lotus (r) Notes (tm) made the world a little smaller.
Since its first release, Notes has enabled teams of people to work together,
even when separated by great distances or when individual contributions
are made at different times. Notes was the world's first viable groupware
product, and it remains today the world's best groupware product. Release
after release, Notes continues to evolve innovative, new capabilities that
support its initial core concept: Collaboration made possible through shared,
secure, online databases.
Much of what has been written about Notes over the years does not contain
enough information about how Notes works to satisfy the needs of IT managers,
application developers, and other technical individuals who are responsible
for purchasing equipment, integrating Notes into their organizations, and
designing appropriate, efficient applications. The purpose of Inside Notes:
The Architecture of Notes and the Domino Server is to describe the internal
architecture of Notes and Domino (tm) in sufficient detail to enable you
to make optimal deployment and programming decisions.
Inside Notes provides a single place where you can quickly learn about
the overall architecture of Notes. It clearly presents gist of Notes design,
without getting bogged down in details. While some of the information
included here has appeared elsewhere, other information has never before
been published.
Contents:
Overview of Notes and Domino Architecture
Notes and Domino components
Fundamental design principles
Notes is multiplatform
Notes must perform and scale well on all platforms
Notes is designed for global use
Client programs can run on servers, and vice versa
The note is the basic data structure
Later releases of Notes support databases created
using earlier releases
Fundamental support for security and groupware is
built into all Notes software
Notes uses its own databases to control many of its
own activities
Notes uses its own databases to implement domain-wide
features
Overview of Notes Object Services
How NOS is organized
The Extension Manager
The Notes remote procedure call client
The Notes database
The database header and other internal structures
The "note" in Notes
Types of notes
Data notes
Administration notes
Design-element notes
Notes in hierarchy
Overview of database replication
Domains and directories
Domain administration
Overview of security
Security issues
Overview of messaging
Client programs
The Domino Server program
Built-in server tasks
Table of built-in server tasks
Add-in server tasks
Table of server tasks that maintain Notes applications
Table of server tasks that manage server and administration
activities
Table of server tasks that manage mail, calendars,
and scheduling
Table of server tasks that manage protocols
Table of server tasks that monitor server activity
Programmability
Developing, creating, and maintaining Notes applications
Creating a template
Creating a new database from a template
Editing and viewing the database
Revising and refreshing a design
The Domino Designer
How Notes/Domino process the built-in interpreted languages
Web authoring tools
Using toolkits, drivers, and connectors
Supported application toolkits
Supported database drivers
Supported Lotus connectors
CORBA support
XML support
Notes Object Services
Figure of NOS architecture
NOS service groups
Table of NOS service groups
NOS portability layer services
Notes language services in NOS
On-disk structure services in NOS
Operating system services in NOS
NOS network services
NOS database services
Notes Storage Facility services in NOS
High-level database services in NOS
AdminReq services in NOS
Agent services in NOS
Calendar and scheduling services
in NOS
Composite-text services in NOS
Folder services in NOS
Full-text search services in
NOS
Log services in NOS
Mail services in NOS
Name services in NOS
Notes Index Facility services
in NOS
View architecture
Registration services in NOS
Subform services in NOS
Other NOS services
Access control list services in NOS
Add-in services in NOS
Alarm services in NOS
Distinguished name services in NOS
Event services in NOS
Extension Manager services in NOS
ID table services in NOS
Message queue services in NOS
Text list services in NOS
Time services in NOS
Security services in NOS
The Notes Storage Facility
Figure of NSF
NSF API functions
Unified Buffer Manager
Open Database list
Database Cache
Directory Manager
Recovery Manager and the Logger
Database structures
Major and minor version numbers
Database class
Database information buffer
Database ID
Database instance ID
Database replication settings
Database replication history
Database notes
Table of note types
Identifiers for notes
Layout of a note
Physical storage of notes in a database
Table of item types
Layout of an item
Server Tasks
Tasks that maintain Notes applications
Tasks that manage server and administration activities
Tasks that manage mail, calendars, and scheduling
Tasks that manage protocols
Overview of statistics and events
Tasks that monitor server activity
Notes and the Web
Types of Web servers
The Domino Web server
Domino Web server object model
Domino Web server architecture
How Domino processes a URL
Security
The Notes/Domino security model
Notes/Domino access control
Restricting access to servers and ports
Restricting access to databases
Restricting access to files
Restricting access to design elements
Restricting access to workstation data
Restricting access to documents
Using access control features for security
Notes/Domino authentication
Notes ID files
Example of Notes/Domino authentication
Cross-certificates
Internet client authentication
Supported authentication methods for Internet protocols
Basic name-and-password authentication
Session-based name-and-password authentication
Examples of name-and-password authentication
SSL authentication
Examples of SSL authentication
Directories
The Domino Directory
Directory catalogs
The mobile directory catalog
The server directory catalog
How a directory catalog works
Directory catalog configuration options
Programmatic access to a directory catalog
Directory assistance
Directory assistance for secondary Domino Directories
Web client authentication in a secondary Domino Directory
LDAP searches in a secondary Domino Directory
Notes addressing lookups in a secondary Domino Directory
Directory assistance for LDAP directories
Web client authentication using a remote LDAP directory
ACL group verification using a remote LDAP directory
LDAP client referrals to a remote LDAP directory
Notes addressing lookups in a remote LDAP directory
Comparison of directory catalogs and directory assistance
The Domino LDAP service
The LDAP schema
LDAP service authentication and access control
LDAP searches in secondary Domino Directories
LDAP referrals to other directory servers
LDAP service and authentication of clients that use
a third-party server
LDAP alternate language searches
LDAP service statistics
Other LDAP features Domino offers
Directory search orders
Name lookups in multiple directories for Web client
authentication
Group lookups in multiple directories for database
access verification
LDAP searches in multiple directories
Notes mail addressing lookups in multiple directories
Directory servers
User and group synchronization between Domino and Windows NT
Migrating users to Notes/Domino
Migrating cc:Mail users
Migrating Microsoft Mail Users
Migrating Microsoft Exchange users
Migrating Windows NT users
Migrating users from an LDIF file
Migrating users from Novell GroupWise
Migrating users from the Netscape Messaging Server
The Administration Process
Table of Administration Process scheduling attributes
Replicas and replication
The Replicator server task and replication commands
Replication controls
Using the access control list in replication
How replication works behind the scenes
Preventing and resolving replication conflicts
Clusters and replication
Domino clusters
Cluster requirements
Cluster components
The Cluster Manager
The Cluster Database Directory
The Cluster Database Directory Manager
The Cluster Administrator
The Cluster Replicator
Failover and workload balancing
When failover occurs
Causing failover to occur
Example of failover
Mail failover
How calendars work in a cluster
Limiting the workload of a server
Managing database availability in a cluster
The Indexer
The Updall task
The Update task
The Domino Directory and indexing
The Router
How the Router works
Router initialization
Message routing
Message transfer queues
Message delivery
Message cleanup
Message state
Message transfer threads
Message transfer over SMTP
Message delivery threads
Controlling the Router task
Daily housekeeping performed by the Router
Failover in clustered mail servers
Message-delivery retry algorithm
Glossary



Comments
Posted by Kent Kurchak At 06:12:58 On 09/12/2009 | - Website - |