Browse Prior Art Database

Local Option Communication

IP.com Disclosure Number: IPCOM000015853D
Original Publication Date: 2002-Aug-24
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Abstract

Local Option Communication

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 91% of the total text.

Page 1 of 2

Local Option Communication

Local Option Communication

Disclosed is a design for a program which provides the customer with an architecture in which the access to IMS transactions and data bases is protected inside the customer's TCP/IP firewall. The only access to the IMS transactions and data bases is through a Web application server such as WebSphere where access would be controlled by the WebSphere Authentication service. The advantages of this approach are two-fold. First, IMS is isolated from TCP/IP access; access to IMS is only allowed from inside the firewall. Second, the performance degradation of going through a TCP/IP firewall for communication between address spaces in the same MVS image is eliminated.

The design utilizes a non-TCP/IP connection interface between IMS Connector for Java executing in the WebSphere address space and IMS Connect executing in its own separate address which uses a WebSphere architecture based MVS Program Call (identified by the MVS PC link in the figure below) for communication between the WebSphere and IMS Connect address spaces. The dashed line in the figure represents the original implementation of IMS Connector for Java in which communication between IMS Connector for Java and IMS Connect is accomplished using TCP/IP. Since most customers route all TCP/IP communications through a firewall, it is easy to see this implementation involves an additional trip through the firewall in contrast to the direct Program Call link be...