You create the JMS driver by importing the driver’s basic configuration file and then modifying the configuration to suit your environment. After you create and configure the driver, you need to deploy it to the Identity Vault and start it.
There are four configuration files. Each file corresponds to one of the supported JMS vendors: JBossMQ, IBM WebSphereMQ, SonicMQ, and TIBCO EMS.
In Designer, open your project.
In the Modeler, right-click the driver set where you want to create the driver, then select
> to display the Driver Configuration Wizard.In the Driver Configuration list, select the desired JMS configuration, then click
.On the Import Information Requested page, fill in the following fields:
Driver Name: Specify a name that is 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
if this driver will run on the Metadirectory server without using the Remote Loader service. Select if you want the driver to use the Remote Loader service, either locally on the Metadirectory server or remotely on another server.(Conditional) If you chose to run the driver remotely, click Step 6.
, then fill in the fields listed below. Otherwise, skip toRemote Host Name and Port: Specify the host name or IP address of the server where the driver’s Remote Loader service is running.
Driver Password: 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: 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
Click
to import the driver configuration.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.
To review or modify the default configuration settings, click Configuring the Driver.
, then continue with the next section,or
To skip the configuration settings at this time, click Configuring the Driver.
. When you are ready to configure the settings, continue withAfter 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 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, Deploying the Driver.
After a driver is created in Designer, it must be deployed into the Identity Vault.
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.If you are authenticated to the Identity Vault, skip to Step 5; otherwise, specify the following information:
Host: Specify the IP address or DNS name of the server hosting the Identity Vault.
Username: Specify the DN of the user object used to authenticate to the Identity Vault.
Password: Specify the user’s password.
Click
.Read the deployment summary, then click
.Read the message, then click
.Click
to assign rights to the driver.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.
Click
, then browse to and select the object with the correct rights.Click
twice.Click
to exclude users that should not be synchronized.You should exclude any administrative User objects (for example, Admin and DriversUser) from synchronization.
Click
.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:
In Designer, open your project.
In the Modeler, right-click the driver icon or the driver line, then select
.For information about management tasks with the driver, see Section 6.0, Managing the Driver.