z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and...

47
© Copyright IBM Corporation 2016. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM. Clearing the Fog: Understanding z Systems Cloud Technology Options Glenn Anderson IBM Lab Services and Training NewEra z Exchange March, 2016

Transcript of z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and...

Page 1: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

© Copyright IBM Corporation 2016. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.

Clearing the Fog: Understanding z Systems Cloud Technology Options

Glenn Anderson IBM Lab Services and Training

NewEra z Exchange March, 2016

Page 2: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

2

Cloud computing is a model for service delivery

Page 3: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

What do people mean when they say “cloud computing?”

§ Cloud computing is a model for service delivery

•  Where is the service coming from? (public, private or hybrid)

•  What kind of service is it? (IaaS, PaaS, SaaS) •  Which characteristics of the cloud service delivery model

are important to you? (what is the problem you are trying to solve?) -  On demand self-service -  Broad network access -  Resource pooling -  Rapid elasticity -  Measured service

3

Page 4: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Mainframe and public cloud

§ What does it mean? – You are choosing to move some/all of your current mainframe

workload to a public cloud service provider. It could also mean new workloads that could have been run on the mainframe will be run by a public cloud service provider instead.

§ Why would you do it? – Someone thinks it will save money

– Move your workloads off of your own z Systems mainframe to one owned by a public cloud service provider

– Someone thinks the mainframe is dead

4

Page 5: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Mainframe and private cloud

§ What does it mean? – You want to use the mainframe to deliver service to your

enterprise using the characteristics of the public cloud service delivery model. These services could be IaaS, PaaS, SaaS, etc……

§ Why would you do it? – To enhance your service delivery to be like public cloud, while

taking advantage of the strengths of the mainframe

– To save money through server consolidation

– Because someone tells you to implement cloud in your current data center

5

Page 6: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

InfrastructureasaService

PlatformasaService

HighVolumeTransactions

SoftwareasaService

Servers Networking Storage

Middleware

Collaboration

BusinessProcesses

CRM/ERP/HRIndustry

Applications

DataCenterFabric

Sharedvirtualized,dynamicprovisioning

Database

Web2.0ApplicationRuntime

JavaRuntime

DevelopmentTooling

What type of service are you delivering?

6

Page 7: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Which of these Characteristics of Public Cloud Computing Interests You as a z Systems IT Organization?

§ On-Demand Self Service •  Pick services you need, when you need them

§ Broad Network Access •  Available over network through thin or thick clients

§ Resource Pooling •  Resources are shared, serving multiple consumers

§ Rapid Elasticity •  Capabilities provisioned, in some cases automatically

§ Measured Service •  Pay only for what you use

7

Page 8: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

IaaS with z/VM and Linux on z Systems

8

z/VM and Linux on z

Server Server Server Server

Infrastructure as a Service

8

Page 9: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Cloud Portfolio for Linux on z Systems

9

Page 10: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

PaaS and SaaS with z/OS

10

z/OS z/VM and Linux on z Server Server Server Server

Infrastructure as a Service

Platform as a Service

Software as a Service

Ser

vice

Ser

vice

Ser

vice

Ser

vice

Ser

vice

10

Page 11: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

11

z/OS and cloud characteristics

Page 12: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

12

z/OS Management Facility (z/OSMF)

Page 13: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

13

Provisioning a Liberty Server (PaaS) on z/OS with z/OSMF

Page 14: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

APIs: the building blocks for apps

14

Page 15: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

15

API economy lifecycle

Page 16: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

API economy: mainframe as a service

16

Page 17: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

17

Liberty Profile for z/OS

z/OS Connect Servlet

CICS

IMS

Batch Interceptors

Service Providers

Data Transform

1

4

RESTful JSON

3

5

6

7

8

z/OS Connect is software function that runs in Liberty Profile for z/OS.

z/OS Connect is described and configured in the Liberty server.xml file

z/OS Connect is designed to accept RESTful URIs with JSON data payloads

A ‘Service Provider’ is software that provides the connectivity to the backend system

server.xml

2

One part of z/OS Connect is a servlet that runs in Liberty Profile z/OS.

z/OS Connect provides the ability to transform JSON to the layout required by backend

‘Interceptors’ are callout points where software can be invoked to do things such as SAF authorization and SMF activity recording

Initially the backend systems supported will be CICS, IMS and Batch

1

2

3

4

5

6

7

8

What is z/OS Connect?

Page 18: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

18

RESTful Services

Stands for Representational State Transfer … this is a protocol built on HTTP, using HTTP verbs (GET, PUT, POST, DELETE), where the URI indicates the service requested:

https://mysite.com/CustomerApp/getCustomer?cn=1234

URI = Uniform resource identifier

Page 19: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

19

JSON – JavaScript Object Notation It is a way of passing data back and forth as a series of name/value pairs.

https://mysite.com/CustomerApp/update?cn=1234

URI = Uniform resource identifier

{ "firstName": "John", "lastName": "Smith", "age": 25, "address": { "streetAddress": “1234 Main Street", "city": “Anytown", "state": "NY", "postalCode": "10021-1234" }, }

The data being passed in is appended to the URI and passed in to the server

JSON can be passed back to the client as well.

Page 20: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

IBM z/OS Connect Enterprise Edition V2.0

13 © 2015, IBM Corporation

High-Level Overview of z/OS Connect EE V2.0

Liberty z/OS

z/OS Connect EE V2.0 Server

Backend Systems(CICS, IMS, DB, etc.)

• IBM z/OS 2.1 or higher

• IBM 64-bit SDK for z/OS, Java Technology Edition V7.1.0 or V8.0.0

Eclipse

z/OS Connect EE V2.0 Tooling

