Skip to main content

Oracle & BEA SOA perspective - Revisited


-->
In a previous post in January I analyzed the SOA perspective of Oracle's BEA acquisition. I predicted that Oracle's future SOA solutions will be dominated by BEA's SOA solutions. Some comments presented different predictions from mine.
According to The Register article published on June 5th Oracle is splitting the BEA AquaLogic products line between Web 2.0 (originated from the Plumtree acquisition) and BPM (based on the Fuego acquisition). The Register also has learned from individuals close to the company that BEA's new owner Oracle is merging the AquaLogic and WebLogic professional service teams.

The AquaLogic Web 2.0 products probably will be overtook by Stellent Content Management which was acquired by Oracle on November 2006.
As described in previous post titled SOA & BPM, SOA and BPM are strongly related.
Another post tiled SOA and BPM: Too much Round Tripping? described an innovative product trying to extend this affinity beyond automatic BPEL based processes to include BPMN human based BPM.

Some comments on the AquaLogic line of products split suggest that AquaLogic BPM will be incorporated into Oracle Fusion Middleware and probably replace current Oracle offerings due to its superiority in human based BPM. (For example read Eric Roch's post).

The assumption is that the AquaLogic BPM will be incorporated into Fusion Middleware seems reasonable; however replacing current offerings is not the only scenario. Other possible scenarios:
  • Choice between two BPM solutions
This scenario is reasonable for the short time, but I would doubt if Oracle keep dual BPM offerings for the long time.
  • · AquaLogic BPM for development and integration of applications and Oracle BPM for Application Suites (e.g. Oracle Applications).
I still think that BEA's WebLogic will be finally Oracle's SOA Application Server.
The possible inclusion of AquaLogic in Fusion Middlewae together with merging AquaLogic and WebLogic professional service teams are first indicators supporting my prediction. Will other BEA"s SOA products included in Fusion Middleware keeping only the brand name and few components from the original Oracle infrastructure?

Comments

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...