6.2 Prerequisites for Configuring the BCC Drivers for Identity Manager

Before you configure the Identity Manager drivers, ensure that your system meets the requirements in this section.

6.2.1 Identity Manager

Before you installed Business Continuity Clustering, you set up and configured the Identity Manager engine and an Identity Manager driver for eDirectory on one node in each cluster. For information, see Section 5.2, Installing iManager and Identity Manager on One Node in Each Peer Cluster.

The Identity Manager plug-in for iManager requires that eDirectory is running and working properly.

6.2.2 eDirectory

The cluster node where Identity Manager is installed must have an eDirectory full replica with at least read/write access to all eDirectory objects that will be synchronized between clusters. For information about the full replica requirements, see Section 4.8, eDirectory 8.8 SP7.

6.2.3 Landing Zone Container

The landing zone that you specify for drivers must already exist. Typically, this is the OU container you created for the peer cluster’s objects. You can optionally create a separate container in eDirectory specifically for these cluster pool and volume objects.

6.2.4 BCC Admin User and Group

BCC Administrator user and group are used to manage BCC. The driver needs to have sufficient eDirectory rights (see Section 4.8.6, Rights Needed by BCC Drivers) in the Cluster context to be able to create, modify, and delete objects related to BCC-enabled cluster resources. This is achieved by making the Driver object security equivalent to the BCC Administrator user.

The procedures in this section assume that you have set up a single BCC Administrator user that is used for all peer clusters. If you have set up a different BCC Administrator user for each peer cluster, then use the corresponding BCC Administrator user when working on drivers for the cluster.

For information about setting up the BCC Administrator user, see Section 5.3, Configuring a BCC Administrator User and Group.