New Parasoft BPEL Maestro simplifies Web service
orchestration and helps your company achieve the
vision of SOA.
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 servic
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 1.5 is an integration platform
satisfying these requirements, offering companies
unprecedented flexibility in Web Service
orchestration. Parasoft BPEL Maestro 1.5 consists of a
toolkit and a BPEL runtime engine.
Toolkit
The toolkit's development environment offers three
views of a BPEL process: a high level view based on a
UML activity diagram, a mid-level tree view based on
the DOM, and a low-level syntax-highlighted text
editor.
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.
next version of BPEL Maestro will continue to evolve
these capabilities.
Runtime Engine
The Parasoft BPEL Maestro Engine executes BPEL
processes. Parasoft took a pure BPEL approach for BPEL
execution. Services are accessed through their WSDL
definitions for a clean, standards-based approach
integration.
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
SOAP/HTTP, local Java, JMS, EJB, JCA, asynchronous
synchronous. The transactional model supports both
short-term atomic transactions and long-running
business activities with compensations.
Download File Size:107.08 MB
|
