BEA Systems at the BEAWorld 2006 San Francisco conference this week stressed SOA as a core technology and unveiled its SOA 360 platform. Comprising multiple BEA products, some of which have yet to be released, the ambitious SOA 360 strategy features multiple role-based offerings for IT as well as a services architecture and modularization of existing BEA products. InfoWorld Editor at Large Paul Krill spoke with Rob Levy, BEA executive vice president and chief technology officer, at the conference about SOA 360 and BEA's growth as a middleware company.
InfoWorld: Would you explain the concepts of SOA 360 WorkSpace 360, WorkSpace Central and microService Architecture?
Levy: Sure. Let’s start with the highest level, which is SOA 360. SOA 360 is a governing approach to modeling, creating, developing and deploying a full lifecycle SOA application. It is a unifying methodology between all the product lines we have, as well as connecting it to other products.… In that respect, think of it as a governing approach that is supported by a set of products, by a common architecture and by a set of standards that govern the lifecycle. So if you drop [down] from that, either to the bottom or the top, depending on how you want to look at that, on the bottom you’re going to need a common architecture that allows you to build those SOA applications across this lifecycle. [This is] mSA, microService Architecture.… Think of mSA as using the SOA practices to componentize our platform and our product line. You take the basic services that exist inside each one of our product lines and you componentize them so they can be reused with all of our products, not just in single products.... To do the SOA lifecycle correctly, the common architecture will also have to have a common repository, [a] catalog of services, where basically each one of the roles contributes a different portion of the knowledge and expertise that is necessary to move forward in the SOA lifecycle. Now let’s leave that for a second, and again I’ll jump back out now this time to the roles. It’s a multiple view of the same problem, it’s all starting from the SOA lifecycle domain. Take WorkSpace 360, and WorkSpace 360 is the tool, or the set of tools, that allow each one of the roles to participate in the SOA lifecycle. The business analysts, the LOB [line of business], have a very specific set of things that they are concerned about. From the application -- from the business process to maybe ROI (return on investment) metrics that they need to measure to the definition of the business requirements. All of these artifacts need to be stored somewhere, and they’ll now be stored in the central repository.
InfoWorld: Which is what product?
Sign up to receive Platforms Resource Alerts
Recommend This
