im02 - soa integration of ims assets - ibm · im02 - soa integration of ims assets 8

ITSO System z SOA Forum 2006

IM02 - SOA Integration of IMS Assets 1

© 2006 IBM Corporation

ITSO System z SOA Forum 2006Powering SOA with IBM Software on System z

IM02 – SOA Integration of IMS Assets

Hélène Lyon z/Middleware Technical SpecialistIBM South-Europe technical [email protected]


© 2006 IBM Corporation2

NoticesThis information was developed for products and services offered in the U.S.A.

Note to U.S. Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.





TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.

Other company, product, and service names may be trademarks or service marks of others.

Redbooks (logo)™IBM eServer™

ibm.com® z/OS® zSeries® AIX® ClearCase® Cloudscape™ CICS® CICSPlex® DB2 Connect™ DB2® DFS™ DRDA® Informix® IBM® IMS™ MQSeries® MVS™

Perform™ Rational® RACF® S/390® SAA® TME® VTAM® WebSphere®



AgendaCore Business Systems Integration

IMS Integration Strategy

Integration of First IMS Asset – IMS Transactions

Integration of Second IMS Asset – IMS Databases

Conclusion





Built to Support Evolution!

Business SystemsDatabases

Business Systems

Front End

Browser

Browser

Browser

Web Server

Appl. Server

ServerPersonal

Computer

"Dumb" Terminal

e-business

e-business with Core Business Systems

Client-Server

GUI Front-End

TerminalProcessing

Internet Enterprise Network Central Site

Web Server

Appl. Server

Personal Computer

Tim

e

App

licat

ion

Inve

stm

ent

Prot

ecti

on

CoreBusiness Systems

Applications



Business Drivers for ChangeChanges in business conditions– Direct customer and partner access

– New business products based on interactive IT

– Regulatory requirements

– Security

– Rapid change in business opportunity

Cost effectiveness– Application integration

– Development productivity

– Operational productivity

– Autonomic computing, per-use charge

Direct business benefit required for every IT investment– IT projects treated as capital investments

– Often require board approval

Distributed System zEnd Users

Online Ordering Customer Service

Partner Portal

Existing Applications and Data

Business Data





How are Core Business Systems changing?New interface requirements – From client/server to Web Services– Web browser access

– Integration and automation broker access

– Evolution of existing interfaces

Modernization to extend useful life of existing applications– Provide access

– Componentize for flexibility and reusabilityFind “business rules”Find separation points for UI logic, business

logic, data logic– Convert overnight batch into online batch

Reduction of maintenance and operations costs of existing applications– Tools support entire application (J2EE

and Core Business)

– Tools support entire lifecycle (analysis, design, test)

– Automate development processes with methodology and workflow

– Adopt modern development practices

– Broaden IT staff skills

Automated application operation and fault recovery

Preservation of current cost performance



Why Core Business Services ?Leverage existing assets– layer of abstraction that wraps existing assets

as services that provide business functions

Easier to integrate and manage complexity– integration point is the service specification and

not the implementation

More responsive and faster time-to-market– ability to compose new services out of existing

ones

Reduce cost and increase reuse– loosely coupled core business services can be

more easily used and combined based on business needs

Be ready for what lies ahead– better flexibility and responsiveness

CoreBusinessSystems

Object-oriented Systems

Service-Oriented Architecture

Business Process Architecture

Component-Based Architecture

Service ProviderSe

rvic

e C

onsu

mer





Why Core Business Services ? …

“The irony is that host applications are probably better suited for exposure as part of an SOA than many applications based on more modern 4GL object-oriented languages, said Phil Murphy, a principal analyst with consultancy Forrester Research, in an interview last year. “When folks wrote screen-based transactions many months ago, they wrote it at a business function viewpoint: I add a customer, I add an order for that customer, I check backlogs for that customer, etc. So in many respects, those CICS screens of 15 years ago are better suited to service orientation than a lot of the newer, distributed code that’s been written over the last several years, because of their affinity with a business function,” he argued, adding: “What did the object-oriented guys do? They took those screens and they broke them down into a thousand different objects.”

• from Enterprise Systems Journal, 7/26/2005http://esj.com/enterprise/article.aspx?EditorialsID=1457



IBM can help you build a service oriented architecture around your core z/OS applications

Choose SOA from IBM so that you can maximize re-use and avoid the cost and risk of new application development projects.

