APPLICATION MANAGEMENT

Design changes and replication
Unless you distribute design changes through templates, design changes and any document updates made in one database replicate directly to replicas, as long as servers have Designer access or greater in the database ACL. To avoid replication conflicts and unexpected changes, only one person -- the database designer or manager -- should make design changes to only one database and maintain its design. Then let replication distribute the design changes to other replicas.

Replication occurs at the times specified by the server's replication schedule. Replicating design changes can take several hours or even a full day if replicas are in different locations and aren't replicated frequently.

Templates and replication

When you use a template to distribute design changes, you must place a replica of the template on each server that has databases that inherit their design from the template. Give servers Designer access or greater in the database ACL of each replica. To avoid replication conflicts, make changes to one template on a "source" server. Then let replication distribute the design changes to template replicas. The updated template replicas then refresh the design of linked databases on the server. To distribute design changes efficiently, the source server should replicate the template replicas before the Designer task runs on each server at 1:00 AM. Any updates you've made to documents replicate directly with other database replicas.

For more information on replication, see Lotus Domino Administrator Help.

See Also