MayFlower develops specialty software products for Lotus Notes & Domino.




Chapter 7 - Coordinating Updates Across the Enterprise
Table of Contents


Why would you want to coordinate Updates?

Oftentimes, different people have access to different sources in the organization. The reasons are sometimes security, or simply convenience. Either way, they can both move data into the same Replica ID simultaneously.


Example: Main Document and Responses

In this example, Person A will put customer information from the Customer Information System from the California office. Person B will add sales and financial information as response documents from the Order Entry System from the New York office. Both have network access to the same server.

Person A schedules the Customer Task for every night at 10:00 PM. Person B schedules the Order Entry Task for every night at 11:30 PM.

Both direct their Notes Destination Server at the Marketing_Server, so that the Main Documents will exist for Person B at 11:30.

What happens if Person A fails to run their task?
When Person B runs their Task, they will receive a log message like the following:
07/22/95 03:54:47 PM: Import Complete.
Import records read: 12
Notes added: 0
Notes updated: 0
Notes with errors: 0
Responses without Parent: 12

The Responses without Parent: 12 section is the clue that no main documents were found.