Introducing IBM z/OS Connect Enterprise Edition V2.0

Madhu B Ananthapadmanabh (madhu.b.a@in.ibm.com)

Digital Economy

Enterprises must learn to “Innovate like a Startup”

……TO

FROM……..“The ‘Uber syndrome’

– where a competitor

with a completely

different business

model enters your

industry and flattens

you.” Judy Lemke, CIO,

Schneider, United States

“52% of the Fortune 500 firms since 2000 are gone.” – R. Ray Wang http://blog.softwareinsider.org/2014/02/18/research-summary-sneak-peaks-from-constellations-futurist-framework-and-

2014-outlook-on-digital-disruption/

© 2016 IBM Corporation3

Consider Disruption in the Banking Industry

Non-bank entrants

New banks

New payment models

New lending models

New depository

Challenge: Disruptive forces are impacting banking industry dramatically

Opportunity: New ways to partner to create new value chains

Digital disruption fueled by APIs blurring traditional industry lines

© 2016 IBM Corporation4

What do the Following Have in Common?

Coffee company goes

digital, builds $1.6B

payments business, drives

21% of transactions

Car company offers

connected car, improves

driving experience, sells

vehicle data to partners

Bank spurs innovation by

offering hackathons,

integrates rewards program

with retailer partners

New Opportunities enabled by APIs

© 2016 IBM Corporation5

An Example of Innovative Application in Banking

– Mobile Wallet

APIMobile

Opportunity:• Improve consumer experience

• Convenience, Availability,

Usability

• Increased loyalty

• Customer retention

• New customers

• New Mobile Commerce channel

Solution:• Mobile App that will allow you to pay

• Credit / Debit card options

• Use for online shopping

• Use for in-store (NFC/QR code)

• Partner with retailer for special

discounts

$720 billion a year mobile payments by 2017 - Gartner estimate

6© 2016 IBM Corporation

Most Common scenario around APIs

Two Key Requirements for Enabling Digital Transformations

Must be agile in responding to marketplace needs and competitiono Solutions must be developed and deployed quickly, and are likely to be taken down just as quickly when replacing

with newer solutions

o An added requirement for enabling this multi-channel (for example, Mobile) digital presence can be a flexible deployment of this solution that is based on changing demand and available resources; for example, cloud-based solutions All enabled by APIs – exposing (Interaction) APIs for customer facing Mobile and IOT apps, and composing new applications accessing other APIs

(including Systems APIs)

Leverage core competency supported by mainframe assetso SOR Assets are built with a lot of due diligence and over a long period of time

Maintained by transactional systems (Create, Retrieve, Update and Delete) with important qualities of service (Reliable, Scalable, Secure, …)

Accessed by all core business processes, e.g., on-boarding a new customer or partner, introducing a new product, updating customer or product information, looking

up information, etc.

Data quality is maintained with a lot of due diligence in data validation

o New digital presence applications (exposed as interactive APIs) need easy access to SOR data Ease of development of System APIs can provide easy and timely access to SOR data

Related Blog entries: "Changing Industry Landscape with Digital Transformation" and "Digital Transformation with Mainframe Assets"

© 2016 IBM Corporation14

A Hybrid Cloud Architecture for Digital Transformation

Bluemix, API Connect, z/OS Connect EE for modern hybrid Enterprise applications

CICS

IMS

WebSphere

DB2

CICS, IMS, DB2,

WebSphere

IBM z/OS Connect EE

Create & run SoR (System)

APIs

IBM API Connect

Create, run, manage & secure

Enterprise APIs & Micro services

IBM Bluemix, zLinux/LinuxONE

Compose deploy & integrate

applications, services

IBM Mobile First

Tight IntegrationAll components located on

mainframe, and linkages are tightly

coupled

Service

OrientedLoose coupling using network-

based protocols such as

SOAP/WSDL

Web AccessScreen-scraping of 3270

applications

MessagingUsing technologies such as

IBM MQ

API EconomyIntegration based on a set

of well-understood and

easily-accessible APIs,

increasingly based on

REST/JSON patterns

These earlier patterns are still in

use and in many cases are the

best pattern for the application.

Just because they came earlier,

does not mean they are now

obsolete.

Evolution of Mainframe Integration Patterns

/what_is_REST?What makes an API “RESTful” ?

{REST}

1

6

REST is an Architectural Style…

• REST stands for Representational State Transfer.

• An architectural style for accessing and updating data.

• Typically using HTTP… but not all HTTP interfaces are “RESTful”.

• Simple and intuitive for the end consumer (the developer).

HTTP

17

• GET http://www.acme.com/customers/12345?personalDetails=true

• RESPONSE: HTTP 200 OK

