Migrating from Redwood to CA Workload Automation AE (AutoSys®) - Drivers, Methodology and Case Study(s)

World®
’16
Migrating from Redwood to CA Workload
Automation AE (AutoSys®) - Drivers,
Methodology and Case Study(s)
Mark Mannion - Managing Director - Extra Technology
MFX130S
MAINFRAME AND WORKLOAD AUTOMATION

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type
of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
Extra Technology encounters an increasing number of customers attracted by the cost-savings
and increased efficiency of consolidating their workload automation solutions, and migrating
silos of expensive, niche tools like Redwood Cronacle to their corporate standard CA Workload
Automation solution.
In this session, we will present a case study of a customer that was recently migrated from
Redwood Cronacle to CA Workload Automation AE (AutoSys®). We will discuss the main
drivers for the conversion, the tools and methods used, gotchas and pitfalls as well as the
successful end result.
Mark
Mannion
Extra Technology
Managing Director

Agenda
INTRODUCTION AND BACKGROUND
THE DRIVE FOR WORKLOAD AUTOMATION CONSOLIDATION
WRAP UP
MIGRATING FROM REDWOOD CRONACLE TO CA WORKLOAD AUTOMATION AE
CUSTOMER CASE STUDY 1
CUSTOMER CASE STUDY 2
1
2
3
4
5
6

Introduction & Background
Who?
§ 2007 - Founded by CA Workload Automation SMEs
§ Vendor Professional Services & Tech Support
§ WA Administrators for Global Corporates
§ FS, Retail, Manufacturing, Govt
§ US, UK, Europe, Middle East and Beyond
§ Wide Experience of CA WA Competitors
§ CA Worldwide Conversion Partner
Extra Technology www.extratechnology.com

The Drive For Workload Automation Consolidation
Why?
§ Customers using multiple WA tools silos
§ Niche tools addressing specific business
requirements
§ Disparate systems
§ Either complex inter-dependencies &
integration
§ Or no inter-dependencies & integration
§ Separately licensed, hosted, maintained
§ Expertise, standards & best practices diluted
or lost
§ High Cost, High Complexity, Increased Risk

The Drive for Workload Automation Consolidation
Why?
§ Benefits of Consolidation
– Single, company-wide standard, with
centralised control
– Simpler to own and operate
– Best Practices enforced
– Tighter Integration
– Reduced licensing cost
– Smaller, better focussed WA
administration teams
§ Reduced Cost, Reduced Complexity,
Reduced Risk

Migrating from Redwood Cronacle to CA WA AE(CA AutoSys)
§ A Little about Redwood Cronacle
– Niche product, hard to find skills or expertise
– Tightly bound to Oracle®, but only Oracle
– Heavy reliance on Oracle-specific features and functionality
– Latest version is essentially a new product:
§ Either migrate to competitor WA product, or…
§ Vendor offers paid conversion
What?

Redwood Cronacle
§ Basic Object Oriented (e.g. call single job
multiple times)
§ Embedded scripts/SQL
§ Job scheduling information in database
§ Dependencies in database
§ Embedded Security
§ It’s a Development Framework
Migrating from Redwood Cronacle to CA WA AE(CA AutoSys)
A Few Differences
CA WA AE(CA AutoSys)
§ Flat Name Space
§ External scripts/SQL
§ Job scheduling information via JIL
§ Dependencies via JIL
§ External Security
§ It’s a Workload Automation tool

Customer Case Study 1
§ Conversion = part of migration
& set up of new business
§ Decision = consolidate
Redwood to CA WA AE
– CA WA AE the Preferred WA Solution
– No shortage of CA WA AE skills in
Europe or India
– Dedicated WA Tool, Not A
Development Framework
A European Financial Services Company

§ Simple architecture
§ Several hundred jobs,
– Shell scripts, PL/SQL
§ Shell scripts running:
– UNIX Commands
– FTP
– SQL

§ Conversion Process Overview
– Redwood extract
– ET Automated Migration Tool
§ Convert Redwood data to basic JIL
§ Extract shell scripts and PL/SQL from Redwood database
§ Apply naming conventions
§ Set ‘owner’, ‘machine’, ‘std_out’, ‘std_err’ globally
§ Inter job dependencies inferred from data
§ Shell scripts, PL/SQL, variables created separately

§ Conversion Challenges:
– Variable handling
– Account credentials
– Calls to Redwood specific functions
– Interaction with (and storage to) Redwood database
– ‘Un-picking’ of Redwood ‘lock-in’
§ Requires in-depth testing
§ Application SME input required

§ Conversion Successes:
– Workflow visibility radically improved
– SQL & FTP processes no longer hidden
in scripts
– No Skills Shortage for Admin &
Operations staff
– Reduced Risk
§ Workflows less reliant upon complex
scripting
§ SLAs monitored via CA WA iDash
§ Straightforward support

§ Conversion = pilot for global WA
consolidation
§ CA WA AE selected over two rivals
– Product reliability
– Vendor relationship
– Product roadmap
– Eliminate role duplication
– Eliminate infrastructure duplication
– Dedicated WA Tool, Not a development
framework
A Global Financial Services Company

§ Global architecture
– Agents on UNIX, Linux, Windows and i5
§ Complex scripted workflows
– Extremely complex scripting
– No boundary between application and WA code
– Redwood functions too deeply embedded within application code
§ Redwood functionality changes require significant un-picking
– Compelling event
– Even continuing with Redwood will require major ‘migration’

§ Conversion Process Overview
– Redwood extract
– ET Automated Migration Tool
§ Convert Redwood data to basic JIL
§ Extract shell scripts and PL/SQL from Redwood database
§ Apply naming conventions
§ Set ‘owner’, ‘machine’, ‘std_out’, ‘std_err’ globally
§ Inter job dependencies inferred from data
§ Shell scripts, PL/SQL, variables created separately

§ Conversion Challenges:
– Extremely complex scripting
§ Redwood functions were too embedded within Application code
§ Required access to customer’s dedicated Redwood development team
– Variable handling
– Many calls Redwood specific functions
§ Many obsolete in latest version of Cronacle
– Significant dependence on Redwood database

§ Conversion Successes:
– Common Global WA infrastructure
– Advanced Workload Analytics using CA WA
iDash
– Separation of application & workload code
– Simplified workflow monitoring
– SQL and FTP processes no longer hidden in
scripts
– Reduced Risk
§ Workflows less reliant upon complex scripting
§ Straightforward support

Wrap-Up
§ Reduced Cost
§ Reduced Complexity
§ Reduced Risk
Migrating Redwood to CA WA AE(CA AutoSys) Delivers…

Questions?

Thank you.
Stay connected at communities.ca.com

Mainframe and Workload Automation
For more information on Mainframe and Workload Automation,
please visit: http://cainc.to/9GQ2JI

Migrating from Redwood to CA Workload Automation AE (AutoSys®) - Drivers, Methodology and Case Study(s)

Recommended

More Related Content

Similar to Migrating from Redwood to CA Workload Automation AE (AutoSys®) - Drivers, Methodology and Case Study(s) (20)

More from CA Technologies (20)

Recently uploaded (20)

Migrating from Redwood to CA Workload Automation AE (AutoSys®) - Drivers, Methodology and Case Study(s)