© 2017 IBM Corporation

St Louis CMG

Modernizing and Managing Enterprise Applications in the API EconomyChris Walker – Offering Manager, IBM z Systems Monitoring

January 2017

Abstract

Businesses are realizing that there is considerable value gained from exposing existing core applications as APIs for developers to rapidly build cloud and mobile apps. This session will explain how hybrid applications that span the enterprise from distributed to the mainframe can benefit from an end to end application performance management view, including a focus on z/OS Connect, Java workloads, as well as traditional workloads such as CICS and IMS on z Systems.

A user will simply

delete an application

that does not deliver a

satisfactory experience

3

APIs connect partners

to core business

applications, but only if

the APIs perform

The Digital Economy is forcing business to transform

A single dissatisfied

user experience can

result in significant

social impacts

Transaction Processing

Data Serving

Mixed Workloads

Operational Efficiency

Trusted and Secure Computing

Reliable, Available, Resilient

Virtually Limitless Scale

Explosion intransaction growth

driven by mobility and the

Internet of Things

Analytics is moving to real time

to capture new opportunities

at the point of impact

Hybrid cloud is the new standard

for delivering service,

agility, trust and efficiency

A user will simply

delete an application

that does not deliver a

satisfactory experience

4

APIs connect partners

to core business

applications, but only if

the APIs perform

User experience is the measure of app performance

A single dissatisfied

user experience can

result in significant

social impacts

A user will simply

delete an application

that does not deliver a

satisfactory experience

5

APIs connect partners

to core business

applications, but only if

the APIs perform

Enterprises must learn to “Innovate like a Startup”

A single dissatisfied

user experience can

result in significant

social impacts

……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/

What is the API Economy?

6

In the API economy, application programming interfaces (APIs) act as the digital

glue that links services, applications and systems. This allows businesses to

make the most of their data to create compelling customer experiences and

open new revenue channels. IBM

The API

economy is an

enabler for

turning a

business or

organization into

a platform.Gartner, Christy Pettey

June 2016 1

1 http://www.gartner.com/smarterwithgartner/welcome-to-the-api-economy/

What is meant by “API”?

7

An API is a set of commands, functions, protocols, and objects that

programmers can use to create software or interact with an external system. It

provides developers with standard commands for performing common

operations so they do not have to write the code from scratch. TechTerms.com

Where are APIs? Everywhere!

8

The Strategy is Simple…

9

Unleash Enterprise Investments to Disrupt Competitors

Existing Enterprise

IT Investments

Exposed as

APIs

Self Service

Consumed by

Developers

To Develop

Innovative

Apps

Delivering

Differentiated

Customer

Experiences

…With Hybrid Applications

z Systems is the ideal System of Record for Hybrid apps

No other platform provides the reliability, availability and performance

Secure access to mainframe data via mobile and cloud applications

Clients have built and tuned core applications on the mainframe using CICS, IMS, DB2 over many years

10

$6 trillion

in card payments

annually

30 Billion

business

transactions per day

91%

of CIOs said new

user apps access z

80 %

of the world’s

corporate data

Systems of

Record

CRM HR

DB ERP

Systems of

Engagement

Barriers to entering to the API Economy for enterprises

11

MobileFirst

Platform

(cloud)

• Skills and Development Processes• Technologies• Ease of Access• Security• Costs• Impact to Performance• Service Management!

Speed & Agility

Integration & Scale

Core Enterprise

Digital

Ecosystem

Fast

Speed

Steady

Speed

Digital Transformation through Multi-Speed IT

What does this mean to my development processes?

12

Speed & Agility

Integration & Scale

Core Enterprise

Digital

Ecosystem

Fast

Speed

Steady

Speed

Challenges with Multi-Speed IT

What business outcome is expected?

How will business & IT roles be impacted?

How to manage the consumption of APIs across the enterprise?

How to provide self-service for internal & external developers?

How to enforce security at runtime?

How to throttle and provide controlled access?

How to introduce change with new versions?

How do I know who is using my service and how much?

How much should I charge for access to my service?

13

What does this mean to my IT environment?

14

14

Partner AppCustomer App

Internal App

Partner App

Internal App

Customer AppInternal App

Partner App

Customer App

Controlling Costs!

Too much expert time is

wasted in crit-sit war

rooms!

Additional workload will

drive up our MIPS!

Training developers is

expensive!

Skills and Agility!

Our app dev team

knows Java not COBOL!

We can’t install new app

versions every week!

“They” don’t include

“us” in strategy or

architecture!

Managing Risks!

How do I know who is

calling our APIs?

How can I predict /

protect the workload?

How do I know if the

user experience is

impacted by my host

performance?

15

What scares the z team about managing hybrid apps?

Application

UnderstandingExpose APIs Consume APIs

Operational

Monitoring

Operational

Analytics

16

The Lifecycle of a Hybrid Application

Unlock the value of existing assets

• Understand the structure of your business critical applications across languages and environments

• Challenge for mainframe clients is knowing/understanding the assets already available

• Decide what has value to be exposed as an API

• Look to reduce risk and time and increase quality of changes through tooling that can identify those dependencies between assets

• Result is ability to create or refactor assets to be consumed as API’s

Application

Understanding

Create Microservices and APIs

• From the identified assets, develop microservicesthat perform a single task to interact with the System of Record

• Example: “getCustomerByID”

• These microservices can be later integrated, if needed, to form exposable APIs to end users.

• Use tooling to create the mapping from existing application endpoints into a RESTful interface

