Difference between OIM 10g and OIM 11g

1.        10g Request Management has been replaced by SOA composite which has a customized schema accommodating BPEL and Human Task.

2.        Reconciliation engine has been re-written in 11g to enhance the performance by introducing the cache mechanism.

3.        OES libraries are used as an authorization engine unlike 10g had its own object vs view based authorization.

4.        Plugin services platform is introduced in 11g to have easy customization in place which can be some what mapped to entity adapter functionality in 10g.

5.        Groups in 10g are now called as Roles in 11g with some modifications which makes it like ldap roles.

OIM 10g	OIM 11g
Reconciliation Manager in Design Console	Event Management in Admin Console.
Object Form	Request Dataset
Creation of new IT Resource from Design/Admin Console.	Creation of new IT Resource from Admin Console.
Struts based UI.	ADF based UI.
Approvalworkflow creation from Design/Admin Console	Approval workflow creation from IDE using SOA Plugin.
Custom workflow engine	Using BPEL as workflow engine.
No Notification Tasks	Notification tasks which are separate from Schedule Task’s jobs.
No Approval Policies.	Approval Policies
No Need of BI Publishers.	Need BI Publisher for OOTB reporting.
No need of RCU (Repository Creation Utility)	Need of RCU (Repository Creation Utility)
Groups	Roles
No concept of Request Template.	Request Template for controlling the Attributes of the request.
Entity Adapters on User Form.	Event Handlers on user form.
Support only old APIs.	Support old and new APIs.