Pre-Con Education: Migrating to CA Release Automation 5.5.2 to Exploit New Features with Engineering Services Tips

Pre-Con Education: Migrating to
CA Release Automation 5.5.2 to
Exploit New Features with Engineering
Services Tips
Donald Gall
DevOps: Continuous Delivery
CA Technologies
Engineering Services Architect
DO4X98E
#CAWorld

2 © 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
For Informational Purposes Only
Terms of this Presentation
© 2015 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The presentation provided at CA
World 2015 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer
references relate to customer's specific use and experience of CA products and solutions so actual results may vary.
Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights
and/or obligations of CA or its licensees under any existing or future license agreement or services agreement relating to any CA software
product; or (ii) amend any product documentation or specifications for any CA software product. This presentation is based on current
information and resource allocations as of November 18, 2015, and is subject to change or withdrawal by CA at any time without notice. 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 may make such release available to new licensees in the form of a regularly scheduled major product release. Such
release may be made available to licensees of the product who are active subscribers to CA maintenance and support, on a when and if-
available basis. The information in this presentation is not deemed to be incorporated into any contract.

Abstract
Join members of the CA Technologies Engineering Services
team for a presentation and Q&A about upgrading your
environment and migrating your applications in order to
fully exploit new features in CA Release Automation. In this
session, you will learn about the server architecture and
connectivity, how to prepare for an upgrade or migration,
and best practice methodologies based on real world
experience.
Don Gall
CA Technologies
Engineering Services
Architect

Agenda
WHAT’S NEW IN CA RELEASE AUTOMATION 5.5.X
UPGRADE BEST PRACTICES
QUESTIONS AND ANSWERS
MIGRATION BEST PRACTICES
CA RELEASE AUTOMATION APPLICATION MIGRATION BEST PRACTICES
CA RELEASE AUTOMATION 4.X TO 5.5.X ARCHITECTURE DIFFERENCES
1
2
3
4
5
6

What’s New in CA Release Automation 5.5.X

What’s New in CA Release Automation 5.5.x
Marquee Features
EASE OF USE
Migrate Process Design
experience from
Automation Studio to ROC
Improve
usability
Improve look
and feel
DASHBOARD AND REPORTING
Get insight into key metrics and
historical data
Consolidate
Reporting

What’s New in CA Release Automation 5.5.x
Marquee Features
ENTERPRISE READINESS
Improve Product
Stability
Performance
Enhancements
Increase
Scalability
ENVIRONMENT CONFIGURATION
Add Environment Configuration capabilities

Migrate over
Upgrade
New operating system and/or
hardware for management
servers
Ability to Test upgrade without
impacting Production instance
Upgrade
In-place upgrade of an existing
CA Release Automation
infrastructure
Migration
Create a new CA Release
Automation infrastructure and
Migrate existing applications
and deployments
Upgrade or Migrate

Upgrade Best Practices
 Ensure that the existing infrastructure meets the
hardware requirements for the new version
 Ensure that any additional network port changes have
been planned
 In-place upgrade will automatically upgrade existing
applications
 Upgrades will need to be modified to utilize any new
functionality

Upgrade Best Practices (continued)
In-place upgrade strategy
 Backup Database, NAC, and NES
 Disable any CI integrations and UI access to Management
Server (NAC)
 Disable any scheduling triggers
 Upgrade Release Automation Management Server (NAC)
 When upgrading Highly Available Management Servers shutdown
secondary node before upgrading primary node
 When upgrading secondary node ensure that Primary node is shutdown

Upgrade Best Practices (continued)
In-place upgrade strategy
 Upgrade a small network of an Execution server and agents to
be used for validation of the upgrade
 Upgrade Remaining Execution Servers
 Upgrade all Agents
 Number of agents to be upgraded is controllable via the system
setting “Agent upgrade batch size”
 Uninstall any CI server plugins and Install new version
 Modify any applications using REST calls integrating with
Release Automation Management Server (NAC)

