The IBM UrbanCode solution enables continuous release and application deployment allowing organizations to deliver applications rapidly and improve overall time to market.

1. © 2013 IBM Corporation
Helping Organizations Realize the Value of DevOps with Continuous Software Delivery Featuring IBM Urban{Code}
Steve Boone DevOps SME and UrbanCode Sales, IBM Software, Rational

2. © 2013 IBM Corporation
DevOps as the Optimization of the Software Delivery Pipeline
Optimizing the software delivery pipeline
•Reduce time to market
•Improve quality
•Decrease costs

3. © 2013 IBM Corporation
The Pipeline is an Assembly Line

4. © 2013 IBM Corporation
Balancing the Assembly Line
4
Equal process throughput avoids backlogs
Upgrading a proceeding process causes downstream backlogs
Upgrading downstream process throughput re- establishes balance

5. © 2013 IBM Corporation
Common patterns impacting continuous delivery
Failures due to inconsistent dev and production environments
Bottlenecks trying to deliver more frequent releases to meet market demands
Complex, manual, processes for release lack repeatability and speed
Poor visibility into dependencies across releases, resources, and teams
How do we ensure that we release and deploy
What we want, When we want, Where we want!

6. © 2013 IBM Corporation
Our customers are facing the same challenges
*Data based on UrbanCode customer survey

7. © 2013 IBM Corporation
Implementing a DevOps toolchain
SCM
Build / CI Server
Unit testing Test Automation Test Stubbing
Delivery Pipeline
Environment Configuration
Automated Monitoring
Asset Repository

8. © 2013 IBM Corporation
Continuous Delivery Pipeline

9. © 2013 IBM Corporation
Multi-tier applications introduce additional complexity
Middle Tier Server
Client Tier Devices
Back-end Data & Services
Coordinating separate pipelines for each tier is critical
•Disparate teams
•Different processes
•Separate tools

10. © 2013 IBM Corporation
Systems of Engagement (SoE) Apps
Rapid
Releases AppStore
Monitor
and Optimize
Release
and Deploy
Develop
and Test
Integration Test
10
Monitor
and Optimize
Develop
and Test
Web Apps
Frequent
Releases
Production
Environment
Databases
Systems of Record (SoR) Apps
Fewer
Releases
Databases
The need: Integrate systems of engagement with systems of record
By bringing together the culture, processes, and tools across the entire
software delivery lifecycle – spanning mobile to mainframe platforms

11. © 2013 IBM Corporation
Build System
Post build script
z/OS DeployToolkit
Create new version
z/OS
CodeStation
in USS
Server
Agent
Download artifacts
Review PDS in version and request deploy process
Pre-processing steps TSO, REXX, SHELL
Deploy data sets
PDS
PDS/E
Update Inventory status
High Level Overview of z Deployment Capabilities
z/OS LPAR, Build system
z/OS LPAR
Note: LPARs can be the same or different LPARs
Store meta data
Store version artifacts
Fetch artifacts via copy or FTP
Post-processing steps TSO, REXX, SHELL
deploy
1
2
3
4
5
6

12. © 2013 IBM Corporation
Deployment Automation Requires a Tool That:
Defines and executes a deployment process.
Manages deployed files in an Artifact Repository
Replaces deployment scripts with integrations
Coordinates deployment of multiple tiers
Secure and scalable support for large networks
Is audit friendly
–Streamlined Approvals
–Ties a deployment to the deployed files
–Tracks which version is where
–Supports separation of duties
–Is highly traceable

13. © 2013 IBM Corporation
Common Deployment Types
Content Deployments
–Incremental content updates
–Rollbacks
Middleware Code Deployments
–Install and rollback of code
–Run-book automation (restart, etc.)
Middleware Configuration Deployments
–Declarative description of configuration change
–Install and rollback of config change
DB Deployments
–Execution of DB change scripts in order
–Rollback

14. © 2013 IBM Corporation
Application Deployment
Components
–Tiers or services
Environments
–Collection of targets “resources”
–Env. Specific Config
Processes
–Coordinates Component processes
Pet ShopContentJ2EE AppMySQL DBSITWEBMIDDBPRODWEBMIDDBTomcatDeploy ProcessRollback ProcessRestart Process

15. © 2013 IBM Corporation
Applications are made of Components
UrbanDeploy deploys applications and components
Components are versioned deployables
–Web Services (SOA Components)
–Middleware Configurations
–Infrastructure (WAS, WL, etc.)
–Databases
–Business Intelligence Systems
An Application is a collection of components that are often deployed together

16. © 2013 IBM Corporation
Components
Components are comprised of:
–Versions: a set of files
–Processes: automations associated with the Components.

17. © 2013 IBM Corporation
Application Models
Applications models are comprised of:
–Components
–Environments:
•Named collection of servers / resources
•Each server has role(s) tied to components
–Processes: automations coordinating Component processes

18. © 2013 IBM Corporation
Snapshots
A Snapshot is a fixed set of Component Versions – a “Release Candidate”
Snapshots define the intended state for a target environment

19. © 2013 IBM Corporation
Deploying a Snapshot, ctd
Inventory Service: knows what version is installed and only deploys changes
New Servers: When added to an environment are easily made to look like all other machines of its type

20. © 2013 IBM Corporation
Deployment: Integrations (Plugins)
Repositories
–Internal: CodeStation
–External: AccuRev, ClearCase, CVS, Dimensions, Git, Harvest, Mercurial, MS TFS, Perforce, PVCS, RTC, SVN
J2EE Platforms
–WebSphere
•With DM and Stand-alone
•Cluster or Node/Server
•Start/Stop/Restart Application
•Start/Stop /Restart Server
•Install/Update /Uninstall App.
–WebSphere Message Broker
–WebLogic
–JBoss
–Tomcat
–Geronimo
BI & EAI Platforms
–Tibco
–Business Objects
–Informatica
Microsoft Platform
–MS IIS
–MS SharePoint
–MS BizTalk
–MS SQL RS
Databases
–MS SQL Server
–Oracle
–JDBC
Mainframe (z/OS)

21. © 2013 IBM Corporation
www.ibm.com/devops

22. © 2013 IBM Corporation
© Copyright IBM Corporation 2014. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
www.ibm.com/devops