3.2 Perparing to Install

3.2.1 Creating Containers

Before you install, you need to specify or create some containers when importing the driver configuration:

  • Container for holding the DirXML-pbxSite objects

  • Container for holding the DirXML-nwoWorkOrder objects

  • Container for holding the DirXML-pbxExtension objects, if you are using them

    The sample base configuration uses these objects, but in a production environment you would usually transform events for DirXML-pbxExtension objects into events for User objects.

  • Container for holding the DirXML-pbxAudixSubscriber objects, if you are using them

You should restrict rights to these containers so that only authorized administrators can change these containers or the objects they hold.

These containers and objects are also described in Section 2.1, Planning Issues for All Configurations and Section A.0, Schema for PBX Management.

3.2.2 Use Emulation

This driver is different from other Identity Manager drivers because it provides emulation capabilities. Creating a robust test environment can be a challenge, because the only PBX available in an environment might be the production PBX. To solve this problem, we recommend using the driver’s emulation mode. See What Is Emulation Mode and Why Should I Use it? for more information before installing the driver.

3.2.3 Installing the Driver Preparation

You need to install the following:

  • The driver shim ( Avayashim.jar). Install it on the server where Identity Manager is installed or on a server where you will use Remote Loader to run the driver.

  • The driver policies for the driver ( AvayaPBXShip-IDM3_5_0-V2.xml and AvayaUser-IDM3_5_0-V2.xml) and the iManager plug-ins for using work orders. Install them on the iManager server.

If Identity Manager and iManager are on the same server, you only need to run the install program once. Otherwise, you need to run the install program on servers that are running the different components (Remote Loader, Identity Manager, iManager).