This session will demonstrate how to use the Zowe open source framework to extend modern devops tooling and practices to the mainframe and to enhance the mainframe developer experience. A follow-up to the overview session, the hosts will drill into the Zowe architecture while demoing key capabilities including the command line interface (CLI) and API Mediation Layer. Organized by the Linux Foundation’s Open Mainframe Project, Zowe opens the mainframe to the next generation of talent. Join this interactive session to learn how to “un-silo” the mainframe to accelerate software delivery and drive true cross-platform applications.

1. Mainframe DevOps
Using Zowe Open
Source
Thursday,Apr. 11, 2019
Sponsored by

2. Panelists
Joe Winchester is an IBM Senior Technical Staff
Member working for IBM as part of the IBM Z Systems
software division. He is based in Hursley, UK. Before
joining Project Zowe where he is lead of the
Onboarders squad, Joe was the architect of IBM's CICS
Tools portfolio as well as the technical lead for the z/OS
Explorer Aqua platform. Joe has extensive experience
with open source having been a member of the Java
Community Process as well as a committer and team
lead for the Eclipse Foundation.
Michael Bauer is a Sr. Product Owner at Broadcom
responsible for the CA Brightside Command Line
Interface (CLI) which was recognized as the Most
Innovative DevOps Solution of the Year for 2018 by
DevOps.com. He is also the squad lead for the Zowe
CLI component of Zowe, the first open source project
based on z/OS. Before transitioning into a product
management role, Michael was a developer for
traditional mainframe system applications. He is based in
Pittsburgh, Pennsylvania.

3. Agenda
• Zowe overview
– Introductory webinar available on demand @ DevOps.com, 3/28
• API Mediation Layer introduction and demonstration
• Command Line Interface introduction and demonstration
• Q & A

4. Open source mainframe interface for
the next generation
ABOUT ZOWE
• Part of Linux Foundation’s Open
Mainframe Project (OMP)
• First open sourced project based on
z/OS
• Four main components:
• Command line interface (CLI)
• API mediation layer
• Web UI
• Microservices
• Initial contributions from IBM,
Broadcom, Rocket
• Over 2,500 downloads
• v1.0 released February 11th
• Zowe.org
ü Bridges enterprise devops to the mainframe
ü Shifts the mainframe balance of power from
vendors/proprietary to community/OSS
ü Makes mainframe an exciting career choice

5. Zowe Framework and Ecosystem at a Glance
• Core Zowe includes API
Mediation Layer, CLI, and Web
Desktop.
• Vendors can build ‘Zowe
Compliant’ plugins that will
leverage this framework.

6. Zowe/Brightside association
CLI
APIML
VS Code extension

7. 7
Server A
TSO
Server B
REST API
Server C
REST API
Server D
Web
Server E
Client A
3270
client B
HTML
Client C
Command
Line
Client D
Another
HTML
Client E
Telnet:23
HTTPs:32070
HTTPs:1234
HTTPs:26504
HTTPs:8080 To configure the PC each
client must know the
port for each server
• If ports change all
clients need
reconfiguring
• Clients need to be told
about the existence of
new servers
• Host network stack
must expose each
server’s port
increasing attack
surface
Why do I need an API gateway ? - endpoint consolidation

8. 8
Server A
TSO
Server B
REST API
Server C
REST API
Server D
Web
Server E
Client A
3270
client B
HTML
Client C
Command
Line
Client D
Another
HTML
Client E
Telnet:23
HTTPs:32070
HTTPs:1234
HTTPs:26504
HTTPs:8080
Why do I need an API gateway ? - credential challenges
Each server has to
independently
authenticate each client
• Poor usability with
repeated password
challenges
• Persistent passwords
vulnerable to attack
vector by theft from
weakest usage

9. 9
Server A
TSO
Server B
REST API
Server C
REST API
Server D
Web
Server E
Client A
3270
client B
HTML
Client C
Command
Line
Client D
Another
HTML
Client E
Telnet:23
HTTPs:32070
HTTPs:1234
HTTPs:26504
HTTPs:8080 Different server
endpoints present
different certificates
• TLS Certificates need
independent trusting
by the client
• Server certificate
consolidation
difficulties lead to self
signed and cross
signed certificate
proliferation
• Cross origin signing
and cross site errors
Why do I need an API gateway ? - certificate management