Analyze your applications to reveal reusable business servicesTrace usage patterns / service levels

Improve cooperation between your mainframe and client-server application teams using open integration technologies and common tools

Program z/OS applications (WAS, CICS, IMS and DB2) with the latest Eclipse-based development workbench

Automatically generate web-interfaces for core CICS and IMS applications

Create state-of-the art user interfaces without deep programming skills

Integrate multiple core and new applications within the same workspace

Compose business level web services from existing CICS and IMS transactions

Retain mainframe availability, scalability, security and recoverability

Connect applications right across your enterprise, across all platforms

Use the latest middleware and management tools to reduce operational overheads

Meet new requirements by leveraging your most valuable z/OS assetsRe-utilization practices





Flexible connectivity infrastructure for integrating applications and services to power your SOA

Color = Data type

Shape = Protocol

Enterprise Service Bus – the centerpiece of a SOAROUTINGROUTING messages between services

CONVERTINGCONVERTING transport protocols between requestor and service

TRANSFORMINGTRANSFORMING message format between requestor and service

HANDLINGHANDLING business events from disparate sources



Data Store

EJBServlet

JSPxml/http ERP

Core Business Applications

EJB

IBM WebSphere Application Server - the Core Engine

html/http

JCA Connectors

JDBC

JMS

The J2EE Application ServerProviding extended connectivity with various application servers and transactional capabilities …

Web Services platformWebSphere V6 & Services Oriented Architectureincluding

SOAP/JMSWS-Security / Kerberos, WS-Trust, WS-PolicyWS-Trans / WS-CoordinationWorkload managementAnd more

Web Services

Soap/wsdl/http

cei

EJBWeb

ServiceOther

Application

Business Integration (EAI, BPM, …)

* cei – common event infrastructure





IBM WebSphere - The foundation to implement various integration patterns

Data Store

Business Integration

(EAI, BPM …)

Web Services

xml/http

Soap/wsdl/http

jms/xml/wsdl

ERP

Core Apps

Other Application Server

Business Integration (EAI, BPM

…)

Other

Application

html/http

Connectors

Messaging

User to application

Application to Applicationsynchronous

Application to ApplicationAsynchronous



DELIVERYCHANNEL

WebSphere Application Server

INTERFACE B

usin

ess

Logi

c A D A P T E R

J2C

JDBC

JMS

CICS

DB2

IMS/DB

EIS / DATA

Presentation Layer Business Logic Layer Data Access Layer

CLIENTS

J2EE - 3-tiered Distributed Computing Architecture

IMS/TMIMSConnect

CTG

WMQ





J2EE Connector Architecture (JCA)Application Component (e.g EJB)

JCAResource Adapter

Enterprise Information System (e.g CICS, IMS)

System Contracts

Container-ComponentContract

Connection ManagementTransaction ManagementSecurity Management

Common Client Interface (CCI)

EIS SpecificInterface

Standard for connecting from J2EE Server to EIS

Resource adaptor is provided by EIS

J2EE Server(e.g WebSphere Application Server)



The SOA Reference Architecture

Business Innovation & Optimization Services

Dev

elop

men

tSe

rvic

es

Integrated environment for design

and creation of solution

assets

Manage and secure services,

applications &

resources

Facilitates better decision-making with real-time business information

IT S

ervi

ceM

anag

emen

t

Infrastructure ServicesOptimizes throughput,

availability and performance

ESBFacilitates communication between services

Partner Services Business App Services Access Services

Connect with trading partners

Build on a robust, scaleable, and secure services environment

Facilitates interactions with existing information and application assets

Interaction Services Process Services Information Services

Enables collaboration between people,

processes & information

Orchestrate and automate business

processes

Manages diverse data and content in a

unified manner

Leverage z/Middleware for maximum business flexibility.

App

s &

In

fo A

sset

s









Conclusion



IMS TM/DB Fulfilling Customer NeedsIMS Today

– Over 95% of Fortune 1000 Companies use IMS

– IMS Manages over 15 Million GBs of Production Data

– Over 50 Billion Transactions a Day run through IMS

– IMS Serves Close to 200 Million Users a Day– Over 100 Million IMS Trans/Day Handled by

One Customer– 6000 Trans/sec across TCP/IP to single IMS

IMS Strategy– Easier Systems Management (Common

Service Layer, Dynamic Resource Definition, etc.)

– Availability and capacity (Shared Queues, IMSPlex, etc)

