How to create an Extensible Conectivity 2.0 MA that call a web service in FIM 2010 R2? RRS feed

  • Question

  • I created my web service to create, update and delete users from one of our systems.

    Now I am to create MA to use my web service and export users into that system, there is no need to import!

    I tried to use web service configuration tool but had lots of errors and could not find an example of configuring run profiles.

    Now I am trying to write Extensible Conectivity 2.0 Management Agent. I need help as there is no examples available for how to call/use web service in MA.


    Monday, February 24, 2014 5:54 AM

All replies

  • Hello Emadina
    You need a web service reference in your Management Agent Extension code to get access to the exposed functions.
    And you not only need functions to create/modify/delete objects, you also need a function to read the objects from the custom data source for two reasons:
    a) to be able to join your existing objects
    b) for confirming imports.

    I think the best point to start your own Extensible Management Agent extension is the following link:

    Cheers, Henry

    Monday, February 24, 2014 10:27 AM
  • Hi!

    I would consider writing a Custom workflow activity instead if i only wanted to have trigger that calls a web service and did not care about life cycle management for that system.

    This is a good way to get going:

    Monday, February 24, 2014 9:22 PM
  • If you can get at your webservice using PowerShell, you could give my PowerShell MA a go ( instead of writing up your own ECMA (unless you want to learn how to write an MA, of course)

    Calling a webservice from an ECMA is just the same as calling from any other C# / VB .NET code - this shouldn't be FIM specific, btw

    Regards, Soren Granfeldt
    blog is at | facebook | twitter at!/MrGranfeldt

    Tuesday, March 11, 2014 6:57 PM
  • Let me add some personal notes here.

    Now you have three Options.

    a) write an Extensible MA

    b) write a workflow activity

    c) use Powershell MA

    Debugging is easier in a) and b).  

    a) and c) are state-based while b) is event driven. You have to extra maintain export Errors.

    maintaining changes later on is best using Sorens MA just by simply changing some lines in a script. No need for compiling and distributing DLLs.


    Tuesday, March 11, 2014 7:08 PM