Collaxa within two months plans to release a Web services deployment tool that utilizes the Business Process Execution Language for Web Services (BPEL4WS) specification backed by IBM, Microsoft, and BEA Systems.
Collaxa Orchestration Server 2.0, which is now available in an evaluation release, is intended to enable developers to publish asynchronous and synchronous Web services and utilize them for transactional business flows, according to Redwood Shores, Calif.-based Collaxa. A console based on BPEL4WS provides for reporting, auditing, and debugging capabilities. The product offers the industry's first implementation of a BPEL4WS-based orchestration server, said Doron Sherman, Collaxa CTO.
The primary intention of Orchestration Server is to develop reliable business flows using XML, Web services, and J2EE,
"Basically, an orchestration server coordinates Web services," said
The product backs two proposed standards from IBM, Microsoft, and BEA: BPEL4WS and WS-Transaction. By supporting these, Collaxa can provide a standard way for developing business flows without having to utilize proprietary EAI mechanisms,
BPEL4WS competes with a Sun-proposed specification, Web Services Choreography Interface (WSCI), although
Collaxa anticipates BPEL4WS will become an industry standard,
While WSCI has been submitted to the World Wide Web Consortium (W3C) for its consideration as an industry standard, BPEL4WS has yet to be submitted to such an organization.
Version 2.0 of Orchestration Server supports Web services deployments on the BEA WebLogic Server, JBoss, IBM WebSphere, and Sun ONE (Open Net Environment) application servers. JBoss is bundled with the evaluation product.
Additional features in Version 2.0 include the ability to monitor execution of business flows via a visual audit trail, a BPEL4WS debugger, support for e-mailing of Microsoft Excel files, the ability to send and receive messages through JMS (Java Message Service) queues, and topics and manipulation of XML documents via XPath.