Fusion Applications - Bits and Pieces of Future Direction

While I believe this information to be reliable, please insert the appropriate legal boilerplate: these thoughts are my own and do not represent those of Oracle; while I believe this information to be accurate, I do not present them with the intent that any person or enterprise to rely on this content to their detriment, the author accepts no personal liability, blah…blah…blah…

Now that the CYA is finished, let’s get on with sharing the news.

Release 12

R12 of the E-Business Suite is, to a large degree, a delivery iteration on the path to Fusion Applications. Although we all already know that R12 will run on Fusion Middleware, I’m not sure we all understand that one of the major points of R12 is to extend the functionality of the E-Business Suite using Fusion Middleware. In other words, this might be a worthwhile release for those E-Business customers ready to dive deeper into SOA.

Fusion Applications

- Oracle Forms will be replaced by Java Server Faces (”JSF”)
- The combination of Business Process tools and a BPEL execution environment will replace the Oracle Workflow product
- Fusion 1.0 will not eliminate PL/SQL and C++ from the apps environment, but the intent is for both to be eliminated at some point
- The Fusion development effort is still on-track to release individual applications in 2007 and the integrated Fusion Applications Suite in 2008.
- Oracle has released their flavor of an SOA maturity model, which you can read about here. This model provides substantial insight on where Fusion is headed.
- JDeveloper with ADF will continue to be the IDE and framework of choice for development work within the Fusion Applications environment.

Well, that’s all I have for now. Like I stated earlier, it’s in bits and pieces. There is not much of a unifying thread running through all this, it’s just chunks of info that seem worthy of sharing.