140 likes | 461 Views
BPEL. Business Process Execution Language. BPEL Design goals. XML-based language Interacts through WSDL only Build on Web services standards. Pros & Cons. Pros Easy to implement communication with different web-services Execution as transactional state machine
E N D
BPEL Business Process Execution Language
BPEL Design goals • XML-based language • Interacts through WSDL only • Build on Web services standards
Pros & Cons • Pros • Easy to implement communication with different web-services • Execution as transactional state machine • Means of graphical representation • Cons • XML-based language, not support for all data structures • Hard to create levels of abstraction
What we’ve used • Eclipse Indigo • BPEL Visual Designer 0.5.0 • Apache ODE 1.3.5 • Apache Tomcat 6.0.35
What to try first • How to implement business logic • How to communicate with others • How to debug & test BPEL processes
Business Logic: Lessons • Convenient service invocation • Looks better than coding • (ONLY if you don’t look into XML) • …and for simple processes • Operating only with XML data is difficult • Available operators and functions are too limited
Communication: Lessons learned • RESTful BPEL is not implemented yet
Debugging & Testing • Playing with logging category
Debugging & Testing • ODE Management API (in DEMO) • Implemented as Web-service • http://localhost:8080/ode/processes/ProcessManagement?wsdl • http://localhost:8080/ode/processes/InstanceManagement?wsdl • Difficulties with java interaction • Couldn’t get debugging information