Connected Data Source Extensions for File-Based Data Sources

Note

With the release of ECMA 2.0, this feature has been deprecated and will be removed in future versions. You should use the Extensible Connectivity 2.0 Management Agent Reference for Connector development going forward.

The following sections contain code examples that show how to create a connected data source extension for file-based data sources.

All the examples assume that the file-based data source consumes an XML file that is in the following format:

<sample-objects>
    <object>
        <objectclass>Person</objectclass>
        <delta>Add</delta>
        <anchor-attribute>1</anchor-attribute>
        <name>Object1</name>
        <email>Object1@fabrikam.com</email>
    </object>
</sample-objects>

In How to: Create Data Source Extensions for File-Based Import and Export, the example generates a comma-delimited file using a helper function. The function expects an XML file that is stored in the root directory and that contains either new objects to be added to the Forefront Identity Manager Synchronization Service (FIM Synchronization Service) database (metaverse), or existing objects that contain new attribute values.

The expected files are:

  • Sample_full_import.xml
    Contains objects that already exist in the metaverse.
  • Sample_delta_import.xml
    Contains objects that already exist in the metaverse. These objects have modified attribute values that must be synchronized.

During inbound synchronization, FIM Synchronization Service uses this comma-delimited file to generate an intermediate file that FIM Synchronization Service uses to import the objects into the metaverse. For outbound synchronization, FIM Synchronization Service generates an XML file that the file-based connected data source can process.

If the connected data source extension is import-only, the extension generates an intermediate file that FIM Synchronization Service uses to import the objects into the metaverse. For export-only connected data source extensions, the extension generates an XML file that the file-based connected data source can process.

See Also

Concepts

Connected Data Source Extensions Code Examples
Creating Connected Data Source Extensions
Connected Data Source Extensions for Call-Based Data Sources