Petals ESB v3.0 is finally out (two years after the v2.0 release), there are many changes in this version but here are the main ones :
Petals ESB 3.0, includes a lot of improvements for users, as well as optimisations, and nice new features :
– Dynamic configuration, and hot-deployment of new nodes
– Redesigned webconsole for administration, and deleted statistics monitoring (based on OW2-OpenSUIT)
– SCA support: SCA engine (OW2-FraSCAti), and SCA designer (Eclipse)
– BPEL support: BPEL engine, and BPEL designer (Eclipse), with validation (based on a new BPEL engine!)
– WS Notification and WS-BorkeredNotification support (EDA)
– more and more things…
Integration with new Petals Camelia softwares :
– Petals Studio: Complete Eclipse development environment, for Petals ESB
– Petals Master: SOA Governance (OW2-Dragon)
– Petals View: Business flow monitoring based on Petals EDA feature (based on OW2-OpenSUIT)
The main advantage of SCA over other approaches, like BPEL or EIP, is that you can define the composition with Java instead of XML. The SCA composite defines services, which are exposed in the bus. It also defines references, which point to services that might be called or used by the composite at runtime. These references define possible dependencies. And eventually, your composite embeds a Java implementation which allows you to manipulate the references as simple Java objects. This makes the user job easier, in particular to call a service operation or test conditions on a service call result.
For more details on SCA, on tools and more, take a look at the links below :
SCA is a specification defined by the Open SOA consortium.
SCA is in standardization process by the OASIS Consortium.
OW2 FraSCAti is the SCA platform the SCA service engine is based on.
Eclipse SCA Tools exist and are hosted by the SOA Tools Platform project. They can be used with the SCA service engine.
PEtALS Eclipse tools complete the STP SCA tools for PEtALS specifics (PEtALS Maven plug-in support, packaging for PEtALS…).