web Admin Console - Release Management · Abstract > Release management workflows let’s you get a...
Transcript of web Admin Console - Release Management · Abstract > Release management workflows let’s you get a...
Terms of This Presentation
This presentation was based on current information and resource allocations as of October
2009 and is subject to change or withdrawal by CA at any time without notice.
Notwithstanding anything in this presentation to the contrary, this presentation shall not serve
to (i) affect the rights and/or obligations of CA or its licensees under any existing or future
written license agreement or services agreement relating to any CA software product; or (ii)
amend any product documentation or specifications for any CA software product. The
development, release and timing of any features or functionality described in this presentation
remain at CA’s sole discretion. Notwithstanding anything in this presentation to the contrary,
upon the general availability of any future CA product release referenced in this presentation,
CA will make such release available (i) for sale to new licensees of such product; and (ii) to
existing licensees of such product on a when and if-available basis as part of CA maintenance
and support, and in the form of a regularly scheduled major product release. Such releases
may be made available to current licensees of such product who are current subscribers to CA
maintenance and support on a when and if-available basis. In the event of a conflict between
the terms of this paragraph and any other information contained in this presentation, the
terms of this paragraph shall govern.
2 October 12, 2009 Web Admin Console- Release Management Copyright © 2009 CA
For Informational Purposes Only
Certain information in this presentation may outline CA’s general product direction. All
information in this presentation is for your informational purposes only and may not be
incorporated into any contract. CA assumes no responsibility for the accuracy or completeness
of the information. To the extent permitted by applicable law, CA provides this document “as
is” without warranty of any kind, including without limitation, any implied warranties or
merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be
liable for any loss or damage, direct or indirect, from the use of this document, including,
without limitation, lost profits, lost investment, business interruption, goodwill, or lost data,
even if CA is expressly advised of the possibility of such damages.
3 October 12, 2009 Web Admin Console- Release Management Copyright © 2009 CA
Abstract
> Release management workflows let’s you get a handle on
how software is distributed in a managed environment.
Using the Web Admin Console (WAC) see how release
management is implemented, including the capability to
release software that follows ITIL Release Management
best practices. In this session we will look at how release
management is achieved with our out-of-the-box
implementation and then explore some of the options for
customization of the workflows that support this feature.
Agenda
> Overview
What is Release Management?
CA Release Management
Types of Releases
Web Console Release Management Architecture
> Setup and Configuration
> Using Release Management
> CA Workflow and Sub Activities
> Q & A
What Is Release Management?
> To design and implement efficient procedures for
installation and distribution of changes to IT systems.
> To communicate and manage expectations of the
customer during the planning and rollout phases.
> The focus is the protection of live environment and its
services through use of formal procedure and checks.
CA Release Management
> Partially implements ITIL Release Management.
> Optionally - Update Service Desk” activity to integrate
with CA Service Desk Manager.
> Predefined Process Definition in CA Workflow.
> Four types of Releases available:
“Major"," Minor” ,”Emergency” ,”Custom”.
> Optional - “Release Backout” phase.
Types of Releases
> Major Release:
Incorporates Release Validation and Release Approval phase.
Release initially deployed on Test environment before the
Production Environment.
> Minor Release:
Has only the Release Approval phase before deploying onto the
Production Environment.
> Emergency Release:
Used to deploy Release without Release Approval.
> Custom Release:
Templates with customized parameters created and used here.
Release Management Flow
Release
Management
Rejected
Rejected
Accepted
Accepted
Minor Release Major Release
CA
Workflow
Select Release from the Definitive
Software Package Catalog
Release
Type
Deploy Release on
Test Environment.
Release
Validation
Release
Sign Off
Release Notification.
Deploy Release on
Production Environment.
Configuration Steps:
1. Embedded Entitlements Manager
2. Workflow component
3. ITCM - Web Admin Console
4. ITCM - LDAP
5. Service Desk with LDAP
Configure Embedded Entitlements Manager
> Configure the EEM Server to reference global users and
groups.
Release Management Process Definition Roles
> Following are the actors that need to be configured:
DSMWebService: (Invokes the Software Delivery Web
Services)
> RM flow
ReleaseValidator: (Performs Release Validation Activity)
ReleaseApprover: (Performs Release Approval Activity)
Configure ITCM Web Admin Console
> Open the configuration file:
<install-drive>:\Program
Files\CA\DSM\WebConsole\webapps\wac\WEB-
INF\classes\com\ca\wac\config\WACConfig.properties
> Populate the below keys:
WorkflowInstalled=true
WorkflowURL=http://<CA_WorkflowMachineHostname>:
<PortNumber>/pm
WorkflowProcessDefination=Release Management
ServiceDeskEndpoint=http://<CA_ServiceDeskMachine_Hostnam
e>:<PortNumber>/axis/services/USD_R11_WebService?wsdl
CA Service Desk Manager Integration
> Optional
> Can Share EEM and WF
> Will update associated Change Order with
Release progress
Release Management Workflows
> Implemented using CA Workflow
> Stand alone or integrated with WF from:
CA Service Desk Manager
CA Service Catalog
50 © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.
Any further questions?