IBM Z for the Digital Enterprise 2018 - Automate Delivery Pipeline

IBM Z / © 2018 IBM Corporation
Automate Delivery
Pipeline
Suman Gopinath
Solution Architect, DevOps for Z
Enterprise
IBM Z for the Digital Enterprise
Hyderabad
January 2018

Disclaimer
 IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without
notice and at IBM’s sole discretion.
 Information regarding potential future products is intended to outline our general product direction and it
should not be relied on in making a purchasing decision.
 The information mentioned regarding potential future products is not a commitment, promise, or legal
obligation to deliver any material, code or functionality. Information about potential future products may not
be incorporated into any contract.
 The development, release, and timing of any future features or functionality described for our products
remains at our sole discretion.
 Performance is based on measurements and projections using standard IBM benchmarks in a controlled
environment. The actual throughput or performance that any user will experience will vary depending upon
many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the
I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be
given that an individual user will achieve results similar to those stated here
2IBM Z / © 2018 IBM Corporation

Emerging technologies drive business transformation
Cloud
60% of banks process
most transactions
in cloud by 2016
Collaboration
60 million US
households conducting
P2P payments
Big Data
2.5 billion gigabytes of
data generated every day
Intelligent/
Connected
Systems
7.9 million in U.S.
adopted NFC e-
Wallets
Mobile
35% transaction growth
driven through mobile
annually through 2017
Analytics
Moving to real time
+7.6% in customer lifetime
value for firms using
engagement analytics
$226B – annual cost of
health care fraud
Security
$5.65 million – average cost
of a security breach in the US

Delivering Business Capability: Hybrid Applications, Hybrid
Platforms, Hybrid Teams
4
Development SCM Build Package
Repo
Deploy
Repo
Deploy
Repo
Deploy
Repo
Deploy Test Stage Production
Application N
Application C
Application B
Application A
Enterprise
Release
Business
Capability

What is DevOps
Continuous
Customer Feedback
& Optimization
Collaborative
Development
Continuous
Monitoring
Continuous Business Planning
Continuous
Testing
Operate Develop/
Test
Deploy
Steer
DevOps
Continuous
Feedback
Culture
Foundational
values and
principles
Think
Conceptualization
refinement, and
prioritization of
capabilities Code
Generation,
enhancement,
optimization and
testing of
features
Deliver
Automated
production and
delivery of offerings
Run
Services, options,
and capabilities
required to run in
the Cloud
Manage
Ongoing
monitoring,
support, and
recovery of
offerings
Learn
Continuously learn
based on
outcomes from
experiments
Continuous Release& Deployment
Accelerate
software delivery –
for faster time to value
Balance speed, cost,
quality and risk –
for increased capacity to
innovate
Reduce time to customer
feedback – for improved
customer experience
Process
Culture
Technology
Enterprise capability for continuous software delivery and
management that enables organizations to innovate rapidly
to capitalize on new market opportunities, and reduce the
cycle time to collect and react to customer feedback
Lean and
Agile principles
Analytics & Cognitive

DevOps Transformation
 Breaking down the barriers between teams
 Creating cross functional teams across the application space
 Includes all platform types
– One part of an application process can’t be fundamentally different and move at the speed of business
– No reason the mainframe can’t be as agile or DevOps as the rest
 Start with the biggest business problem and a single team to show value then grow

Mainframe Specific Challenges
7
 Long time stable development and deployment process – it has worked for years
 More mature development organization – comfortable with existing tools and processes
 Highly integrated, monolithic applications
 Limited test environments
– Static hierarchy
 Limited Automated testing

End to End Strategy
 End to End strategy sets direction for steps along the way
 Single DevOps pipeline or as close as possible improves collaboration and reduces friction between teams
8
Workitems/Planning
Build artifact repository
Pipeline Automation
Deployment
Build
IDE, Unit Test, Code Rules
Release Management
Environment Provisioning
Testing tools, Test Data ManagementCode quality, Security

What does an Automated Delivery Pipeline involve?
A Robust and Agile change management system
A Modern Development Environment
An Infrastructure that allows IT teams to spin-up and bring down flexible environments to run their individual changes
Automated Tests
Gating mechanisms and Quality checks at each stage of development
A Versioned Deployment mechanism to ensure that the right code moves to production at the right time.

About JKE Bank (Fictitious Bank – Not real)
 JKE Bank is a Multi-national bank, headquartered in
the United states and branches across the world
including their branches in India.
 Among the major businesses, JKE Bank supports
