CA Workload Automation AutoSys 4.x to r11 Upgrade Tips · PDF fileCA Workload Automation AutoSys 4.x to r11 ... Verify that jobs are regularly executing on each ... Explain the signficant

CA Workload AutomationAutoSys 4.x to r11Upgrade TipsKeith MaconiTrans Global Industries, Inc.

AutoSys 4.x to r11 Upgrade Tips

2

October 12, 2009 AutoSys 4.x to r11 Upgrade Tips Copyright © 2009 CA

Abstract

This session will cover helpful tips that can be utilized to

ease the transition from AutoSys version 4.x to the

current release of AutoSys r11. Topics will include simple

tasks that can prepare your environment and an

overview of the important steps in performing the

upgrade.


3


Agenda

> The key areas that will be covered are:

Planning

Preparation

Installation

Testing

Training

Migration


4


Speaker Information

Keith Maconi

Trans Global Industries, Inc.

Over 20 years experience with system administration and

job scheduling in the manufacturing, banking, investment,

defense and outsourcing industries.

Trans Global Industries, Inc. is a CA Workload Automation

Service and Education Partner that provides skilled

AutoSys and WCC service, support and training.

[email protected]

Phase 1: Planning

CA Workload Automation AutoSys 4.x to r11 Upgrade Tips


6


Summary: Planning

A key element in the successful upgrade process is to

sufficiently plan the upgrade. A few key steps will greatly

increase your chance for a smooth transition.

> Survey

Know what you currently have

Verify all of the environment

> Architecture

Learn how to or obtain skilled resources to plan new

environment


7


Planning: Survey

> Know your environment

Perform a complete survey to verify all installed

components

Verify that jobs are regularly executing on each installed

agent

Determine when upgrade windows may exist due to

natural job lulls

Verify all configuration information


8


Planning: Survey

> Survey users

Determine who is actually currently directly interacting

with AutoSys

Verify what methods they use:

– User vs. group accounts

– Command line vs. GUI

Determine if user access should be modified with new

environment


9


Planning: Architecture

> Training vs. Consulting

A properly configured r11 environment is complex

Expert assistance can ensure timely deployment

Training and practice are required to self-architect

Plan sufficient time to obtain training or skilled assistance

> New or Existing Servers

It is much easier to install the new central components on

clean servers than on existing servers

Phase 2: Preparation



11


Summary: Preparation

Once an architecture has been developed, proper

preparation of the environment is important. Some key

elements of this process are:

> Correct issues

Fix naming of objects (jobs, calendars, global variables)

Clean up unused agents, obsolete jobs and user access

> Set expectations

Ensure all involved parties understand how the upgrade

will affect them


12


Preparation: Correct Issues

> Fix naming issues

Check for multiple jobs with the same name but different

case (MyJob vs. myjob)

Fix or create plan to fix object names that do not comply

with r11 enforced naming policies

– a-z, A-Z, 0-9, period (.), underscore (_) and hyphen (-)

– Watch for previously allowed characters (such as @)


13



> Clean up

There is no requirement to remove unused agents, but

identify them to prevent a new agent installation

Archive old jobs, calendars, global variables that are not

required

– Not critical, but can benefit new environment if significant


14



> Set expectations

Explain the signficant differences between the versions

– Change in interface options (WCC vs. GUI)

Schedulers must begin using new naming conventions

Decide if new log file strategy is required

– WCC allows review of prior run logs

– Log retention and database job run history should be

similar

– Not all jobs should have unique logs

High frequency or looping jobs

Phase 3: Installation



16


Summary: Installation

Install the new environment in parallel to the current

environment, as designed. Ensure that all required

patches are applied across the environment.

> Install components in proper order

> Install required patches

> Build installation process for agents


17


Installation: Installation Order

> Install components in proper order

Build order can vary based on architecture

System hosting EEM should be built first

Install WCC before Reporting

Do not install additional agents until all core servers are

functional


18


Installation: Installation Patches

> Install required patches

Review support.ca.com for all latest patches

– Ensure you obtain patches for every OS you will use

– Verify patch prerequisites to ensure all patches are found

Save the patch instructions on every server

– Keep the .TXT file for every patch

– Save in a single directory on every server

– Helps identify which patches have been applied


19


Installation: Build Agent Installation Process

> Build installation process for agents

Agents are instance-less

– Only one process required per OS type

Ensure all required patches are included in process

To ease maintenance, do not install Clients where not

required

– Client allows users to execute AutoSys commands locally

Phase 4: Testing



21


Summary: Testing

Ensure that you test each of the key elements and jobs that

you identified during the Planning stage. Some key

elements to test are:

> Agents and Jobs

> Security and Access

> Views

> Failover and Recovery

> Data Migration


22


Testing: Agents and Jobs

> Agents and Jobs

> Security and Access

> Views

> Failover and Recovery

> Data Migration


23


Testing: Agents and Jobs

> Agents

Test each agent as it is added to the environment

Maintain a "test job" for each agent installed

> Jobs

Test each job type identified during the survey

Test a job for each agent and user combination


24


Testing: Security and Access

> Security

Validate security rules match design

Ensure that Active Directory integration is working

> Access

Verify that all users can access WCC

Verify that all users have proper access to AutoSys


25


Testing: Views

> Views

Verify that all existing views are created in new

environment

Ensure proper security exists

Validate that every view is functional

– It might be adviseable to test after data migration or you

can create test jobs


26


Testing: Failover and Recovery

> Failover

Verify that any failover or high-availability solution is

properly working

– When possible, actually fail the server or database

– Test all combinations of failures

> Recovery

A proper Disaster Recovery solution is critical

Test solution prior to go-live, if possible

Have written procedures in place


27


Testing: Data Migration

> Data Migration

Test your data migration process

Time the entire procedure to validate upgrade window

Ensure that no errors occur during data migration

– Fix any errors found and re-test until clean

Validate that all data arrived

Be careful

– Don't migrate live jobs into a running target environment

– Modify commands to disable. " command: Echo .... "

Phase 5: Training



29


Summary: Training

Training is key to ensuring success and the ability for users

to obtain the services that they require.

> For large organizations, consider "train-the-trainer"

> Onsite training may be more cost effective


30


Training: Train-the-trainer

> Identify key or power users in each group

> All operators and production schedulers should receive

direct training, when possible

> Prior experience with AutoSys 4.5 is helpful, but no

substitute for AutoSys r11 training

> Developer groups need training, even if they do not

directly create jobs

Ensure developers understand new capabilities


31


Training: Onsite Training

> Cost effective for groups of 6 or more

> Can be scheduled around your needs

> Training can be done on your new AutoSys r11 servers

Users learn how to use AutoSys and your standards

Existing environments can use their own jobs as examples

> Schedule training no more than 4 weeks prior to go-live

Phase 6: Migration



33


Summary: Migration

Data migration is the final step in the upgrade process. The

process should have been fully tested prior to this step.

> Save time by migrating non-changing items in advance

> Migration order is key to a manual migration


34


Migration: Advanced items

> Freeze changes prior to actual go-live

> Migrate non-changing items in advance

Calendars

User Credentials (for AutoSys jobs)


35


Migration: Migration Order

In general, the following is a good order to move elements:

1. Calendars

2. Credentials

3. Global Variables

4. Jobs (without schedules or dependencies)

5. Job statuses

6. Job Dependencies

7. Job Schedules

Questions?


Documents

CA Workload Automation AutoSys 4.x to r11 Upgrade Tips · PDF fileCA Workload Automation AutoSys 4.x to r11 ... Verify that jobs are regularly executing on each ... Explain the signficant