BPEL Routing Slip Extensibility for Location-Transparent Business Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
BPEL lacks constructs and libraries to implement complex business logic, relying on externally defined and managed Web Service implementations, which limits its ability to execute distributed processes and competes for resources with the BPEL processing engine.
Innovation Solution
A system and method for orchestrating Web Services using BPEL that achieves location transparency and routing slip extensibility by directing messages to appropriate locations based on addresses, allowing extensions to be executed without modification to the BPEL process or engine, and enabling dynamic distribution and load-balancing of extension elements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom code extensions are co-located on the same physical computer as the BPEL processing engine, then complex business logic can be implemented, but resource competition occurs between extensions and the BPEL engine
Solution Approach 1:
The system segments the BPEL execution environment by separating extension elements from the main BPEL processing engine. Extensions are deployed as independent Web Services that can be executed remotely, while the BPEL engine maintains orchestration capability. This segmentation eliminates resource competition while preserving business logic implementation through the use of separate deployment units that communicate via standardized Web Service protocols.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of Web Service infrastructure and routing slip technology. This intermediary layer enables communication between the BPEL engine and extension elements without requiring direct co-location. The Web Service protocol acts as a mediator that transfers control and data between the orchestrator and extended functionality, eliminating the need for shared physical resources.
2Ease of operation
If BPEL processes are centralized on a single location, then orchestration control is simplified, but distribution across multiple computer systems is extremely difficult
Solution Approach 1:
The patent adds a new dimension to BPEL execution by introducing location transparency through Web Service deployment. Instead of distributing BPEL processes horizontally across multiple engines, the solution allows vertical separation where the BPEL engine remains centralized for orchestration control while extension elements are distributed across multiple Web Service endpoints. This dimensional approach maintains operational simplicity while enabling geographic and architectural distribution.
Solution Approach 2:
The system achieves distribution capability through the universal Web Service interface. The BPEL engine maintains its centralized orchestration role while invoking extension elements that can be deployed anywhere in the Web Service ecosystem. This multi-functional approach allows the same BPEL process to leverage extensions from different locations, vendors, and platforms without modifying the orchestration logic, thus enabling distribution while preserving ease of operation.
3Adaptability or versatility
If extension elements are moved from computer to computer dynamically, then location transparency is achieved, but the BPEL process must be modified to accommodate location changes
Solution Approach 1:
The patent employs copying mechanisms through Web Service deployment descriptors and routing slip configurations. Instead of modifying the BPEL process when extensions move locations, the system updates the service endpoint registry or routing configuration. The BPEL engine continues to invoke extensions using the same process definition, while the underlying deployment infrastructure handles location changes through copied or replicated service binding information.
Solution Approach 2:
The routing slip infrastructure acts as an intermediary that decouples the BPEL process from extension locations. When extensions move dynamically, only the routing configuration needs updating, not the BPEL process itself. This intermediary layer absorbs the complexity of location management, allowing the BPEL process to remain static while achieving location transparency through the mediator's ability to resolve dynamic endpoints.
Data Source
AI summary
In order to achieve location transparency and routing slip extensibility, a system and a method for orchestrating a web service using Business Process Execution Language are disclosed. The method includes: receiving a message, wherein the message comprises an address identifying an extension element; determining, from the address, a location of the extension element identified by the address; responsive to determining the location of the extension element, directing the message to an appropriate location; and storing the message in a computer readable storage medium.