WCC Agent Inventory - Agent staging failure

Products

• Autosys Workload Automation

Issue/Introduction

One of the common errors seen when using the Agent Inventory agent upgrade is an error "Staging Failure".  This gives an overview on how the Agent Inventory works

Environment

Release : 12.0/12.1

Resolution

1. Ensure the logged in user has permissions in EEM (Agent Inventory Error: User does not have permission to perform the action)
   
   
2. WCC works through AutoSys Application server to send a couple of adhoc command jobs to the target agent. These jobs are generated internally by the app server, so they are not jobs defined in Autosys or run by the scheduler.
   
   
3. The first command job creates some files in the agent spool directory.
   
   
4. The second command job executes a script (created by the first job) to download the agent installer from the WCC server. This is done by a Java based web service call back to the WCC server URL over the WCC port (8443 or 8080). So, ensure:
   • The WCC Server URL is resolvable from the Agent host
   • Connection from Agent to the WCC port is open for communication
   • If WCC URL is using SSL certificates, that SSL certificate and its certificate chain should be available for the Agent's Java layer (<AGENT_INSTALL_FOLDER>/cacerts  keystore). If not, that chain should be manually imported into the cacerts keystore of the agent
     
     
5. If the above all are configured properly, there is a folder wcc_agent_cmd that gets created in the spool folder. In that folder there is a subdirectory with a very long name and a time stamp that gets created around the same time Staging or Upgrade of the Agent was attempted, example:
   
   drwxr-xr-x. 2 root root 65 Mar  7 23:39 1678232369197-10dfeff726914416902c18ce91b0c52f


6. In that directory and there are files like below that can be reviewed for clues on why the operation failed. Correct appropriately and retry the Agent Inventory Upgrade/Stage

• -rw-r--r--. 1 root root    826 Jul 17 15:48 b64.js
-rw-r--r--. 1 root root   6172 Jul 17 15:48 cmd.jar
-rw-r--r--. 1 root root   2692 Jul 17 15:48 cmd.log
-rw-r--r--. 1 root root 168296 Jul 17 15:48 log.zip
-rw-r--r--. 1 root root      0 Jul 17 15:48 log.zip.b64.out
-rw-r--r--. 1 root root      0 Jul 17 15:48 log.zip.b64.err
-rw-r--r--. 1 root root 224416 Jul 17 15:48 log.zip.b64