return on investment (ROI)
Web services inspection language (WSIL)
Universal description, discover, and integration (UDDI)
usiness process execution language (BPEL)
was submitted to the Organization for the Advancement of Structured Information Standards (OASIS) in March 2003
(predecessor languages of XLANG and WSFL)
Web services/WSDL as component model
XML as data model (data loose-coupling)
Synchronous and asynchronous message exchange patterns
Deterministic and nondeterministic flow coordination
Hierarchical exception management
Long-running unit of work/compensation
web services description language (WSDL)
extensible markup language (XML)
simple object access protocol (SOAP)
Making Web services work is a two-step process:
Publish the services.
Publishing a service involves taking a function within an existing application or system and making it available in a standard way.
Compose, or orchestrate, the services into business flows.
Orchestration involves composing multiple services into an end-to-end business process.
synchronous and asynchronous services
dehydration capability that enables the states of long-running flows to be automatically maintained in a database, thus enabling clustering for both fail over and scalability
Oracle BPEL Process Manager provides a user-friendly and reliable solution for designing, deploying, and managing BPEL business processes.
bindings to hundreds of legacy systems through Java connector architecture (JCA) adapters
Bindings are available for JMS, e-mail, JCA, HTTP GET, HTTP POST, and many other protocols enabling simple connectivity to hundreds of back-end systems.