Untitled Document
Today's announcement by Oracle of the rollouts of Fusion Middleware 11g is
a bit anticlimactic in that the details are pretty much according to the plan
that came out exactly a year ago today. Although the Fusion stack is comprised
of multiple parts, internally developed and acquired, the highlight is that
it represents the fruition of the BEA acquisition. Oracle had Fusion middleware
prior to acquiring BEA, but there's little question that BEA was the main event.
WebLogic filled the donut hole in the middle of the Fusion stack with a server
that was far more popular than Oracle Containers for Java EE (OC4J). Singlehandedly,
BEA catapulted Oracle Fusion into becoming a major player in middleware.
Oracle largely stuck to the previously announced roadmap for convergence of
BEA products, with the only major surprises being in the details. As planned,
Oracle incorporated WebLogic as the strategic Java platform, JDeveloper as the
primary development environment, dual business process modeling paths, with
master data management, data integration, and identity management driven largely
by Oracle offerings with some added BEA content.
Although the Oracle Fusion product portfolio came from far more diverse sources
than BEA (as Oracle was obviously a more aggressive acquirer), the result is
far more unified than anything that BEA ever fielded. Before getting swallowed
by Oracle, BEA had multiple portal, development, and integration technologies
lacking a common framework. By comparison, Oracle has emphasized a common framework
for mashing the pieces together.
That's rooted in Oracle's heritage for developing native tools and utilities,
dating back to the Oracle Forms 4GL and the various utilities for managing the
Oracle database; the tools were sufficiently native that they typically were
confined to Oracle shops. But that approach to native tooling morphed with development
of a broader framework that is optimized for Oracle platforms. It's an outgrowth
of the mentality at Oracle that good is the enemy of best, and that what Oracle
is building is a platform rather than discrete products.
It's an approach that also makes Oracle's tagline of Fusion being standards-based
as being more nuanced. Yes, the Fusion products are designed to support Oracle's
"hot pluggable" best of breed strategy to work with other vendors
products, but for designing and managing the Fusion environment, Oracle has
you surrounded with native tooling if you want them. Call it a subtle pull for
encouraging customers to add more Oracle content.
-1-