How to cold start a Workload Automation Agent

Products

• Workload Automation Agent
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation DE - Business Agents (dSeries)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation AE - Business Agents (AutoSys)

Issue/Introduction

In some cases, a cold start of the WA Agent may be necessary to resolve an issue.

Environment

All suopported versions of the Workload Automation System Agent

Any OS

Resolution

IMPORTANT: Please note that when performing a cold start of an agent, 

• jobs processing may experience interruption/delay.
• jobs that are running at the time of performing cold startjob will not get an updated status as the agent, as the agent will lose track of job processes.

Note: To help reduce the above mentioned problems, follow below steps before performing cold start steps.

• Take the agent offline so as to prevent new jobs from starting on the agent in question.
  • AutoSys: Take a Machine Offline Manually
  • dSeries: Quiesce Agent/Advanced Integration
    
    
• And for jobs that are actively processing, either allow them to complete or cancel them from the manager.
  If the decision is made to cancel/terminate jobs see below:
  
  • AutoSys: Kill a Job
  • dSeries: Cancel a Running Job

---

To cold start the Workload Automation Agent, perform the following steps.

1. Stop all the jobs from the manager (if any are running)
2. Stop the Workload Automation Agent.
3. Navigate to Workload Automation Agent install directory.
4. Make a backup of the current database directory.
5. Delete the database directory in installation directory (see example)
   cd /opt/CA/WA_Agent
rm -rf database
6. (Optional) Remove log and spool directory inside the Workload Automation Agent install directory
7. Start the agent again, a new database directory will be created.

Additional Information

Please refer to this link for more information on troubleshooting WA Agent.