Several years ago, BEA began to lag behind competitors Oracle and IBM in the integration and enterprise platform space. Its goal was to focus in on SOA, and its strategy was to take that market by storm. AquaLogic Service Bus 2.1 proves that BEA's hiatus from the competitive market was well worth the wait.
AquaLogic is installed within a stripped down, lightweight version of WebLogic Server (WLS) 9.1. It's essentially a stand-alone J2EE product, capable of being installed as a module within any WLS container, but it does not support deployment within other J2EE containers, such as JBoss or IBM WebSphere.
AquaLogic is stateless, using JMS for persistence of state only when necessary. It does not require a metadata repository unless you want to take advantage of its included reporting and monitoring capabilities, which can then be configured to use an existing RDBMS or the default embedded Pointbase database.
BEA AquaLogic Service Bus Console
Click to enlarge in another window
Deployment to the bus is instantaneous because the AquaLogic design-time environment is completely Web-based, and it takes advantage of the HTTP session-management capabilities of WLS to keep track of what the designer is doing. The design-time environment is also completely drag-and-drop and worked equally well in both Internet Explorer and Mozilla Firefox 1.4. In fact, AquaLogic is unique in its use of a Web browser as its design-time environment. We easily defined services, which can be published to BEA's embedded Systinet Business Service Registry or to an external registry, and orchestrated those services from within a composite service.