Oracle's BEA acquisition SOA perspective – Revisited again

A Keynote presentation titled Oracle Fusion Middleware and BEA:
an inside Look – Product Strategy, may clarify some of Oracle's SOA directions discussed in a post immediately after the acquisition and a follow up post.

It is a presentation on SOA products strategy as well as to other related products strategy.

The approach is to define mix of BEA and Oracle products as strategic components composing Oracle's SOA platform.

The leading brand name is Oracle Fusion., however in some areas Oracle offerings include two competing products: Oracle's and BEA's. In other cases one of product is a preferred solution.

The most relevant slide is presented above. This slide presents a SOA suit.

In my opinion, although quantitatively more Oracle components are included, the most significant elements are BEA's products. The ESB is BEA's Aqua Logic and Complex Events handling is based upon BEA's product.

It should be noted that not all SOA infrastructure products are included in this slide. The missing parts include Repository and Registry, SOA Governance tools, Data Integration and Application Server and Portal.

According to my understanding of the keynote presentation slides, the directions are:

• BPM suite is based upon Aqualogic BPM suit for Design and Execution. BPEL, BAM and Business Rules are based on Oracle's product.

• BEA Web Logic Integrator is not a part of the suite. Although according to another slide it is not yes in maintenance mode, I completely agree with recent Forrester Research's BPMS market analysis (Integration-Centric Business Process Management Suites, Q4 2008 by Ken Wollmer) referring to it as a risky product.

• Application Server suite is labeled Oracle WebLogic Suite. No doubt that BEA's WebLogic Application Server is the strategic solution although oracle Application Server is included in the suite.