home mortgages.
 JKE Bank has been in this business for many many
years and is known to be very customer friendly.
 JKE Bank provide multi channel interface, through a
terminal , web page or Mobile App.
 JKE Bank has a facility for interested clients to
check the monthly mortgage value (EMI) for a loan
they are planning for.

JKE Bank Software
 JKE Bank application has evolved over the years and has
been built on IBM COBOL and CICS software and hosted
on IBM Z.
 JKE bank has always been ahead on the technology curve
and has a hybrid cloud environment using born on the
cloud applications for systems of engagement, REST APIs
for integration and agile across cloud as well as Z
application assets.
– They have an Automated Delivery Pipeline that allows
them to respond to market needs instantly.
 For instance, their software stack involves,
– IBM CICS 5.4, COBOL v6, DB2
– z/OS Connect v2 , IBM API Connect, and ADDI
– Enterprise DevOps tools supporting Continuous
Integration and Continuous Delivery

Story Board : Mortgage Calculator
 JKE Bank is known across the world for providing the
best benefits and experience for their clients.
 This continues to give them the edge over other
competitors and continuously attract new clients and
grows their business.
 In a recent off-site, the leaders come across an idea to
extend more value to clients by discounting mortgage
charges to clients with good credit scores.
 Leadership team loves the idea as it’s a win-win for the
bank and the client . They however need this done
ASAP to reap the benefit of a property show event that
can add many new clients…
 Leadership team asks support of LoB leader, John to
get this done in time for the property show.

All of them Agree that this indeed can be achieved in time …
Pari & Kunal take it over to the teams and the work begins….
Tanuj the Project Lead is in charge and Bob is the developer in the project ..
Story Board – Mortgage Calculator
John, the LoB Leader
Kunal, Cloud Architect
Pari, Enterprise Architect
“Equally good on backend ,
ADDI will help understand
where to change, what to test“
.. with zCEE we can invoke
APIs from our CICS APP.. “Our
automated CICD pipeline will
ensure quick build and deploy. I
will work with the team
“Should be a
simple change on
the front end and
should be quick
redeploy with Cloud
as well”

Bob
Application Developer
14
Goals
• On-time delivery of project and tasks
• Quality of deliverables
• Communication and Collaboration with
stakeholders and team members
Productivity
• Ability to learn new technologies and
understand business needs
Challenges
• Deal with delays and bottlenecks across the software
delivery lifecycle caused by lack of automation, standard
processes, parallel projects and Sev 1 issues from
Operations
Communicate effectively with clients and co-workers;
working remotely with colleagues.
• Work with multiple tools across multiple projects.
• Create and consume documentation across the
team especially due to existing insufficient documentation
on legacy code
• Grapple with multiple integration methods across
applications during the translation of design to code
Limit time to learn new tools or technologies.
Pari
Enterprise Architect
Goals
• Align IT investments to business
priorities, leveraging an IT architecture
strategy and roadmap.
• Drive collaboration between business
owners and IT infrastructure managers
to promote simplification, efficiency and
cost reduction.
• Develop and enforce standards,
manage the lifecycle of application
portfolio and evaluate/introduce best
practices.
Challenges
• Maintain project scope and timelines.
• Balance time spent on business strategy against demands
from the IT organization.
• Find ways to make data and information actionable for
senior leadership.
• Ensure new and existing IT components will support future
business demand and roadmap goals.
• Acquire a deep technological perspective to support
changes brought by digital technologies.
• Balance long term quality versus quick and low-cost.
• Handle the growing complexity of data architecture and
data security issues that stem from digitalization and
mobility.
• Contend with tools for mobile and cloud that are still
immature and may not support the enterprise architecture
very well

DEMO

What does an Automated Delivery Pipeline involve?
A Robust and Agile change management system
A Modern Development Environment
An Infrastructure that allows IT teams to spin-up and bring down flexible environments to run their individual changes
Automated Tests
Gating mechanisms and Quality checks at each stage of development
A Versioned Deployment mechanism to ensure that the right code moves to production at the right time.

