Using Liberty for DevOps, Continuous Delivery, and Deployment

Book description

This IBM® Redbooks® publication provides an example approach for an agile IT team to implement DevOps capabilities in their software delivery of a Java application. We introduce several tools that show how teams can achieve transparency, traceability, and automation in their application lifecycle to all of the stakeholders to deliver a high-quality application that meets its initial requirements. The application that is built highlights the composable and dynamic nature of the Liberty run time. The Liberty run time helps developers to get their applications up and running quickly by using only the programming model features that are required for their applications.

The target audience for this book is IT developers, IT managers, IT architects, project managers, test managers, test developers, operations managers, and operations developers.

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. Introduction
    1. 1.1 DevOps
      1. 1.1.1 DevOps architecture
      2. 1.1.2 Business value
    2. 1.2 WAS Liberty
      1. 1.2.1 Advantages for development
      2. 1.2.2 Advantages for operations
    3. 1.3 DevOps application lifecycle phases
      1. 1.3.1 Planning
      2. 1.3.2 Development
      3. 1.3.3 Build
      4. 1.3.4 Testing
      5. 1.3.5 Deployment
    4. 1.4 Objective
      1. 1.4.1 DevOps products
    5. 1.5 Overview of the application use case
  6. Chapter 2. Project planning by using Rational Team Concert and Rational Quality Manager
    1. 2.1 Software development
      1. 2.1.1 Requirements management
      2. 2.1.2 Functional specifications
      3. 2.1.3 Architecture and design documents
      4. 2.1.4 Development
      5. 2.1.5 Quality assurance
      6. 2.1.6 Release management
      7. 2.1.7 Documentation
      8. 2.1.8 Delivery
    2. 2.2 Infrastructure
      1. 2.2.1 Scenario
      2. 2.2.2 Monitoring and event management
      3. 2.2.3 Provisioning
    3. 2.3 Planning a software development project with Rational Team Concert
      1. 2.3.1 The role of Rational Team Concert in DevOps
      2. 2.3.2 Scrum project lifecycle and iterations mapping: Development
      3. 2.3.3 User story
    4. 2.4 Integrating the Eclipse Java Platform, Enterprise Edition client with Rational Team Concert and WAS Liberty
    5. 2.5 Rational Quality Manager for test planning
      1. 2.5.1 Acceptance criteria
      2. 2.5.2 Creating a test plan for your project
      3. 2.5.3 Creating test cases
      4. 2.5.4 Linking the test cases to the test plan
      5. 2.5.5 Creating the test scripts
      6. 2.5.6 Linking test scripts to a test case
      7. 2.5.7 Reviewing the test case
      8. 2.5.8 Creating test case execution records
  7. Chapter 3. Code development, source code management, and build
    1. 3.1 How developers code and collaborate by using Rational Team Concert
      1. 3.1.1 Coding
      2. 3.1.2 Unit testing
      3. 3.1.3 Code reviews
      4. 3.1.4 Code delivery
    2. 3.2 Jenkins as an alternative for building code
      1. 3.2.1 Install and configure the Rational Team Concert plug-in on Jenkins
      2. 3.2.2 Configure the Rational Team Concert server connection
      3. 3.2.3 Create a Jenkins build engine
      4. 3.2.4 Create a Jenkins build definition
      5. 3.2.5 Create a Jenkins job by using the Rational Team Concert plug-in
  8. Chapter 4. Continuous testing
    1. 4.1 Rational Quality Manager for system testing
      1. 4.1.1 Structure of the Rational Quality Manager project
      2. 4.1.2 Configure the Rational Quality Manager Adapter
      3. 4.1.3 Create a unit test case
      4. 4.1.4 Create a unit test script
      5. 4.1.5 Associate the test case and test script
      6. 4.1.6 Create a test case execution record
      7. 4.1.7 Execute test cases
    2. 4.2 Rational Test Workbench for test virtualization
      1. 4.2.1 Create and run a database stub
      2. 4.2.2 Edit the data in the database stub
    3. 4.3 Test environment for Liberty configuration testing
  9. Chapter 5. Deployment
    1. 5.1 How to use UrbanCode Deploy for application deployment
      1. 5.1.1 Publishing component artifacts from Jenkins to UrbanCode Deploy
      2. 5.1.2 Configuring UrbanCode Deploy for system deployment
    2. 5.2 How to use Jenkins to deploy applications to IBM Bluemix
  10. Chapter 6. Production environment
    1. 6.1 Solution architecture
      1. 6.1.1 Target environment
      2. 6.1.2 DevOps platform
      3. 6.1.3 Delivery pipeline
    2. 6.2 Liberty profile cluster deployment with UrbanCode Deploy
      1. 6.2.1 Creating a controller component
      2. 6.2.2 Creating a member component
      3. 6.2.3 Defining agents and component distribution
      4. 6.2.4 Configuring the LibertyCloudTrader application and environment
      5. 6.2.5 Adding the required configuration to the server.xml file
    3. 6.3 Monitoring and analytics
      1. 6.3.1 Required software products
      2. 6.3.2 Configuration of Data Collector
      3. 6.3.3 Visualize the data in the Application Performance dashboard
    4. 6.4 DevOps Services
      1. 6.4.1 Plan
      2. 6.4.2 Development
      3. 6.4.3 Build and deploy
  11. Chapter 7. Conclusion
    1. 7.1 Advantages of DevOps
    2. 7.2 Advantages of Liberty
  12. Appendix A. Additional material
    1. Locating the web material
    2. Using the web material
  13. Related publications
    1. Online resources
    2. Help from IBM
  14. Back cover

Product information

  • Title: Using Liberty for DevOps, Continuous Delivery, and Deployment
  • Author(s):
  • Release date: November 2015
  • Publisher(s): IBM Redbooks
  • ISBN: 9780738441160