Upgrade Best Practices – Steps
Enduser
Outage
Announcement
Disable UI
Load Balancer
(if required)
Disable CI
Plugins or
External
Systems
Ensure no
Deployments
are In-Progress
Stop
Management
Server
Pause Database
Mirroring
Back up the
database
Upgrade NAC
on Primary
Node
Upgrade
Single
Execution
Server
Upgrade a Few
Agents to Test
Application
Deployment
Test
Application
Deployment
Validate
Upgrade is
Successful
Roll Back
Upgrade
Stop NAC
and NES
Restore
Database to
Previous version
Upgrade
Remaining
Execution
Server
Switch NAC to
Primary NAC
Upgrade NAC on
Secondary
Node
Complete
Upgrade
Upgrade CI
Plugins
Enable CI
Plugins
Upgrade
Remaining
Agents
Revert
NAC/NES to
Backup
Uninstall and
Install Previous
Version
Uninstall
Upgrade Agents
Start NAC and
NES
Enable CI
Plugins
or
No
Yes Upgrade
Checkpoint
Yes/No

CA Release Automation In-Place Upgrade
Nolio
3.3
Nolio
4.1
Nolio
4.5
Release Auto
4.7.1
Release Auto
5.0.x
Release Auto
5.5.x
Nolio 4.1
Nolio 4.5
CA Lisa Release Automation 4.7.1
CA Release Automation 5.0.x
CA Release Automation 5.5.x
5.0.2.b78
5.0.1.b716
4.7.1.b360
4.7.1.b343
4.7.1.b322
4.7.1.b385
5.0.0.b617
4.7.1.b413
End of Service Announcements
3.x / 4.x March 31st 2015
4.5.1 and 4.7.1 October 2015
5.5.2.b191
5.5.1.b1312
5.5.0.b831

Migration Best Practices
MIGRATION STEPS
NOTE: Exports do not contain ROC
level details or artifacts. These will
need to be manually recreated.
Install Management
Server (NAC) on new
server with same version
as in production.
Install Execution Servers. Deploy Agents.
1 2 3
Export Applications from
original server.
Import Applications into
new environment.
Upgrade environment
using in place upgrade.4 5 6

Applications will need to be modified to utilize any
new functionality, and we will discuss this in the
upcoming section
Note : The Design Process data that is exported
from the ASAP UI can only be imported
into an environment of the same version.

CA Release Automation Application

CA Release Automation Application Migration
Best Practice
When moving to CA Release
Automation 5.5.x from
previous versions,
modifications need to be
made to make full use of the
new functionality supplied
with 5.5.x
Large processes should be
reviewed, and core
functionality should be
broken into smaller processes
that can be reused

CA Release Automation Application Migration
Flows that previously used XPath queries to parse
xml files and set parameters can be replaced with
Collection Elements; This new type of flow loop
allows for a much more efficient method for
handling this functionality
Best Practice

Artifact Deployment
ARTIFACT DEFINITION'S ARE EXPOSED WITHIN THE DESIGNER UI AS PARAMETERS
When these parameters are
used within a published
process that is used within a
deployment plan, the
artifacts are automatically
either copied to the relevant
execution servers that will
take part in the deployment
or to an artifact cache on the
agent machines.
Any artifact copy processes
within the application should
be reviewed and modified to
utilize this new functionality.
Utilizing the artifact cache
will speed up the
deployment time because
the artifacts are copied
locally instead of over the
network.

Artifact File Caching – CA Release Automation 5.5.x
Artifact
Repository
Artifact Retrieval
Agent Cache
Folder
Execution Server
Cache Folder
When NES routing is
configured the artifact
will be routed via other
NES’s
For an
Environment
with single NES the
artifacts are sent directly
to the Agent machine
Execution Server
Cache Folder
Agent Cache
Folder
Release LocationAGENT MACHINE
CANolioAgentartifact_store
Program FilesCAReleaseAutomationServerartifact_store

New Parameter Types
Environment Parameter
The value of an environment parameter
can either be set in the
ROC/administration/Environment
Configuration or via an action. When
creating a deployment any environment
parameters within the application, it
will be updated with the relevant
environment parameter.
Note: Environment Parameters are automatically
created during an upgrade for any parameters that
has the value set within the Environments tab.
Release Parameter
Release Parameters can be updated
using the manifest file, which can be
created from the deployment template
or by using an action.

CA Release Automation 4.7.1 Fundamentals
Initialization
steps
Deployment
steps
Post
Deployment
steps
APPLICATIONS
PROCESSES
ENVIRONMENTS
TEMPLATES ARTIFACTS
RELEASES
Actions & Flows
AUTOMATION STUDIO RELEASE OPERATIONS CENTER

