AutoSys Workload Automation

I have a few questions.

1. Do you have the following customer cases?
   Autosys Manager 11.3.x <--> Autosys agents 4.5
   If you have such customers, please provide the details below.
   - customer :
   - autosys version :
   - number of machine :
   - number of jobs :
   - The period of operation in such a way :

  What I want to know is whether the interworking between these other versions is stable enough through reference.

2. Does autosys 11.4 and later also support interoperation with 4.5 agent?

3. Could you please let me know the roadmap for workload automation ae in the future?

The 4.5 Remote Agent is no longer supported by CA as I'm sure you know. 

We once tested the combination of r11.3 Servers with 4.5 Remote Agents a few years ago, and the 4.5 Remote Agent caused a great many problems when posting statuses back to the AutoSys database.

This is a combination that I absolutely can not recommend.

I wouldn’t even bother… there’s too much difference. I would just load the new agent on and move forward ..

The agents are so different … they can live side by side..

Steve C.

Hi Han

In addition to previous comments, you can configure the System Agent release 11.3 to behave like legacy 4.5 and 11.0 remote agents on Windows and Unix/Linux.

For details click here

Configure the Agent to Behave Like Legacy Remote Agent - CA Workload Automation System Agent - 11.3 - CA Technologies Do… 

Regards

Jean Paul

Hi,

There is an 11.3 Relnotes pdf that covers new features:

Starting in r11.3, CA Workload Automation Agent for UNIX, Linux, or Windows replaces the legacy remote agent that was available for r4.5 and r11. However, CA Workload Automation AE r11.3 provides backward compatibility with the legacy remote agent.

https://support.ca.com/cadocs/7/CA%20Workload%20Automation%20AE%20r11%203-ENU/Bookshelf_Files/PDF/WA_AE_Release_ENU.pdf

Best regards,

Faouzia

Faouzia, I realise that technically an r11.3x Manager still supports the 4.5 Remote Agent.  However I feel I must restate that this combination is not desirable, and should not be suggested as a possibility if it can be avoided at all.

For example, the 4.5 Remote Agent of course has to post data directly in to the AutoSys database.  Under some circumstances the 4.5 Remote Agent does not release database connections properly.  This can lead to all sorts of unwanted behaviour, such as connection pools becoming exhausted, or job statuses arriving in the wrong order (STARTING > SUCCESS > RUNNING).  I have seen this stuff happen and it is not pretty.

Getting the new System Agent to sit alongside the old Agents is easy and is much the better approach.

I fully agree Antony, this is another case where some of the ca people do not fully understand the Book answer vs. Real World. 

r11.3.x Instance wide encryption will have to be turned off for any legacy agent support and that is a compromise. Your compliance auditors are not going to like it