You are previewing How Walmart Became a Cloud Services Provider with IBM CICS.
O'Reilly logo
How Walmart Became a Cloud Services Provider with IBM CICS

Book Description

The world has changed. With the new cloud options, enterprises no longer must rely on only their IT organization to meet their computing needs. Business units now have options that were not available just a few years ago. They can get some of their needs met by traditional IT processes, and reach out to a cloud provider to meet other needs. The concern is that if you, working in a traditional IT organization, do not meet these needs, someone else will.

This IBM® Redbooks® publication helps you to understand the benefits of becoming your own cloud service provider. It describes a simple approach that allows you to be successful. The main focus of the book is lessons learned from the implementation by an IBM client, Walmart Stores, Inc.®, that achieved impressive results in their efforts to become their own cloud service provider to their developer community. In this way, Walmart successfully made z Systems a relevant part of their Hybrid Cloud strategy.

Walmart embarked on this journey to help their application developers achieve results that were previously time-consuming and difficult to deliver. In the process, they realized that they had everything that they needed to become a services provider to their developer community. This book describes the choices that Walmart made, and explains the steps they took to be successful.

The goal of the book is not to imply that the only way to achieve success is by following Walmart’s process exactly. Rather, this book allows you to use the same basic constructs, but choose implementation details that fit your environment so that you can achieve success on your own terms. With IBM CICS® Transaction Server (TS) for z/OS®, you also have the resources for a successful transition to becoming your own cloud service provider.

IBM Design Thinking is a methodology that is used by designers to solve complex problems by focusing on individual user roles. This book is organized from the viewpoint of these roles in the IT organization. It provides guidance in the following areas:

  • What does the line of business expect from a cloud service?

  • What topology and high availability characteristics does the system programmer need?

  • What unique facilities does IBM CICS provide to the service developer?

  • How does a developer discover and consume services in an application?

  • How does the operations team manage the service in production?

  • One of the services that Walmart built and how the decisions made by each job role affected the overall outcome of the service are used as an example throughout this book. It shares the experience of the team that created this and other business critical cloud services that are all hosted in CICS. Comments from Walmart IT leaders that were captured during the authoring process are presented to emphasize why the company adopted cloud and how cloud has helped Walmart to achieve success.

    Developers understand the risk protection that IT groups provide. They also understand that waiting to move applications to production, or for a service to be provisioned, compromises the agile environment required by today's businesses.

    This book is intended for enterprise service providers looking to enable their developers to increase the speed at which functionality is delivered to the business. For more information about creating IBM z/OS cloud services, see Creating IBM z/OS Cloud Services, SG24-8324

    Table of Contents

    1. Front cover
    2. Notices
      1. Trademarks
    3. IBM Redbooks promotions
    4. Preface
      1. Authors
      2. Now you can become a published author, too!
      3. Comments welcome
      4. Stay connected to IBM Redbooks
    5. Chapter 1. Reasons to become a cloud service provider
      1. 1.1 The development obstacle
      2. 1.2 The developer is the consumer
      3. 1.3 How z/OS and CICS are relevant to cloud
        1. 1.3.1 The journey from development obstacle to cloud services
      4. 1.4 Challenging the roles of IT
      5. 1.5 Summary
    6. Chapter 2. The service consumer
      1. 2.1 Consumer requirements
      2. 2.2 Walmart caching requirement
      3. 2.3 Self-service
      4. 2.4 Connecting platforms
      5. 2.5 CICS as a consumer
      6. 2.6 Summary
    7. Chapter 3. The service provider
      1. 3.1 Why Walmart chose CICS for the caching service
        1. 3.1.1 Mixed language support
        2. 3.1.2 Everything in the box
        3. 3.1.3 Monitoring and diagnostics
        4. 3.1.4 Vendor environment
      2. 3.2 Foundational underpinnings
        1. 3.2.1 Naming conventions
        2. 3.2.2 Standards
      3. 3.3 Five essential characteristics of cloud
        1. 3.3.1 On-demand self-service
        2. 3.3.2 Broad network access
        3. 3.3.3 Resource pooling
        4. 3.3.4 Rapid elasticity
        5. 3.3.5 Measured service
      4. 3.4 Microservices architecture
        1. 3.4.1 Application design pattern
        2. 3.4.2 Independent, limited function services
        3. 3.4.3 Encouraged by cloud delivery model
      5. 3.5 Summary
    8. Chapter 4. The CICS systems programmer
      1. 4.1 CICS architecture
      2. 4.2 Service owning region
      3. 4.3 CICS resource definitions
        1. 4.3.1 CICS resource definitions for services
      4. 4.4 Security
        1. 4.4.1 SSL certificates and TCP/IP services
        2. 4.4.2 Wildcard certificates and host names
        3. 4.4.3 Basic authentication
        4. 4.4.4 Authentication at the server level
        5. 4.4.5 Authentication at the service level
      5. 4.5 Multitenancy
      6. 4.6 Network access
      7. 4.7 Summary
    9. Chapter 5. The z/OS systems programmer
      1. 5.1 Sysplex architecture
        1. 5.1.1 Resource pooling, rapid elasticity, and measured service
        2. 5.1.2 Unique characteristics
        3. 5.1.3 Important pieces
      2. 5.2 Workload manager
        1. 5.2.1 LPAR weighting
        2. 5.2.2 Service class
        3. 5.2.3 WLM ASID weights
      3. 5.3 TCP/IP
        1. 5.3.1 Enabling sysplex distribution
        2. 5.3.2 Establish shared ports
        3. 5.3.3 Assign DVIPA
        4. 5.3.4 Domain Name System
      4. 5.4 High availability
      5. 5.5 VSAM RLS
        1. 5.5.1 Feature enablement
        2. 5.5.2 Sizing
        3. 5.5.3 System managed assignments
      6. 5.6 z/OS configuration
      7. 5.7 Security
      8. 5.8 Summary
    10. Chapter 6. Operational considerations
      1. 6.1 Capacity planning
        1. 6.1.1 The concerns of a capacity planner
        2. 6.1.2 Partnership with capacity planners
      2. 6.2 Scaling and elasticity
      3. 6.3 Metering and measurement
        1. 6.3.1 Charging for service usage
        2. 6.3.2 Use of measurement information for scaling
        3. 6.3.3 Evolution of service-oriented architecture to cloud service
      4. 6.4 Maintenance
      5. 6.5 Problem determination
        1. 6.5.1 Isolation of consumers in a multi-tenant environment
        2. 6.5.2 Standards
        3. 6.5.3 Communication with other teams
      6. 6.6 Summary
    11. Chapter 7. DevOps perspective
      1. 7.1 The challenge of variable speed IT
      2. 7.2 The role of DevOps
      3. 7.3 Cloud services
      4. 7.4 Promotion to production
      5. 7.5 Process and governance
      6. 7.6 Service versioning
      7. 7.7 Summary
    12. Related publications
      1. IBM Redbooks
      2. Other publications
      3. Online resources
      4. Help from IBM
    13. Back cover