– Exploit new programmer skills (IMS Java)– Enhanced connectivity (IMS Connect and

IMS Connect Extensions)– Improved development productivity provided

by Rational Application Developer and WebSphere Developer for zSeries

Distributed System zEnd Users

Online Ordering Customer Service Partner Portal

IMS Data

IMS Applications

and Data

37 Years of Proven Quality, Performance and CommitmentOver 2.6 Million MIPS running on IMS





IMS ConnectWMQ

Appl.

IMS

TM

. . . Appl.

IMS Database ManagerDB2

TransactionManager

IMS Message Queues

IMS Data Comm.

Open Transaction Manager AccessAPPC Comm.

Common Interface (XCF)

ODBA

APPC/MVS

VTAM(LU0 LU1 LU2 LU6.1 LU6.2) TCP/IP for zOS

z/OS

MQSeries

Telnet

B B

D D

MFS P

D

What assets in IMS can be accessed? IMS Transaction– No presentation layer– Access to Resource Managers (RM)

IMS DB, DB2, MQ– Very simple design

Get Input MessageRM callsISRT Output Message

IMS Database– Hierarchical design– JDBC access– XML datastore

IMS MFS – Description of input and output

messages and device map– Not used in client/server

implementations

B

D

P

DB2 SP



Agenda

Core Business Systems Integration


Integration of First IMS Asset – IMS Transactions– Accessing IMS directly from workstations on the Internet– Integrating IMS Transactions into an On Demand Application

Direct connection model– 3270 Emulation– JCA Connector

Messaging and Queuing modelPublishing as a Web Service


Conclusion





IMS Transactions - Connectivity Solutions

JCA Connector:IMS Connect / IMS Connector for Java IMS

Connect

IMS Connector for

Java TCP/IP

WASIMS

Appls.OTMA

IMS DB

DB2

B DB

WebSphere Host Access Transformation Services(HATS)

IMSAppls.

IMSTM

WebSphereHAST

3270

WAS

IMS DB

DB2

P B DB

JMS Connector:MQ to IMS Bridge MQ-IMS

Bridge(XCF)

MQJMS to MQ

MQ QueuesWASIMS

Appls.OTMA

IMS DB

DB2

B DB

SOAP Access:IMS SOAP Gateway IMS

Appls.OTMA

IMSConnectTCP/IP

IMS SOAP Gateway IMS

DB

DB2

SOAPB

B D



Which architecture should I use?Standard architectures provide a choice of options and support – JCA (J2EE Connector Architecture)

– SOAP (Simple Object Access Protocol)

– JMS (Java Messaging Service)

Lots of factors including …– Architectural limits

– Synchronous or asynchronous invocation

– Transactionality

– Security

– Performance

IMS Information– http://www-306.ibm.com/software/data/ims/toolkit/

– And also Redbook “IMS Connectivity in the On Demand Environment - A Practical Guide to IMS Connectivity”

/





Web-to-Host using HATS

WebSphere Host Access Transformation Services (HATS) – Increase productivity and reduce training costs. Convert green screens into intuitive Web

interfaces

– Extend existing applications to new users, such as business partners, suppliers and customers

– Integrate traditional applications into enterprise portals. Provide a single, personalized point of access.

– Reduce development costs by avoiding rewrite of core business applications.

Solution Benefits– No changes in application (CICS, IMS or TSO)

– No middleware to install on z/OShttp://www.ibm.com/software/webservers/hats

IMSTMWebSphere

HAST

3270

WASIMS DB

DB2

P DB

IMStransaction

B



IMS Connect – The TCP/IP Gateway to IMS

High performance TCP/IP access to IMS environment– IMS is the server, the workstation application is the client

– Client uses TCP/IP to send IMS transaction and receive reply

– IMS Connect defines the required message protocol.

Solution Benefits– An IBM tool prior to IMS V9

– Integrated IMS Connect function in IMS V9

– Used by several vendors as basis of their connectivity solutions

IMSConnectTCP/IP

Any TCP/IP ClientIMS

Appls.OTMA

IMS DB

DB2

B DB

http://www-306.ibm.com/software/data/ims/connect/index.html





IMS Sockets client

IMS Connect - a TCP/IP Listener program

Prepare data and pass to IMS

Retrieve data from IMS and respond to TCP/IP client

TCP/IP for zOS

Socket

XCF

Connect Write LLLL LLZZ*IRMREQ*...

LLZZ trancode data04ZZ

