Index Changes

Difference between version and version     

Back to IMS, or IMS Info


At line 1 changed 2 lines.
!!!IMS
----
!!!IMS BC
!!About Information Management System (IMS)
At line 4 removed 2 lines.
!!General Description
At line 8 changed 4 lines.
!!External Connectivity - background
!!IBM Currently supports the following versions of CICS TS for z/OS:
!IBM Currently supports the following versions of CICS TS for z/OS:
At line 16 changed 5 lines.
!! IMS web sites:
* [IMS home page|http://www-306.ibm.com/software/data/ims/]
* [IMS Connect|http://www-306.ibm.com/software/data/ims/connect/index.html]
* [IMS MFS Web Support|http://www-306.ibm.com/software/data/ims/toolkit/mfswebsupport/]
* [IMS SOAP Gateway|http://www-306.ibm.com/software/data/ims/soap/]
!! Overview
The IMS BC enables connection to IBM's IMS/TM mainframe applications through IBM's IMS Connect. The implementation of the IMS BC is in accordance with IBM's IMS Connect Guide and Reference. These documents describe the OTMA protocol and contain important prerequisite information for the configuration IMS Connect on the mainframe. The IMS BC supports the following external IMS applications: - IMS Version 9. The IMS BC requires IMS Connect to interface with IMS. IMS Connect is a companion product to IMS, available from IBM. Software Requirements for IMS Connect: - IMS Connect, Version9.1 and
Resource Access Control Facility (RACF) or an equivalent product.
At line 22 changed 3 lines.
The IMS BC supports the following external IMS
applications:
- IMS Version 9.
Note: This document uses the term RACF when referring to RACF (Resource Access Control Facility) or equivalent products.
\\
\\
!! IMS BC Architecture
The following figure depicts the architecture of IMS Binding Component
\\
[{Image src='arch.jpeg' align='left'}]
\\
!!Development Information
* [Features|IMS BC Features]
At line 26 changed 3 lines.
The IMS BC requires IMS Connect to interface with IMS.
IMS Connect is a companion product to IMS, available from
IBM.
!!Using the IMS Binding Component
*[IMS BC Extensibility Elements]
At line 30 changed 45 lines.
Software Requirements for IMS Connect:
- IMS Connect, Version9.1.
- Resource Access Control Facility (RACF) or an equivalent
product.
Note: This document uses the term RACF when referring to
RACF (Resource Access Control Facility) or equivalent
products.
!![IMS Requirements and Use Cases]
!!CAPS 5.0 Solution
The CAPS 5.0 IMS eway provides access to the Input and Output Descriptors (MID/MOD) of the IMS applications without requiring changes to the application. By capturing the field contents before screen formatting, the eWay is not affected by cosmetic changes to the application’s screen design.
The eWay includes the IMS Message Format Service (MFS) Wizard conversion utility to facilitate the creation of input and output Object Type Definitions (OTDs) from IMSMFS files.
The implementation of the IMS eWay is in accordance with IBM’s IMS Connect Guide
and Reference. These documents describe the OTMA protocol and contain important
prerequisite information for the configuration IMS Connect on the mainframe.
A sample project for the IMS eWay is included on the installation CD-ROM which
demonstrates how a non-conversational scenario (simple send/response) is managed.
!!CAPS 6.0 Design - Binding Component Option
The IMS BC enables connection to IBM's IMS/TM mainframe applications through IBM's IMS Connect.
The IMS BC provides access to the Input and Output Descriptors (MID/MOD) of the IMS applications without requiring changes to the application.
By capturing the field contents before screen formatting, the eWay is not affected by cosmetic changes to the application's screen design.
The IMS BC includes the IMS Message Format Service (MFS) Wizard conversion utility to facilitate the creation of input and output
WSDLs from IMS MFS files.
The implementation of the IMS BC is in accordance with IBM's IMS Connect Guide and Reference.
These documents describe the OTMA protocol and contain important prerequisite information for the configuration IMS Connect on the mainframe.
The IMS BC will implement wire protocol using TCP/IP sockets
It will Use Apache MINA Java NIO framework.
!!CAPS 6.0 Design - HTTP/SOAP Option
Alternatively we can use the IBM IMS SOAP Gateway which is a Web service solution that integrates IMS assets in an SOA. The IMS SOAP Gateway enables IMS applications to inter-operate outside of the IMS environment through SOAP to provide and request services thereby enabling IMS applications to be invoked as Web services. This requires IMS Connect. See [http://alaska.stc.com:10000/alaska/attach/CICSBC/Mainframe_SOA_redp4152.pdf] for details. We will experiment with this approach as a first fast track solution using the httpSoap BC.
“IMS SOAP Gateway Version 9.2 is now available at no additional charge to all IMS Version 9 customers.”
[IMS SOAP Gateway Version 9.2|http://www-306.ibm.com/software/data/ims/soap]
!!Milestones
!! IMS Binding Component Artifacts/Demos
At line 77 removed 9 lines.
!!Future enhancements and features
* Coming soon
!!Using the IMS Binding Component
* Coming soon
!! IMS Binding Component Artifacts
* IMS Design Document
At line 87 changed 1 line.
* Coming soon
* [IMS home page|http://www-306.ibm.com/software/data/ims/]
* [IMS Connect|http://www-306.ibm.com/software/data/ims/connect/index.html]
* [IMS MFS Web Support|http://www-306.ibm.com/software/data/ims/toolkit/mfswebsupport/]
* [IMS SOAP Gateway|http://www-306.ibm.com/software/data/ims/soap/]
At line 90 changed 2 lines.
*__Manager:__ Fred Aabedi
*__Main Developer:__
*__ Venkat Srinivasan
*__Gautami Kondapaneni
At line 54 added 1 line.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-7) was last changed on 08-May-07 04:48 AM, -0700 by GautamiKondapaneni