Metaverse to External System RRS feed

  • Question

  • Hi all,

    Just have some questions and need your supports

    - Is that possible to export metaverse objects to External system by using only FIM Sync (without outbound rule created on FIM portal). Seem that we need to create provisioning rules on extensions...?

    - I see "the attribute flow" on MA but have no ideas what is different between them and the rule on outbound/inbound sync rule that be able to be created on FIM portal.

    Thanks !

    Wednesday, March 4, 2015 7:21 AM

All replies

  • Hello,

    yes of course this is possible, it good old time (MIIS/ILM) this was the only way to sync attributes on objects, and its still possible and needed many times.

    In order to create new objects in a connector space (and export them after that) you need to do provisioning with a mv rules extension, thats correct.

    If all objects exists already in both data source you can simple let one MA project objects to MV and let the other joid, with approp. criterias in MA.

    There are a lot of differences between sync rules and MA classic rules, see documentation on that.
    One point is that classic rules can have also rules extension to handle attribute data on import and export, beside other things, while sync rules have OOB functions to do controldata flow.


    Peter Stapf - ExpertCircle GmbH - My blog:

    Wednesday, March 4, 2015 8:35 AM
  • Thanks Peter for your support.

    I have 2 questions still need your help:

    1. without MV rules extensions or outgoing rules of FIM service, can we push data from metaverse to connector space..

    For example: We have:  A ======CS1=====Metaverse======CS2======B

    A==>CS1: Import via MA

    CS1==> Metaverse: Sync action by projecting and map attributes based on attribute flow

    Metaverse==>CS2: Wonder that if we dont have any rules.. we cannot push data from Metaverse to CS2? And the attribute flow for exporting is just for export from CS2 to B

    2. In order to create new objects on B, do we must have some certain conditions on rules.

    For example: If B is Active Directory, outgoing rule MUST define DN attribute (I just tested with outgoing rules to map just only displayname and samaccountname but seems not work)

    Thursday, March 5, 2015 3:07 AM
  • Hello,

    to Q1:

    The step from pushing data from a MV object to Destination CS (creating a connector for a new object in System B) is named "provisioning" you can only do this by povisioning code (MV Extension) or via sync rule declarative provisioning. Thats how it works.

    to Q2:

    Yes you are right, there is a Special Attribute which must be set on creating new connectors in a CS. Ist called the "anchor" Attribute. On AD and other LDAPs it is the DN. On other Systems it is a Attribute choosen by you.

    You have to set this Attribute in the Provisioning code (or have an inital flow in sync rules)

    Provisioning is basicly a simple 3-step Operation:

    1. Create new connector (for example on type Person)

    2. Set Anchor Attribute (for example DN)

    3. Commit Connector.

    Here is an example:

    Dim dn as ReferenceValue
    Dim rdn as String
    # Set values for RDN and Container/OU
    rdn = "CN=" & mventry("cn").Value
    MA = mventry.ConnectedMAs(MA_Name)
    dn = MA.EscapeDNComponent(rdn).Concat(OU_Name)
    # Create the new connector
    csentry = MA.Connectors.StartNewConnector("user")
    csentry.DN = dn
    # Set other values as initial flow once


    Peter Stapf - ExpertCircle GmbH - My blog:

    Thursday, March 5, 2015 8:12 AM
  • Very clear ! Really appreciate your support.

    Friday, March 6, 2015 1:51 AM