ReadDisconnect

Connect Write (...*SAMPLE*...)...

Connect Write (...*HWSJAV*...)...

OTMA

XCF

IMS

MPP

GU IOPCB

ISRT IOPCB

WAS for z/OS

HTTPServer

z/OS

Local

Java Sample using Sockets

IMS Connector for Java

IMS Connect …

IMS

Con

nect

or

for J

ava

Distributed WAS



IMS Connect …reminderIMS Connect V1.1– End of Service – November 2003

IMS Connect V1.2– Marketing Withdrawal – September 2003

– End of Service – April 2005

IMS Connect V2.1– Current version, old release

– Marketing Withdrawal – June 2004

– End of Service – September 2006

IMS Connect V2.2– Current version, current release

– GA 24th June 2004

IMS Version 9 - Integrated IMS Connect function





IMS Connect Extensions – Problem/SolutionProblem: IMS Connect does not log performance data

–Of the components that contribute to overall transaction response time, only IMS Connect does not provide this data

Difficult to rule out IMS Connect as a cause of slow response timesDifficult to diagnose and fix problems

Solution: provide the same high level of instrumentation and performance reporting as other components

Webapplications IMS systemsIMS Connect

Webapplications IMS systemsIMS Connect

IMS ConnectExtensions

IMS Connectinternal events

Reports

Records key events in the life of eachIMS Connect transaction

Similar format toIMS performancereports



Primary Feature

IMS Connect ExtensionsEvent Collection and Recording – Enhances and augments the services of IBM IMS Connect

– Receives notification of significant events, as transactions are being processed by IMS Connect

– Collects and reports on performance-monitoring and system availability data

Advanced Functions– Transaction Routing and workload balancing

Allows for dynamic transaction routing to alternative datastores and workload balancing

Supports pacing of incoming messages to datastores to prevent overloading– Security Improvements

Optional verification of user access to IMS ConnectEnhanced performance of userid/password validation by keeping ACEEs in memory

– Dynamic addition, reload, deletion, disabling or enabling of user exits

Requires IMS Connect 2.2





JCA - IMS Resource Adapter

IMS Connector for Java– Provides connectivity to IMS Transactions

With an option to use a global transaction scope between the 2 business logic parts (distributed Two-Phase Commit)

Solution Benefits– The “Direct Connection” Choice!

Prereqs installation of IMS ConnectNo changes to IMS applications

– The “Strategic” option for IMS Lab

– From any WebSphere platform, zOS or distributed with J2EE Quality of Services

IMSConnect

IMS Connector for

Java TCP/IP

WASIMS

Appls.OTMA

IMS DB

DB2

B DB

http://www-306.ibm.com/software/data/db2imstools/imstools/imsjavcon.html



JCA - IMS Resource Adapter …JCA 1.5 & 1.0 compliance

Global transaction support using RRS

Distributed XA transaction support

SSL support

Multiple development platforms– Windows (NT, 2000, XP)

– Linux

Multiple runtime platforms– z/OS

– Windows

– AIX, Solaris, HP-UX

– Linux

– Linux for z/OS

Functions– Accept input message from java client

application

– Build OTMA headers

– Build IMS Connect header (IRM)

– Interact with a Connection Factory to obtain a connection

– Issue socket calls

– Interact with WebSphere Application Server to support aspects of distributed two-phase commit, security, etc.

– Remove reply headers

– Return reply message to java client application





JCA - IMS Resource Adapter …

z/OS1

z/OS2

Linux for z/OS

Windows / AIX / Solaris / Linux

and z/OS

WebSphereApplication

ServerIMS Resource

Adapter


Server

IMS ResourceAdapter


ServerIMS Resource

Adapter

IMS

TCP/IP

XCF

XCF

IMS

IMS

IMS Connect

IMS Connect

IMS Connect

B D

B D

B D

Local



JCA - IMS Resource Adapter - TransactionalityCapability that allows IMS transactions to participate as a resource in two-phase commit external transactions – Requires a syncpoint coordinator

RRS on z/OS and/or an external coordinator, e.g.,IBM WAS (Websphere Application Server)

– Requires client code that uses IC4J

Local Environment– WAS, IMS Connect, IMS, and RRS must be in the same

z/OS image *

Distributed environment (Global XA transaction)– IMS Connect, RRS and IMS must all exist in the same z/OS image **

– Remote environments use XA

