Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
   

Configuring IIFP to Sync User Attributes

Page 1 | Page 2 | Page 3 | Page 4 | Page 5 | Page 6 | Page 7

Creating Run Profiles

A run profile is basically a group of tasks that a MA can execute.  In order to get any data into the metaverse, at least one MA must run an Import step.  If you want to get data from the metaverse into a connected data source, the MA for that data source must run an Export step.  In MIIS, there are two types of spaces where data is stored.  The first is the connector space and the other is the metaverse itself.  Doing an Import step retrieves objects from the connected data source and places them in the connector space for that MA.  Only objects that are in the selected containers that meet filtering rules, or rule extension filtering logic, are placed into the connector space.  An Export takes objects from the connector space for an MA and sends them to the connected data source.  Again, only objects that are not filtered out are processed.

In order to get data from the metaverse to the connector spaces for MAs, a synchronization step must occur.  The synchronization step will analyze the join and projection rules defined on a MA to either link objects in the connector space to objects in the metaverse, and add or update attributes of those objects in the metaverse, or create new objects in the metaverse.  This is if the MA is set to Import on attribute flow only.  On the other hand, if the MA is set to Export on its attribute flow, objects and their attributes will be sent from the metaverse to the connector space.  Once connector objects have been imported into the connector space and synchronization has been carried out, the metaverse should be populated.  This assumes that the Import and Synchronization steps were run against an MA that had its attribute flow set to Import.

Once the metaverse is populated, another MA, or the same MA if its attribute flow has been defined in both directions,  needs to then run a Synchronization and Export step.  This will replicate objects from the metaverse to the connector space of that MA.  Then the Export step will send objects and attributes from the connector space to the data source.

In the picture below, CD represents the Connected Data source.  CS is the Connector Space.  MA is the Management Agent that connects the CD to CS.  MV is the MetaVerse.  An Import step takes data from the CD and places it into the CS.  A synchronization step takes data from the CS and places it into the MV or from the MV to the CS.  The Export takes data from the CS and sends it to the CD.  For more information read Microsoft?s MIIS_Overview.doc, available at: http://www.microsoft.com/downloads/details.aspx?familyid=d7894cc9-eeeb-40d9-8f5f-573050624f67&displaylang=en.

A.    Creating  run profiles for the Source Domain MA

1.      Click the Management Agents button in the Identity Manager console

2.      Click the ?Source Domain? MA and click Configure  Run Profiles under Actions

3.      Click New Profile?

a.       Step 1: Full Import (Stage Only)

i)        Enter ?Setup Metaverse? for the name and click Next >

ii)      Select Full Import (Stage Only) from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

b.      Step 2: Full Import and Full Synchronization

i)        Click New Step?

ii)      Select Full Import and Full Synchronization from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

iv)    Confirm that the steps are similar to those shown below

4.      Click New Profile?

a.       Step 1: Full Import and Delta Synchronization

i)        Enter ?Refresh Metaverse? for the name and click Next >

ii)      Select Full Import and Full Synchronization from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

iv)    Confirm that the step settings are similar to those shown below and click OK

B.     Creating  run profiles for the Target Domain MA

1.      Click the ?Target Domain? MA and click Configure Run Profiles under Actions

2.      Click New Profile?

a.       Step 1: Full Import (Stage Only)

i)        Enter ?Setup Metaverse? for the name and click Next >

ii)      Select Full Import (Stage Only) from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

b.      Step 2: Full Import and Full Synchronization

i)        Click New Step?

ii)      Select Full Import and Full Synchronization from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

iv)    Confirm that the steps are similar to those shown below

3.      Click New Profile?

a.       Step 1: Full Import and Delta Synchronization

i)        Enter ?Export to AD? for the name and click Next >

ii)      Select Full Import and Full Synchronization from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

b.      Step 2: Export

i)        Click New Step?

ii)      Select Export from the ?Type:? drop-down list and click Next >

iii)    Take the default options on the Management Agent Configuration screen and click Finish

iv)    Confirm that the step settings are similar to those shown below and click OK

Configuring IIFP to Sync User Attributes

Page 1 | Page 2 | Page 3 | Page 4 | Page 5 | Page 6 | Page 7

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008