Directory Synchronization

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.

Exporting Directory Entries from Exchange to GroupWise

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:

1. Based on the information from the initial query, the GroupWise connector creates an export message containing the transactions necessary to complete an update or a full reload.
2. The connector places the message in the Togwise folder.
3. The connector's router component picks up the export message and sends it to the input queue (API_IN) of the API gateway.
4. The API gateway sends the messages to the GroupWise system and the system updates the GroupWise directory.

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.

Importing Directory Entries from GroupWise to Exchange

1. The GroupWise connector generates a request for a full reload and the router puts the request in the input queue (API_IN) of the API gateway.
2. The API gateway routes the message to the GroupWise system, and the GroupWise system generates a response after polling the GroupWise directory. GroupWise sends the response back to the output queue (API-OUT) of the API gateway.
3. The router checks the output queue of the Gateway according to determined polling intervals. After it acquires messages, it places them in the Dirsync folder.
4. The Connector maps GroupWise attributes to Exchange attributes according to the configured mapping rules. It adds GroupWise users and groups to Active Directory as contacts, users, or security-disabled users in the import container that you choose.

Synchronizing Groups

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.

Synchronizing Resources

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 Topics