– IMS ConnectActs as an extension to RRS and is the SDRM (Server Distributed Syncpoint Manager)Assists RRS in communicating with other syncpoint coordinatorsActs as the CRM (Communications Resource Manager)

YES **Local Optionz/OS

YES*TCP/IPz/OS

YES*TCP/IP on Hipersockets

zLINUX

YES*TCP/IPDistributed

Global Trans

ProtocolWAS Server platform + IC4J





Get context

Input msg withcontext ID

(access/updateother resources)

PreparePrepare IMSPrepare other

Prepare complete

CommitCommit IMS Commit other

Commit complete

Context ID

ACK

Express interest

Output

Prepare return

Commit return

IBM WAS for z/OS withIMS Resource Adapter

IMS Connect RRS/MVS IMS

z/OS

Express interest

Prepare return

Commit return

also goes throughRRS

JCA - IMS Resource Adapter – Transactionality …z/OS Support



Distributed IBM WAS withIMS Resource Adapter

IMS Connect RRS/MVS IMSA

Context IDIMS Tranb with

context ID

IMS Trana with XID

IMS Tranb with XID

PreparePrepare IMSA

Prepare IMSB

CommitCommit IMSA

Commit IMSB

ACK

z/OS B

Context ID

IMS Trana withcontext ID Express interest

Output

Prepare return

Commit return

Express interest

Output

Prepare return

Commit return

z/OS A

ACK

IMS ConnectRRS/MVSIMSB

JCA - IMS Resource Adapter – Transactionality …Distributed Environment– Example of running 2 IMS Transactions





The Other Revamping Solution - MFS Web Enablement

Enables MFS transactions to be run from HTML devices– Exploits WAS, IC4J and IMS Connect at run time …

… but is developed without need for WebSphere tooling– downloadable from IMS Web page

Includes two sample style

sheets

MFS Web Enablement

servlets

loads Stylesheet

WASMFS Web Enablement Adapter

XMIRepository

DEV MSGBytestream

OutputRecord

InputRecord IMS

Connector forJava

IMSConnectTCP/IP

IMSAppls.

OTMA

IMS DB

DB2

B D



JMS – Access to IMS TransactionsWMQ IMS Bridge– Transfers the message to the

unchanged IMS transaction.

– Transfers the output message to the Reply_To_Queue.

Solution Benefits– The “Asynchronous Connection” Choice!

MQ Trigger Monitor– Run as an IMS application which use

MQ API to call the business logic program.

Solution Benefits– Trigger Monitor is a real MQ based

application which allows some additional processing outside of the IMS application

MQ Trigger Monitor

MQJMS to MQ

MQ QueuesWAS

B

CICS or IMS Transaction

CICS or IMS Transaction

BIMS DB

DB2

D

MQBridge





IMS Connect

z/OS

Windows / AIX / Solaris

WebSphere Appl. Server

Bean

WebSphere Appl. Server

Bean

IC4J

Through WAS– using IMS Connector for Java (IC4J)

– from any WebSphere platformz/OS or distributed

– with J2EE Quality of Services

Through WebSphere MQ– using MQ IMS Bridge

Through IMS SOAP Gateway– Using IMS Connect

WMQ for z/OS

JMS

IC4J

Windows / AIX / Solaris

WAS

Bean JMS

WMQ

XCF

IMS SOAP Gateway

Windows/AIX

SOAP RequestSOAP

RequestP

B

e.g. Java,.NET, SAP

SOAP – Access to IMS Transactions

IMS Callout Survey for customer requestshttps://www-950.ibm.com/survey/oid/wsb.dll/studies/imscallout.htm

IMSAppls.

OTMA IMS

DB

DB2

B D



IMS SOAP GatewayA Web Service solution for IMS with direct SOAP support– Leverages existing IMS applications as Web Services without the need of a J2EE

server– Supports different types of applications – Microsoft .Net and Java

Supports Web Service specifications and leverage Open standards– SOAP/HTTP 1.1, WSDL 1.1, WS-I Basic Profile 1.0– UTF-8 encoding for SOAP messages

Web service-enabled IMS application with easy deployment– Makes your IMS application a web service with easy deployment and configuration –

no programming needed

Transforms XML data without changing IMS application– XML transformation can also be handled by IMS application – IMS Connect XML Adapter in Beta - COMING SOON!

Transforms XML data using IBM WebSphere Developer for zSeries XML converters eliminating the need to modify the IMS application code





