Service Testing & Virtualization in an Enterprise Environments

1. 3370, Service Testing & Virtualization
in an Enterprise Environments
John Chewter: IBM STSM, Chief Architect
Mark Garcia: Senior Certified Executive IT Architect

2. Please Note:
1
• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice 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.

3. Outline
2
• Test Challenges in Enterprise Environment
• Overview of Product’s Mainframe Support
– IMS Connect
– CICS
– MQ/z
– DB2/z (Batch and CICS)
– JCL Batch Automation
• Typical Scenario Analysis
• Benefits & Vista
• Questions

4. Test Challenges in Enterprise
Environment

5. Multi-tier applications introduce additional complexity
Middle Tier ServerClient Tier Devices Back-end Data & Services
4
CICS
IMS

6. Only one tenth of an iceberg is visible
5
Presentation
layer
Integrations,
data and
business logic
Traditional UI testing:
Automated Integration
Testing and Service
Virtualization:
The majority of risk in modern systems is seldom tested as it is unseen.

7. • Testing beneath
the UI
• Validate side
effects
Integration Testing

8. What does an enterprise environment mean to you?
7
• An enterprise environment usually:
– Has both open and mainframe environments
involved and inter-connected together
– Distributed and inter-connected through
multiple protocols
• HTTP/JSON at front-end
• HTTP/SOAP, JMS at backend open platform
• ECI, IPIC, native link at backend mainframe
platform
– Have multiple middleware installed even
from multiple vendors
• IBM WAS, MQ, IMS, CICS, DB2
• Oracle Fusion, Database
• …

9. What challenges you encounter with development and
testing within such an environment?
8
• As a developer, I don’t like to:
– Fight with testing teams for mainframe/database
resources which are limited and usually have to be
shared
– Be asked by testing teams to produce the mighty test
data which will reproduce the defects found in testing
environment
– …
• As a Tester, I don’t like to:
– Share the same MIPS and DASD with development
team which are told have high charge back rates
– Be limited to very short testing time frames of
mainframe middleware which are part of regular
production environment
– …

10. Overview of Product’s Mainframe
Support

11. Mainframe Scenarios
10
TEST
VIRTUALIZE
VIRTUALIZE

12. CICS – Transaction Gateway Test and Virtualization
WAS (Adaptor)
Custom code (C)
Custom code (Java)
• Reduced MIP Charges
• Reduced DASD Charges
• Decoupling from mainframe during development and test
• Reduction in scheduling constraints
• Shortening the ratio between defect identification and resolution.
Motivation

13. CICS – Transaction Server DPL Virtualization
Program BProgram A DPL
• Provisioning virtual, simulated CICS regions at a fraction of the cost
• Reduction in scheduling constraints
• Ability to model and change linked programs (COMMAREA) on the fly
• Shortening the ratio between defect identification and resolution.
Motivation

14. 13
z/OS
CICS
Region J
Program
A
CICS
Region I
Program
B
IBM
RIT Agent
PROD 1 LPAR
CICS
Region A
Program
C
CICS
Region B
Program
D
PROD 2 LPAR
CICS
Region C
Program
E
CICS
Region D
Program
F
PROD 3 LPAR
(DEV)
RTCP
RIT
IBM
CICS Exit
IBM
CICS Exit
IBM
CICS Exit
IBM
CICS Exit
IBM
CICS Exit
IBM
CICS Exit
IBM
RIT Agent
IBM
RIT Agent
1
2 3 Program
F1
CICS Virtualization Distributed Program Link(DPL)
CICS – DPL Virtualization Scenarios

15. IMS – IMS Connect - Testing and Virtualization
WAS (TRMA)
Custom code (C/Java)
IMS Connect
Proxy
• Reduced MIP Charges
• Reduced DASD Charges
• Decoupling from mainframe during development and test
• Reduction in scheduling constraints
• Shortening the ratio between defect identification and resolution.
Motivation

16. COBOL - CICS – DB2 - Testing and Virtualization
COBOL- CICS
• Provide COBOL Developers with their own test data (DB2)
• Ability to test their programs more thoroughly (negative test cases)
• Reduction in scheduling constraints
• Shortening the ratio between defect identification and resolution.
Motivation

