Browse Prior Art Database

Step out to IMS Screen through Service

IP.com Disclosure Number: IPCOM000244474D
Publication Date: 2015-Dec-15
Document File: 4 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method of integrating the user interface of a web portal with an IMS online screen to enable user navigation between the two systems to complete a business process or a transaction.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 31% of the total text.

Page 01 of 4

Step out to IMS Screen through Service Background

In today's complex IT landscape, information is present and processed by systems that span across different technologies and platforms. Most often existing Mainframe legacy systems continue to provide business value and organizations try to reuse the existing systems and integrate them with newer systems. This is usually accomplished by exposing the legacy screens like IMS transactions as services using different methods such as MQ, OTMA (Open Transaction Manager Access), Web etc., which can be consumed by other systems. In most cases, the front end systems is interested in consuming only the business logic in the legacy system and hence the actual green screen does not come into the picture in these type of integrations. However, at times there is a need to integrate a front end web interface with a legacy system and reuse the legacy screens/user interfaces as-is when the legacy screens contain a combination of complex user interactions and business rules. In addition there are other reasons to enable users to step out to a green screen from a Web portal to complete a transaction, such as;


1. Transaction processing that require multiple steps which involve multiple interactions with the system through question & answers (Q&A) and based on the responses a business rule based back-end system would determine the next steps. If such Q&A based back-end systems are already built using Mainframe green screens it would be expensive and time consuming to rebuild it on a web portal. Moreover in such cases multiple interactions between the front end and back-end rule system would increase response times and it would make sense to continue using the green screens for processing.


2. Certain transactions like customer service would involve initiating a customer call which would need to be started from a web portal which would provide the capability to initiate an outbound call. Then later on, the process would require completing the transaction on an existing mainframe green screen application.


3. An organization might have some existing capabilities built on a set of green screens which might be used by a large group of users and as part of a new business need would require the process to be available to another business area which uses web portals. In such a scenario, it would be easier for the organization to let the new group of users step out to the IMS screens from the web portal to complete the required transactions rather than create and maintain two different systems.


4. In case of conversational IMS transactions, multiple conversations are required to complete a transaction. If these type of IMS screens were to be exposed as services to be consumed by a front end web application, then multiple requests and responses would be required between the two systems which would make the interface complex, having to deal with Commit and rollback scenarios in case of partial failures. Letting t...