Update (July 2): Archived Webcast is now available from this page.
Oracle President Charles Phillips has just completed his introduction of the Webcast, characterizing the BEA deal as "not just another acquisition" and explaining the reasons why: including the facts that BEA was a leader and pioneer in the middleware area, because it offered a complementary product set/architecture, and because of its strength in key markets, especially China.
But here's the key take-away: All BEA products will continue to be supported under the same timelines previously published by BEA prior to its acquisition, and there will be no forced migration policy. (This approach is quite similar to the well-known Apps Unlimited one, which according to Charles has resulted in a 96% renewal rate for PSFT apps, e.g.).
Charles also said that Oracle will be taking a "pragmatic" approach to product integration - in other words, "best-of-breed" will be the watchword going forward, as usual.
Thomas Kurian is still in the process of deep-diving, which I cannot relay in its entirety. But here are the points that I personally find the most interesting:
- Some products are "Strategic" (immediate integration into Fusion MW stack), some are "Continue & Converge" (some redesign necessary with gradual integration into stack; support for at least 9 years), and some are in "Maintenance" mode (those same products identified as such by BEA pre-acquisition; support for at least 4 years)
- WebLogic Server is now Oracle's strategic JEE container and will be integrated into Fusion Middleware stack immediately; OC4J dev to continue though. TopLink/JPA, Coherence, SCA, and other key technologies will be areas of "convergence" with WLS.
- Technical direction is to continue to modularize the AS under the OSGi model.
- JRockit is "critical" JVM technology for Oracle going forward, but Fusion Middleware will continue to support other JVMs
- (Added July 2): Tooling: JDeveloper will remain Oracle's strategic IDE, but the Eclipse-based Workshop will continue to be available (and it's now free, just as JDeveloper is); eventually Workshop will become part of the Oracle Eclipse Pack offering
- SOA: all components will continue to be hot-pluggable; combined platform offers tools, middleware, governance, and packaged components
- SOA: Oracle ESB and AquaLogic ESB to be converged into the new Oracle Service Bus
- BPM: Oracle to combine system-, human-, doc-, decision-centric BPM into single runtime under combined BPEL/BPMN metadata model
- Portal: WebCenter Framework and WebCenter Suite continue their key roles, Ensemble and Pathways to provide lightweight REST-based portlet assembly in those offerings; continued development of WebLogic Portal and WebLogic AquaLogic UI (now called WebCenter UI) but eventual integration with WebCenter portfolio
- Systems management: Enterprise Management Packs to be extended to BEA products; BEA Guardian will be integrated with Oracle Enterprise Manager
- SOA Governance: AquaLogic Enterprise Rep becomes Oracle's SOA governance repository; Oracle Service Registry will continue as the UDDI registry
- Support: No forced migrations; BEA products to be supported under pre-existing policies (before acquisition); existing Fusion Middleware support to be extended by 1 year
I will provide some interesting tidbits from Thomas' upcoming briefing with bloggers later this AM.
BTW: The first wave of BEA-related downloads and product info can now be found on OTN.
Update (11:51am) - I just want to add some choice quotes/points from Thomas during his call with bloggers:
- "BPM makes SOA declarative"; this is a big requirement from customers
- "When we don't have a product offering in a particular market, we try not to stretch the truth about that"/"We want to be clear about what we're solving, and what we're not solving" (in reference to question about SOA governance from Vance McCarthy)
- "Why do you need a single BPM runtime? Because every system process has human-oriented behavior, and every human process has system-oriented behavior"
- "Today, the notion of a grid that runs on someone else's server is called 'cloud computing' "
- "SOA and grid/cloud are very complementary"; it is much easier to deploy a stateless SOA (workload, services) onto a low-cost-hardware grid than otherwise
- Oracle is exploring the concept of a packaged product in the "SOA Grid" area, but that would be difficult