4.2 Creating the Driver in iManager

You create the JMS driver by importing the driver’s basic configuration file and then modifying the configuration to suit your environment. After you’ve created and configured the driver, you need to start it.

4.2.1 Importing the Driver Configuration File

There are four configuration files. Each file corresponds to one of the supported JMS vendors: JBossMQ, IBM WebSphereMQ, SonicMQ, and TIBCO EMS.

  1. In iManager, click Driver icon to display the Identity Manager Administration page.

  2. In the Administration list, click Import Configuration to launch the Import Configuration wizard.

  3. Follow the wizard prompts, filling in the requested information (described below) until you reach the Summary page.

    Prompt

    Description

    Where do you want to place the new driver?

    You can add the driver to an existing driver set, or you can create a new driver set and add the driver to the new set. If you choose to create a new driver set, you are prompted to specify the name, context, and server for the driver set.

    Import a configuration into this driver set

    Use the default option, Import a configuration from the server (.XML file).

    In the Show field, select Identity Manager 3.6.1 configurations.

    In the Configurations field, select the JMS configuration file that corresponds to your JMS vendor.

    Driver name

    Type a name for the driver. The name must be unique within the driver set.

    JMS Broker Value

    Specify the URL for this message broker. The URL usually contains a protocol, an IP address, and a port number.

    Driver is Local/Remote

    Select Local if this driver will run on the Metadirectory server without using the Remote Loader service. Select Remote if you want the driver to use the Remote Loader service, either locally on the Metadirectory server or remotely on another server.

    Remote Host Name and Port

    This applies only if the driver is running remotely.

    Specify the host name or IP address of the server where the driver’s Remote Loader service is running.

    Driver Password

    This applies only if the driver is running remotely.

    Specify the driver object password that is defined in the Remote Loader service. The Remote Loader requires this password to authenticate to the Metadirectory server.

    Remote Password

    This applies only if the driver is running remotely.

    Specify the Remote Loader’s password (as defined on the Remote Loader service). The Metadirectory engine (or Remote Loader shim) requires this password to authenticate to the Remote Loader

    Define Security Equivalences

    The driver requires rights to objects within the Identity Vault and to the input and output directories on the server. The Admin user object is most often used to supply these rights. However, you might want to create a DriversUser (for example) and assign security equivalence to that user. Whatever rights that the driver needs to have on the server, the DriversUser object must have the same security rights.

    Exclude Administrative Roles

    You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.

    When you finish providing the information required by the wizard, a Summary page, similar to the following is displayed.

    At this point, the driver is created from the basic configuration file. To ensure that the driver works the way you want it to for your environment, you must review and modify the driver’s default configuration settings.

  4. To modify the default configuration settings, click the linked driver name, then continue with the next section, Configuring the Driver.

    or

    To skip the configuration settings at this time, click Finish. When you are ready to configure the settings, continue with Configuring the Driver.

4.2.2 Configuring the Driver

After importing the driver configuration file, the driver will start. However, the basic configuration probably will not meet the requirements for your environment. You should complete the following tasks to configure the driver:

  • Configure the driver parameters: There are many settings that can help you customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). Although it is important for you to understand all of the settings, your first priority should be to review the Driver Parameters located on the Driver Configuration page.

  • Configure the driver filter: Modify the driver filter to include the object classes and attributes you want synchronized between the Identity Vault and the JMS vendor.

  • Configure policies: Modify the policies on the Subscriber and Publisher channels. For information about using policies, see the Policies in Designer 3.5 or Policies in iManager for Identity Manager 3.6.1 guide.

After completing the configuration tasks, continue with the next section, Starting the Driver.

4.2.3 Starting the Driver

When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. Identity Manager is an event-driven system, so after the driver is started, it won’t do anything until an event occurs.

To start the driver:

  1. In iManager, click to display the Identity Manager Administration page.

  2. Click Identity Manager Overview.

  3. Browse to and select the driver set object that contains the driver you want to start.

  4. Click the driver set name to access the Driver Set Overview page.

  5. Click the upper right corner of the driver, then click Start driver.

For information about management tasks with the driver, see Section 6.0, Managing the Driver.