CA Release Automation 5.5.x Fundamentals
APPLICATIONS
PROCESSES
ENVIRONMENTS
ARTIFACT TYPES
Actions & Flows
DEPLOYMENTS
Initialization
step
 Pre-Plan Step
 Pre-Deployment
Step
 Environment
Build Step – 5.5
Deployment
step
Post
Deployment
step
DEPLOYMENT TEMPLATES
TEMPLATE CATEGORIES
ENVIRONMENT CONFIGURATION
DEPLOYMENT PLANS
PROJECTS
Initialization
steps
Deployment
steps
Post
Deployment
steps
ARTIFACT PACKAGE
ARTIFACT
DEFINITIONS
AUTOMATION STUDIO RELEASE OPERATIONS CENTER
ARTIFACT VERSIONS

Deployment Plan
INITIALIZATION STEPS
The Pre-Plan step is used to add an artifact
package to your deployment plan. The
artifact package is comprised of all artifacts
required for the deployment. The Pre-Plan
step can also be used to set release and
template parameters.
The Pre-Deployment step is used to update
your deployment according to the selected
environment. When the deployment plan is
created, the target environment is selected,
and this means that the Pre-Deployment
step can be used to set parameters based on
the target environment.
NOTE: The pre-plan step runs after
deployment plan creation.
NOTE: A new Initialization step had be introduced with 5.5.x to integrate with
Configuration Management tools to run baseline checks.

Deployment Plan
Deployment Steps
When reengineering 4.x applications,
the core components within the
application should be broken down into
functional modules and published as
individual processes. These processes
are brought together as deployment
steps and can be ordered using the
dependencies functionality within the
deployment plan.
Post Deployment Steps
Post Deployment steps would normally
include any testing or validation
activities required to ensure that a
deployment has been successful.

CA Release Automation 4.X to 5.5.X
Architecture Differences

CA Release Automation 4.7.1 Internals
Monitoring, Test,
Build,
Virtualization &
Cloud etc
SCM
SVN, TFS
Repository
Artifactory, Nexus,
Archiva
ALM Systems
Service Desk
ServiceNow
CI Server
TFS, Hudson,
Jenkins
Actions SDK
Actions / Plugins
Inventory
Database Users,
Process, Release,
Audit
Environment
Artifacts
Repository
PRESENTATION LAYER
ASAP - Swing UI Dashboard - WEB ROC - WEB
OpenAPIsREST,
SOAP,CLII
DataAccessFramework
Hibernate
CENTER CORE SERVICES
Application
Mgmt
Artifact
Mgmt
Environment
Mgmt
Users, Roles &
Permissions
Process Flow &
Compilation
Template Release &
Compilation
Execution Engine
License Mgmt
Scheduler &
Calendar
Audit &
Report
Server Mgmt
Local/Geo
Proxy
Flow Control Events /
Messages
File Distribution &
Caching
EXECUTION SERVER
Workflow Engine & Actions Executor
AGENT
THIRD-PARTY
INTEGRATIONS
INFRASTRUCTURE
LAYER

CA Release Automation 5.5.x Internals
SCM
SVN, TFS
Repository
Artifactory, Nexus,
Archiva
Help Desk
Service Desk,
Service Now
CI Server
TFS Hudson,
Jenkins
THIRD-PARTY
INTEGRATIONS
INFRASTRUCTURE
LAYER
Database
Users, Process,
Release, Audit
Environment
Repository
Artifacts,
Repository &
Action Pack, Store
Nexus
PRESENTATION LAYER
Designer Swing UI Dashboard UI
Release Operations
Center UI
OpenAPIs
REST,SOAP,CLII
DataAccessFramework
Hibernate
DATA MANAGER
Application
Mgmt
Artifact
Mgmt
Environment
Mgmt
Users, Roles &
Permissions
Process Flow
& Compilation
Template
Release &
Compilation
Execution
Engine
Action Pack
Download
Manager
Scheduler &
Calendar
Audit &
Reports
Server Mgmt Active MQ
Local/Geo
Proxy
File Distribution
& Caching
Flow Control
Events / Messages
EXECUTION SERVER
Active MQ
Workflow Engine & Actions Executor
AGENT
Provisioning
CA Cloud Manager
Monitoring
Test Systems
Authentication
Ldap / ADAuthentication
Ldap / ADAuthentication
Ldap / AD
File Caching - Artifacts

