Copyright: Avi Rosenthal, 2002- 2003. all rights reserved 1 IBM MF and Web Services Avi Rosenthal Avi Rosenthal Independent Consultant [email protected]

Copyright: Avi Rosenthal, 2002-20Copyright: Avi Rosenthal, 2002-2003. all rights reserved03. all rights reserved

11

IBM MF and Web IBM MF and Web ServicesServices

Avi RosenthalAvi Rosenthal

Independent ConsultantIndependent Consultant

[email protected]@netvision.net.il


22

Overall Overall Presentation GoalPresentation Goal

PresentingPresenting the potential and obstacles the potential and obstacles for realization of Web Services in for realization of Web Services in

Legacy MF applicationsLegacy MF applications


33

Learning ObjectivesLearning Objectives

• Understanding current status of IBM Understanding current status of IBM MF technology and applications.MF technology and applications.

• Understanding new trends and Understanding new trends and directions in IBM MF environment.directions in IBM MF environment.

• Assessing the practical implications for Assessing the practical implications for Web Services and Java implementations Web Services and Java implementations in IBM Mainframe environment. in IBM Mainframe environment.


44

Speaker’s Speaker’s QualificationsQualifications

• 30 Years in IT.30 Years in IT.

• Technologies and Architectures Consultant for 30 Technologies and Architectures Consultant for 30 organizations.organizations.

• Working with leading Analysts Groups Working with leading Analysts Groups

• Consultant for Leading Edge Core Banking Consultant for Leading Edge Core Banking

endeavor (2000-2002).endeavor (2000-2002).

• Assessing software products initiatives for VCs. Assessing software products initiatives for VCs.

• Many years of experience as CTO, Technical Many years of experience as CTO, Technical Manager and Technical Expert.Manager and Technical Expert.


55

Presentation Presentation AgendaAgenda

• CurrentCurrent MFMF InfrastuctureInfrastucture

• MF Trends & DirectionsMF Trends & Directions

• Introduction to Web Services Introduction to Web Services

• Web Services and MFWeb Services and MF

• SummarySummary


66

CurrentCurrent MFMF InfrastuctureInfrastucture

• Data:Data:

DB2, other Relational (e.g. CA Datacom), DB2, other Relational (e.g. CA Datacom), other DBMS (e.g. IMS-DB, Adabas, IDMS), other DBMS (e.g. IMS-DB, Adabas, IDMS), VSAMVSAM

• OLTP Monitors:OLTP Monitors:

TX Series (CICS), IMS-DC TX Series (CICS), IMS-DC

• Business Logic:Business Logic:

COBOL (70%-80%), PLI, 4GL (e.g. VAG, COBOL (70%-80%), PLI, 4GL (e.g. VAG, Cool:Gen, Natural, Ideal)Cool:Gen, Natural, Ideal)


77


• Communication: Communication:

SNA, TCP/IPSNA, TCP/IP

• BatchBatch

• MMI: MMI:

3270, C/S, Web to Host3270, C/S, Web to Host

bll


88


• High Availability and ReliabilityHigh Availability and Reliability

• Scalability and High PerformanceScalability and High Performance

• Clustering: SysplexClustering: Sysplex

• Partitioning and Workload Management.Partitioning and Workload Management.

• Business Critical Applications and DataBusiness Critical Applications and Data

bll

All Rights Reserved to: Avi Rosenthal


99


• Dominated by IBMDominated by IBM

The only vendor which produce servers.The only vendor which produce servers.

The only traditional Operating Systems The only traditional Operating Systems vendor.vendor.

Largest market share: OLTP, DBLargest market share: OLTP, DB


1010


• Current MF InfrastuctureCurrent MF Infrastucture

• MFMF Trends &Trends & DirectionsDirections



• SummarySummary


1111

MFMF TrendsTrends & & DirectionsDirections

Z/OSZ/OS

• Web Sphere is the strategic platform for IBM Web Sphere is the strategic platform for IBM

• New development: Java and J2EE.New development: Java and J2EE.

• Integration and Interoprability of new J2EE Integration and Interoprability of new J2EE applications with exsisting systems on the MF.applications with exsisting systems on the MF.

• Integration with Distributed Environments.Integration with Distributed Environments.

• 3 Modal addressing: 64 bit, 31 bit, 24 bit.3 Modal addressing: 64 bit, 31 bit, 24 bit.


1212

LinuxLinux

• Server Consolidation of Linux instances. Server Consolidation of Linux instances.

• Linux instances under VM. Linux instances under VM.

• Lower prices for software and servers for Linux: Lower prices for software and servers for Linux: Z800 Z800 modelsmodels

• Support of major Linux vendors: Support of major Linux vendors:

Red Hat, Su-Se (United Linux) and othersRed Hat, Su-Se (United Linux) and others

• Development: Java and J2EE:Development: Java and J2EE:

Web Sphere, Web LogicWeb Sphere, Web Logic



1313


Linux evolution on MFLinux evolution on MF

