What is better 1 or more MAs for Export to backend database?
Hi, We are using Oracle as the HR source of data. We have a read-only view of the data we need to replicate to AD via FIM. However, there are some attributes that will need to be written back to Oracle (e.g. samaccountname, telephone, etc) Each of these attributes however are all in different tables...so Do we create a new MA (per attribute essentially) to write back to each Oracle table? Or do we create one table/view in Oracle to update all these attributes? what is the recommended method? thanks
February 13th, 2011 2:39am

Hi, having one MA per one data source is always better, especially when your data source has a lot of entries (if you create multiple MAs to the same source, each one will have it's own CS, and will take up resources and time to process). Of course it's a general recommendation, if it's possible to have just one MA. In your scenario, will it be technically possible to create one view that will accept updates to attributes you need to update? If not you still have few options before creating multiple MAs. For example, maybe update the attributes in other tables by triggers set up on your main table (in this case it would have to be a table, and a writable one), of course you won't be able to track from FIM if the triggered changes succeeded, but that might be OK in some scenarios. If you will have to create multiple MAs, at least try to consolidate all the other attributes in one table/view so you will just have one extra MA. hope this helps, Piotr
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2011 3:02am

Thanks Piotrek.
February 13th, 2011 3:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics