Auto-Generating SOA Artifacts for Asynchronous Enterprise Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in provisioning asynchronous interaction with enterprise suites that have synchronous integration points, requiring additional layers for interaction, which is complex and resource-intensive, especially when manual development of SOA artifacts is necessary.
Innovation Solution
A digital processing system auto-generates Service-Oriented Architecture (SOA) artifacts to enable asynchronous interaction with synchronous integration points, allowing external systems to interact asynchronously with enterprise suites, simplifying the provisioning process by deploying these artifacts in an SOA server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If additional layers are provided between synchronous integration points and external systems to enable asynchronous interaction, then asynchronous interaction capability is improved, but system complexity increases
Solution Approach 1:
An SOA server is introduced as an intermediary component between external systems and synchronous integration points. The server includes an artifact repository for storing SOA artifacts and a processor for automatically generating and managing these artifacts. This mediator enables asynchronous interaction without requiring complex custom development layers, as the SOA server handles the transformation and coordination automatically.
Solution Approach 2:
The system implements self-service through automatic generation of SOA artifacts. The processor automatically creates the necessary service-oriented architecture artifacts based on the interaction requirements, eliminating the need for manual development. This self-configuration capability reduces complexity by allowing the system to adapt itself rather than requiring complex manual provisioning.
2Adaptability or versatility
If manual development of SOA artifacts is performed to enable asynchronous interaction, then interaction functionality is improved, but operational effort increases
Solution Approach 1:
The processor automatically generates SOA artifacts based on the interaction requirements between external systems and integration points. This self-service mechanism eliminates manual artifact development, reducing operational effort while maintaining full asynchronous interaction functionality. The system configures itself by automatically creating the necessary service definitions, mappings, and interaction protocols.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the artifact repository with templates and structures for SOA artifacts. When asynchronous interaction is required, the processor can quickly generate appropriate artifacts from these pre-prepared structures, significantly reducing the operational effort compared to creating artifacts from scratch each time.
3Adaptability or versatility
If additional provisioning layers are implemented for asynchronous access, then interaction flexibility is improved, but resource consumption increases
Solution Approach 1:
The SOA server is designed as a universal platform that handles multiple types of interactions (synchronous and asynchronous) and supports various integration points through a single artifact repository and processor system. This multi-functionality reduces resource consumption compared to implementing separate specialized systems for different interaction types, as the same infrastructure serves multiple purposes.
Data Source
AI summary
An aspect of the present invention simplifies provisioning of asynchronous interaction with enterprise suites having synchronous integration points. In one embodiment, a digital processing system receives, from a user, data indicating that asynchronous interaction is required for a synchronous integration point of an enterprise suite, and in response, auto-generates a set of service oriented architecture (SOA) artifacts designed to synchronously invoke the synchronous integration point and provide asynchronous interaction with external systems. The auto-generated SOA artifacts are then deployed in SOA server, whereby external systems can interact asynchronously to access a functionality provided by the synchronous integration point. According to another aspect, the system, also receives from the user, a second data indicating a set of policies to be applied, and in response, auto-generates the set of SOA artifacts to implement the set of policies during asynchronous interaction with external systems.