Oracle & BEA Middleware "FUSION" Strategy

I have been eagerly waiting for this events for past couple of weeks. With no doubt the strategy set forth by Oracle is good for both Oracle and BEA customers.

Oracle has categorized the Fusion Middleware into three categories. Strategic, Continue & Converge and Maintanence Products as presented by Mr.Kurian.

Strategic: Some of the BEA products are being adopted immediately with limited re-design into Oracle Fusion Middleware. Few Oracle products converge with BEA products with rapid integration over 12-18 months

Continue & Converge: BEA products will be incrementally redesigned to gradually integrate with fusion middleware technology to broaden the features with automated upgrade.Oracle will invest to continuely develop and maintain these products for atleast 9 more years

Maintanence: BEA products that were EOL'd before acquisition will be maintanined under the same contract for 5 more years

Now coming into the details of the product offerings and strategy as outlined by Thomas Kurian. Product strategy in SOA area is to unify Aqualogic Service Bus and Oracle ESB and in complex event processor Weblogic event server will be merged. BEA WL-Integration will continue to evolve with common services & techonology with BPEL process manager

In the Development tools arena Oracle Eclipse Pack is added into Fussion Middleware pack with no additional licensing costs. The idea is to package BEA Workshop along with Eclipse Pack. Oracle JDeveloper will continue to evolve as Strategic product along with ADF.

Most complex merger of products is in the BPM arena, integrating BEA AL-BPM with Oracle BPEL PM to form Oracle BPM. Both Oracle BPA designer and AL-BPM designer will co-exist as strategic products. As oracle BPA is intended to be used for more structured and rigourous process modelling, where as AL-BPM designer will be used for iterative process modeling

Most significant direction is the BEA Weblogic named as the strategic Application Server going forward.