ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

R12.0 Questions x

book

Article ID: 145807

calendar_today

Updated On:

Products

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

Issue/Introduction

1.  The "Supported  Operating System Platforms" only shows "Windows Server 2016, Windows Server 2019". Does this mean that Windows 2012 is NOT supported as a FULL Client/Agent? If so, why not?

2.  The list does not include "Solaris sparc". I assume then that it's not supported? We have approx. 100+- as Full Clients.

3. Is Solaris 11 not supported for the Full Client or Agent also?

4. Regarding Oracle 19c dbase support..  Is AutoSys 12.0 still a 32-bit application and would the database still need to 64-bit but with 32-bit libraries? Any other thing to know?

5. Is the supported AdoptOpenJDK 8 an add'l license?

6. Can the Java used by the Agent and Client both be symlinked to a package that's installed elsewhere on the server?

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

1. The "Supported Operating System Platforms" only shows "Windows Server 2016, Windows Server 2019". Does this mean that Windows 2012 is NOT supported as a FULL Client/Agent? If so, why not?
Correct. Windows Server 2012 R2 is already out of mainstream support from Microsoft, therefore we are not supporting it. Our software will most likely run on the older platform but we are not testing it there.
2. The list does not include "Solaris sparc". I assume then that it's not supported? We have approx. 100+- as Full Clients.
From all publicly available messaging and the lack thereof about the future of Solaris all we can determine is that Solaris is dying. For example, if you look at Oracle’s own site for Java SE downloads, you will notice Oracle is not even porting Java to the Solaris platform. The agents/clients that run on Solaris will continue to be supported and are backward compatible with the 12.0 release.
3. Is Solaris 11 not supported for the Full Client or Agent also?
Correct.
4. Regarding Oracle 19c dbase support.. Is AutoSys 12.0 still a 32-bit application and would the database still need to 64-bit but with 32-bit libraries? Any other thing to know?
AutoSys 12.0 is native 64-bit and will require the 64-bit Oracle client, which is the default available from Oracle. We don’t care what bitness that Oracle database is, just like the current AutoSys releases. The Oracle client libraries handle all differences.
5. Is the supported AdoptOpenJDK 8 an add'l license?
The AdoptOpenJDK is included with the product at no additional cost. You have the option of using it or a comparable Oracle JRE if you choose to provide it.
6. Can the Java used by the Agent and Client both be symlinked to a package that's installed elsewhere on the server?
Yes. You may provide your own JRE for the product to use or use the embedded one we provide. The agent, client, and server components will all share a single JRE instance by default.