3.4 Importing the Driver Configuration in iManager

The Create Driver Wizard helps you import the basic driver configuration file. This file creates and configures the objects and policies needed to make the driver work properly.

  1. In Novell® iManager, click Identity Manager Utilities > New Driver.

  2. Select a driver set.

    If you place this driver in a new driver set, you must specify a driver set name, context, and associated server.

  3. Select Import a Driver Configuration from the Server (.XML file), then select AvayaPBXShip-IDM3_5_0-V2.xml.

    The driver configuration files are installed on the Web server when you install Identity Manager. During the import, you are prompted for the driver’s parameters and other information.

  4. Specify parameter values. See Table 3-1 for more information.

  5. Click Import.

    When the import is finished, you should define security equivalences and exclude administrative roles from replication.

    The driver object must be granted sufficient eDirectory™ rights to any object it reads or writes. You can do this by granting Security Equivalence to the driver object. The driver must have Read/Write access to users, resources, and distribution lists. Normally, the driver should be given security equal to Admin.

  6. Review the driver objects in the Summary page, then click Finish.

    Table 3-1 Specify Values for These Parameters

    Parameter Name

    Parameter Description

    Driver name

    The actual name you want to use for the driver.

    Emulation Mode:

    Will this configuration be initially setup to use emulation mode? Emulation mode provides you with the ability to test live data but not write it out to your phone systems. Default is Emulation.

    Polling Method:

    Select the method the driver should use to poll for changes. By Interval means the driver will poll every so often for a given interval specified in minutes. By Time means the driver will poll only at a specified time. Or, you may choose to do both.

    Driver is Local/Remote

    Configure the driver for use with the Remote Loader service by selecting the Remote option, or select Local to configure the driver for local use. If Local is selected, you can skip the remaining parameters.

    Site Container:

    Specify the container where site objects will be placed in the directory. For example: ou=PbxSite.o=MyOrganization.

    Work Orders Container:

    Specify the container where work order objects will be placed in the directory. For example: ou=WorkOrders.o=MyOrganization.

    Users Container:

    Specify the container that will hold the User objects in the directory. For example: ou=Users.o=MyOrganization.

    PBX Name:

    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]

    Driver will Manage Avaya Extensions:

    Select whether this driver will be managing Avaya Extensions. Default is Yes.

    Driver will Manage Audix Subscribers:

    Select wheter this driver will be managing Audix* subscribers. Default is Yes.

    Extensions Container:

    Specify the container where extension objects will be placed in the directory. For example: ou=Extensions.o=MyOrganization.

    Subscriber Container:

    Specify the container where subscriber objects will be placed in the directory. For example: ou=Subscribers.o=MyOrganization.

    LDAP Host IP Address:

    Specify the LDAP host IP address to be used in emulation mode, for example: [151.65.137.1].

    LDAP Host Port Number:

    Specify the LDAP host port number to be used in emulation mode, for example: [389].

    LDAP Host User DN:

    Specify the LDAP host users DN used for authentication to the emulation LDAP system, for example: [cn=Admin,o=Org].

    LDAP Host Password:

    Specify the LDAP host users password to be used in emulation mode, for example: [Novell]. Confirm the password.

    Extensions Container:

    Specify the LDAP host container that will be used for the emulation of extensions, for example: [ou=PbxEmulationExtensions,o=Org].

    Poll Interval (minutes):

    Specify a poll interval, in minutes, for the driver to use. For example, 120.

    The additional driver parameters are set to default values during the import process, but they can be modified in iManager (by clicking the Driver Configuration tab on the driver object).

    Table 3-2 Additional Configuration Information

    Import Prompt

    Description

    Poll Time

    If you choose to use a polling time, this prompt is displayed when you click Next.

    Select a poll time for the driver to use. For example, 12:00 AM.

    Remote Host Name and Port

    For remote driver configuration only. If you specify Remote in the Driver is Local/Remote prompt, this prompt is displayed when you click Next.

    Specify the host name or IP address and port number where the Remote Loader Service has been installed and is running for this driver. The default port is 8090.

    Driver Password

    For remote driver configuration only. If you specify Remote in the Driver is Local/Remote prompt, this prompt is displayed when you click Next.

    The Driver object password is used by the Remote Loader to authenticate itself to the Identity Manager server. It must be the same password that is specified as the Driver object password on the IDM Remote Loader.

    Remote Password

    For remote driver configuration only. If you specify Remote in the Driver is Local/Remote prompt, this prompt is displayed when you click Next.

    The Remote Loader password is used to control access to the Remote Loader instance. It must be the same password that is specified as the Remote Loader password on the IDM Remote Loader.

    If you use the Emulation mode, specify the following parameters when importing the driver.

    Table 3-3 Specify Parameters for Emulation Mode

    Import Prompt

    Description

    IP Address for LDAP Host for Emulation

    For emulation, the driver needs to access an LDAP host (eDirectory or any other host).

    Specify the IP address of the LDAP server.

    Port of LDAP Host

    Specify the port number of the LDAP server used for emulation.

    DN of the Login User for Emulation

    For emulation, the driver needs to know which username 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.

    User Password for Emulation

    Specify the password of the user who accesses the LDAP server.

    Extension Container DN for Emulation

    Specify the DN of the container where the driver will add or modify extension objects (this container must already exist on the LDAP server.)