Example: Connected Data Source Extension for File-Based Data Sources

  • Article

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 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 File-based Import and Export, the example generates a comma-delimited file using a helper function. The function expects an XML file stored in the root directory that contains either new objects to be added to the metaverse or existing objects that contain new attribute values.

The expected files are:

Term Description

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 have to be synchronized.

During inbound synchronization, ILM 2007 FP1 uses this comma-delimited file to generate an intermediate file that ILM 2007 FP1 will use to import the objects into the metaverse. For outbound synchronization, ILM 2007 FP1 generates an XML file that the file-based connected data source can process.

If the connected data source extension is import-only, then the extension generates an intermediate file that ILM 2007 FP1 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.

Send comments about this topic to Microsoft

Build date: 2/16/2009