Database Reference
In-Depth Information
• To improve application server reliability and performance as Oracle iAS10
g
, at
the time, was already an obsolete OC4J-based server
• The Business Activity Monitoring tool was quite detached from the entire Fusion
stack and based on a separate technology platform
• Rule Engine proved to be quite fast, but the rules' authoring and management was
rather unfriendly, and that jeopardized its acceptance
• Oracle JDeveloper 10.1.X was noticeably slow compared to other IDEs and was
not fully integrated with all SOA Suite components (unfortunately, jumping
ahead, we can say that this is still the truth)
• In addition, Oracle's own Service Bus could not keep up with the closest compet-
itors for some aspects
Oracle addressed these issues quite radically, acquiring BEA. The next generation of Fu-
sion Middleware, 11
g
(2009), came equipped with AquaLogic Service Bus (OSB), BPM
Studio, Enterprise Service Repository, and most importantly,
WebLogic Application
Server
(
WLS
), one of the best J2EE servers available; all of these are based on the very
reliable JVM. It took almost two years to reassemble and repackage all the new middle-
ware components with the new WLS Application Server as the foundation and other BEA
components. JDeveloper 11
g
proved to be more reliable and more integrated with most
core frameworks, such as DB and SOA Suite, but it still did not cover the ESB develop-
ment lifecycle. The standard of
Service Component Architecture
(
SCA
) was adopted in
SOA Suite, where BPEL's role was rearranged and three other equally important compon-
ents were added. Together with SOA Suite, three other suites were offered for
Event
Driven Architecture
(
EDA
), BPM, and Governance, with overlapping functionality. Fu-
sion's hot-pluggability option allows customers to select only the functionality that they
really need at the moment, reducing resource wastage.
After the first radical turn, the next huge acquirement of Sun Microsystems was a com-
pletely logical thing in shaping the Fusion strategy. Now Oracle had the true foundation of
all Java resources—the Java language itself. In addition, the Oracle family inherited Sun's
Java-based, nonstrategic, but very attractive, products—Glassfish Application Server (
ht-
tps://blogs.oracle.com/theaquarium/entry/java_ee_and_glassfish_server
;
Oracle GlassFish
Server will not be releasing a 4.
x
commercial version), OpenESB, and NetBeans IDE.
Despite their nonstrategic status, these products are quite capable of playing their parts in
the construction of an SOA infrastructure of any size, and are quite cost effective as well.
All these products are supported by open communities (
http://www.open-esb.net/in-
dex.php?option=com_content&view=article&id=90&Itemid=469
) and in some cases, are
more advanced than the Fusion middleware stack (for instance, Glassfish is the first Java
Search WWH ::
Custom Search