Directory synchronization consists of two separate processes: exporting user data from Exchange to GroupWise and importing user data from GroupWise to Exchange. When you schedule a synchronization, one process follows the other. Note that in Novell GroupWise, each individual directory update is transmitted in a separate mail message, so directory synchronization can take a long time.
The following diagram provides an overview of directory synchronization.Enlarge figure
Exporting actually consists of two cycles. In the first cycle, the GroupWise connector polls the GroupWise directory to take a snapshot of current GroupWise users before it begins the cycle of exporting directory entries.
In the second cycle, directory entries are exported. The steps are as follows:
Note The API gateway does not produce confirmation messages or return codes. Some errors may be visible in the API gateway log file, and Administrative Agent (ADA) error messages are sent as mail messages to a designated administrator mailbox. The GroupWise administrator should review these logs regularly.
Connector for Novell GroupWise supports propagation of the names of groups to Exchange and GroupWise. The Connector does not synchronize the memberships of the groups. The target system (either Exchange or GroupWise) must expand the group for message delivery to the membership of the list.
In Exchange, GroupWise groups (called distribution lists in GroupWise 5.x) appear as contacts. In GroupWise, Exchange groups appear as foreign users.
GroupWise has a directory object class called Resource, which is used for conference rooms, equipment, and other shared resources. In Exchange, GroupWise resources appear as contacts.
Related TopicsControlling Directory Synchronization Route Mail Using Address Spaces