Migrating from REDWOOD CRONACLE TO CA WORKLOAD AUTOMATION GUIDE

Migrating to Redwood from Control-M

Overview

• Our expertise and how we work
• Migration demo
• Summary - What we offer you

key questions:

• Is is a lot of work ?                       Yes , but less than you might think
• Is there risk ?                                Yes, but it can be controlled
• Is there one perfect way?             Not for everyone , but for you individually

Considerations

lift& shift _______ optimize

Lift and shift is nver just lift and shift (for all WLA product)

Plan for optimal use if the Redwood prodcut for

• Better performance
• Usability
• Development effort
• Maintenance effort

Align your automation strategy

• What other areas of automation and orchestration that should be added in the furture.

Who's involved in the automation

How do you want to govern the automation?

Do you want to use this opportunity to drive change?

Migration Project

• Migration assessment
• Project apprach
• System configuration

For each phase

Initial Import

• Using automated migration tool

Evaluate

• Analysis everything is correct
• Define standard for optimization

Optimize/Reimport

• Automate/manual adjustments

Test

• Tests according to customer's testplan

Promote/Schedule

• Schedule the imported processes
• Promotion in next Env

Agenda

• Introduction and Background
• The Drive for workload automation consolidation
• Migrating from REDWOOD CRONACLE TO CA WORKLOAD AUTOMATION
• CUSTOMER CASE STUDY1
• CUSTOMER CASE STUDY2
• WRAP UP

The Drive for Workload Automation Consolidation Why?

Benefits of Consolidations

• Single ,Company-wide standard , with centralised control
• Simpler to own and operate
• Best Practises enforced
• Tighter Integration
• Reduced licensing cost
• Smaller,better focussed WA adminstration team

Reduce Cost ,Reduced Complexiity, Reduced Risk

Migrating from REDWOOD CRONACLE TO CA WORKLOAD AUTOMATION(CA AutoSys)

What?

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
• Lastest version is essentially a new product:

            Either migrate to competitor WA product

           Vendor offers paid conversion

A Few Differences

Redwood Cronacle(Runmyjobs)

• Basic Object Oriented (eg. call single job multiple times)
• Embedded scripts /SQL
• Job Scheduling information in database
• Dependencies in database
• Embedded Security
• It's a Development framework

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

A European Financial Service Company

• Conversion = part of migration & set  up of new business
• Decision = consolidate Redwood to CA WA AE

         - CA WA AE the Prefered WA Solution

        - No sortage of CA WA AE  skills in Europe or India

       - Dedicated WA Tool , Not A Development Framework

• Simple architecture
• Serveral 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 process no longer hidden in scripts

- No Skills Shortage for Admin & Operations staff

- Reduce Risk

•   Workflow less reliant upon complex scripting
•  SLAs  monitored via CA WA iDash
• Straightforward support.

Customer Case Study 2

A Global Financial Services Company

• 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

• 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 up-picking

      - Compelling event

      - Even continuing with Redwood will require major 'migration'

• Conversion Process Overview

     - Redwood extract

    - ET Automated Migration Tool

          - Convert  Reedwood 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 function

   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

   Workflow less reliant upon complex scripting

  Straightforward support.

Wrap-Up

Migrating Redwood to CA WA AE(CA AutoSys) Delivers

• Reduced Cost
• Reduced Complexity
• Reduced Risk