Replication will occur based upon access rights, replication settings, replication history, and the replica ID of a database. The location and filename of a Notes application does not matter as long as the application exists within the Notes server'’ data directory or a subdirectory relative to the data directory.

Field level replication is automatically incorporated in version 4 of Notes. Only modified fields within a Notes application will replicate between servers. If a version 3 Notes server is replicating with a version 4 server, the entire document will replicate.

The replication server task is automatically configured to start up per the ServerTasks line in the server’s NOTES.INI file. The name of the task is called "replica".

A pull replication from an initiating server reads from the target server and writes to its own Notes applications.

Multiple replicators may be enabled by creating a server configuration document, modifying the server’s NOTES.INI file, or manually loading another replicator task from the Notes server console.

Replication conflicts will still occur with merge conflicts enabled if the same field was modified by more than one person.

Notes servers within the same Notes named network will appear in the server list.

Notes servers within the same Notes named network do not need connection records between then to route mail – only a replication connection record.

Shared_Mail=1 routes mail to the shared Notes mail application if the message is destined for two or more recipients. If only to one person, mail is delivered to the users personal mail file.

Shared_Mail=2 uses the shared Notes mail application regardless of the number of users the mail is for. This is also the default setting when shared mail is first installed on a Notes mail server.

Shared mail is mostly used to save space on the Notes server

Under the following situations, duplicate copies of a mail message will exist when using shared mail

• user edits a mail message
• user saves a mail message
• user encrypts incoming mail
• user makes a replica copy of a mail file

By default, NO ACCESS is allowed to passthru Notes servers and to connect to destination servers via passthru Notes servers. The restrictions must be configured within the server documents of the respective Notes servers.

When configuring the first server in the organization, the server ID (SERVER.ID), certifier ID (CERT.ID), administrator ID (USER.ID), and public Name and Address book (NAMES.NSF) are all created.

The following files should be backed up if you are going to reinstall a Notes server

• NOTES.INI
• DESKTOP.DSK
• CERT.ID
• SERVER.ID
• USER.ID
• NAMES.NSF
• LOG.NSF

The mail router box (MAIL.BOX) and Notes server log (LOG.NSF) are automatically created whenever a Notes server starts if they do not currently exist.

Lotus Notes Mail licenses may only access Notes mail applications and any applications inheriting their designs from Lotus-approved templates.

The trace connection utility can be used to test connectivity problems between two Notes machines.

The convert server utility will upgrade the mail file from version 3 to version 4 and not affect read and unread marks. The mail file format, however will not change. You need to run the server task "compact" in order to convert the file format from version 3 to 4.

In order to register a new person, the Notes administrator must have proper access rights to the public Name and Address book (AUTHOR with the role CreateUser granted). The administrator must also have a copy of the certifier ID file.

Multiple passwords may be assigned to any ID file including a user, server, or certifier ID file. Also, a required number of successful passwords may be assigned so that more than one person is required in order to unlock a file.

By default, any Notes user can create a new, non-replica Notes application as controlled by the server field Create New Databases.

By default, no user may create new replica databases as controlled by the server field Create New Replica Databases.

Adminp can automate the following tasks:

• Delete user, server, and group documents from the public Name and Address book
• Recertify Notes ID files
• Rename users and servers
• Create and delete users’ mail files
• Create replicas of Notes applications
• Move databases to and from a cluster server
• Add and remove servers from a Notes cluster
• Enable password checking during authentication
• Remove user names from ACL, reader, and author name fields of Notes applications
• Convert users and servers from a flat to a hierarchical naming standard

The Notes server program FIXUP can be used to attempt to repair damaged databases. It can be run from the Notes server console on any unopened Notes applications.

The COMPACT server program will take "white space" out of a Notes application

The UPDALL server program updates a Notes application’s view indices.

Replication formulas can be created to replicate based on field, view, and server.

A Notes administrator may create a server configuration document with a wildcard entry for the server name to modify a NOTES.INI variable on all Notes servers within the Notes domain.

Program records can be created within the public Name and Address book to run programs at a specified time on a Notes server.

A Notes workstation upgrade message may be sent from the public Name and Address book to Notes mail users to upgrade their Notes workstation.

Notes Database Access levels

• No Access – User is not granted access to the database
• Depositor – User is able to create documents, but not view any documents within the database – even documents the user creates.
• Reader – User is able to read documents but not create any documents within the database. Users with this access level may also create personal agents within the Notes application that may run against any document to which they have proper access.
• Author – User is able to read all documents as well as create new documents. However, the server or user is only able to edit those documents the user or server created itself. This setting should be used rather than Editor access to avoid replication and save conflicts.
• Editor – User is able to read, create, and edit all documents
• Designer – User is able to read, create, and edit all documents. In addition, the user is able to edit and create Forms, Views, and create a Full-Text Index.
• Manager – User is able to read, create, and edit all documents. In addition, if using the Notes client, the manager is able to edit and create Forms, Views, and Full-Text Indices. Manager access also allows the editing of the ACL of the database itself. Each Notes application requires at least one entry with Manager access.

If a user appears specifically within the ACL of a Notes database ACL and also is a member of a group that appears in the ACL of the database, the user’s name will prevail. If a user belongs to two or more groups that all appear within the ACL of the database, the group with HIGHER ACL access will prevail.