The Avaya PBX driver must be located on a server that can access the Avaya PBX via telnet. This can be either a Metadirectory server (Metadirectory engine, Identity Vault, and Avaya PBX driver) or a non-Metadirectory server (Remote Loader service and Avaya PBX driver. If the driver is not already installed on the server you want to use, you have the following options:
Install the Metadirectory server (Metadirectory engine and drivers) to a supported server. This requires Novell® eDirectory™ to be installed on the server to provide the Identity Vault. See the instructions in Identity Manager 3.6.1 Installation Guide.
When you install the Metadirectory server, the installation program extends the Identity Vault’s schema and installs the driver shim and the driver configuration file. It does not create the driver in the Identity Vault (see Section 4.0, Creating a New Driver) or upgrade an existing driver’s configuration (see Section 5.0, Upgrading an Existing Driver).
Install the Remote Loader (required to run the driver on a non-Metadirectory server) and the Avaya PBX driver files to a supported server. This assumes that you already have a Metadirectory server installed that the Avaya PBX driver can run against. See Identity Manager 3.6.1 Installation Guide.