IMS SOAP Gateway V9.1 Overview …

IMS

OTMA

MPP/IFP/JMP

GU IOPCB

ISRT IOPCB

IMS Application

IMS Connect

z/OS

IMS SOAPGateway

XML

Web Service Clients,e.g. Microsoft .Net,

SAP, Java, etc..

SOAP

IMS V9

IMS DB(XML DB)

<?xml version="1.0"?><soap:Envelope><soap:Body><INPUTMSG><in_ll>59</in_ll><in_zz>0</in_zz><in_trcd>IVTNO</in_trcd><in_cmd>Display</in_cmd><in_name1>LAST1</in_name1>

</INPUTMSG><soap:Body>

<soap:Envelope>

LLZZIVTNO<?xml version=“1.0”?><INPUTMSG>

<in_ll>59</in_ll><in_zz>0</in_zz><in_trcd>IVTNO</in_trcd><in_cmd>Display</in_cmd><in_name1>LAST1</in_name1>

</INPUTMSG>

Requires Application Changes



IMS SOAP Gateway V9.1 + XML Adapter

In Beta– Supports Windows (2000 + XP) – XML transformation is handled by IMS Connect XML Adapter and WDz converters

XML Adapter code Included in IMS Connect (COBOL support only)– Pre-req:

IBM WebSphere Developer for zSeries (WDz)– WDz takes COBOL copybook of an IMS application and generates WSDL, correlator and XML

ConvertersIMS V9 with integrated IMS Connect + XML Adapter

IMS

OTMA

MPP/IFP/JMP

GU IOPCB

ISRT IOPCB

IMS ApplicationIMS

Connect

z/OS

IMS SOAPGateway

XMLWeb Service Clients,e.g. Microsoft .Net,

SAP, Java, etc..

IMS V9

IMS DB(XML DB)

<?xml version="1.0"?><soap:Envelope><soap:Body><INPUTMSG<in_ll>59</in_ll><in_zz>0</in_zz><in_trcd>IVTNO</in_trcd><in_cmd>Display</in_cmd><in_name1>LAST1</in_name1>

</INPUTMSG><soap:Body>

<soap:Envelope>

LLZZIVTNO DISPLAY LAST1

Adapter Task Manager + COBOL

XML Adapter

WDZ XMLConverters

NOApplication Changes

SOAP





IMS SOAP Gateway V9.1 + XML AdapterLLZZ and Trancode will be part of the XML input data (i.e. IMS SOAP Gateway will not add LLZZTrancode)

IMS Connect COBOL XML Adapter re-computes the LL value after WDzXML converter returns the converted data bytes

HWSSOAP1 exit updated with the new adapter name and tagname (or drivername) fields in the IRM header– HWSSOAP1 will be shipped with IMS Connect

– Adapter type “IBM XML COBOL Adapter” in correlator file -> HWSXMLC0 as the Adapter name in IRM

– Program name in correlator file -> Tag/Driver name in IRM



IMS SOAP Gateway RequirementsCallout

– Allows IMS application to act as web service/SOAP client to invoke an outbound web service and get the data back

Tooling/Adapters support for other languages (MFS, PL/I, etc)

SOAP 1.2 support

CM0/Resume Tpipe/Send Only/ALTPCB

z/OS platform

WS-Transaction

Download from http://www.ibm.com/imsIMS SOAP Gateway InstallShield programIMS Connect User Message Exit HWSSOAP1 Pre-req: IMS V9 + Integrated Connect (9.1)





Web Service access to IMS

Continue to exploit WebSphere MQ for basic messaging and flowing Web services

Widely adopted B2B integration technology that includes IMS connectivity

Comprehensive industry standard for assured messaging

3. JMS/WebSphere MQ

If customer uses WebSphere Application Server to create mid-tier components then the best integration option is usually J2C, using IMS Connector for Java

Widely adopted IMS connectivity with highest qualities of service today

Comprehensive W3C standards for messaging over the Web supporting SOA to IMS

2. JCA

If customer does not wish to write a web services wrapper program (e.g. WAS EJB), then the best integration option is usually “IMS SOAP Gateway”

Basic SOAP Support to access IMS transactionsFuture: Improving QoS, features and performance

Lightweight J2EE standard for messaging over the Web supporting SOA to IMS

1. Using IMSSOAP Gateway

RecommendationPositioningDescriptionStandard architecture

MediumIMS I/O Message or WebSphere MQ API

