AD- OIM Reconciliation with Manager as Approver of Resources

Question

Hi, I'm trying to setup the following scenario:
AD->OIM Reconciliation with user's manager information. Setup the manager as the user's approver for every resource available in OIM.
When a user gets added to the AD, he is reconciled into OIM and I have made 2 user defined fields, one to store his managers distinguished name and another to store the users - "usr_udf_man_dn" and "usr_udf_dn". This is working fine, both columns get populated on reconciliation.
What I would like to do is assign the manager as the approver for all the resources that are requested by the user. I am thinking of populating the usr_manager_key through an sql query, by matching "usr_udf_man_dn" with "usr_udf_dn" and getting the managers "usr_key", then storing it in usr_manager_key of the user. The query is not my real problem.
As I'm new to OIM, I don't yet know how to build the 'logic' of this process. How and where to I make the query? I'm assuming these fields can only be populated after the user has been reconciled (because there won't be any fields to do an sql query on before that). Do I use an adapter? How do I setup the approval process?
Any feedback will be greatly appreciated :)
Message was edited by:
user638778

Answer 1

This is very simple and infact there are 2 ways to do it:
# 1) Create a User Process Trigger that adds on Change Event of your Manager UDF Field. This will kick in as soon as a value is put into the Manager UDF field (doesn't matter - via Recon or by hand). Then create an adapter that looks up a User in AD with the DN (your manager) and returns back a SamAccountName. Based on this returned SamAccountName, get the update the user with manager key. Attach this adapter to your process task event in Xellerate User Process Definition.
# 2) Create an Entity adapter that does the same operation as written in #1. Attach this entity adapter to Xellerate User Update event. This is simpler. Drawback of this is that anytime you update the user (for anything - like last name change , org change etc.) - it will repeat this process of updating the user with its manager key. so any change on employee will trigger the manager update. #1 is more efficient.
As far as the approval processes are concerned, there are 2 ways to achieve that also:
# 1) Attach approval in the standard task and assign it to User's Manager for approval. Limitation is that you can not get rid of this in future once you go production with such a setup. You can but you might not want to.
# 2) Individually on each approval process of each resource object, attach the approval task and assign it to User's Manager. That should do it.
Hope this helps.
rajnishbhatia19
For Additional Code Snippets, you may refer to my Blog site:
http://rajnishbhatia19.blogspot.com
Add RSS feed to your portals (google / yahoo / whichever:)
http://rajnishbhatia19.blogspot.com/feeds/posts/default
Connect to me:
http://www.linkedin.com/in/rajnishbhatia19