Architecture Changes between 4.7.x and 5.5.x
Active MQ Added to
Execution Server and
Management Server (NAC)
Action Pack Download Service
INITIALIZATION STEPS
Port TCP 61616 / 61617 required
between Management Server (NAC)
and Execution Servers
 Management Server (NAC) requires
FTP access to CA FTP site
 Port TCP 8083 required from Browser
to Management Server (NAC)

CA Release Automation 4.7 Interconnectivity Architecture
END USERS
Management
Server (NAC) &
Repository
Database
Server
Execution
Server
Execution
Server
Agent Node
Agent Node
Email Server
(Optional
Active Directory
(Optional
Agent Node
Agent Node
Agent Node
5
6
3
1
1
4
4
1
2
3
4
5
6
LEGEND
HTTP Traffic – HTTP 8080 / HTTPS 8443
Repository Traffic – TCP 8080
Database Communication
Agent Communication – TCP 6600
AD User Authentication – LDAP 389 / LDAPS 636
Email Communication – SMTP 25
Notes:
Agents on Execution servers use port 6900
Ports required to deploy agents from
Execution servers
Windows = TCP 139 / 445
Unix / Linux = TCP 22
1

CA Release Automation 5.5.x Interconnectivity Architecture
END USERS
Management
Server (NAC) &
Repository
Database
Server
Execution
Server
Execution
Server
Agent Node
Agent Node
Email Server
(Optional
Active Directory
(Optional
Agent Node
Agent Node
Agent Node
1
5
6
3
1
1
4
4
1
2
3
4
5
6
LEGEND
HTTP Traffic – HTTP 8080 / HTTPS 8443
Repository Traffic – TCP 8080
Database Communication
Agent Communication – TCP 6600
AD User Authentication – LDAP 389 / LDAPS 636
Email Communication – SMTP 25
Action
Pack FTP
download site
2
8
7
7
8
7
Active MQ – TCP 616161 / SSL 61617
Action Pack Download and Updates Ftp.ca.com
or Internal ftp site – TCP 21
Notes:
Agents on Execution servers use port 6900
Ports required to deploy agents from
Execution servers
Windows = TCP 139 / 445
Unix / Linux = TCP 22

Recommended Sessions
SESSION # TITLE DATE/TIME
DO4X96E
Pre-Con Education: Explore Advanced CA Release
Automation Configuration Topics
11/17/2015 at 3:00 m
DO4T06S
Vision and Roadmap: Learn How Application Release
Solutions Help You Lead the Way
11/18/2015 at 2:00 pm
DO4T35T
Tech Talk: Integrate Infrastructure Configuration
Management with Release Automation for the Best of
Both Worlds
11/19/2015 at 2:00 pm

Must See Demos
CA Release
Automation
CA Release
Automation
Theater 4
Cloud & SaaS
Deployments
CA Release
Automation
Theater 4
CA RA Rapid
Dev. Kit, SDK
CA Release
Automation
Theater 4
Integrations
CA Release
Automation
Theater 4

Follow On Conversations At…
Smart Bar
CA Release
Automation
Theater 4
Tech Talks
CA Release
Automation
Theater 4

Q & A

Seven Strategies for Successful Upgrades

Seven Strategies for Successful Upgrades
1. Don’t Get Left Behind
2. Consider ROI
3. Stay Safe
4. Sweat the Small Stuff
5. Get Organized
6. Make a Plan
7. Enlist the Experts

For More Information
To learn more, please visit:
http://cainc.to/Nv2VOe
CA World ’15

Pre-Con Education: Migrating to CA Release Automation 5.5.2 to Exploit New Features with Engineering Services Tips

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Pre-Con Education: Migrating to CA Release Automation 5.5.2 to Exploit New Features with Engineering Services Tips

Similaire à Pre-Con Education: Migrating to CA Release Automation 5.5.2 to Exploit New Features with Engineering Services Tips (20)

Plus de CA Technologies

Plus de CA Technologies (20)

Dernier

Dernier (20)

Pre-Con Education: Migrating to CA Release Automation 5.5.2 to Exploit New Features with Engineering Services Tips