Oracle Fusion Middleware : 11.1.1.x / 11gR1 Support

Your 11gR1(11.1.1.x) customer does not wish to upgrade to 11gR2 (11.1.2.x) or to 12c (12.1.x) as he probably is not too keen on the new features or is not excited about the cloud yet.

Well, what about support on 11gR1 ? This can be a major factor for upgrade apart from new features!

11.1.1.x Premier support ends June 2015
As per http://www.oracle.com/us/support/library/lifetime-support-middleware-069163.pdf page 36

Note there are three kinds of support - Premier Support, Extended Support and Lifetime Support.

The extended support may not support integrations with new third party vendors and the sustaining support does not include new fixes!

Typically premier support is for 5 years since the launch of the product, extended support for 2 more years and sustaining support thereafter.

Oracle IDM 11gR2 : Integrating with MS Active Directory 2003

The latest versions of OIM and OAM 11gR2(11.1.2.x) donot support LDAP Sync or OIM-OAM Integration using Active Directory(AD) 2003 as per the 11gr2 certification matrix. 

We had a use case to support federation using OAM 11gR2 somehow with AD 2003 as the Identity Store. 

Option 1 : Using OVD

We noticed that the latest version of OVD was 11.1.1.7 which happens to support AD 2003 as per the 11gR1 FMW certification matrix .So potentially we could hook OAM with OVD as the Identity Store and still connect to Active Directory 2003, which is not directly supported!

Extending this theory we could provision to OVD from OIM which finally would create relevant user accounts in Active Directory 2003!!

Oracle confirmed this in SR # 3-9503114871(you may not be able to view it directly but can refer to this in another SR if need be).

Option 2 : Using OID and DIP

Standup OID(11.1.1.7 is the latest as of today) and sync existing users from AD 2003 using a DIP process.

Option 3 : Use IDM 11gR1

Least preferred since it's never a good idea to go back to a older release when the newer release has so much to offer and IDM 12c is in the pipeline.If none of the above can be made to work for whatever reasons, AD 2003 is definitely supported both with OIM and OAM 11gR1(11.1.1.x).

Oracle SOA : SFDC Adapter Issue - Total Requests Exceeded

We faced an issue wherein total API calls to SFDC to check for updated accounts exceeded the limit (due to Quartz Scheduler Polling at regular intervals )

Analysis : 

Once limit is reached , this cannot be undone till 24 hours !

http://bconeadapters.blogspot.com/2014/02/what-are-limitexceeded-errors-i.html

https://help.salesforce.com/apex/HTViewHelpDoc?id=integrate_api_rate_limiting.htm&language=en

Quick Fix : Use a different sandbox if using developer edition of SFDC

Correct way should be to (Work In Progress) -

1)Optimizing API calls to Salesforce.com

Although the Oracle Cloud Adapter for Salesforce.com incorporates several measures to reduce API calls to Salesforce.com (for instance, session management for limiting login calls and cache for limiting metadata fetch calls), you can further reduce calls to Salesforce.com while designing your composites through the offline configuration feature of Oracle Cloud Adapter for Salesforce.com.

2)Use polling interval of Quartz scheduler in couple of minutes than seconds.