BODY { “id” : 12345

“name” : “Joe Bloggs”,

“address” : “10 OldStreet”,

“tel” : “01234 123456”,

• “dateOfBirth” : “01/01/1980”,

“maritalStatus” : “married”,

“partner” : “http://www.acme.com/customers/12346” }

http://<host>:<port>/path/parameter?name=value&name=value

GET

POST

PUT

DELETE

URIs represent things

(or lists of things)

Use HTTP

verbs for

Create, Read,

Update, Delete

(CRUD)

operations

Request/Respons

e Body is used to

represent the data

object

Query Parameters are used for

refinement of the request

Key Principles of REST

18

Relatively

Lightweight

Compared to other technologies (for example, SOAP/WSDL), the

REST/JSON pattern is relatively light protocol and data model,

which maps well to resource-limited devices.

Relatively

Easy

Development

Since the REST interface is so simple, developing the client involves

very few things: an understanding of the URI requirements (path,

parameters) and any JSON data schema.

Increasingly

Common

REST/JSON is becoming more and more a de facto "standard" for

exposing APIs and Microservices. As more adopt the integration

pattern, the more others become interested.

StatelessREST is by definition a stateless protocol, which implies greater

simplicity in topology design. There's no need to maintain, replicate

or route based on state.

Ubiquitous

FoundationIt's based on HTTP, which operates on TCP/IP, which is a

ubiquitous networking topology.

Why is REST popular?

19

So how do we expose z data and services as APIs?

?

Can we do this today?

CTG or CICS SOAP/JSON

Webservices

IMS Mobile Feature Pack

DB2 JSON

CICS

IMS

DB2

MQ

WASJAX RS

Broker

Can we do this today?

CTG or CICS SOAP/JSON

Webservices

IMS Mobile Feature Pack

DB2 JSON

CICS

IMS

DB2

MQ

WASJAX RS

Broker

Completely different

configuration and management

Can we do this today?

CTG or CICS SOAP/JSON

Webservices

IMS Mobile Feature Pack

DB2 JSON

CICS

IMS

DB2

MQ

WASJAX RS

Broker

Completely different

configuration and management

Multiple endpoints for developers

to call/maintain access to

Can we do this today?

CTG or CICS SOAP/JSON

Webservices

IMS Mobile Feature Pack

DB2 JSON

CICS

IMS

DB2

MQ

WASJAX RS

Broker

Completely different

configuration and management

These are typically not RESTful!!!

Multiple endpoints for developers

to call/maintain access to

POST /accounts/create + (JSON with account create information)

POST /accounts/balance + (JSON with account number)

POST /accounts/update + (JSON with account number and deposit)

A collection of individual services

REST interface is very limited, HTTP method is NOT significant.

“Good enough” for some use-cases, but falls short the expectations of REST API consumers.

A naturally RESTful API

/accounts?name=Fred + (JSON with Fred’s information)

/accounts?number=1234

/accounts?number=1234 + (JSON with dollar amount of deposit)

/accounts?number=1234

HTTP verb conveys the operation

against the resources; i.e., POST is

for create, GET is for balance, etc.

URI conveys the resource to

be operated upon; i.e., Fred’s

account with number 1234

The HTTP body encoded in JSON

carries the specific data resulting from the

action (verb) against the resource (URI)

Aligned with API consumer expectations for REST APIs

What’s in a URI ? JSON-RPC style services vs. a “naturally RESTful” API

POST

GET

PUT

DELETE

25

You need an API transformation gateway!

RESTful APIs available from

one endpoint

CICS

IMS

DB2

MQ

WAS

With sophisticated mapping

of true RESTful APIs to

existing mainframe services

and data

CICS

IMS

WAS

MQ1

DB21

REST APIconsumers

z/OS

Create and deliver natural REST APIs for z Systems assets in a unified manner across z/OS subsystems with integrated auditing, security and scalability

API Management

Mobile apps

Web apps

1 see ENUS215-493 Statements of Direction

IBM z/OS Connect Enterprise Edition

Business partner applications

Internal applications

27

Liberty z/OS

z/OS Connect EE

server instance

SoR subsystems

CICS, IMS, WAS,

DB2, MQ, …

IBM 64-bit SDK for z/OS,

Java Technology Edition

V7.1.0 or V8.0.0

z/OS Explorer Aqua V3.0

z/OS Connect EE

API Editor

Windows, Linux or OS/X with

• IBM CICS Explorer V5.3

• IBM IMS Explorer for Development V3.2

• IBM Explorer for z/OS Aqua V3.0

Runtime Server•Includes service capabilities of V1.0

•Adds the ability to hosts APIs

•Integrates with multiple z subsystems

•Liberty + z/OS Connect = “instance”

•You may have multiple instances

Tooling Platform• Integrates with an Eclipse 4.4 environments

• Defines APIs and generates SWAGGER 2.0

• Compose API mapping models

• Deploy APIs to runtime server

• Export API archive for other tools to deploy

1

2

IBM z/OS Connect Enterprise EditionTwo parts to every story

28

Data mapping

Overview

© 2016 IBM

Corporation

29

Data mapping

A closer look

© 2016 IBM

Corporation

30

You’ve chosen a z/OS asset you want to expose as a RESTful endpoint.

Six Steps to Expose a z/OS Asset

Starting point

© 2016 IBM

Corporation

31

Install, set up, and start your new z/OS Connect EE server.

ibm.biz/zosconnect-start-server

ibm.biz/zosconnect-installation

Six Steps to Expose a z/OS Asset

1. Install z/OS Connect EE

© 2016 IBM

Corporation

32

ibm.biz/zosconnect-cics-service-definition-utility

Use a system-appropriate utility to generate a .sar file for the z/OS asset.

(This process also creates schema artefacts used in Step 5.)

ibm.biz/zosconnect-ims-service-creation

For you to start mapping an API, z/OS Connect EE needs a representation of the underlying z/OS asset: a Service Archive file (.sar file).

Six Steps to Expose a z/OS Asset

2. Create your service definition

© 2016 IBM

Corporation

33

Import your .sar file into the API Editor, and start designing your API.

From the editor, create an API Archive file (.aar), which describes your API and how it maps

to underlying services.ibm.biz/zosconnect-create-api

Six Steps to Expose a z/OS Asset

3. Create your API

© 2016 IBM

Corporation

34

Configure the system-appropriate service provider to connect to your backend system in your server.xml.

ibm.biz/zosconnect-configuring

Six Steps to Expose a z/OS Asset

4. Configure your service provider

© 2016 IBM

Corporation

35

(This step uses the artefacts generated with the .sar file in Step 2.)

Deploy the JSON schema and bind files generated by the service definition utility to zFS. Configure the service definition in your server.xml.

ibm.biz/zosconnect-define-services

Six Steps to Expose a z/OS Asset

5. Deploy your service

© 2016 IBM

Corporation

36

Deploy your API using the right-click deploy in the API Editor,or by copying the .aar file to the drop-ins folder.

ibm.biz/zosconnect-deploy-api

Six Steps to Expose a z/OS Asset

6. Deploy your API

© 2016 IBM

Corporation

37

Your API is ready to be consumed: go tell your developers!

Six Steps to Expose a z/OS Asset

Done.

© 2016 IBM

Corporation

38

API ManagementSecure, scale, manage, monitor, and socialize APIs

API Management

• APIs hosted on a zEE server are not “managed”, therefore an API

management (APIm) solution should be used.

• IBM APIm enhances zEE APIs with the following capabilities:

– Secure and scale• manage access to APIs by using API keys and secret keys.

– Manage and monitor• extract API usage and analytics data to quickly react to new opportunities.

– Administration portal• self-registration, quotas, key management and security policies.

– Developer portal• engage application developers and foster use of published APIs.

• customize with branding to advertise, market, socialize and sell APIs.

40

41

A zEE API can be imported into APIm by referencing its

Swagger definition that is hosted on the zEE server.

42

Provide the location of the Swagger definition

on the zEE server.

43

The Swagger definition is parsed and shown

for confirmation.

44

The zEE API is now imported into APIm

and can be managed.

How do I get started?

45

IBM apiconnect

on prem

IBM apiconnect

z/OS Connect

Enterprise Edition

All set - Get connected!

ADDI

z/OS Connect EE pricingInstance based pricing model

48

z/OS Connect EE introduces an innovative new pricing model

on z Systems.

“per instance” pricing metric

•Based upon the maximum number of active concurrent

address spaces

•Tiered usage bands

•provides increasing value as the size of an overall

deployment rises; low cost of entry for small projects

•Auditing is required through SMF89-2 records

•hourly snapshots of the number of concurrent instances,

reports created with utility IFAURP

What about pricing?A new approach

49

Number of

Simultaneous Instances

VUs per Simultaneous Instance

1 to 4 1 VU per Simultaneous Instance

5 to 10 4 VUs + 0.6660 VUs per Simultaneous Instance > 4

11 to 20 8 VUs + 0.4000 VUs per Simultaneous Instance > 10

21 to 40 12 VUs + 0.2000 VUs per Simultaneous Instance > 20

41 to 100 16 VUs + 0.0660 VUs per Simultaneous Instance > 40

101 to 250 20 VUs + 0.0260 VUs per Simultaneous Instance > 100

251 to 500 24 VUs + 0.0160 VUs per Simultaneous Instance > 250

501 to 1000 28 VUs + 0.0080 VUs per Simultaneous Instance > 500

1001 to 3000 32 VUs + 0.0020 VUs per Simultaneous Instance > 1000

>3000 36 VUs + 0.0007 VUs per Simultaneous Instance > 3000

What about pricing?Value Unit exhibit VUE037 (see announcement letter ENUS215-493)

Summary

Evolution of z Asset Integration Capability

Messaging or EAI (MQ)

Enterprise Service Bus(IIB)

API Management

z/OS Connect EE

• Reliable messaging and Transactional invocations of applications, • However, point-to-point hard-coded (adhoc) integration; Lacks agility, and results in complex

integration topology• Asynchronous messaging; Lacking a service view as a request and a response are modeled as separate

messages

• Promotes Service reuse and productivity gain; Business and IT function alignment• Tooling for creating and integrating services; Transformation in ESB for matching client application

needs• Service registry for look up and governance; Policy based control; Loose coupling and flexible

deployment of services• However, lacks consumability and support for client entitlement, and easy set up for external

invocations• Manual mapping required for COBOL Copybook transformation (without z specific tooling)• Inherent complexity due to required round-tripping across app and integration developers

• Simpler (consumable) REST based interfaces and meaningful Swagger based business APIs relating multiple transactions under a single API as operations on a business entity

• Improved consumability with browsable catalog and subscription support• Improved control for enforcing client entitlements (and Insight with usage analytics); Accountability

and support for chargeback• Complements existing SOA investment with improved consumability, control and insight• Support for “Create” and “Run” of Interactive APIs with visual composition tools • Support for API Governance, and developer portal for consuming app developers• z/OS Connect EE makes it very easy to “Create” and “Run” System APIs from z Assets

*Transportation via Planes, Trains & Automobiles can coexist, though not an apt analogy

All three types of integration capabilities may sometimes co-exist* in a single customer environment

•

Analytics run on SoR system for optimal performance

and security

IMS

WebSphere

DB2 An

alyt

ics

System of Record

CICS

Web Services

ESB (IIB)

COBOL

CPYBOOKWeb Services,

Others…

REST APIs

(Open APIs)

REST

RESTREST

Existing SOA Client

Applications

** Other forms of messaging based

integration capabilities may also be

present

*New Managed,

Composite and/or

Systems APIs

REST APIs

Incremental adoption of new z/OS Connect EE based REST APIs and/or managed APIs can co-exist with already deployed SOA based services, and other forms of integration capabilities

Web Svc

APIs

1. Existing investments over the last 10+ years in SOA can be extended with API Connect

2. Provide a first class experience in developing and managing new APIs for z applications and data

MQ, CTG, etc.

z/OS Connect EE

Exposing Mainframe-Based Assets as SOR APIs

53

IBM z/OS Connect Enterprise Edition (EE) V2.0 is the latest evolution of

z/OS Connect! z/OS Connect EE V2.0 is a priced offering, orderable via

Shopz as PID 5655-CEE.

Available now!

Announcement letter ENUS215-493

ibm.biz/zosconnect20_announce

z/OS Connect EE V2.0 includes

A dedicated Liberty profile for z/OS

• GA release includes Liberty V8.5.5.7

New Eclipse-based tooling for API composition with SWAGGER

• Delivered through IBM Explorer for z/OS V3.0 Aqua

The WOLA service provider for access to CICS and BATCH

• Including the WOLA Liberty feature

Utilities to generate service archives for use with CICS programs

• Creates JSON schemas as input for API composition

The REST client for access to “3rd party” REST services

• e.g. JAX-RS applications hosted on WAS for z/OS

IBM z/OS Connect Enterprise EditionProduct summary review

Get ahead of the game! Register your interest todayPreview potential capabilities plus the chance to give direct feedback

54ibm.biz/zosconnectopenbeta

Useful Links

• z/OS Connect EE Knowledge Center

– http://www.ibm.com/support/knowledgecenter/SS4SVW

• z/OS Connect Enterprise Edition Home Page

– http://www-03.ibm.com/software/products/en/zos-connect-enterprise-edition

• Redbook (Building an API Bridge to Your IBM z Systems Applications and Data)

– http://www.redbooks.ibm.com/abstracts/redp5296.html?Open

• z/OS Connect Tooling

– https://developer.ibm.com/mainframe/products/zosconnect/

• IBM API Connect

• http://www-03.ibm.com/software/products/en/api-connect

• EZSource

– http://www.ezsource.com

55

Notices and Disclaimers

56

Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission

from IBM.

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

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of

initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS

DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE

USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY.

IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers

have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in

which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials

and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or

their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and

interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such

laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

Notices and Disclaimers Con’t.

57

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 in connection with this publication 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. IBM does not warrant the quality of any third-party products, or the

ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual

property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,

FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,

Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,

PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,

StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business

Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM

trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

58

Madhu B.AProduct Architect

CICS TG, TXSeries

IBM India Systems

Development Lab

IBM India Pvt Ltd.

Tel: +919731800864

madhu.b.a@in.ibm.com

Thank you!

Thank You