4.1 Creating the Drivers in Designer

This section provides instructions for creating the drivers in Designer. Topics include:

4.1.1 Installing the Packages

Before you attempt to configure the drivers, you need to be sure you have all of the necessary packages in the Package Catalog. When you create a new Identity Manager project, the user interface automatically prompts you to import several packages into the new project. If you choose not to import the packages at the time you create your project, you need to install them later, as described below.

To install the packages after creating a new Identity Manager project:

  1. Once you’ve create a new Identity Manager project in Designer, select the Package Catalog and click Import Package.

    Designer displays the Select Package dialog box.

  2. Click Select All, then click OK.

    Designer adds several new package folders under the Package Catalog. These package folders correspond to the objects in the palette on the right side of the Modeler view in Designer.

  3. Click Save to save your project.

4.1.2 Creating the User Application Driver in Designer

To create the User Application Driver in Designer:

  1. Select User Application in the palette in the Modeler view:

  2. Drag the icon for User Application onto the Modeler view.

    Designer displays the Driver Configuration Wizard:

  3. Select User Application Base and click Next:

    The interface displays a dialog to inform you that need several additional packages.

  4. Click OK to install the required packages.

    At this point, the wizard displays a screen that allows you to name the driver.

  5. You can accept the default driver name, or change it if you like.

    Press Next.

    The wizard now displays a screen that allows you to specify the connection parameters for the driver.

  6. Specify the ID and password for the User Application Administrator, as well as the host, port, and application context for the User Application server. If you want to allow the Provisioning Administrator to start workflows in the name of another person for whom the Provisioning Administrator is designated as proxy, select Yes for Allow Initiator Override:

    The wizard then displays the Confirm Installation Tasks screen.

  7. If everything looks correct, click Finish.

    Designer adds the User Application driver to the Modeler view:

4.1.3 Creating the Role and Resource Service Driver in Designer

To create the Role and Resource Service Driver in Designer:

  1. Select Role Service in the palette in the Modeler view:

  2. Drag the icon for Role Service onto the Modeler view.

    Designer displays the Driver Configuration Wizard.

  3. Select Role and Resource Service Base and click Next.

    The wizard displays a screen that allows you to specify a name for the driver.

  4. You can accept the default driver name, or change it if you like.

    Press Next.

    The wizard now displays a screen that allows you to specify the connection parameters for the driver.

  5. Specify the DN for the base container and the User Application Driver you just created. Since the driver has not yet been ed, the browse function will not show the User Application Driver you just configured, so you may need to type the DN for the driver.

    Also, provide the URL for the User Application, along with the ID and password for the User Application Administrator:

    Click Next.

    The wizard now displays the Confirm Installation Tasks screen.

  6. If everything looks correct, click Finish.

    Designer adds the Role Service driver to the Modeler view:

4.1.4 Deploying the Drivers

To deploy the drivers you’ve just configured:

  1. Select the Driver Set (either in the Modeler view or in the Outline view).

  2. Choose Live>Deploy.

    Designer displays a progress window that shows which objects are being deployed:

NOTE:When replicating an eDirectory environment, you must ensure that the replicas contain the NCP Server object for Identity Manager. Identity Manager is constrained to the local replicas of a server. For this reason, the Role and Resource Service Driver may not start properly if a secondary server does not include the server object.