RAD (for WSDL and SOAP Proxy)

Inbound and outboundAsynchronousAssured delivery

3. JMS/ WebSphere MQ

MediumIMS I/O MessageRAD (for WSDL and SOAP Proxy)

Inbound onlySynchronous with Asynchronous output optionsNO max message size: IMS Connect supports multi segment message (32K limit for one single segment)

2. JCA

LooseIMS I/O Message (llzztrandata)

WebSphere Developer for z (for XML Parser)

Inbound onlySynchronous (HTTP)32 KB limit (single segment)

1. Using IMS SOAP Gateway

CouplingInterfaceDevelopment PlatformCapabilitiesStandard architecture



Web Service access to IMS - Solution Criteria Checklist

>32K OK with IMS Multi-segmentsInbound/outbound support

Asynchronous

>32K OK with IMS Multi-segmentsInbound support onlyOutbound using MQ or APPCSynchronous (but with optional asynchronous “assured delivery” of reply)

32K limitInbound support onlySynchronousNon-conversational trans only

Architectural limits

High availability config based on IMSplex and MQ workload management (cluster or shared queues)

High availability config options available for IMS Connect (especially with zOS TCPIP Sysplex Distributor)

Based on OS usedBest when SOAP Gateway available on z

Reliability / Availability

No results currentlyRequirement to port it to z/OS

No support yet for WS-Security Security from ICON:•SSL•User ID + password

No global transaction support

1 - IMS SOAP Gateway

Carry identity in MQ message. Trust (SSL on channel) or protection of queues

SAF Userid /password validation in MQ IMS Bridge

Lots of optionsContainer managed or component

managed Trust model

SSL or Userid /password validation in IMS ConnectThen SAF security based on Useridin IMS subsystem

Security

Best option todayPerformance / Scalability

No global transaction supportMost robust global tran support – JCA XA support

Transactionality

3 - JMS/ WebSphere MQ2 - JCA









Conclusion



IMS Databases – JDBC Connectivity Solutions

IMSDB

ODBA

WAS zOS+ JDBC Driver

IMS Distributed

JDBC RMI/IIOP

WAS

IMS DB

Using WebSphere II CF WebSphere IICF JDBC or ODBC Client

IMSDB

DRA

WebSphereII

CFTCP/IP IMS

DB

IMSDB

ODBA

WAS zOS+ IMS JDBC IMS

DB

From WAS on z/OS using IMS JDBC

IMSDB

ODBA

DB2Stored

ProcedureJDBC RMI/

IIOP

WAS

IMS DB

Thru DB2 Stored Procedure

From Distributed WAS using IMS Distributed JDBC

DLI Model UtilityDLI Model Utility

CUSTOMER

BILL

COMMAND

ARTICLEPRODUCT

CUSTOMERCUSTOMER

BILLBILL COMMANDCOMMAND

PRODUCTPRODUCT

ARTICLE

B

D

B

B

B

B

D

D

D





IMS Databases – JDBC Connectivity Solutions ...From WAS on z/OS using IMS JDBC– Business logic and data access in the same z/OS image

– Syncpoint management using z/OS RRS

– Workload management using z/OS WLM

– Best security implementation

From Distributed WAS using IMS Distributed JDBC– With IMS Version 9 and a WAS for z/OS Gateway

Thru DB2 Stored Procedure– JDBC to start the DB2 Stored Procedure

– Access to IMS DB in the business logic running in the DB2 SP (written in COBOL, PLI, … or JAVA)

– Same z/OS than the IMS Database Manager

Using WebSphere II Classic Federation– Support for JDBC in any Java application (with or without WAS)

– Support for ODBC

– Integration of several z/OS Data Sources (including IMS DB, VSAM, DB2, IDMS, ADABAS)



Any Application using RRS

Any Application using RRS

DB

RC

DLISAS

IMS DBCTL or TM/DB

Managed by zOS RRS

ODBA Services

Access to IMS Data - Open Database Access (ODBA)

Provides a callable interface to IMS databases from any zOS programs that are not managed by IMS

–DB2 Stored Procedures

–or Any applications that use zOS Resource Recovery Services (RRS) to manage their syncpoint processing

Connection to IMS TM or DBCTL–Uses the Database Resource Adapter (DRA)

–DL/I calls are issued using the Application Interface Block (AIB) interface





Access to IMS Data - IMS JavaA new feature in IMS since IMS V7

