Application Release Automation Partner PGD Cheat Sheet

WW Demand Generation

Who to Call (by title)

VP of IT Planning and Business Operations - IT Governance, Risk & Compliance VP of Applications - Application/Business Service Operations - Application Build/Release Management

Who to Call (by responsibility)

Person responsible for: Deploying the applic mgmt solution Supporting applications Deploying the technology mgmt solution(s) that support the infrastructure Managing the infrastructure nd rd Handling the 2 & 3 line support after an event occurs Managing service availability

Primary Target Accounts

Large companies with business critical applications that change a lot, running Websphere, Weblogic, or Jboss BladeLogic and Remedy installed accounts 100+ Developers or 500+ Managed Servers

Discovery Questions
Improve Application Availability
Can you quantify the per-minute cost of downtime for a given application? How many failures happen shortly after updates are made? How quickly can you identify the root-cause of application downtime?

Customer Pains
Application outages related to deployments Unable to adequately respond to urgent business requests High labor costs, many FTEs association with application release Unable to show compliance with IT policies Cannot predict impact of application release on production systems Variations in application environments between Dev, Test, & Production Rogue configuration changes Unable to rollback changes on errors

Short Description
BMC Application Release Automation allows organizations to automate the process of packaging, deploying, promoting and selectively rolling back application modules. Packaging: Creates a package (or collection) of multiple configuration items that must be deployed at the same time Deployment: Installs the package on servers and tests its effects in a live environment Promotion: Delivers a tested package to an environment of higher criticality (i.e., Development QA, staging Production) specifically coordinating the handoff across teams Compliance: Validates that applications and environments are properly configured for stability, and to assist in troubleshooting

Reduce IT costs
Do you know where you would like to reduce costs? What initiatives do you have in mind to cut application costs or improve quality? What portion of your organizations time is spent on new application development? Application deployment? Firefighting? Compliance? How do you correlate application costs to the value of the business functions supported?

Improve Application Deployment

How much time does your staff spend on deployment script development? Can you describe a scenario where application change/release didnt go as planned? How do you ensure the integrity of your application and/or infrastructure changes as they move across dev, QA, and production? How do you roll back unintended or unwanted changes in your environment?

Compliance and Governance

How often do you undergo an audit? Where were you strong and weak in your last audit report? How did you prove policy compliance to your auditors? How do audits impact your workload and resources? How much money, time, and resources are required for each audit? What are your biggest challenges with application compliance and process governance? How do you enforce and track access privileges?

Cloud Applications
Which applications, if any, would you like to manage with a virtualized/cloud approach? Do you plan to maintain physical and cloud deployments concurrently? How is the move to virtualization/cloud going to impact your application deployments? Which vendors are you using for virtualization/cloud infrastructure & management?

Application Release Automation Partner PGD Cheat Sheet

WW Demand Generation

Value Driver
Improve Application Availability Reduce IT Cost Improve Application Deployment Consistently Enforce Compliance Enable Cloud-based Applications

Metrics for Success

% releases deployed without error % releases deployed within change window Application Downtime (config or release related) Hours of labor per release # of releases per time period (month, quarter) Cost of failures to the business Incident to Change ratio # and seniority/pay-grade of staff allocated to release management Length of average deployment cycle # of audit comments related to application rollout and changes Time and effort required for compliance tracking and reporting # of unauthorized changes

Differentiators
Model-Driven Configuration Management Delivers environmental consistency, reducing application downtime Patented Deployment Packaging Reduces complexity and ensures reliable and predictable releases Role-based Access Control Ensures tamper-proof packages and protected environments Rollbacks Provides environmental integrity when deployments must be undone Full-stack Provisioning and Configuration Policy Management Enables application release teams and IT operations to cooperatively work together for reliable application deployments

Benefits
Reduced application downtime Prevent configuration errors and accelerate troubleshooting Lowered costs Eliminate labor-intensive manual and script-based deployment processes for even the most complex, multi-tiered applications Faster deployments Shorten release cycles from weeks to hours to better support the business Auditing and Governance Detect and remediate changes and demonstrate effective policy enforcement Aligned release teams Improve communications between Development, QA, and Operations, ensuring worry-free deployments

Objections
We dont have any trouble with our release process.

Answers
Does your current solution require you to write and maintain your own scripts? We eliminate the time and expense of script maintenance and also provide audit reporting and compliance enforcement. We complement your current process with robust packaging and configuration capabilities that work for all types of applications: .NET, Java, C++, and packaged.

We have a release automation solution now. We use our build automation solution for release management. We only use packaged applications.

We can manage complex, mutli-component deployments with safety of rollback support so you can deploy major updates with confidence.

Solution Capabilities/How We Do It
Environment definition and consistency Allows release engineers to define each environment within the release process and assure that each environment is configured consistently Consistently manage deployments across multiple platforms; Development, Test, QA, and Production environments; and ensure efficient and accurate release engineering Automated build package definition, assembly and packaging Identifies, assembles and creates application build packages for deployment across multiple platforms without the need for human intervention Composite packaging Allows multiple application components to be packaged for deployment across multiple platforms as a single build package with built-in transaction safety and rollback capability; reduces the number of packages which must be built to accommodate various platforms Role-based access control for all environments Allows organizations to determine, very specifically, which individuals have authority to promote a package from one level to another, or to make changes to the package Creates reusable application deployment packages Align processes across Development, Test/QA, Staging and Production Maintains integrity of production systems Capture and confidently update or rollback application deployments Change detection, reporting and remediation Manage configuration drift and generate reports for auditing and change management Diagnostics Quickly identify differences in application environments for problem resolution

Application Release Automation Partner PGD Cheat Sheet

WW Demand Generation Migration Migrate applications and environments to new middleware versions Supports multiple application deployment environments such as Development, QA, Staging and Production through parameterization of critical release variables Package application updates for custom, .Net, and J2EE applications Define roles and profiles associated with various application environments to allow security and consistency of application builds during rollouts and rollbacks Define application release environments and promotion rules for multi-tenant applications