Todas as Respostas
How about only enabling/disabling Metaverse Rule ,
and how about only enabling/disabling Provisioning Rule ?
We are try to migrate from MIIS to FIM.
The procedure is like the below.
1 full import stage only of all GALMA to FIM.
2 didable Provisioning Rule and full sync all GALMA of FIM.
3 It looks import attribute flow which use rule extension does not work (TargetaddressMapping etc, ) and looks some of existing contact failed to join(some of existing contact succeeded to join).
I am not sure but it might be because tagetaddress or other MV attributes are missing because of disabling Provisioning Rule .
Metaverse extension can implement more interfaces than Provision only - disabling provisioning rules means that Provision will not be called but interface to determine if object should be deleted from MV still can be called. Disabling rule extension completly disables both.
Join and attribute flows are implemented separately and are not affected by this setting.
Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl
anything specified in the PROVISIONING section (see below) within the Rules Extension DLL defined in the Metaverse will be ENABLED/DISABLED
Public Sub Provision(ByVal mventry As MVEntry) Implements IMVSynchronization.Provision
In that section you can configure the provisioning of objects (= creation of new objects in the connector space(s)) and the disconnection of objects (disconnection of objects in (specific) connector spaces from the metaverse object)
Two common reasons exist to DISABLE provisioning:
(1) initial load of data
(2) disaster recovery (which is somewhat similar, if not the same, to initial load of data)
Jorge de Almeida Pinto [MVP-DS] | Principal Consultant | BLOG: http://jorgequestforknowledge.wordpress.com/