In Designer:
Open a project in the Modeler.
Right-click the driver icon
or line, then click
In iManager:
In iManager, click
to display the Identity Manager Administration page.
Open the driver set that contains the driver whose properties you want to edit:
In the list, click .
If the driver set is not listed on the tab, use the field to search for and display the driver set.
Click the driver set to open the Driver Set Overview page.
Locate the driver icon, then click the upper right corner of the driver icon to display the menu.
Click to display the driver’s properties page.
The Driver Configuration options are divided into the following sections:
The driver module changes the driver from running locally to running remotely or the reverse.
Table A-1 Driver Modules
|
Option |
Description |
|---|---|
|
|
Used to specify the name of the Java class that is instantiated for the shim component of the driver. This class can be located in the classes directory as a class file, or in the lib directory as a .jar file. If this option is selected, the driver is running locally. The name of the Java class is: com.novell.nds.dirxml.driver.sentinel.SentinelShim |
|
|
Used when the driver is connecting remotely to the connected system. Designer includes two suboptions:
|
Table A-2 Driver Object Password
|
Option |
Description |
|---|---|
|
|
Use this option to set a password for the driver object. If you are using the Remote Loader, you must enter a password on this page or the remote driver does not run. This password is used by the Remote Loader to authenticate itself to the remote driver shim. |
The authentication section stores the information required to authenticate to the connected system.
Table A-3 Authentication Options
|
Option |
Description |
|---|---|
|
|
Not used in this driver. |
|
or
|
Not used in this driver. |
|
or
|
Used only if the driver is connecting to the application through the Remote Loader. The parameter to enter is hostname=xxx.xxx.xxx.xxx port=xxxx kmo=certificatename, when the hostname is the IP address of the application server running the Remote Loader server and the port is the port the Remote Loader is listening on. The default port for the Remote Loader is 8090. The kmo entry is optional. It is only used when there is an SSL connection between the Remote Loader and the Metadirectory engine. Example: hostname=10.0.0.1 port=8090 kmo=IDMCertificate |
|
) or
|
Specify the maximum event cache file size (in KB). If it is set to zero, the file size is unlimited.
|
|
or
|
Not used in this driver. |
|
or
|
Used only if the driver is connecting to the application through the Remote Loader. The password is used to control access to the Remote Loader instance. It must be the same password specified during the configuration of the Remote Loader on the connected system. |
The startup options allow you to set the driver state when the Identity Manager server is started.
Table A-4 Startup Options
|
Option |
Description |
|---|---|
|
|
The driver starts every time the Identity Manager server is started. |
|
|
The driver does not start when the Identity Manager server is started. The driver must be started through Designer or iManager. |
|
|
The driver has a cache file that stores all of the events. When the driver is set to , this file is deleted and no new events are stored in the file until the driver state is changed to or . |
|
|
This option only applies if the driver is deployed and was previously disabled. If this is not selected, the driver re-synchronizes the next time it is started. |
The Driver Parameters section lets you configure the driver-specific parameters. When you change driver parameters, you tune driver behavior to align with your network environment.
Table A-5 Driver Parameters
|
Parameter Name |
Parameter Descriptions |
|---|---|
|
Driver Name |
The actual name you want to use for the driver. This parameter is only available during the import of the driver configuration file. The associations for this driver are based on the driver name. If the driver object is renamed, all of the associations on each object are also renamed, and this can take a long time. |
|
Broker Type |
Select the type of broker you are using. The broker type is determined by the version of Sentinel you are using. Sentinel: Sentinel/Sonic MQ Sentinel RD: Sentinel RD/ActiveMQ |
|
Broker URL |
The URL (Uniform Resource Locator) for the Sentinel broker. The following are examples for the different versions of Sentinel. The ports listed are the default ports for the brokers. Sentinel: tcp://xxx.xxx.xxx.xxx:10012 Sentinel RD: ssl://xxx.xxx.xxx.xxx:61616 |
|
Broker Name |
The name of the user used to authenticate to the Sentinel broker. If you are connecting to a Sentinel system, use a random username. If you are connecting to a Sentinel RD system, use a valid ActiveMQ username.This field must not be blank. |
|
Broker Password |
The password of the authentication user for the Sentinel broker. |
|
Default message expiration (milliseconds) |
Determines how long a message lives in the destination. This setting is global for all messages. The default value of 0 means that the message lives indefinitely in the destination. |
|
Default message expiration (millisecond) |
Determines how long a message lives in the destination. This setting is global for all messages. The default value of 0 means that the message lives indefinitely in the destination. |
|
Heartbeat interval (minutes) |
The number of minutes of inactivity that elapse before the Publisher channel sends a heartbeat document. More than the specified number of minutes can elapse, because this parameter defines the lower bound. |
Enables you to add ECMAScript resource files. The resources extend the driver’s functionality when Identity Manager starts the driver.