It is possible to configure the system agent service to startup automatically after the server reboot in all the supported operating systems.
This technical document provides guidance on creating Run Control scripts to automatically start the WA Agent along with the server reboot.
CA Workload Automation System Agent 11.3 and higher on all supported Linux / Unix platforms.
CA Workload Automation System Agent installer skips creating the Run Control scripts if the option to start service at system boot is not selected during the installation. And, so WA Agent does not automatically start on server reboot.
Windows:
The System Agent service in the windows services console (services.msc) can be switched to Automatic start in the properties.
Right-click on the service name and properties
Switch the Startup-type to "Automatic". Apply the changes and click on OK.
Linux:
Follow the instructions in the KB article:
https://knowledge.broadcom.com/external/article/32893
Solaris 10 and higher:
ii) Create the following run control scripts/symbolic links:
# cd /etc/init.d/
# ln -s cybagent-AGENT.init /etc/rc0.d/K64cybagent-AGENT.init
# ln -s cybagent-AGENT.init /etc/rc1.d/K64cybagent-AGENT.init
# ln -s cybagent-AGENT.init /etc/rc2.d/K64cybagent-AGENT.init
# ln -s cybagent-AGENT.init /etc/rc3.d/S00cybagent-AGENT.init
After executing the aforementioned scripts, execute the following command to confirm their existence.
# ls -l /etc/rc?.d/*cybagent-AGENT.init
lrwxrwxrwx 1 root root 29 Jan 11 2013 /etc/rc0.d/K64cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxrwxrwx 1 root root 29 Jan 11 2013 /etc/rc1.d/K64cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxrwxrwx 1 root root 29 Jan 11 2013 /etc/rc2.d/K64cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxrwxrwx 1 root root 29 Jan 11 2013 /etc/rc3.d/S00cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
AIX
# cd /etc/rc.d/
# ln -s cybagent-AGENT.init /etc/rc.d/rc2.d/K001cybagent-AGENT.init
# ln -s cybagent-AGENT.init /etc/rc.d/rc2.d/S000cybagent-AGENT.init
Confirm these exist:
# ls -l /etc/rc.d/rc?.d/*cybagent-AGENT.init
lrwxrwxrwx 1 root system 22 Feb 24 17:41 /etc/rc.d/rc2.d/K001cybagent-AGENT.init -> ../cybagent-AGENT.init
lrwxrwxrwx 1 root system 22 Feb 24 17:41 /etc/rc.d/rc2.d/S000cybagent-AGENT.init -> ../cybagent-AGENT.init
HP-UX:
# cd /sbin/init.d/
# ln -s cybagent-AGENT.init /sbin/rc0.d/K099cybagent-AGENT.init
# ln -s cybagent-AGENT.init /sbin/rc1.d/K099cybagent-AGENT.init
# ln -s cybagent-AGENT.init /sbin/rc2.d/K099cybagent-AGENT.init
# ln -s cybagent-AGENT.init /sbin/rc3.d/S436cybagent-AGENT.init
Confirm these exist:
# ls -l /sbin/rc?.d/*cybagent-AGENT.init
lrwxr-xr-x 1 root sys 29 Sep 25 00:27 /sbin/rc0.d/K099cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxr-xr-x 1 root sys 29 Sep 25 00:27 /sbin/rc1.d/K099cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxr-xr-x 1 root sys 29 Sep 25 00:27 /sbin/rc2.d/K099cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
lrwxr-xr-x 1 root sys 29 Sep 25 00:27 /sbin/rc3.d/S436cybagent-AGENT.init -> ../init.d/cybagent-AGENT.init
NOTE: The sequence numbers for Run Control scripts (Kxxx and Sxxx) can be different than what is given in the aforementioned examples.