![]() ![]() Objects always provision to the FIM MA*įor any resource type that has an Object Type Mapping with a metaverse resource type, any object projected to the metaverse will provision to the FIM MA connector space.The FIM MA always projects new objects to the Metaverse*įor any resource type that has an Object Type Mapping with a metaverse resource type, the projection rule is declared (true).This means neither Synchronization Rules nor MA Rules Extensions are used for complex data flow between the FIM MA Connector Space and the Metaverse. All Flows between the FIM MA and Metaverse are directĪll attribute flows between the FIM Service and Metaverse are direct and must be configured in the Management Agent properties.In any event it is true for understanding synchronization with the FIM MA and there are 4 effects imposed by this design choice: Technically, this is not the whole story as there are separate schemas for the Metaverse and FIM Service, and there is no requirement to configure additional attribute flows at all (perhaps there should be). This information is important, and helps iron out some of the weirdness in the FIM MA. Identity data managed by the FIM MA has a direct relationship to the Metaverse. ![]() From a synchronization perspective that's ALL it is, albeit with some configuration set by design. Think of the FIM MA as just another Management Agent, and the FIMService database as just another data source. This management agent extends the functionality of Forefront Identity Manager to leverage codeless provisioning, management policy application, reporting, and self-service by connecting aggregated identity data in the Metaverse with a separate data source, the FIMService database. The FIM Service Management Agent (FIM MA) is a call-based MA used to communicate with the FIM Web service. ![]() The FIM MA is just another Management Agent ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |