Log files contain configuration settings, grid, process, and installation information, which makes them valuable tools for troubleshooting problems. This section describes the types of log files generated by the installation programs and components and how you can gather and send these files to BMC Customer Support or use them yourself to diagnose problems.
In this page, AO_HOME represents the BMC Atrium Orchestrator installation directory.
Log file names and locations
Platform installer log
BMC Atrium Orchestrator Development Studio installer log
Content installer log
BMC Atrium Orchestrator creates the grid.log file shortly after the peer is started for the first time. If a peer is running for five minutes and this file does not appear, then there is probably something wrong with the default logging, or there has been a change to the logging configuration.
Logging information generated by BMC Atrium Orchestrator workflows
catalina.log or catalina.out
Log messages on actions by the container, actions on startup and shutdown, and any actions taken to load a web application
Logging information for BMC Atrium Single Sign-On
Logging information for the repository
Logging information for BMC Atrium Orchestrator Operator Control Panel, including connectivity and user interface errors
|dashboard.log||AO_HOME/DB/tomcat/logs||Logging information for the dashboards|
If the installation is successful, BMC Atrium Orchestrator copies installer logs to the AO_HOME directory. However, if the installation is not successful, the installation log file stays in the temporary directory. For more information, see Installation log files.
Installation log locations
The following table lists the locations of the installation files by operating system.
Default installation log location
Red Hat Linux
Usually in C:\DOCUME~1\<userName>\LOCALS~1\Temp