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.In Designer:
Open a project in the Modeler, then right-click the driver line and 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
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 driver’s Java class is: com.novell.nds.dirxml.driver.nds.DriverShimImpl |
|
This option is not used with the Avaya PBX driver. |
|
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
Option |
Description |
---|---|
or
|
Specify a user application ID. This ID is used to pass Identity Vault subscription information to the application. Example: Administrator |
or
|
Specify the IP address or name of the server the application shim should communicate with. |
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 hostname is the IP address of the application server running the Remote Loader service 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
|
Specify the password for the user object listed in the field. |
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
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 Disabled, this file is deleted and no new events are stored in the file until the driver state is changed to Manual or Auto Start. |
|
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.
The Avaya PBX driver does not have any Driver Options or Subscriber Options. The following table describes the Publisher Options.
Table A-5 Publisher Options
Parameter |
Description |
---|---|
General Options |
|
|
Specify the name of the PBX site object. This is the same name you use for the creation of the PBX site object in the directory. For example: [ProvoPBX] |
|
Select the container where the PBX site object resides. |
|
Select the container where the PBX work orders object resides. |
|
Select the container where the PBX extension objects will be created. This is required only if your configuration uses extension objects. If your configuration writes PBX information directly to user objects (like the workforce tree configuration does), you do not need to specify an extension container. |
|
Select the container where the Audix subscriber objects will be placed in the directory. If your configuration does not include Audix subscribers, you do not need to specify a subscriber container. |
|
Specifies the number of minutes between checks for available transactions to process. The default is . Use 0 to disable the polling interval, in which case you need to set a poll time. |
|
Select a poll time for the driver to use. For example, 12:00 AM. If no poll time is selected, the driver uses the poll interval only. |
Emulation Options |
Use these options to set up emulation for testing purposes. For information about additional tasks required to set up emulation, see Section 4.2.3, Using Emulation to Test the Driver. |
|
Select to display the emulation options. Select if you don’t need to see the options. |
|
For emulation, the driver needs to access an LDAP host (eDirectory or any other host). Specify the IP address of the LDAP server. |
|
Specify the port number of the LDAP server used for emulation. The default is . |
|
For emulation, the driver requires a username that has access to the LDAP server. This user must have rights to read/write to the extension containers on the server. Specify the name of the user for the LDAP server. |
|
Specify the password of the user who accesses the LDAP server. Confirm the password. You can also clear the password by selecting (iManager) or (Designer) and then clicking . |
|
Specify the DN of the container where the driver will add or modify extension objects (this container must already exist on the LDAP server.) For example, ou=PbxExtensions,ou=AvayaPBX,o=Novell |
Displays an ordered list of ECMAScript resource files. The files contain extension functions for the driver that Identity Manager loads when the driver starts. You can add additional files, remove existing files, or change the order the files are executed.
Displays an ordered list of Global Configuration objects. The objects contain extension GCV definitions for the driver that Identity Manager loads when the driver is started. You can add or remove the Global Configuration objects, and you can change the order in which the objects are executed.