• Server Consolidation of Linux instances. Server Consolidation of Linux instances.

• Hyper Socket Hyper Socket connection to Z/OS.connection to Z/OS.


1414

GeneralGeneral

• E-Buisiness on DemandE-Buisiness on Demand

Computing on DemandComputing on Demand

Autonomic Computing( Self Managing, Self Autonomic Computing( Self Managing, Self Healing etc.)Healing etc.)

TheThe vision of e-Buisiness on Demand vision of e-Buisiness on Demand isis forfor heteregoneusheteregoneus platforms.platforms. It is designed for creating the Service It is designed for creating the Service Oriented Infrastructure Architecture.Oriented Infrastructure Architecture.



1515

Java on Z/OSJava on Z/OS

• J2EE Application Servers:J2EE Application Servers:

IBM Web Sphere, BEA Web Logic IBM Web Sphere, BEA Web Logic

• Traditional transction Servers: Traditional transction Servers:

CICS, IMS/DCCICS, IMS/DC

• CORBA based:CORBA based:

IONAIONA


1616

Why Why Java on MFJava on MF??

• Narrowing of MF advantage in Availability, Narrowing of MF advantage in Availability, Reliability and Scalability.Reliability and Scalability.

• Higher TCO of MF for non High-End Higher TCO of MF for non High-End oragnizations.oragnizations.

• Availability of ISVS solutions and Packaged Availability of ISVS solutions and Packaged solutions is a key for platform decisions.solutions is a key for platform decisions.

Java and XML are the key enabling Java and XML are the key enabling technologies for ISVS and Packaged technologies for ISVS and Packaged applications availability.applications availability.


1717

App Servers vs. App Servers vs. TraditionalTraditional OLTPOLTP

CICSCICS WSWS

MaturityMaturity very maturevery mature imatureimature

EJBsEJBs SessionSession BeansBeans

allall

ScalabilityScalability 5,0005,000++ tr/sectr/sec 500500 tr/sectr/sec

ExternalExternal IntegratioIntegratio

nn

GoodGood?? very goodvery good

InternalInternal IntegratioIntegratio

nn

excelentexcelent evolvingevolving


1818

App Servers vs. App Servers vs. TraditionalTraditional OLTPOLTP

CICSCICS WSWS

TransactionTransactionss

OLTPOLTP MonitorMonitor

App ServerApp Server

WebWeb adaptingadapting very very goodgood

BusinessBusiness ComponentComponentss

nono yesyes


1919




• IntroductionIntroduction toto WebWeb ServicesServices


• SummarySummary


2020

IntroductionIntroduction toto Web Web ServicesServices

The two “heads” of Web ServicesThe two “heads” of Web Services

1. Interoperability1. Interoperability andand IntegrationIntegration

• Reuse of exsisting functionality and Data Reuse of exsisting functionality and Data as Services.as Services.

• Interoperability and Integration of Legacy Interoperability and Integration of Legacy code and Data.code and Data.

• Developed by traditional AD toolsDeveloped by traditional AD tools

• Invoked by standard based Interfaces.Invoked by standard based Interfaces.


2121

Web Services Web Services InteroprabilityInteroprability

Client

Service

Client Interface

Service Interface


2222

IntroductionIntroduction toto Web Web ServicesServices

The two “heads” of Web Services The two “heads” of Web Services

2. Building2. Building newnew functionalityfunctionality asas ServicesServices• Implemented by New development platforms Implemented by New development platforms

e.g. Dot Net, J2EE.e.g. Dot Net, J2EE.• Service Oriented ArchitectureService Oriented Architecture• Object Oriented and Componentized.Object Oriented and Componentized.

• Designed for the Web.Designed for the Web.

• Support of industury standardsSupport of industury standards


2323

"If you ask 5 people to define "If you ask 5 people to define Web Services you will get 6 Web Services you will get 6 definitions.”definitions.”

DiscussionDiscussion GroupGroup inin W3CW3C

Web Services Web Services DefinitionDefinition


2424

Web Services Web Services DefinitionDefinition

HurwitzHurwitz Group,Group, 3.023.02

AA set of software, content and networkset of software, content and network standardsstandards 34%34%

Offers a means of delivering integratedOffers a means of delivering integrated computingcomputing solutionssolutions 43%43%

Any kind of service delivered over the Any kind of service delivered over the WebWeb

19%19%


2525

My definitionMy definition

Web Services are standard XML Web Services are standard XML interfaced application services, which interfaced application services, which use SOAP (Simple Object Access use SOAP (Simple Object Access Protocol) standard and optionally other Protocol) standard and optionally other standards (e.g. WSDL).standards (e.g. WSDL).


2626




• Introduction to Web ServicesIntroduction to Web Services

• WebWeb ServicesServices andand MFMF

• SummarySummary


2727

WebWeb ServicesServices and and MFMF

• MF applications are the largest source of MF applications are the largest source of exsisting functionality.exsisting functionality.

• Could be used as Web Services for Could be used as Web Services for Integration and/or InteroprabilityIntegration and/or Interoprability but....but....

