CA Workload Automation Agents

What's New

  • CA Workload Automation Agent 11.5 General Availability

    We are pleased to announce that the CA Workload Automation Agent 11.5 release is now GA.

    New features for CA Workload Automation Agent R11.5 include: 

    • Enhanced security – Agent now provides the ability to restrict the use of a cryptkey.txt to a particular machine, to specify the owner and group accounts for installed files on UNIX and to restrict the access to the cryptkey.txt file to just owner and group on UNIX platforms.
    • Enhanced log administration – you can now specify the maximum length that an individual log message may be before having the message truncated.
    • Improvements to file scanning – A new file monitoring algorithm has been implemented to improve performance for File Watcher/File Trigger jobs.
    • CPU monitoring on multiple CPU machines without manually setting scalefactor – Agent checks for the number of CPUs on the machine dynamically whenever it calculates the machine CPU utilization and will report the CPU usage based off the load average by default. The workload automation engines no longer require manual configuration of the objmon.cpu.scalefactor setting for accurate CPU information.
    • Support for AdoptOpenJRE – On platforms where the agent install provided its own bundled Java runtime (Windows, Linux), there is now an option to install the bundled Java runtime (AdoptOpenJRE8) or specify an alternate Java runtime like Oracle JRE.
    • New OS and Platform support – Agent is now certified on Windows 2019, SuSe Linux 15 and RHEL Linux 8 OS platforms and PeopleSoft PeopleTools 8.57.

    Please refer to the GA announcement letter for a complete list of all the details.

Latest Discussions

  • Jose, I would like to add one small note that may save you a little time in Step 1. Quesce the agent, and monitor a custom view of job(s) running on the agent until they are complete, then restart.  This gives you the ability to prevent anything from ...

    1 person recommends this.
  • Hi, In the end it was as follows. "cold start" of the Agent by using the following steps: 1. Preferably wait to find a short period during which there will Not be any jobs running on the Agent 2. Stop the Agent Service 3. Take a backup of the "database" ...

Unanswered Threads

  • From last couple days, we are observing that the failure emails are not coming out. When I hit the mailx command, it works absolutely fine. We have moved all the old method to notification to the delivered function of sending notification using the send_notification ...

  • Hello,    We currently have 4 Windows servers with Systems Agents installed on them "standalone". The Application owner now wants to create a Cluster with these 4 servers. I'm familiar with installing new Agents in a clustered environment, but we've ...