10. 10
Server A
TSO
Server B
REST API
Server C
REST API
Server D
Another
Server E
Why do I need an
API gateway ?
• Smooth user experience
• Single credential
challenge
• Client has to
accept/manage single
certificate
• Client must know the
port for one server
• Decreased attack surface
• No CORS
Client A
3270
client B
HTML
Client C
Command
Line
Client D
Another
Client E
API Gateway
TSO:23
Socket:44
HTTPs:1234
HTTPs:8080
SOAP:10
Why do I need an API gateway ?

11. API Gateway
API
Catalog
API
Discovery
MVS
UI
JES
UI
USS
UI
File
API
JES
API
7554
7552 7553 8547 8545 8548 8546 8550
TN327
0
VT
ZLUX
8544
zssServer
8542
ZWESIS01
X-MEM
z/OSMF
In progress
What is the Zowe API Mediation Layer ?
REST APIs
Workflows
TSO Commands
MVS Commands
Files, USS, JES
7443
MVS Explorer JES Explorer USS Explorer
Zowe Desktop
TN 2170VT Terminak
CLI
Zowe API ML
• Gateway is single
access endpoint
for z/OS services
• API Catalog visual
rendering of
Swagger/open API
and availability
• Discovery service
registers API
instances
• Provides HLA and
API workload
balancing

12. API Gateway
API
Catalog
API
Discovery
MVS
UI
JES
UI
USS
UI
File
API
JES
API
7554
7552 7553 8547 8545 8548 8546 8550
TN327
0
VT
ZLUX
8544
zssServer
8542
ZWESIS01
X-MEM
z/OSMF
In progress
Extending Zowe API gateway services ?
REST APIs
Workflows
TSO Commands
MVS Commands
Files, USS, JES
7443
MVS Explorer JES Explorer USS Explorer
Zowe Desktop
TN 2170VT Terminak
CLI
Existing
z/OS
Address
space with
REST API
New
REST API
Static
Registration
Dynamic
Discovery with
Springboot Eureka
xxxxyyyy
Extending the
API gateway ?
• Static definition of
existing REST API
• Dynamic Discovery
with Springboot
Eurka
z/OS
Address
space
TSO
Socket

13. API Mediation Layer Summary
• A scalable, highly available, lightweight mediation layer for all service-oriented
REST APIs, originating from the mainframe platform.
• Enables a single point of access to multiple mainframe service APIs and offers
enterprise cloud-like features such as high-availability, scalability, dynamic API
discovery, consistent security and documentation
• Extensible for existing z/OS servers to surface their APIs and benefit from SSO,
single certificate, simplified client configuration management, growth into
integrated server to server scenarios.
• Futures to include more z/OS subsystem APIs unlocking more of the platform

14. Zowe CLI
• A robust, extensible, cloud-like Command Line Interface into the mainframe
platform.
• Enable developers and DevOps engineers to control, script and develop on
the mainframe like any other cloud platform and allow them to make use of
familiar, industry-standard, open-source tooling. By accomplishing this, Zowe
CLI:
– Addresses the skills gap by making mainframe development more attractive and
accessible to next-generation developers
– Improves the application delivery lifecycle by allowing mainframe applications to be
integrated into enterprise DevOps pipelines

15. Challenge

16. z/OS Command Groups & Plugins
• Zos-files – datasets and USS files
• Zos-jobs – submit jobs, retrieve results, and more with JES
• Zos-console – issue z/OS Console commands
• Zos-tso – issueTSO commands
• Provisioning – provision on-demand dev-test environments
• Zos-workflows – create and manage z/OSMF workflows
• Db2 – run stored procedures, create synthetic data, extract and copy tables
• CICS – deploy and activate COBOL CICS programs and transactions
• IMS – deploy and activate IMS programs and transactions

17. Demo - CLI
• Introduce Zowe Command Line Interface and show interactive use
• Demonstrate how commands can be used with modern scripting languages to
build automation for z/OS
• Demonstrate how the CLI can be used with modern frameworks to abstract
commands into tasks that provide even greater value
• Show how the CLI enables the use of popular CI/CD orchestration tools for
mainframe applications

18. Q&A
• To learn more and get started, visit zowe.org
• Next webinar in this series, Extending API-first to the Mainframe (dateTBC)
Joe Winchester:WINCHEST@uk.ibm.com
Mike Bauer: michael.bauer2@broadcom.com