17. COBOL - DB2 - Batch Testing and Virtualization
COBOL Batch
• Provide COBOL Developers with their own test data (DB2)
• Ability to test their programs more thoroughly (negative test cases)
• Reduction in scheduling constraints
• Shortening the ratio between defect identification and resolution.
Motivation

18. PL1 - DB2 - Batch Testing and Virtualization
PL1 Batch
• Provide PL1 Developers with their own test data (DB2)
• Ability to test their programs more thoroughly (negative test cases)
• Reduction in scheduling constraints
• Shortening the ratio between defect identification and resolution.
Motivation

19. • Emulate the server application
• No changes to the client or server applications
• Distributed or Host
• Single or multiple queues
• No need to disable the server application
WebSphere MQ – Testing and Virtualization
Client Application

20. Typical Scenario Analysis

21. Customer Case I Architecture
20

22. Customer Case I Analysis
• Pain Point:
– Both the distributed MQ and backend mainframe are out of the test
cycle with its integration point, resources are limited.
• Solution:
– Build MQ virtual services that can be leveraged by front-end
applications.
–Leverage MQ/z virtualization capability to make a stub for MQ on
mainframe to serve distributed MQ requests
21

23. Customer Case II Architecture
22
Mainframe
WebSphere Application
Server
WebSphere CICS
Transaction Gateway
CICS
Region 1
Region 2
DB2/zCobol Batch
Programs

24. Customer Case II Analysis
• Pain Point:
– Insufficient number of CICS regions to thoroughly test their programs on the
mainframe
– Testing cycles were consistently delayed due to bottlenecks caused by multiple testing
and development teams vying for the same CICS region
– Costs to testing mainframe applications were spiraling out of control.
– Lack of test automation to CICS/CTG and JCL/Batch.
• Solution:
– Leverage CICS CTG virtualization capability to make automation test script and build
up stubs to virtualize dependency to CICS region
– Leverage DB2/z virtualization capability to virtualize dependency to real DB2 database
on Z.
23

25. Customer Case III Architecture
24
Logical Architecture
JES Sysout
Reports
zOS
DB2/zCobol Batch
Programs
JES Sysout
Reports
Linux RD&T
DB2/z Cobol Batch
Programs
COBOL Migration
Rational Integration Tester
(JCL Batch Execution)
JES Sysout
Reports (Deltas)

26. Customer Case III Analysis
• Pain Point:
– Customer migrated many COBOL/PL1 systems from the mainframe to RD&T (Linux).
– Issues verifying the migration process (previously, all verification was done by running
batch jobs manually on both systems)
– Costs were skyrocketing from manually testing migration process.
– Testing schedules were being prolonged
• Solution:
– Leverage Rational Integration Tester to execute JCL batch jobs on both zOS and
RD&T (Linux)
– Compare outputs from both systems and highlight differences if they exist.
– Use existing process to automate JCL Batch testing
25

27. Benefits & Vista

28. What benefits you gain when you apply these concepts
• What benefits we gained from automation test & virtualization in an enterprise
environments:
– First of all, virtualization of mainframe always dramatically decreases the
cost for extra MIPS and DASD serving for ever growing development and
testing efforts.
– Secondly, the development and test cycles are decoupled between open
front end and mainframe backend by applying virtualization to both sides.
– Thirdly, more business aligned test resources (e.g., test data) are recorded
and automatically applied to virtualization test to achieve better test case
requirement.
27

29. Questions?
28

30. Take Advantage of these DevOps Workshops
Mandalay Bay | Lagoon F

31. Don’t Miss the DevOps Zone!
Solution Center EXPO | Mandalay Bay

32. WIN a GoPro® a day!
Enter the raffle to win a GoPro ® Hero 4!
Giveaways Mondays – Wednesdays
Don’t Miss the DevOps Zone!
Solution Center EXPO | Mandalay Bay

33. DevOps Day is Tuesday at dev@!
Solution Center EXPO | Mandalay Bay

34. Notices and Disclaimers
33
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

35. Notices and Disclaimers Con’t.
34
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 herein 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.

36. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.