Cross Instance between R11.3.6 SP5 and 11.3.6 SP2

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent

Issue/Introduction

 

How To configure Cross Instance Scheduling in Workload Automation AE with different version ?

Environment

WAAE 1.3.6 spx

Resolution

 

NOTE:Your source and target Workload Automation AE instances do not have to be the same AE version. These instructions assume that both environments are at least r11.3.6.

 

SRC	TGT
source_server	target_server
AE: r11.3.6 SP1	AE: r11.3.6 SP2

 

 

 

CONFIGURE THE SCHEDULER FOR CROSS INSTANCE SCHEDULING

 

1. From the SOURCE server, open the config.$AUTOSERV (or config. %AUTOSERV%) file

2. Find the CrossPlatformScheduling parameter and update the parameter: CrossPlatformScheduling=2

3. Save the file

4. On Windows, pause/resume the application server service; on Linux/Unix, do a ‘kill -HUP pidxxx’ command on the application server process ID

5. From the TARGET server, repeat steps 1-5

    

 

DEFINE THE EXTERNAL INSTANCE

 

1. From the SOURCE server, define an external instance for the TARGET server

 

SRC

/* ----------------- TGT ----------------- */   insert_xinst: TGT xtype: a xmachine: target_server xport: 9000 xcrypt_type: DEFAULT

 

 

 

1. You can confirm the external instance has been defined by looking in the event_demon:

 

SRC

CAUAJM_I_40245 EVENT: REFRESH_EXTINST CAUAJM_I_50407 Reading external instance information. CAUAJM_I_50410 Instance=[TGT]: Type=[a] Server=[target_server] Port=[9000]

 

 

 

1. From the TARGET server, define an external instance for the SOURCE server

 

TGT

/* ----------------- SRC ----------------- */   insert_xinst: SRC xtype: a xmachine: source_server xport: 9000 xcrypt_type: DEFAULT

 

 

 

1. You can confirm the external instance has been defined by looking in the event_demon:

 

TGT

CAUAJM_I_40245 EVENT: REFRESH_EXTINST CAUAJM_I_50407 Reading external instance information. CAUAJM_I_50410 Instance=[SRC]: Type=[a] Server=[source_server] Port=[9000]

 

 

 

CONFIRM THE SOURCE/TARGET MACHINES ARE DEFINED

 

1. On the SOURCE server, the TARGET machine should exist in the AEDB

2. You should be able to successfully autoping the TARGET machine from the SOURCE server

   CAUAJM_I_50023 AutoPinging Machine [target_server]

   CAUAJM_I_50025 AutoPing WAS SUCCESSFUL.

3. On the TARGET server, the SOURCE machine should exist in the AEDB

4. You should be able to successfully autoping the SOURCE machine from the TARGET server

   CAUAJM_I_50023 AutoPinging Machine [source_server]

   CAUAJM_I_50025 AutoPing WAS SUCCESSFUL.

    

 

DEFINE A JOB TO TEST CROSS INSTANCE SCHEDULING

 

You can test your cross-instance scheduling using the sample jobs below.

 

If you want to schedule a job from the SOURCE server to a TARGET Windows server, use this job:

 

WINDOWS

/* ----------------- cross_win ----------------- */   insert_job: cross_win   job_type: CMD command: cmd /c "cd %AUTOUSER & dir" machine: target_server owner: [email protected]_server permission: date_conditions: 0 std_out_file: "C:\Temp\cross_win.out" std_err_file: "C:\Temp\cross_win.err" alarm_if_fail: 1

 

 

 

• This job will change to the Workload Automation AE install directory and do a listing.

• The command assumes that the %AUTOUSER% environment variable is already set

• This command executes in a regular command prompt and NOT in the WAAE Command Prompt

• The std_out and std_err files are written on the TARGET server

    

 

If you want to schedule a job from the SOURCE server to a TARGET Linux/Unix server, use this job:

 

LINUX/UNIX

/* ----------------- cross_lnx ----------------- */   insert_job: cross_lnx   job_type: CMD command: "cd $AUTOUSER && ls -al" machine: hudja03-U158937 owner: [email protected] permission: date_conditions: 0 std_out_file: "/tmp/cross_lnx.out" std_err_file: "/tmp/cross_lnx.err" alarm_if_fail: 1

 

 

 

• This job will change to the Workload Automation AE install directory and do a listing

• The command assumes that the %AUTOUSER% environment variable is already set

• The std_out and std_err files are written on the TARGET server

 

NOTE: The job owner should be able to access the TARGET machine and be defined in autosys_secure on the SOURCE server.

 

START THE CROSS INSTANCE JOB

 

Use the following command to start the cross instance job:

 

From the SOURCE server to the TARGET server: sendevent –E STARTJOB –j job_name –S SRC

 

From the TARGET server to the SOURCE server: sendevent –E STARTJOB –j job_name –S TGT