[FIM] How to import data from A, synchronize data to B, delete data in system A, retain data in system B, and modify the status

In FIM synchronization, apart from the previous mention, after deleting database A, you need to delete database B synchronously (Click here ). There is also a common requirement:

Generally, a database record is not deleted in an application system, but only marked.

Operation logic:

1. Delete the user from the data source-> Delete the corresponding Metaverse object (in this case, the CS object corresponding to the application system and the corresponding Metaverse object disconnected)

2. Custom Extension is used to modify the status.

Before specific settings, let's take a look at the default behavior of FIM:

By default, a Metaverse object is deleted only when all associated CS objects are deleted. We can achieve this through configuration. Once this object is deleted in a specified CS, the music video will be deleted. For example, the HR system of a company has left the company, we can naturally think that the corresponding mv object should not exist.

It is worth mentioning that, no matter how you set it, FIM will ensure that the corresponding MV will be deleted after the CS object in the Last MA loses contact with the mv. The reason is simple, because any music video object must have at least one data source for support. Since there is no data source, it is naturally impossible.

Go back to this article to go to The Metaverse design interface.

The red part is "Delete the corresponding Metaverse object when data disconnect in any selected MA ".

After this setting is complete, when the data is deleted in MA (IMPORT) and a SYNC operation is performed, the corresponding Metaverse will be deleted.

What will be done when Metaverse is deleted? Open the configuration interface of the corresponding application system (the State value to be modified) MA, as shown in:

It is worth mentioning that the difference between disconnectors and explicit disconnector in option 1 and option 2 is that after the mv is deleted, they are in the Connect = FALSE state, but the former will create a Metaverse object at the next SYNC, but the latter will not create any more.

In this article, we should select the last item and implement it through code. Because none of the other three options can express the value of Status we want to set. Therefore, we need to add the corresponding code in the corresponding MAExtension. If no extended code is used, the system will prompt you to enter one.

The Code is as follows:

DeprovisionAction IMASynchronization.Deprovision(CSEntry csentry){    csentry["Status"].Value = "Deleted";    return DeprovisionAction.ExplicitDisconnect;}

 

Recommended reading:

1. Understanding Deprovisioning in FIM

Http://social.technet.microsoft.com/wiki/contents/articles/understanding-deprovisioning-in-fim.aspx

2. [FIM] How to import data from A, synchronize data to B, delete data in system A, and delete data in system B
Http://www.cnblogs.com/volnet/archive/2012/01/03/2310786.html

3. Account Deprovisioning Scenarios

Http://www.wapshere.com/missmiis/account-deprovisioning-scenarios