Debugging Applications Manager V8.0

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Debugging Applications Manager V8.0

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Symptoms

You are having an issue with Applications Manager and need to gather debug logs for support.

 

---

 

Cause

Need to gather logs to determine. THis KBE will cover how to gather logs for the most common Applications Manager issues.

 

---

 

Resolution

Automation Engine Issues:

Please do the following if the Automation Engine is in a status other than Running or you are receiving RMI server errors.

1)Stop the instance:

stopso all

stopso awcomm

2)Enable Debug

Please navigate to the $AW_HOME/site directory of the master and edit the awenv.ini file.

under the [default] section please add the following line:

Debug=true

3)Restart the instance:

startso all

4)Gather logs:

Reproduce the issue then navigate to the $AW_HOME/log directory and send us the latest RmiServer<timesatmp>.log file

Agent Issues:

Please do the following if a remote agent or the Automation Engine's local agent will not start or is in a status other than Running.

1)Stop the Agent

stopso <AGENT NAME>

2)Enable Debug

Navigate to the agent's $AW_HOME/site directory and edit the awenv.ini file.

Under the [default] section please add the following line:

Debug=true

From the User Interface go to Help>About Applications Manager and check Server

3)Restart the agent

startso <AGENT NAME>

4)Gather logs:

Reproduce the issue then navigate t the master's $AW_HOME/log directory and send us the latest RmiServer<timestamp>.log file then from the Agent's $AW_HOME/log directory send us the matching AgentService<timestamp>.log file.

Job Issues:

Jobs are aborting or not running as expected.

1)Enable DebugFrom the User Inter

Launch Error:

Job Aborting: