BEA and Oracle's Middleware Strategy Briefing

Marco Gralike 3

I just got a hint from my colleague Lucas, via the AMIS internal channels (aka "sharepoint"), that there will be a strategy briefing via webcast about "Oracle Fusion Middleware and the important role BEA’s products will play". I think this is worthwhile listening / viewing. I installed this weekend the BEA WebLogic Server 10.3 Technical Preview to get myself acquinted again with BEA’s products. BEA WebLogic is an Application Server that I once mastered while supporting a PeopleSoft environment.  I always enjoyed working with the BEA WebLogic Server because it had a clear interface and (in my time) was a stable environment in conjunction with the PeopleSoft structures.

I have a guess that the BEA WebLogic Server will be indeed a important asset in Oracle’s Product line. I am curious what the future of OC4J will be in Oracle’s strategy, how BEA AquaLogic will fit in, ESB or EBA BPM Studio.

Anyway have a go at 18:00 CET (9:00 a.m. PT / 12:00 noon ET) via the following URL: 

BEA Welcome and Oracle’s Middleware Strategy Briefing

Don’t miss the special Juli 1 Webcast featuring Oracle President Charles Philips and Senior Vice President Thomas Kurian (SVP Fusion Middleware).

Join Oracle executives Charles Phillips, President, and Thomas Kurian, Senior Vice President, for an informative briefing that will explore how the addition of BEA products to Oracle Fusion Middleware creates a best-in-class combination, advances a common vision, and reinforces Oracle’s middleware strategy.


3 thoughts on “BEA and Oracle's Middleware Strategy Briefing

  1. Thanks Simon. Your blog entry was informative as well, and also the Oracle group thread. I’ve used EJB3 in JDev declaratively, so to me JDev and declarative includes much of what happens there. ADF seemed mentioned mostly in the context of Faces, which is an implementation of JSF of course. I think ADF/BC brings a lot of power to the table, but the drawback to it is it’s one of the few non-standard major architectural pieces in the stack left. This makes sense to have when you consider the closer to the database the tech goes, the more Oracle-specific things are in an Oracle world, and the more value being that way. But that will be part of the challenge in winning over many of the BEA Java diehards. I’m probably reading too much in, but seems like a good compromise if they were to bring in the generation to EJB3 from BC to ADF development proper and perhaps merge the two technologies to keep the power of BC along with the standard of EJB3. I don’t know enough about the underlying architectural challenges to take it further than a hunch, but sure seemed they were giving the nod of recognition to EJB, or maybe just throwing a bone 😉 again. The rest of the presentation was very deliberate and clear in it’s details.

  2. @Robert: Thomas Kurian did mention “declarative development” once or twice, especially in the context of making business developers more productive. I think ADF was on a slide as one of 3 strategic products within development tools (along with JDev and Eclipse Pack) – I interpreted that as meaning ADF Faces and ADF BC.

  3. Hi, this was very interesting indeed. Most makes a lot of sense. A couple curiosities for me were that EJB was mentioned twice, yet ADF/BC had no mention. This makes sense industry-wise and in context with BEA, but after attending Shaun O’Brien’s session at ODTUG where it was let on that they were generating EJBs from ADF/BC for BPEL consumption, and now today, I wonder if ADF/BC will continue to be considered the target Fusion model layer technology. Being a Portal 10.1.4 user, I also took note of the continuation of WebCenter, even more brazenly, as the replacement platform for portals, only now they are porting the suite to WebLogic.

Comments are closed.

Next Post

Agile software development, the principles. Principle 7: Working software is the primary measure of progress.

Facebook0TwitterLinkedin This is the seventh of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto ( and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of […]