Deploy to all Z environments
COBOL, PL/I, C++, Java,
EGL, Batch, Assembler
IBM Z
IMS
MQ
DB2
CICS
WAS
RTC RIT
UCD
IDz
DT
z/OS Connect EE
z/OS
Rational Team Concert
Solid line : Development
Gray line : Continuous Integration & Test
Collaboration
Change
Management
Planning
CICD Pipeline and Integration Architecture
Source Code
Config
Mobile/Tablets
External APIs
Consume
External
APIs
Expose existing assets
as APIs for Mobile
Applications
UrbanCode Deploy
Rational Functional
Tester
Invoke Testcases
Update Workitems
Invoke CI Deploy Pipeline
Test Scripts
X86 PC or HX5 Blade
running Linux
COBOL, PL/I, C++, Java,
EGL, Batch, Assembler
MQ
IMS DB2
CICS
WAS
RTC RIT
UCD
IDz
DT
z/OS
z/OS Connect EE
zD&T
Requirements
Application
Discovery and
Delivery
Intelligence
IBM Developer
for z Systems
(IDｚ,
former RDz)
Code
Coverage
Code
Review
Code
coverage
Info from Builds
Application
Understanding
Impact Analysis
Discovery
and Analysis
Source, Unit Testcases SonarQube
SonarLint
z/OS Connect EE

Trademarks
Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations
such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements
equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance
characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business
contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the 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.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.
This information provides only general descriptions of the types and portions of workloads that are eligible for execution on Specialty Engines (e.g, zIIPs, zAAPs, and IFLs) ("SEs"). IBM authorizes customers to use IBM SE only to execute the
processing of Eligible Workloads of specific Programs expressly authorized by IBM as specified in the “Authorized Use Table for IBM Machines” provided at www.ibm.com/systems/support/machine_warranties/machine_code/aut.html (“AUT”). No
other workload processing is authorized for execution on an SE. IBM offers SE at a lower price than General Processors/Central Processors because customers are authorized to use SEs only to process certain types and/or amounts of workloads as
specified by IBM in the AUT.
* Registered trademarks of IBM Corporation
The following are trademarks of the International Business Machines Corporation in the United States and/or other countries.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a Registered Trade Mark of AXELOS Limited.
ITIL is a Registered Trade Mark of AXELOS Limited.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VMware, the VMware logo, VMware Cloud Foundation, VMware Cloud Foundation Service, VMware vCenter Server, and VMware vSphere are registered trademarks or trademarks of VMware, Inc. or its
subsidiaries in the United States and/or other jurisdictions.
Other product and service names might be trademarks of IBM or other companies.

Modern Development Environment
21
 Provide a modern development environment (IDE)
 Includes capabilities such as code rules, unit test, program understanding, debug
 Start requiring the use of code rules and unit test to help push the use of the modern environment
 Understand developers will need time to learn and will need training
 Provide training and support as teams transition

Shift Left and Automated Testing
22
 Automated testing critical to DevOps pipeline
 Multiple testing tools will be used due to platform differences
 Multiple types of automated testing, unit, function, regression
 With limited existing automated tests building up a regression bucket can be seen as a challenge
– Will take a concentrated effort
– Build interface tests to cover a large percentage of the application – Test at the boundary from the front
end or mid tier
– Use Code coverage to understand what has been tested

Code Quality Scanning and Unit testing
23
 Add code rules scanning to the standard process – relatively easy to add, step to understand where you are
with your code
 Should be automated the same way your distributed scanning is done
 Start requiring Unit tests for new code and code changes
 Think of what a Unit is for your z/OS application
– It could be a program or a transaction – COBOL and PL/I are not Java the unit will vary
 With a modern SCM
– require check before delivery to shared development stream or branch
– check in test cases along with source code

Test Environments
24
 Developers need isolated test environments for the team generally
– Perform unit tests without interference from other teams
– Have the ability to restore data easily for testing
 Pipeline needs it’s own test environment to run automated tests
– As you build a pipeline the process needs to be able to have isolated environments with ability to set
data to run automated tests and validate results before moving forward
 Standard process should be to provision environment as part of pipeline and give it back at the end of the
test
 This can be on existing systems in isolated regions and data base or separate LPAR or use of zD&T
 Need a deployment methodology that allows the deployment to new environments that can also be used to
deploy to production

Modern SCM and Build Capability
25
 Mainframe Library managers isolate the traditional z/OS development teams
 Harder to easily change the build process for new actions such as code coverage
 Harder to integrate into pipeline
 No branching or stream capability, limited parallel development
 No easy way to build on alternative environments, including zD&T
 Modern SCM provides all the capabilities for all artifact types, including service definitions and test cases
 Provides process enforcement

IBM Z for the Digital Enterprise 2018 - Automate Delivery Pipeline

More Related Content

IBM Z for the Digital Enterprise 2018 - Automate Delivery Pipeline