Work Order Database Configuration

As described in the Base Configuration section, you can use eDirectory as your work order database, using work order objects. However, if you have another work order database that you are already using to enter PBX work orders, the Identity Manager Driver for Avaya PBX can fit into that environment as well. The driver can perform work orders that are created in another application and synchronized to eDirectory.

For example, if personnel in your organization are accustomed to using a JDBC database product to enter work orders for phone extensions, you could preserve the existing process for entering work orders while using the Avaya PBX driver to automate how the work orders are performed. This kind of solution would use two Identity Manager drivers, one for Avaya PBX, and one for the JDBC database.

The samples provided for this kind of configuration (in a file named OracleWorkOrderNew.xml) are some individual policies that contain scripting that could be used in a driver configuration for the JDBC driver. A complete driver configuration is not provided, but this section explains the concept of this kind of solution.

This solution could be combined with the Workforce Tree configuration example, so that work orders can have two sources:

• Automated requests triggered by user events in eDirectory, such as new extensions assigned for new employees.
• Manual requests for existing employees entered in a work order database by administrative assistants or IT personnel, such as modifying a display name or moving offices.

In this section:

• How You Could Configure a Work Order Database Configuration
• About Work Order Systems
• Planning for the Work Order Database Configuration
• Setting Up the Work Order Database Configuration
• Using Log/Reporting Functionality to Report Warnings