Simple Account Provisioning Walkthrough: Data Files
Applies To: Windows Server 2003 with SP1
Previous Steps in This Walkthrough
Table 2.12 lists the attribute-value pair data files that are provided in this scenario. Files in this scenario with -avp in their names are formatted as attribute-value pairs, which means that each line contains a single value for a single attribute for one object. Objects are separated with a blank line.
Table 2.12 Attribute-Value Pair Data Files
Files | Description |
---|---|
fabrikam-hr-avp.txt |
This file contains the 100 users that will be provisioned using this scenario. |
fabrikam-hr-avp-change01.txt |
This file contains a change in employee status to inactive that should trigger disabling the user account and moving it from one container to another. It is used in a delta import. |
fabrikam-hr-avp-change02.txt |
This file contains a change in employee status to active and should reverse the changes made with the change01 file. It is used in a delta import. |
fabrikam-hr-avp-change03.txt |
This file shows a change of name and is used in a delta import. |
fabrikam-hr-avp-change04.txt |
This file sets the value of the employeeStatus attribute for an employee to terminated and is used in a delta import. This should result in the deletion of the employee’s metaverse object and when exported using the Fabrikam AD MA, it should result in the deletion of the user’s account. |
fabrikam-hr-avp-change05.txt |
This file shows a transfer of an employee with changes in the branchID, managerID, and title. After using a delta import, when this change is exported to Active Directory, the title, department and manager are changed. |
fabrikam-hr-avp-obsolete.txt |
This file contains a single record and is used in a full import run of the MA. Because it is a full import, any objects not included in this file are deleted from the HR MA connector space, and deprovisioned. |
fabrikam-hr-avp-zerobytes.txt |
This file is an empty file to generate an import error and stop the MA run. |
Table 2.13 lists the fixed-width pair data files that are provided in this scenario. These files are formatted with attributes in a certain position and length on each record. A header row provides the attribute names, positions and lengths by virtue of the placement of the attribute names (EMPID in the first position with the E in the first character of the file and Name in the twelfth character determines the fields on all subsequent rows).
Table 2.13 Fixed-Width Pair Data Files
Files | Description |
---|---|
fabrikam-telinfo-fw.txt |
This file contains telephone information for 88 of the employees in this scenario. In a full import run, it is joined with the HR data using the telephone system’s EMPID attribute. |
fabrikam-telinfo-fw-change.txt |
This file contains a change of telephoneNumber for one employee and is used in a delta import. |