A set of classes that...– Offers Java support to access IMS

Databases from various environments (IMS, CICS, DB2, WebSphere)

– Enables SQL access through the JDBC interface

Rapid Application Development

Extend the life and scope of IMS applications and databases

Leverage existing marketplace, industry-sanctioned standards - they are the slowest

changing and most persistent

JDBC and J2EE are standardsLeverage new and abundant skills in the

marketplace and mitigate the loss of 390 skills for customers

CEETDLI Interface

JNI

Base

App DB

JDBC / SQL

Customer Code

IMS Java Class Library

C Layer Interface to IMS

IMS DB MetadataBusiness Logic

Mapping to DL/I APIs

IMS Dep. RegionTransaction andMessage Processing

JDBC, JCA interface Java to C interface

IMS JavaApp

DLIDatabase

View



COPYLIB

PSBs

DBDs

CEETDLI Interface

JNI

Base

App

DB

JDBC / SQL

IMS JavaApp

DLIDatabase

ViewStored Procedure

EJB

JCICS

IMS DB

CEETDLI Interface

JNI

Base

App

DB

JDBC / SQL

IMS JavaApp

DLIDatabase

View

Java Virtual Machine

Java Virtual Machine Java Virtual Machine

CEETDLI Interface

JNI

Base

App DB

JDBC / SQL

IMS JavaApp

DLIDatabase

View

DBDGEN

PSBGEN

ACBGEN

EJB

Java Virtual Machine

Classic FederationJDBC Client

CEETDLI Interface

JNI

Base

App

DB

JDBC / SQL

IMS JavaApp

DLIDatabase

View

IMS JDBC ResourceAdapter

CEETDLI Interface

JNI

Base

App

DB

JDBC / SQL

IMS JavaApp

DLIDatabase

View

DRA

ODBA

Access to IMS Data – Outside of IMS Transactions





Websphere Information Integrator Classic Federation for z/OSRead from and write to mainframe data sources using SQL

Standards-based access via ODBC, JDBC, or Call Level Interface

Multi-threaded with native drivers for scalable performance

Metadata-driven means:– No mainframe programming required – Fast installation & configuration– Ease of maintenance

Works with existing and new:– Mainframe infrastructure– Application infrastructure– Toolsets

DB2 UDBfor z/OS

Software AGAdabas

VSAM CA IDMS

CA Datacom

IMS DB & TM

Websphere Information IntegratorClassic Federation for z/OS



IMS Callout Enhancements (Version 10)Enable IMS applications as clients – Asynchronous outbound support from IMS applications.

IMS pull of information/data from distributed system – IMS application initiates request to outbound WAS or other applications,

and receives response back

Asynchronous Callout to EJB– Customer provides code in JCA EJB application

Asynchronous Callout to Message Driven Bean (MDB)– Use JCA 1.5 inbound architecture support of EIS, e.g., IMS to initiate

communications to the J2EE application server, eg. WAS

– End-to-end tooling available

Outbound Web services support to external SOAP server for IMS SOAP clients

ExternalApplication

IMS

IMS Application

z/OS

Anyplatform

Callout

InitiatingClient









Conclusion



XML, SOAP & Web Services = Open Integration TechnologiesJDBC, ODBC = Interoperability for Application Developers

SOAP IMS - Helping Customers Build their SOASimplify access to existing backend systems– Seamlessly integrate distinct enterprises

B2B data exchange– Modernizing IMS Transactions and data

– XML, SOAP/Web Services to access IMS transactions

– IMS XML data storage

– Distributed access to IMS data

Easing Integration– WebSphere and J2EE compliant application server

– Designed to support open integration technologies

– Support collaboration among IMS and other components, both within and beyond enterprise boundaries





SummaryCore Business applications are critical to enterprise customers– Business Integration need to consider them

– Maintain forward progress (preserve customer investments)

– Ratio of COBOL to J2EE developers typically 5x to 10x

– Applications must live for a long time!

An on demand business is an enterprise whose business processes — integrated

end-to-end across the company and with key partners, suppliers and customers —can respond with speed to any customer demand, market opportunity or external

threat.



Thank YouMerci

Grazie

Gracias

Obrigado

Danke

Japanese

English

French

Russian

GermanItalian

Spanish

Brazilian PortugueseArabic

Traditional Chinese

Simplified Chinese

Thai

im02 - soa integration of ims assets - ibm · im02 - soa integration of ims assets 8

Documents