Oturum Aç
 
Ana SayfaKütüphaneEğitimIndirinSorun GidermeForumlar
BT Uzmanları için Kaynaklar >
> 
> 
How to create an Template Input File in Extensible Connectivity Management Agent in ILM2007?

Yanıt How to create an Template Input File in Extensible Connectivity Management Agent in ILM2007?

  • 16 Şubat 2012 Perşembe 22:06
     
     
    Oylamak İçin Oturum Aç
    0

    In reference to my previous question (link).  I am stuck at selecting a Template Input file while creating an Extensible Connectivity Management Agent in ILM2007.

    Does anybody know how to create one?

    I think it is related to showing what are the objects available.

    And on a related note, if I using only password synchronization then do I need to configure Connected Data Sources Extensions.  It is asking me to select the .dll but I don't think I need to provide the custom .dll for pwd sync.  That should be at the end.

    Thanks.


    • Düzenleyen Mitul Suthar 17 Şubat 2012 Cuma 13:32 Added a hyperlink
    •  
     

Tüm Yanıtlar

  • 16 Şubat 2012 Perşembe 22:28
     
     
    Oylamak İçin Oturum Aç
    1

    Hi-

    The template is simply used for figuring out what attributes are initially available. You can change it later. What file format input is your XMA using?

    For password sync, you will need to provide a custom DLL that includes a password extension if you want to sync passwords to your XMA.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

     
  • 17 Şubat 2012 Cuma 13:31
     
     
    Oylamak İçin Oturum Aç
    0

    Thanks Brian,

    Is there a sample file format available?  I would be syncing userDN and Password to a third party system.  Should I create a template input file with these attributes then?

     
  • 17 Şubat 2012 Cuma 14:57
     
     Yanıt
    Oylamak İçin Oturum Aç
    1
    The file format will be whatever your XMA creates as it reads in data from your external source.  It should include the userDN and any other data that might be needed to join to existing metaverse objects.  I don't think the password should be part of the template file.  That would be handled by the password extension only, not the import/export process that the template file is used to construct.
    • Yanıt Olarak İşaretleyen Mitul Suthar 17 Şubat 2012 Cuma 15:25
    •  
     
  • 17 Şubat 2012 Cuma 15:27
     
     
    Oylamak İçin Oturum Aç
    0

    To give you a little bit background.  I don't need to read anything from the XMA.  I will be only updating pwd when a change is detected through a webapi through pwdExtension.  In this case do I still need the Template file format thing or  I can do away with it.  Because it is just one way flow from MV to this webAPI.

    Thanks again for the help.


     
  • 17 Şubat 2012 Cuma 17:18
     
     
    Oylamak İçin Oturum Aç
    1

    To give you a little bit background.  I don't need to read anything from the XMA.  I will be only updating pwd when a change is detected through a webapi through pwdExtension.  In this case do I still need the Template file format thing or  I can do away with it.  Because it is just one way flow from MV to this webAPI.

    Thanks again for the help.



    It's a bit more complicated than this. You will need to read at a minimum the data necessary to join to the metaverse objects for this to work. Your password extension won't get called for someone unless they have a connector in the XMA that's joined to the metaverse object that the password change came in for.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com