The following sections explain concepts you should understand before implementing the GroupWise driver:
GroupWise accounts are managed through the GroupWise snap-ins for ConsoleOne. The GroupWise driver replaces certain management tasks you perform through the snap-ins. For example, you can use the driver to automatically provision GroupWise accounts to new eDirectory users.
We recommend that you use either iManager or ConsoleOne (without the GroupWise snap-ins) to administer users in eDirectory, then let the driver synchronize any changes into GroupWise. In particular, you should not use the GroupWise snap-ins for ConsoleOne, iManager tasks associated with GroupWise, or other GroupWise administration tools for anything the driver is configured to do.
When you have the driver installed, if you manage GroupWise user accounts with the GroupWise snap-ins or other tools, it results in redundant synchronization of data because data changes are synchronized by both the snap-ins and the driver. Redundant synchronization of data might result in warnings or errors in the Identity Manager logs. However, these warnings or errors can usually be ignored.
Not all GroupWise account information can be managed through the driver. You should use the GroupWise snap-ins for ConsoleOne to manage these components of GroupWise accounts:
GroupWise system-wide parameters, such as nickname expiration date
X.400 information
Resources
Mailbox and library maintenance
Client options and preferences
Grafting (use caution)
Backup and restore
The driver uses the following components:
This API is necessary for the driver to perform the required actions in GroupWise. It is installed at the same time as the driver shim.
A Java* driver shim is used to communicate between the Metadirectory engine and the GroupWise API. This driver shim is installed at the same time as the GroupWise API.
The driver packages contain all Identity Vault objects necessary for the driver, including the appropriate policies for adding, modifying, and deleting or disabling GroupWise accounts. In addition, the default policies control the information being sent from the Identity Vault to GroupWise.
The driver filter specifies the classes and attributes that GroupWise publishes to eDirectory. We do not recommend making changes to the driver filter regarding which attributes are published to eDirectory. If the filter is changed, it can cause objects to not synchronize correctly.
GroupWise accounts are administered through eDirectory. Driver customizations are usually done in the Subscriber channel or at the driver level. The Subscriber channel receives commands from the Metadirectory engine and executes those commands in GroupWise. The Subscriber channel is used to synchronize eDirectory events with GroupWise. It watches for additions, modifications, renames, moves, and deletes in eDirectory and creates events in GroupWise to reflect those changes.
You can add to the base configuration that comes with the driver. However, do not remove or modify preconfigured attributes from the Subscriber filter or the Mapping policy.
To ensure that the driver has access to the correct objects, be aware of the following:
The driver can only access Identity Vault objects located in the partitions on the server associated with the driver set.
Users, post offices, resources, and distribution lists must be in the same partition. Or, the partitions containing these objects must all have replicas on the server associated with the driver set.
The driver can only synchronize to a GroupWise system that is installed in the same eDirectory tree where the Metadirectory server is installed.