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.By default, the Driver Configuration page is displayed.
In Designer:
Open a project in the Modeler.
Right-click the driver icon or line, then select click
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 Module
Table A-2 Driver Object Password
The authentication section stores the information required to authenticate to the connected system.
Table A-3 Authentication
Option |
Description |
---|---|
or
|
This option is not used with the SOAP driver. The SOAP driver requires separate authentication settings for both the Publisher channel and the Subscriber channel. |
or
|
This option is not used with the SOAP driver. |
or
Port
|
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 host name 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. Click to set the file size to unlimited in Designer. |
or
|
This option is not used with the SOAP 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 Option section allows you to set the driver state when the Identity Manager server is started.
Table A-4 Startup Option
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.
The parameters are presented by category:
Table A-5 Driver Settings
Option |
Description |
---|---|
|
Specify <nds>, <input>, and <output>. if you want the driver shim to remove and add the required XML elementsThe required elements are removed from XML documents sent to the application and are added to XML documents received from the application before presenting the document to the Metadirectory engine. Otherwise, specify to turn off this element handling. |
|
Select if you have developed custom Java classes to extend the driver shim’s functionality. Otherwise, select .For more information, see Section B.0, Using Java Extensions. |
|
Select if you have developed a custom Java class to process data as XML documents. |
|
Select if you have developed a custom Java class to process data as a byte array. |
|
Select if you have developed a custom Java class to replace the default HTTP transport layer for the Subscriber channel. |
|
Select if you have developed a custom Java class to replace the default HTTP transport layer for the Publisher channel. |
|
Select if you have developed a custom Java class to provide the application schema to the driver. |
Table A-6 Subscriber Settings
Table A-7 Publisher Settings
Option |
Description |
---|---|
|
Specify the IP address of the server where the SOAP driver is installed and the port number that this driver listens on. If you imported a sample configuration file, this field contains the IP address and port that you specified in the wizard. |
|
Specify the Authentication ID of the remote server to validate incoming requests. If the remote server does not send an Authentication ID, leave this field empty. If you imported a sample configuration file, this field contains the IP address and port that you specified in the wizard. |
|
Specify the authentication password of the remote server to validate incoming requests if you entered an Authentication ID above. Otherwise, leave these fields empty. If you need to clear the password, select , then click . |
|
Specify the KMO name to be used in eDirectory. When the server is configured to accept HTTPS connections, this name becomes the KMO name in eDirectory. The KMO name is the name before the “-” (dash) in the RDN. Leave this field empty when a keystore file (see Keystore file below) is used or when HTTPS connections are not used. |
|
Specify the keystore name and path to the keystore file. This file is used when the server is configured to accept HTTPS connections. Leave this field empty when a KMO name is used (see KMO name above) or when HTTPS connections are not used. |
|
Specify the keystore file password used with the keystore file specified above when this server is configured to accept HTTPS connections. Leave this field empty when a KMO name is used or when HTTPS connections are not used. |
|
Specify a Server key alias when this server is configured to accept HTTPS connections. Leave this field empty when a KMO name is used or when HTTPS connections are not used. |
|
When this server is configured to accept HTTPS connections, this is the key alias password (not the keystore password). Leave this field empty when a KMO name is used or when HTTPS connections are not used. |
|
When using SSL, it is common to do only server authentication. However, if you want to force both client and server to present certificates during the handshake process, you should require mutual authentication. |
|
Specify the heartbeat interval in seconds. Leave this field empty to turn off the heartbeat. |
NOTE:A SOAP client calling the web service in the publisher channel must specify a URL ending with a slash. For example, http://1.1.1.1:9095/. Without a context path (the slash), the driver does not process the request received.