• ThereThere areare manymany TechnicalTechnical andand CulturalCultural issues, whichissues, which couldcould hinderhinder exploitation.exploitation.


2828

CICS WS potential as CICS WS potential as exampleexample

• Used by 490 of Fortune 500Used by 490 of Fortune 500

• 30 billions transactions per day.30 billions transactions per day.

• Transactions of more than 1 trilion $ per Transactions of more than 1 trilion $ per day.day.

• 30,000 CICS COBOL modules30,000 CICS COBOL modules


2929

example2:example2: COBOL potentialCOBOL potential

• 70% of the world Business Data is processed 70% of the world Business Data is processed by MF COBOL applications (Aberdeen Group)by MF COBOL applications (Aberdeen Group)

• According to Gartner Group it is closer to 75%.According to Gartner Group it is closer to 75%.

• 200 billion lines of code in COBOL currently 200 billion lines of code in COBOL currently run on MF (Micro Focus).run on MF (Micro Focus).

Replacement of all COBOL applications Replacement of all COBOL applications in the foreseeable future is unrealisticin the foreseeable future is unrealistic


3030

MF WebMF Web ServicesServices LimitationsLimitations

• No Service Oriented Architectures.No Service Oriented Architectures.

• Silo Applications and not Component Based.Silo Applications and not Component Based.

• Usually Tightly Coupled.Usually Tightly Coupled.

• No explicit boundaries between layers.No explicit boundaries between layers.

The required change is both Technical and The required change is both Technical and Cultural.Cultural.


3131

• notnot SOASOA major Reengineeringmajor Reengineering

• Tightly Coupled SOA.Tightly Coupled SOA. designdesign changechange • Loosely Coupled SOA.Loosely Coupled SOA. EasyEasy

e.g. Dot Net, J2EEe.g. Dot Net, J2EE

Some Business Functions could be Some Business Functions could be exposed as Servicesexposed as Services butbut itit is is unrealisticunrealistic toto changechange thethe overalloverall nonnon SOASOA architecturearchitecture toto SOASOA

Adapting to Web ServicesAdapting to Web Services difficulty


3232

WebWeb Services and JavaServices and Java

• Major J2EE 1.4 specs (currently in Beta) Major J2EE 1.4 specs (currently in Beta) for Web Services support.for Web Services support.

• J2EE 1.4 Web Services support:J2EE 1.4 Web Services support:

PortabiltyPortabilty

XML, SOAP, WSDLXML, SOAP, WSDL


3333

MF WebMF Web Services Services LimitationsLimitations

• SNASNA

Many Sites are not using TCP/IP.Many Sites are not using TCP/IP.

• SOAP support in CICS is new (3.03) SOAP support in CICS is new (3.03)

• IMS/DC SOAP???IMS/DC SOAP???

• Tactical ISVs SOAPTactical ISVs SOAP solutionssolutions or Apache SOAP (now Axis).or Apache SOAP (now Axis).

• The majority of applications executed under CICS and The majority of applications executed under CICS and IMS/DC and not under Web Sphere or Web Logic.IMS/DC and not under Web Sphere or Web Logic.


3434


• SOAP listner should resolve ASCII-EBCDIC SOAP listner should resolve ASCII-EBCDIC during Serialization-de Serialization.during Serialization-de Serialization.

• Complex XML messages Serialization-de Complex XML messages Serialization-de Serialization is a performance bottleneck in Serialization is a performance bottleneck in other platforms.other platforms.


3535


• No native SOAP support in Web Sphere 4.No native SOAP support in Web Sphere 4.

• Web Sphere 5 supports native SOAP (JSR Web Sphere 5 supports native SOAP (JSR 109: embedded SOAP parser in Java).109: embedded SOAP parser in Java).

• Web Sphere 5 GA 11.02Web Sphere 5 GA 11.02

• but:but: WebWeb SphereSphere 55 GAGA forfor Z/OS only in Z/OS only in 2Q03.2Q03.


3636






• SummarySummary


3737

SummarySummary

• MF environment executes the largest MF environment executes the largest Business Functionality and Data, which Business Functionality and Data, which could be exposed as Web Services,could be exposed as Web Services,

ButBut there are huge challenges there are huge challenges hindering the exploitation.hindering the exploitation.

• The major issues for achieving The major issues for achieving Interoprability by Web Services on MF are Interoprability by Web Services on MF are technical, architectural and cultural.technical, architectural and cultural.

It is more than just technology.It is more than just technology.


3838

SummarySummary

• For Short Term integrating specific For Short Term integrating specific functionality as Web Service is functionality as Web Service is realistic,realistic,

but exposing entire enterprise MF but exposing entire enterprise MF site functionality as services issite functionality as services is unrealistic.unrealistic.


3939

Q & A?

Documents

Copyright: Avi Rosenthal, 2002- 2003. all rights reserved 1 IBM MF and Web Services Avi Rosenthal Avi Rosenthal Independent Consultant [email protected]