Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Rational Development & Test for z Systems 9.5 Webinar with Rogers Communications

338 views

Published on

Slide deck from webinar held June 8, 2016 covering the newest release of RD&T and what value customers have seen in using.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Rational Development & Test for z Systems 9.5 Webinar with Rogers Communications

  1. 1. © 2016 IBM Corporation Overcome your Continuous Integration blockers with RD&T David Callingham, Rogers Communications Inc. david.callingham@rci.rogers.com Calin Groza, Rogers Communications Inc. calin.groza@rci.rogers.com Alisa Morse, IBM alisa@us.ibm.com
  2. 2. © 2016 IBM Corporation2 Agenda  Mainframe software delivery pressures  What is RD&T?  Roger’s Communications’ use of RD&T  What’s new in RD&T 9.5  Deploying RD&T via IBM Cloud Managed DevOps
  3. 3. © 2016 IBM Corporation3 Business constraints with mainframe environments today Do any of these pressures sound familiar? All teams share one dev/test LPAR. If someone gets behind, or causes an error in the environment, everyone is impacted. Systems programmers need a safe place to practice, test new software updates, recreate issues etc… Agile has meant a threefold increase in compilations testing. We have better productivity but development chargebacks also increased dramatically. A new version of the COBOL compiler has been released and an impact assessment is required before switching to the new release When production systems do quarterly accounting, development is squeezed and work slows. Sometimes necessary testing does not happen and quality suffers. Agile software delivery requires prototyping and tinkering. Developers and testers can’t touch mainframe configurations, and sometimes it takes weeks to have operations make an experimental change.
  4. 4. © 2016 IBM Corporation4 Typical z Systems Testing Architecture Organized by project team, vertically scaled, sharing resources, limited automation z/OS Dev/Test LPARProject Team [April Maintain] Project Team [Prototype SOA] Project Team [June New Func] Project Team [Dec Sys Upgrade] Data App App App 1.Shared resources combined with overlapping schedules can elicit conflicts, impede innovation and slow code delivery 2.Coordination of environmental changes and releases cause bottlenecks, delays and additional overhead 3.Shared test data is difficult to manage and can lead to over testing or incorrect test results
  5. 5. © 2016 IBM Corporation5 The result… Teams are delivering applications at variable speeds…with SoR speed inhibiting business agility Rapid iterations Develop Build Test Deploy Systems of Record Slower iterations Develop Build Test Deploy Slower iterations Systems of Engagement Production Production API Catalog Bottleneck!
  6. 6. © 2016 IBM Corporation6 Evolution to Continuous Delivery Continuous User Feedback & Optimization Collaborative Development Continuous Release and Deployment Continuous Monitoring Continuous Business Planning Continuous Testing Operate Develop/ Test Deploy Plan DevOps Continuous Feedback Develop Build Deploy Test Provision RD&T can improve these activities
  7. 7. © 2016 IBM Corporation7 Agenda  Mainframe software delivery pressures  What is RD&T?  Roger’s Communications’ use of RD&T  What’s new in RD&T 9.5  Deploying RD&T via IBM Cloud Managed DevOps
  8. 8. © 2016 IBM Corporation8 Add mainframe dev & test capacity, without increasing your MIPS Affordable off host development and test environment IMS DB2 CICS WAS MQ z/OS COBOL, PL/I, C++, Java, EGL, Batch, Assembler, X86 PC or HX5 Blade running Linux IBM SoftLayer Infrastructure RD&T RTC RDz RIT Rational Development and Test Environment for z Systems (RD&T) • Develop and test z/OS applications anywhere, anytime • Free up mainframe development MIPS for production workload • Eliminate costly delays by reducing burden on existing IT operations staff • Reduce time to value and minimize ongoing administration and capital expense with RD&T Cloud Managed DevOps • Expanded DevOps scenario coverage with UCD z/OS Agent 6.1.1.6 • Exploit the z13 hardware capability, including z13 Crypto Express 5S • Improve development coverage with newer z/OS 2.1 software stack, including MQ 8, COBOL 5.2, and RTC 6.0.x Note: This Program is licensed only for development and test of applications that run on IBM z/OS. The Program may not be used to run production workloads of any kind, nor more robust development workloads including without limitation production module builds, pre-production testing, stress testing, or performance testing. “RD&T improved our development and testing timeline and provided stability and quality” Developer, Large Enterprise Computer Services Company https://www.techvalidate.com/tvid/C99-3E2-1ED NEW NEW NEW
  9. 9. © 2016 IBM Corporation9 Typical RD&T use cases  Modernization- drive newer technologies and levels of software to production more quickly – Prototyping – z/OS software betas or upgrades – Development  Employee Education in an indestructible, approachable environment  Distributing development and test activities for higher availability, quality, and productivity. Benefits: – Increased availability of mainframe dev/test environment – Reduces issues with shared data – No waiting for sys admins to make changes on the mainframe  Enabling new software delivery methodologies such as Continuous Integration  Enabling development and test for geographically dispersed and outsourced teams
  10. 10. © 2016 IBM Corporation10 Challenges API Economy is quickly emerging, and with it new challenges Size of API Economy market by 20181$2.2T Connected things in smart homes by 2017$1B 70% Of U.S. Organizations have an API Strategy today Trends  Respond quickly to LOB and extend IT org new app requests  Expose SoR data securely via APIs  Identify problem components within an application Experience an evolving 4th tier for Modern Digital Applications driven by APIs and Microservices
  11. 11. 11 Rogers Communications Overcome your Continuous Integration blockers with RD&T Webinar – API Modernization Use Case David.Callingham @ rci.rogers.com Calin.Groza @ rci.rogers.com
  12. 12. 12 • Overview of Rogers Communications • Cable Subscriber Management Application • API Modernization with RD&T Presentation today will cover Agenda Overview Disclaimer: The views and opinions expressed in this presentation are those of the authors and do not necessarily represent official position of Rogers Communications. All products, brand names, or company names mentioned in this presentation are properties and trademarks or registered trademarks of their respective companies.
  13. 13. 13 • Rogers Communications Inc. is a diversified Canadian telecommunications and media company. In Wireless, we are Canada's largest voice and data telecommunications services provider and the country's only national carrier operating on the combined world standard GSM/HSPA+/LTE technology platforms. • Our Cable segment is a leading Canadian cable services provider, offering high-speed Internet access, television, and telephony products • Business Solutions segment, we provide business telecom, networking, hosting, managed services and IP solutions to small, medium and large enterprise, government and carrier customers. • Our Media segment is Canada's premier group of category-leading broadcast, specialty, print and online media assets, with businesses in radio and television broadcasting, televised shopping, sports entertainment, magazine and trade journal publishing and digital media. Introduction to Rogers Rogers Communications Inc. Overview Corporate overview http://www.rogers.com/web/ir/overview/
  14. 14. 14 • Functional Capabilities o Customer Management o Product Ordering o Work Order and Service Order Scheduling o Billing Credit & Collection In-house developed, continuously evolved Cable Subscriber Management Application Introduction 1981 – Dev start 1993 – GUI & SOA 3270 1998 – MQ SOA 2001 – GUI VB 2004 – ESB Web Services 2012 – Moderniza -tion
  15. 15. 15 • Technical Profile o Over 1000 online programs o 140 CICS Services consumed by GUI (via 3270) o 60 CICS Services consumed by ESB (via MQ) o SOA o Telnet 3270 and MQ initiated CICS transactions • Volumetrics o 2.2 million customers o 15,000 online users, 6000 concurrent users o 7 million transactions per day o 250 peak tps o 60% via 3270 40% via MQ CICS/COBOL/IMS/VSAM Cable Subscriber Management Application RD&T Webinar Application Overview
  16. 16. 16 • Begun in 2012 • System Software Upgrade o z/OS 1.4 to z/OS 1.13 • Hardware Replacement o Z9 to BC12 o new disk and tape sub-systems • Improve GUI and ESB APIs with SOAP/REST Web services o Limitations GUI Client o message size & 3270 emulator costs o ESB mediation o Reduce Middleware dependency o XML-COBOL mapping logic in 3rd team Bring application and infrastructure current Modernization Project RD&T Webinar Modernization
  17. 17. 17 SOA since 1993 2004 Current API Implementations – 3270 & MQ COBOL Current APIs 17 GUI Mapping-Comms HLLAPI …CICS AOR Server1 Server1 Server1 Comms Scheduler Server1 Comm Server TCP/IP Z/OS 3270 Transport COBOL messages over Telnet 3270 ESB CICS MOR Broker CICS AOR Server1 Server1 Server1 Comms’ Scheduler’ Server 1 SERVICE_REQUEST_Q SERVICE_REPLY_Q MQ Client Channels XML- COBOL xform Web service provider - HTTP COBOL COMMAREA 1998
  18. 18. 18 Chapter 3 Scenario 2 - modernize API Design Pattern – API Modernization RD&T Webinar Enterprise Architecture http://www.redbooks.ibm.com/redbooks/pdfs/sg248225.pdf developerworks
  19. 19. 19 RD&T increased agility and time to market Goal - Web Service APIs by end of 2015 RD&T Webinar RD&T March RD&T CICS 5.2 and Liberty April end-to-end PoC May Deployment alternatives & logging June HTTP Basic Auth August SSL September 2015 DEV LPAR available • zIAW February 2015 - Liberty or classic CICS pipeline (IBM SWG Workshop) • Problem • CICS 5.2, Java 7.1 and Liberty not available on DEV LPAR till September 2015 • Solution • RD&T w/CICS 5.2 • Full authority • No process barriers
  20. 20. 20 Complete an end-to-end test to uncover technical issues & confirm design Technology Validation Prototype RD&T Webinar RD&T CICS 5.2 Liberty 8.5.5 Test Client CICS 5.1 RD&T DEV LPAR IPICSOAP HTTP Prototype Scope • Eclipse 4.2.2 Java EE, WLP, CICS Explorer plug-ins • WSDL definition • AdminService:ExecutePgm • Java code gen JAX-B • CICS 5.2 • CICS CONTAINERS • Liberty jaxws and cicsts features Out of Scope • Basic Auth • HTTPS • Authentication with RACF RD&T Benefits • Hands on learning • Quick cycle time for app changes • No security – full access to config, logs and commands LINK COBOL Service ExecutePgm method ExecutePgm Map Java objects to byte arrays Create CICS channel and containers Put the byte arrays in the containers Link to CICS program Get data from containers Map container data into Java objects GET CONTAINER INTO(request) Proceed as per usual PUT CONTAINER FROM (response) Return <server> <feature>cicsts:core-1.0</feature> <feature>jaxws-2.2</feature> <feature>jaxrs-1.1</feature> <feature>servlet-3.0</feature> <feature>cdi-1.0</feature> <feature>jndi-1.0</feature> <applicationMonitor dropins="dropins” pollingRate="60s” updateTrigger="polled"/>
  21. 21. 21 How Liberty authentication interacts with RACF, Java method and CICS-COBOL HTTP Basic Authentication RD&T Webinar RD&T CICS 5.2 Liberty 8.5.5 Client CICS 5.1 RD&T DEV LPAR IPICUser Pw Prototype Scope • RACF SAF user-repository • Change Password • Password Expired • Revoked ID • Session Token handling • Failed Authentication Challenge • HTTP Basic Auth does not support password change or errors for expired/revoked Ids Solution • Use Basic Auth protocol and Lightweight Third-Party Authentication (LTPA) • Second level of authentication in the COBOL application layer RD&T Benefits • Full access to server config and logs • Quick cycle time for app changes LINK COBOL Logon BA+ Login method <server> ... <feature>cicsts:security-1.0</feature> <feature>appSecurity-2.0</feature> .... <safCredentials unauthenticatedUser="CWSABC"/> <safCredentials profilePrefix="CWSABC"/> <webAppSecurity ssoCookieName="SessionId"/> .... </server> EXEC CICS VERIFY USERID() PW() Angel RACF RACF
  22. 22. 22 Configure Certificate in RACF and configure Liberty for SSL SSL-TLS RD&T Webinar RD&T CICS 5.2 Liberty 8.5.5 Test Client RD&T HTTPS Angel RACF • Challenge o Minimum level of security (MLOS) compliance mandates SSL/TLS for web-services invocations o RACF configuration certificates complex with many options • RD&T Benefits and Solution o RD&T has separate RACF database o Full access to RACF admin and server.xml o RACF steps tested o Create a self-signed certificate as placeholder o Generate a Certificate Signing Request o Receive the signed certificate o Replace certificate, add to key ring o Other things we learned o Managing SSL certificates is a complex activity o Have tools handy to check and troubleshoot the SSL configuration: openssl, portcle o Intermediate and root CA certificates for GeoTrust already on desktop configuration o Liberty config details for keystore - RACF keyring, ssl- id referring to RACF certificate name <server> ... <feature>ssl-1.0</feature> <keyStore filebased="false" id="racfKeyStore” location="safkeyring://CWSDABC/RNGABC" password=”..." readOnly="true" type="JCERACFKS"/> <ssl id="defaultSSLConfig” keyStoreRef="racfKeyStore" sslProtocol="SSL_TLS" serverKeyAlias=”ABC LPAR CERT-CA"/> </server>
  23. 23. 23 Build simple and reliable application deployment procedures Web-Services Application Deployment RD&T Webinar RD&T • Challenge o Web-services java code is packaged in a WAR file o Multiple deployment options: dropins, Liberty application , CICS bundle. Pros and cons for each option o z/OS java deployment new at Rogers Communication, existing tools only partly applicable • RD&T Benefits and Solution o Experiment with different deployment options o Final decision – dropins for developers, deploy as a Liberty “application” for QA and PROD o Procedure tested till perfect o Other lessons learned o Keep in mind that the process will be automated. Scripts can easily manipulate files as a whole (copy, rename) but are less suitable to modify a configuration file (e.g. change an XML attribute) o Instrument the application to report what version of the application is running and what is the build number/date-time o In a clustered environment, provide an endpoint on each node for support and monitoring purposes
  24. 24. 24 • Disconnect development from the z/OS software upgrade cycle o Early access to new features o Reduce distraction of sys prog staff o No differences when code moved to z/OS LPAR • Bypass normal security constraints o Loose security for CICS, RACF, USS etc o Config changes by dev team with sys prog assistance o Test ID for RACF crypto setup o Eliminate hand off delays, request/approval/configure/test repeat • Fail fast o Learn by trying - cycle time reduced o Liberty/CICS docs provide examples with slight differences – able to quickly try out config changes RD&T enabled agile design of complex solutions Conclusions RD&T Webinar
  25. 25. 25 Thank you! RD&T • Dave Callingham &Calin Groza - DCA group consultants
  26. 26. © 2016 IBM Corporation26 Agenda  Mainframe software delivery pressures  What is RD&T?  Roger’s Communications’ use of RD&T  What’s new in RD&T 9.5  Deploying RD&T via IBM Cloud Managed DevOps
  27. 27. © 2016 IBM Corporation27 Rational Development and Test + UrbanCode Deploy Efficiently manage configurations across environments and provide self-service capabilities Introduce DevOps practices and improve software delivery -- Implement DevOps practices (eg TDD, CI, CD) to improve quality and delivery time -- Provide a unified solution for continuous delivery of heterogeneous enterprise applications -- Ensure that throughput of each process (Develop, Build, Deploy) is equal Reduce costs -- Accelerate delivery and reduce deployment time by over 95% to develop/test multi-tier applications across heterogeneous environments and platforms -- Reduce amount of manual labor, resource wait-time, and rework by eliminating errors & providing self- service environments Remove bottlenecks -- Accelerate deployment by enabling development teams to self deploy with automation -- Automate managing configuration and version deployment reducing deployment outages -- Greater visibility of “what is where” with the ability rollback to any prior version at ease
  28. 28. © 2016 IBM Corporation28  XEN hypervisor support – Generically supported, tested on Citrix XenServer 6.2  System z13 EC CPU CPU architecture instruction set  z13 Cryptographic Enhancements – Emulated Crypto Express 5S support including VISA Format Presentation Enhancement (FPE) support  CP Assist Crypto Facility (CPACF) Updates  z13 EC Coupling  System Time Protocol (STP) support – Synchronized time of day between zPDT instances  Support for read-only DASD volumes zPDT 1.6 (GA6) FP2 System z architecture emulator enhancements
  29. 29. 29 © 2016 IBM Corporation  z/OS V2.1, including sub-features • Encryption Facility • z/OS Security Level 3 Feature and z/OS Communications Server Security Level 3 Feature • IBM HTTP Server • DITTO/ESA • IBM z/OS Management Facility  IBM PD Tools • Tools Base for z/OS • IBM Debug Tool 13.1 • IBM File Manager 13.1- evaluation • IBM Fault Analyzer 13.1- evaluation  CICS Transaction Server • CICS 4.2, 5.1, 5.2 • CICS/VSAM Recovery 5.1, 5.2 • CICS Transaction Gateway 9.0  CICS Tools • CICS Deployment Assistant 5.1, 5.2  Tivoli • Tivoli System Automation for z/OS 3.5 • Tivoli NetView 6.2 • Tivoli Workload Scheduler for z/OS 9.2  Compilers • IBM Compiler for REXX 1.4 • IBM Enterprise PL/I 4.5 • IBM COBOL 5.2 • IBM Rational COBOL Runtime 6.0.1 (EGL) • XL C++ 2.1 • IBM Java SDK for z/OS 6.0, 6.0.1, 7.0, 7.1, 8.0  WebSphere Application Server for z/OS 8.0, 8.5, Liberty Profile  DB2 for z/OS • DB2 for z/OS 10, 11 • DB2 Utility Suite for z/OS • DB2 Administration Tool for z/OS • DB2 Object Comparison Tool for z/OS • DB2 for z/OS QMF  IMS • IMS 12, 13 • Note: Multiple IMS tools have been removed due to royalty  WebSphere MQ for z/OS 8  Rational Developer for System z 9.1.1 z/OS components  Rational Team Concert 6.0.x z/OS components  UrbanCode Deploy 6.1.1.6 z/OS Agent Updated z/OS 2.1 Distribution
  30. 30. © 2016 IBM Corporation30 Agenda  Mainframe software delivery pressures  What is RD&T?  Roger’s Communications’ use of RD&T  What’s new in RD&T 9.5  Deploying RD&T via IBM Cloud Managed DevOps
  31. 31. © 2016 IBM Corporation31 RD&T via Cloud Managed DevOps Services Simplifies access to development and test environments by optimizing… Configuration planning Server install and configuration Image customization Administration, maintenance, Upgrades Hardware acquisition Data and Application migration
  32. 32. © 2016 IBM Corporation32 RD&T as a Managed Service provides the core RD&T offering on a virtual private cloud, without the setup and maintenance IT costs  Provides the RD&T offering, customized and configured for each client  On a scalable, single-tenant, IBM SoftLayer Infrastructure  Provides 99.9% availability (SLO)  Managed by IBM Services IBM Customer Success Services IBM SoftLayer Infrastructure
  33. 33. 33 © 2016 IBM Corporation Types of managed services provided by IBM Services: IBM Customer Success Services We ensure that your platform is running smoothly, with dedicated support, updates, availability, and speed!  Security compliance  RD&T image set-up  RD&T On boarding services  Infrastructure & RD&T hosted image support  z/OS management services  Client success management
  34. 34. © 2016 IBM Corporation34 RD&T Cloud Managed Services benefits include:  Optimized operation cost (lower total cost of ownership)  Ability to scale up and down the service (monthly)  Accelerated time to value: On Premise Customization with In-House Resources* RD&T as a Managed Service  Customization and Rollout Planning, Hardware Acquisition, Install, configuration Rollout Productive Use Productive Use Wider rollout ~3 months Provisioning: Hours, Customization: 2-4 weeks Examples Rollout *Based on Customer Feedback (factoring in resource availability and scheduling)
  35. 35. © 2016 IBM Corporation35 Key Points • Insufficient mainframe Dev & Test LPAR availability leads to defects and missed schedules • Tightly controlled mainframe environment prevents agile experimentation and prototyping • High cost of mainframe development and test hardware and software • Skill gaps due to off shoring, outsourcing and the majority of skills being near retirement Business Challenges Business Benefits Cost Savings Lower cost dev/test LPARS: Additional capacity necessary for adopting DevOps practices available on Intel compatible hardware MIPS reallocation : Initial Dev & Test activities performed on RD&T enables reallocation of MIPS to higher value production workload Economical training platform: Portable, indestructible environment for skill building Quality Shift Left testing : Better test coverage earlier in the cycle on high fidelity z/OS Dev & Test environment leads to quality and quicker delivery Work in parallel vs serially: Distributed environments reduce errors caused by contention and enable easier problem determination on easily provisioned systems Agility Adapt to changing business requirements : z/OS on x86 hardware that can be virtualized and reset offers a developer sandbox for prototyping and V2V migration Portability: Teams can Dev & Test z/OS applications anytime, anywhere. Outsourced teams can work without mainframe access.
  36. 36. © 2016 IBM Corporation36 Resources  RD&T Product Page  Short RD&T video  DevOps for the Enterprise tech talks: http://bit.ly/1b4wl18  IBM Cloud Managed DevOps Services  Automated z Systems Application Testing on the Cloud  RD&T Tech Validate facts  RD&T Product Documentation, including zPDT Redbooks  RD&T Hub  Request your test drive today: http://www.ibm.com/developerworks/downloads/rdtsandbox_systemz/index.html
  37. 37. © 2016 IBM Corporation37 Thank You Merci Grazie Gracias Obrigado DankeJapanese English French Russian German Italian Spanish Brazilian Portuguese Arabic Traditional Chinese Simplified Chinese Thai
  38. 38. 38 © 2016 IBM Corporation Backup

×