Why Scarbo ?

Scarbo aims to prove, using SCA, that Open Source, BPM and SOA are a match in heaven that solves traditional BPM pitfalls, and brings together orchestration and workflow paradigms.

BPM Issues

Historically, BPM promised to the entreprise to bring improved productivity, improved business monitoring and ROI metrics, and business flexibility - by adapting to changes in business practices. However, its concrete implementations have been at first hardly quick and easy successes, mainly because they have been hampered by two rampant problems :
  • the BPM Babel Tower issue : (too) many incompatible paradigms, standards, implementations and tooling drives ease of integration down, whereas BPM should foster it. Proprietary vendors didn't have any incentive in solving this issue, because it kept competition out. The answer is focus on openness, standards, integration specifications and interoperability tools, which the JWT community aims to provide.
  • evolution of the entreprise Information System : unmanaged System Information integration meant that whenever a BPM-integrated business application was deployed in a new version (which could be as simple as removing a column in a database), impacted BPM processes were in risk of not working anymore, with losses in business as a consequence. Proprietary vendors had less of an incentive in solving it, because it brought them a steady stream of incoming business, and anyway it just was not their job to do. The answer is loosely coupled integration and information system governance, which SOA provides.

SOA issues

  • SOA and services are too complex and technical for the business user to understand it. The business user needs rather a simple way of depicting its needs (that's business processes), that can later be implemented on top of an SOA architecture.
  • standing on its own, SOA lacks value-added features that are directly useful to the business user when using services in business processes (sending an email, waiting for another operation...). BPM is the swiss knife that SOA needs.

Scarbo's answer

As an Open Source SOA service platform, OW2 FraSCAti brings meaningful benefits to the" JWT for SOA" vision :
  • as an implementation of the SCA specifications, it is based on acknowledged standards, as well as being an heterogeneous, non intrusive answer to SOA
  • thanks to its SCA-provided unified service model, integrating FraSCAti once in a business process engine allows it to call services using any kind of supported protocols (Java, Web Services, RMI...)
  • being built on top of the OW2 Fractal component model, the service component model is at the heart of its architecture, making it flexible and extensible, IoC and AOP benefits being at the door among others
  • its efficiency relies on renowned, robust Open Source components, like Apache CXF.
Scarbo implements a unique integration of SCA service orchestration within workflows (business processes involving human operators). This feature relies on JWT's Task Engine Framework and APIs, which are designed to integrate a Java service platform within a Java business process engine, as easily and as compliant to standards as it can be. Scarbo builds on it to achieve integration of the OW2 FraSCAti service platform with Bonita 4 workflow engine.