You create the Manual Task Service 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 start it.
In iManager, click to display the Identity Manager Administration page.
In the Administration list, click Import Configuration to launch the Import Configuration Wizard.
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 desired Manual Task configuration file (MTDAccess, MTDCellphone, MTDRoomNumber, or MTDWelcome). The configuration files include the filters and policies needed to implement each scenario. If you have a different scenario you want to implement, you should select the basic configuration that most closely resembles your desired scenario and modify it as needed. |
Driver name |
Type a name for the driver. The name must be unique within the driver set. |
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. 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 (if necessary) the driver’s default configuration settings.
To modify the default configuration settings, click the linked driver name, then continue with the next section, Configuring the Driver Object.
or
To skip the configuration settings at this time, click Finish. When you are ready to configure the settings, continue with the next section, Configuring the Driver Object.
There are many settings and policies that you use to configure and optimize the driver. The ones you use depend on what you are trying to accomplish with the driver. The driver settings and policies are explained in Section A.0, Driver Settings, Policies, and Templates.
After configuring the driver, it must be started. Continue with the next section, 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:
In iManager, click to display the Identity Manager Administration page.
Click Identity Manager Overview.
Browse to and select the driver set object that contains the driver you want to start.
Click the driver set name to access the Driver Set Overview page.
Click the upper right corner of the driver, then click Start driver.
For information about management tasks with the driver, see Section 5.0, Managing the Driver.