OIM 11g Upgrade from OIM 9.1.1

Question

Hi All,
We are planing to upgrade OIM 9.1.1 to OIM 11g, I have seen the impact analysis in the link "http://www.oracle.com/technetwork/middleware/id-mgmt/learnmore/upgrading-oim9x-to-oim11g-wp-365479.pdf". I am bothering about OIM Objects (Forms,Adapters,Lookups), How the impact will be?
In that document, they said, There is no Prepopulated adapters and changes in Enitity adapters and APIs are also changed.
1. So de we need to implement all adapters in OIM 11g again, or can we directly import them?
2. For API changes, Do we need to update all APIs in my custom adapters? or will old APIs work on OIM 11g?
3. Can we directly load all Lookups directly?
We dont have any Approval workflows, We have simple direct provisioning using custom adapters, we dont have policies also. Through Groups, we have assigned the AD and Exchange resources to the users
Please suggest me.
Thanks

Answer 1

The document details which pieces of OIM exist in 9.x and 11g. Table 2.2.1 identifies all the request related objects in 9.1 and 11gR1 and which can be migrated. It lists pre-populate adapters, but this could only be on the object side, they will still exist as is in the process side for provisioning. As part of your upgrade plan, you will need to identify how to recreate the non-upgradable items and how they are integrated into the parts of OIM once it is migrated to 11gR1.
In section 2.7 Entity Adapters and Event Handlers behave differently. So in 9.x if you have any of these for custom code, you will need to identify how to recreate these in 11gR1 and attach them into the existing processes so your existing functionality will be intact.
As for APIs, none of the old APIs go away. A portionof them listed in section 2.8.2 have been identified as legacy APIs and how they map to the new service. You can continue usage of old ones, but the suggestion is to make any new ones with the latest API set. I woudl assume the only exception for APIs that wont work would be the tcRequestOperationsIntf since this will not exist in 11g. You'll need to use the APIs to access the BPEL and SOA data in the database instead.
The overall process is an evaluation of every connector you have implemented and all your functionality. Identify which pieces can and can't be migrated, and then either recreate the functionality in 11g or create new functionality within the 11g product instead. It will be a very lengthy process, which is essentially reviewing your whole implementation.
I hope this gives you some idea of the changes to be expected. The utility will migrate the pieces it can, but then it's up to you and your client to implement the pieces that could not be converted. Then you get to evaluate the new features of the product and which ones you want to use.
-Kevin