A passion for innovation is what drives Collaborate. One issue of interest to functional, technical, and business users inside the Oracle community is scalability and ensuring that modifications you make to your ERP suite today will still be relevant in the future.And thus we come to the crux of this Collaborate 14 Outtake – Oracle ADF vs. Oracle OAF.
ADF vs. OAF Who Cares? Here’s Why You Should
Oracle Application Framework (OAF) and Application Development Framework (ADF) are two application development technologies from Oracle. The challenge in front of customers is making a decision about what technology to choose their custom requirements. There are different factors which should drive a decision between ADF and OAF and below are a few factors that you need to consider to make the right decision.
OAF vs. ADF, Part I – Level of Customizations
For personalization’s or customizations in Oracle Applications (11i/R12) OAF is a preferred choice because OAF is the default technology for all Oracle E-Business Suite releases prior to R12.2.
However, if your requirements involve entirely new Oracle R12 functionality:
- Strongly consider using ADF to ensure compatibility with future Oracle E-Business Suite and/or Fusion Applications releases. However, keep in mind that you’ll likely need to make an additional upfront investment in the form of Web Logic licensing and infrastructure costs. The same application can be used in future versions of Oracle EBS or Fusion Applications.
- You can avoid these Web Logic and infrastructure costs, but in truth you’re just delaying costs as the customization cannot f upgraded to Fusion Applications in future.
Remember – all customizations in Fusion Applications use ADF.
OAF vs. ADF, Part II, Level of Integration with Applications
If the custom requirements represent tight integration with standard Oracle EBS, consider OAF as seamless integration of standard OAF R12 applications with ADF is not yet possible.
If the custom requirements represent little or no integration with standard Oracle EBS, choose OAF or ADF based on life span of the solution, affordability of new licenses and level of future readiness required.
OAF vs. ADF, Part III, Version of Applications
One thing to keep in mind – the version of the Oracle Applications determines the available technology stack.
All Oracle E-Business Suite versions earlier to R 12.2 use Oracle Application Server (OAS) which onlysupports OAF.
Oracle R12.2 and everything that has and will come after it will use Web Logic Server (WLS) which supports ADF as well as OAF
Hence, if you’re not on Oracle R12.2 you need separate license for WLS for using ADF. If you are on either EBS 12.2 or Fusion Applications, the default WLS gives you the required infrastructure and licenses for using ADF.
|Level of IntegrationApplications Version||Oracle EBS version 12.1.3 or earlier (OAS)||Oracle EBS version 12.2 and beyond (WLS)||Oracle Fusion Apps V1 (WLS)|
|Tight integration with applications||OAF||OAF||ADF|
|Little or no integration with applications||OAF (short term but low cost solution)|
ADF (future ready solution with upfront investment)
|OAF (short term solution)|
ADF (future ready solution)
Still seeking more insight into the OAF vs. ADF Debate? Stop by Booth 1049 and ask to speak to one of our experts in person! Remember, for more information, please visit our Collaborate 14 Resources page and/or check out our Development Services offerings.