IMS SOAP Gateway Deployment Utility for Legacy Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enabling legacy system applications, such as IBM IMS, to be accessed as web services using SOAP is complex and error-prone, requiring a simplified process to facilitate interoperability and reuse of existing business logic.
Innovation Solution
A deployment utility that generates and deploys web services to an IMS SOAP gateway, utilizing a web service description language file, connection bundle, and correlator file to enable SOAP-based communication between clients and legacy applications, simplifying the integration process by providing a user-friendly interface and automating the generation of necessary artifacts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a legacy system application is enabled to be accessed as a web service using SOAP through manual configuration, then the application can achieve interoperability with distributed systems, but the process becomes complex and error-prone
Solution Approach 1:
The patent introduces a gateway server as an intermediary component that mediates between the legacy system application and SOAP-based web services. The gateway server handles the complex configuration and protocol translation, shielding users from complexity while enabling interoperability. The gateway maintains connection bundles, correlator files, and interface modules that facilitate seamless communication without requiring direct complex configuration in the legacy application.
Solution Approach 2:
The deployment utility enables self-service by automatically generating and deploying web service configurations based on user input. The system performs self-configuration through automated generation of WSDL files, correlator files, and connection bundles, eliminating manual complex setup while maintaining adaptability for interoperability.
2Ease of operation
If manual configuration is used to enable web service access, then flexibility in customization is achieved, but the process becomes time-consuming and error-prone
Solution Approach 1:
The patent implements preliminary action through the deployment utility that pre-generates all necessary configuration files (WSDL, correlator files, connection bundles) before actual web service deployment. This preliminary automated configuration reduces deployment time and eliminates manual errors while maintaining ease of operation through a streamlined process.
Solution Approach 2:
The deployment utility performs self-service by automatically generating web service artifacts and configurations without requiring manual intervention. The system takes user input and autonomously produces deployment-ready configurations, significantly reducing deployment time while improving ease of operation through automation.
3Adaptability or versatility
If existing legacy application code is modified to enable web service access, then direct integration capability is improved, but the risk of introducing errors and the cost of modification increase
Solution Approach 1:
The patent applies segmentation by separating the web service integration functionality from the legacy application code. The gateway server and its associated components (connection bundles, correlator files, interface modules) handle integration logic independently, allowing the legacy application to remain unchanged. This segmentation improves integration capability while maintaining reliability by avoiding modifications to proven legacy code.
Solution Approach 2:
The gateway server acts as an intermediary that enables integration capability without modifying legacy application code. It translates between legacy system protocols and SOAP web service protocols, providing direct integration capability while eliminating the error risk associated with modifying legacy code. The intermediary handles all adaptation logic externally.
Data Source
AI summary
Various embodiments of a method, system and computer program product enable an application to be accessed as a web service. In response to a command, a web service is deployed to a gateway server, and a connection bundle and a correlator file are provided such that they are accessible to the gateway server. The web service was generated based on a web service description language file that is based on an input-output message description of the application, and is accessible to a client using a SOAP message. The gateway server sends a request message to the application based on the SOAP message in accordance with the web service, and receives a reply message from the application. The connection bundle comprises connection information to interface with the application. The correlator file comprises a name of an interface module associated with the application and the name of the connection bundle.