• Example: mapping a COBOL copybook into a JSON structure

Expose APIs

Surely, our clients can do this today?!

CTG or CICS SOAP/JSON Webservices

IMS Mobile Feature Pack

DB2 JSON

CICS

IMS

DB2

MQ

WAS

JAX RS

Broker

Expose APIs

Yes, but …

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

Expose APIs

A transformational gateway is required

CICS

IMS

DB2

MQ

WAS

RESTful APIs available from one endpoint

With sophisticated mapping

of true RESTful APIs to

existing mainframe services

and data

Discovery using OpenAPI

(aka Swagger)

Expose APIs

Managing APIs

The challenge:

• Who is accessing the APIs?

• Is it public? Who has keys?

• How can socialize (advertise) the APIs?

• What is the quality of service?

• Do we have traffic policy enforcement (throttling)?

• Can we meter any chargebacks?

Consume APIs

API management and orchestration

CICS

IMS

DB2

MQ

WAS

• How do you combine multiple backend services in a single useful API?

Other

Enterprise

servers

?

Consume APIs

24

Faster problem isolation with visibility into mainframe components

End-to-End monitoring of hybrid applications

• Application driven monitoring changes the focus of what is meant by acceptable performance

• Need to leverage existing investments in z monitoring and management into overall view of hybrid application

• Consistency of data between LOB Application Owner and z Operations teams

Operational

Monitoring

25

25

IT Infrastructure

Line of

Business

Application

Owner

The business

application isn’t

performing like it

should. Where’s that

infrastructure contact?

It’s probably the

mainframe.

z SME

DB2, MQ and

CICS on z/OS

are all performing

fine

DB Admin

Uh-oh! It’s a DB

lock on distributed

slowing down the

response time?

Typical hybrid app scenario with a mainframe today

X

Evolution of personas that need and use monitoring data

Application Owner z/OS Subject Matter Expert

26

27

Minimize outages with Analytics

• Real-time monitoring provides ability to manage effects on performance however there is also a need to observe and react to a bigger picture

• The impact of API usage draws in metrics from various sources:

• Traditional monitoring resource data

• Real-time feeds of SMF data and log data

• Client (mobile) connection information

• Unstructured data

• Creates a feedback loop that identifies the bottlenecks, usage levels and value of the APIs and services

Operational

Analytics

© 2017 IBM Corporation

Example Scenario:BreadBox Grocery

© Copyright IBM Corporation 2015

• Family run retail business.• Started by 2 brothers in

Ohio.• Rapid Growth via

commitment to clients and Innovation in IT.

• Global footprint. • Optimize and Innovate in IT• New Services Online fast to

reach new clients.• Leverage Social & mobile for

better client engagement• Maintain Industry

Leadership

The Story

50 years ago Today Where they want to be

• Enterprise operations - 50 states• 3 data centers in the US• 500 distribution centers• 45000 trailers & 4000 drivers• 12000 stores• Growth through acquisitions.

Drive additional sales to the stores of forgotten items

Increased customer satisfaction

What do I need? Yup, I’ve got everything I need from the Bread Box Grocery Store

Before

After

What do I need?Yes, I do need milk!

I love this app!

I’ve got everything I need including the milk!

The next morning…

I’m glad I got my milkat Bread Box!

Oh no! I forgot the milk! I need to run to another store

No milk to cry over

31

Virtual Shopping List Architecture

DP Cluster

(DMZ)

IBM

Cloudant

List Service

Mobile AppRecommendation

Service

Distribution Centers Stores

Inventory App

Store Sales AppZ/OS

Connec

t

Miki – Application Owner

32

MikiApplication Owner

• Responsible for one or more applications. Most often employee of the business unit

• Needs to ensure that applications are running and meeting SLAS.

• Looking ahead at trending and capacity planning.

• Needs to understand when problems happens if those are application or dependent component related (Middleware, Infrastructure)

Scenario

33

MikiApplication Owner

• Miki is the Application Owner for the Virtual Shopping List at Bread Box Groceries

• Miki uses Application Performance Management to monitor the overall responsiveness of the application using Synthetic Transactions

• Miki has been notified that the response time for the application is slow

• Miki logs onto the APM UI and notices that there are warning events in the application dashboard indicating that the CICS transaction used by the VSL are slow

• Miki contacts the CICS SME to let him know that the slow CICS transaction times are impacting her application

34

Virtual Shopping List Architecture

DP Cluster

(DMZ)

IBM

Cloudant

List Service

Mobile AppRecommendation

Service

Distribution Centers Stores

Inventory App

Store Sales AppZ/OS

Connec

t

35

What happens when there is a problem?

DP Cluster

(DMZ)

IBM

Cloudant

List Service

Mobile AppRecommendation

Service

Distribution Centers Stores

Inventory App

Store Sales AppZ/OS

Connec

t

??? ???

???

??? ???

Application Performance Management

DP Cluster

(DMZ)

IBM

Cloudant

List Service

Mobile App Recommendation

Service

Z/OS

Connec

t

TEPS TEMS

APM 8.1.3

OMEGAMONMonitoring APM Hybrid

Gateway

APM UI

Node.js

Node.js

DataPower

Datacenter

JVM

CICS

DB2

z/OS

36

Conclusions

The API Economy is already here

The investment already made by enterprises in z Systems needs protecting

Application-level monitoring and management is driving change

37

© 2017 IBM Corporation

Thank You

Notices and Disclaimers

39

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.

IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.”

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.

40

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.