More about Parasoft BPEL Maestro...

Both efficiency considerations and changing market conditions are driving the need for business
process integration. Requirements of flexibility, interoperability, and cost-effectiveness point to
service-oriented architectures based on Web service standards. These services need to be
orchestrated to achieve business goals and BPEL provides the standard for this orchestration. BPEL
processes need to be executed by a runtime engine that supports a number of requirements, including
native support for Web service standards as well as asynchronous messaging, process persistence,
and transactional models consistent with long-term processes.

Parasoft BPEL Maestro satisfies these requirements by providing a unique set of technologies, and
thus offers companies unprecedented flexibility when it comes to driving Web Services oriented
business processes. Parasoft BPEL Maestro consists of a development toolkit and a BPEL engine.

Toolkit

The toolkit, which currently operates as a plugin within the Eclipse framework, facilitates the
development of pure BPEL processes. It is extremely BPEL oriented and BPEL aware.

The toolkit's development environment offers three primary views: UML, DOM (tree view) and
Serialized XML. The toolkit offers BPEL debugging with the capability to remotely debug BPEL
processes, a feature that can also be applied during runtime.

The toolkit's management capabilities include the ability to deploy and undeploy servers and engines.
The environment allows for centralized management and monitoring of the servers and distributed
engines. The next version of BPEL Maestro will continue to evolve these capabilities.

Engine

The Parasoft BPEL Maestro Engine executes BPEL processes. Parasoft took a pure BPEL approach
for BPEL execution. The engine contains no Java extensions or .NET extensions; execution is based
on BPEL and WSDL, with the WSDL approach to WS.

The deployable artifacts from the engine include BPEL processes, WSDLs, and schemas. Meta
information is available to employ persistent processes in conjunction with a relational database. The
models of invocation (messaging models) include traditional HTTP/HTTP, local Java, JMS, EJB, JCA,
asynchronous and synchronous. Transactions and business activities are both supported at the
atomic level.