Novell Doc: Identity Manager 3.6 Driver for Avaya PBX Implementation Guide - How the Workforce Tree Configuration Works

7.2 How the Workforce Tree Configuration Works

The Subscriber adds to the work order the ID of the user object for which the phone number is being provisioned. This can be an ID of your choice, for example, Employee ID or Social Security number. The sample configuration uses Workforce ID. When the Publisher has configured the extension, it updates the user object with the extension number. The driver puts the Object ID in the Cable field of the extension in the PBX. This field has a character limit of 5 characters.

Figure 7-1 Workforce Tree Configuration

Figure 7-2 Flowchart of the Workforce Tree Configuration

7.2.1 How the Driver Uses the ObjectID to Identify and Update Users

The following figure shows where the ObjectID comes from and how it is used by the driver to update users. In this diagram you can trace the role of the ObjectID; the user’s ID becomes the ObjectID of the work order, and is entered into the PBX as an attribute of the extension. After the task is complete, the ObjectID is used to identify the user object that needs to be updated.

Figure 7-3 How the Object ID Is Used in the Process

7.2.2 How the Subscriber Channel Is Configured

In the workforce tree configuration, the Subscriber channel listens for events that pertain to work orders and users. (PBX site objects must also exist in eDirectory™, but they are used only for the driver to query for information about how to contact each PBX. Changes to PBX objects are not processed by the Subscriber; instead you must restart the driver for changes to be recognized.)

In the workforce tree configuration, a work order can be created or a user can be created, which then causes Identity Manager to create a work order.

Table 7-1 Configuring the Subscriber Channel

Rule or Policy	What it does
Subscriber Filter	Allows only events for nwoWorkOrder and User objects to be processed.
Event Transformation	Not used in the sample configuration.
Matching Rule	Not used in the sample configuration.
Create Rule	Contains rules only for nwoWorkOrder and User objects. For an nwoWorkOrder object, requires values for the following attributes. PBXName nwoStatus nwoSendtoPublisher nwoDoItNow nwoAction nwoDisplayName For a User object, requires values for the following attributes. Surname L As an example in the sample configuration, L (location) is used to provision the extension differently depending on where the user is physically located. (You could customize the policy to use L to determine which PBX site to use, or what setcor restrictions to use.) Workforce ID The Workforce ID is important in the sample configuration because it is used to populate the ObjectID so the user can be identified with a work order. If values are not present for the required attributes, the work order is not sent to the Publisher, and therefore is not performed in the PBX. For a description of these attributes, see Section B.2, DirXML-nwoWorkOrder Object and Section B.5, User Objects and Their Identity Manager Associations.
Placement Rule	Maps work orders from the work order container you specified to the Identity Manager Driver for Avaya PBX. This mapping is necessary so that the Subscriber can check the work orders to see whether the DoItNow flag is set to True. Maps user object containers to the Identity Manager Driver for Avaya PBX. This makes sure that users, when they are created, are sent to the driver so that work orders can be created to provision their phone extensions.
Command Transformation	Takes user events and changes them to PBX actions. Converts a user Add event into a work order object. Determines the PBX and node to use based on the Location attribute of the user object. (The configuration includes sample code for how to do this. You could use another user attribute instead, such as job title.) Determines the phone type based on the Location attribute of the user object. Then, determines the dupe extension to use based on the phone type. The sample configuration shows an example of mapping phone type to dupe extension.
Schema Mapper	Maps the eDirectory namespace to the PBX namespace. Handles mapping of work orders, extensions, and PBX site objects.
Output Transformation	For work orders you create in the work order container, maps the phone type to the duplicate extension if the dupe extension is not indicated in the work order. (Use the PBX “template” for how to configure the phone type).

7.2.3 How the Publisher Channel Is Configured

Through the Publisher channel, the Identity Manager Driver for Avaya PBX queries the PBX for information about extensions, places work order objects in the correct container, performs work orders, and sends updates to user objects.

Table 7-2 Configuring the Publisher Channel

Rule or Policy	What it does
Input Transformation	Not used in the sample configuration.
Schema Mapper	Maps the PBX namespace to the eDirectory namespace. Handles mapping of work orders, extensions, and PBX site objects.
Event Transformation	Transforms pbxExtension Add, Modify, or Delete events into events that modify user objects. Transforms nwoExtension Add events into user Modify events. Uses the ObjectID from the work order to identify the user so it can add the new extension to the User object's telephone number. Transforms Modify events into events to modify the preferred name or object ID. Transforms Delete events for extensions into Modify events to remove the extension from all users who have it in their phone list. This is done by a query for users, rather than by the Object ID.
Publisher Filter	Allows only events for nwoWorkOrder, User, and extension objects to be processed.
Matching Rule	Not used in the sample configuration.
Create Rule	Not used in the sample configuration.
Placement Rule	Places work order objects in the correct container. Places extension objects in the correct container.
Command Transformation	Not used in the sample configuration.

7.2.4 User Events That Can Trigger a Work Order

Table 7-3 Configuring User Events

User event from the Human Resources application	Work Order that is created by the policies	Ideas for what you could do when customizing the policies
New employee is entered in HR application	An Install work order is created to install new extension The work order is marked DoItNow, so it is performed immediately The user is updated with the new phone extension in the Identity Vault	You could configure the HR driver to update the user’s information in the HR application.
Employee moves to a different location	No action is taken in the sample configuration.	You could customize the policies to do the following: Create a Move work order If the move requires a new extension update, give the employee a new extension Remove the old extension from the user object.
Employee’s name changes	A Modify work order is created and is performed immediately The display name in the PBX is modified, so the user’s phone shows the correct name on outgoing calls.
Employee goes on extended leave	No action is taken in the sample configuration.	You could customize the policies to create a Disable work order.
Employee leaves the company	No action is taken in the sample configuration.	You could customize the policies to disconnect the extension.