Dynamic Service Binding in Cross-Enterprise BPM
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business process management systems, such as BPEL4WS, are limited to static deployment of business processes and do not allow for dynamic specification of new principal services, which hinders adaptability and flexibility in responding to timely business insights and changes in on-demand computing environments.
Innovation Solution
A system and method for dynamically binding principal services to activities in a cross-enterprise business process management system, utilizing a business process specification document processing engine, deployment service, and link base authority to generate and deploy partner link instances, allowing for dynamic changes to endpoint references and notification of partner link instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If static deployment of business processes is used, then system stability and simplicity are improved, but adaptability and flexibility to respond to business changes deteriorate
Solution Approach 1:
The patent implements dynamic service binding by allowing the endpoint reference of principal services to be changed at runtime through partner link instances. The system transitions from static service bindings defined at deployment time to dynamic bindings that can be modified without redeploying the business process, thus achieving both stability and adaptability
Solution Approach 2:
The patent introduces partner link instances as intermediary components between the business process and principal services. These instances act as proxies that can be dynamically reconfigured to point to different service endpoints, enabling flexible service substitution without affecting the core business process logic
2Adaptability or versatility
If dynamic service substitution is implemented, then adaptability and responsiveness to business insights are improved, but system complexity and deployment overhead increase
Solution Approach 1:
The patent segments the service binding functionality into separate partner link instances that can be independently configured and managed. This segmentation allows dynamic service substitution without requiring changes to the overall business process structure, thereby limiting the increase in system complexity to isolated, manageable components
Solution Approach 2:
The patent uses partner link instances as proxy copies of the actual principal services. These instances replicate the service interface and can be dynamically reconfigured to point to different underlying services, enabling service substitution without directly modifying the business process configuration and thus controlling complexity
3Adaptability or versatility
If business process configuration is unloaded for changes, then service substitution capability is improved, but processing time and operational continuity deteriorate
Solution Approach 1:
The patent performs preliminary actions by pre-configuring partner link instances with the capability to bind to different principal services. The dynamic binding mechanism is prepared in advance through the deployment service, which creates the infrastructure for service substitution without requiring the business process configuration to be unloaded, thus maintaining operational continuity and reducing time loss
Data Source
AI summary
The present invention is a method, system and apparatus for dynamically binding principal services to activities in a business process in a cross-enterprise business process management system. In a preferred aspect of the invention, the system can include a business process specification document processing engine configured to process business process specification documents in which each of the documents defines a business process. A deployment service can be coupled to the engine and programmed to generate and deploy partner link instances for corresponding partner links specified in the documents. Finally, a link base authority can be configured to notify each partner link instance when an endpoint reference to a principal service has changed. Notably, the business process specification documents can include BPEL documents. As such, the business process specification document processing engine can include a BPEL4WS run-time engine.