• Windows or Linux• IBM CICS Explorer V5.3• IBM IMS Explorer for Development V3.2• IBM Explorer for z/OS Aqua V3.0

Runtime Server• Runs on Liberty z/OS• Hosts APIs you define to run in it• Connects with backend system• Liberty + z/OS Connect = “instance”• You may have multiple instances

Tooling Platform• Integrates with an Eclipse environment• Define APIs• Define data mapping• Deploy APIs to runtime server• Export API archive for other tools to deploy

1

2

Overview of z/OS Connect EE V2.0

Page 21: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

IBM z/OS Connect Enterprise Edition V2.0

19 © 2015, IBM Corporation

Discoverable APIs with Swagger 2.0

z/OS Connect EE V2.0

Server Instance

Swagger 2.0

Support

/API_one/API_two:/API_99

Configured APIs

IBM API Management

Any Swagger-

compatible

function or device

Swagger UI

Function

“Standard*” Swagger API

description

document

The inclusion of Swagger 2.0 support in z/OS

Connect EE V2.0 makes exchange of API information

standardized, which provides compatibility with a

wider set of devices and functions

* An emerging accepted industry standard, but not an official open standard

z/OS Connect

EE V2.0 Tooling

Tooling also produces

Swagger 2.0 for use

by z/OS Connect EE 2

Runtime environment

Client developers

Discoverable APIs with Swagger 2.0

Page 22: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

MobileFirst and z/OS Connect

2. The mainframe and mobile computing

§  z/OS Connect – a single gateway for mobile connectivity – provides protocol conversion

§  Ships with WebSphere on z/OS, CICS and IMS – at no additional charge

§  Integrated into z/OS services (e.g., WLM, SMF, etc.)

WOLA

REST / JSON

z/OS

WAS

z/OS

Batch

z/OS

CICS or IMS

z/VM

Linux

MobileFirst Platform

Foundation Server

REST JSON

z/OS

z/OS Connect

22

Page 23: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

23

IBM API Management

Page 24: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

24

Get started with API Management

Page 25: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

© 2016 IBM Corporation

CICS ®

IMS™

WebSphere ®

DB2 ®

StrongLoop runs on-prem (using Linux on z Systems), in the cloud (via Bluemix), as well as other distributed pla?orms

MobileFirstPla2orm(cloud)

Serving mobile data directly from z/OS is 40% less expensive than exporDng to a system of engagement

z/OS Connect EE and

LoopBack Connector

API

API API

MobileFirstPla2orm(on-prem)

API

API API

AddiDonal enterprise APIs

AddiDonal enterprise APIs

25

MobileFirstPla2orm(on-prem)

API

API API

Node.js is 2x faster on z13 vs Haswell

ColocaDon of Node.js on Linux with z/OS cuts response Dmes by 60% and improves throughput by 2.5x

API Connect

API Connect

z Systems and the API Economy

Page 26: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

26

z/OS Client Web Enablement Toolkit

Page 27: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Cloud Services provided by z Systems

27

z/OS z/VM and Linux on z Server Server Server Server

Infrastructure as a Service

Platform as a Service

Software as a Service

Ser

vice

Ser

vice

Ser

vice

Ser

vice

Ser

vice

27

WLM Parallel Sysplex Sysplex Distributor Middleware as a service

PR/SM

Page 28: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Mainframe and hybrid cloud

§ What does it mean? – You want to combine the strengths of the mainframe with the

benefits of the public cloud service delivery model

§ Why would you do it? –  Offers a mix of on and off premises – the best of both worlds

–  To use public cloud services in a “Fit for Purpose” model that follows the “Systems of Engagement” and “Systems of Record” architecture

– Because it sounds like a cool thing to do

– As a compromise between an all public cloud strategy and your current mainframe-based environment

28

Page 29: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

The hybrid cloud reality

Hosted Private

Trad Hosting

Public

SaaS App

Private Cloud

“Hybrid” Data Center

On-premises Off-premises 29

Page 30: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

30

Hybrid cloud service delivery model

Page 31: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

31

Hybrid cloud example: Adding a loyalty program

Page 32: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

32

Loyalty program separation

Page 33: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

33

z Systems Hybrid Cloud Example

Page 34: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

34

The mainframe and IBM Bluemix

Page 35: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

35

What is IBM Bluemix?

Page 36: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

36

Bluemix services and APIs

Page 37: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

37

Connecting Bluemix to z/OS

Page 38: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Hybrid cloud: z/OS Connect and Bluemix

38

Page 39: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Containers

§  Container technology provides an easy way to make applications more mobile in a hybrid cloud

§  Containers are much smaller in size than virtual machines

§  Containers provide more freedom in placing workloads

§  Container technology will be integrated in OpenStack

§  Docker is a consumer of containers

39

Page 40: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

40

The Open Container Project

Page 41: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

*

DevOpsHybridCloud:DockerArchitectureonzSystems

Applica@onandrun-@medeployment

Container technology provides an easy way to make applications more mobile in a hybrid cloud

Page 42: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

42

Virtualization options and Docker on z Systems

Page 43: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

43

Docker containers on Bluemix

Page 44: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

44

The cloud service delivery model……

Page 45: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Things to Remember…….

§ What is the problem you are trying to solve?

§ What is meant by “We should be doing cloud computing?” (ask the three questions)

§ Focus on the future directions of cloud: hybrid

cloud, containers and the API economy.

§  z Systems can provide cloud-like service delivery if that is what your business requires.

§ Make sure you, and z Systems, are a part of the cloud conversation at your shop.

45

Page 46: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

Don’t Let the Cloud Fog Your Vision!

46

Page 47: z cloud tech options handout · runs in Liberty Profile for z/OS. z/OS Connect is described and configured in the Liberty server.xml file z/OS Connect is designed to accept RESTful

47

ibm.com/training/events