Troubleshooting problems in BMC Atrium Orchestrator Operator Control Panel

The BMC Atrium Orchestrator Operator Control Panel application might have trouble connecting to a grid, display error messages, or have workflows that end in a failed condition.

This section contains the following topics:

• BMC Atrium Orchestrator Operator Control Panel fails to start
• No visible workflows
• Workflow does not display properly
• RSL error
• Resolving failed workflows

Operator Control Panel log

The Operator Control Panel service has its own log file named aoocp.log. 

Log file location

You will find the aoocp.log in the tomcat/logs directory on the BMC Atrium Orchestrator peer where the Operator Control Panel service is installed.

Log file configuration

After the initial installation, the aoocp.log file is set by default to log Operator Control Panel interactions at the Debug level.  To reduce the amount of information being written to this file, the administrator can edit the log4j.properties file to reduce the logging level. The log4j.properties file is located in the tomcat/webapps/baoocp/WEB-INF/classes directory on the peer where the Operator Control Panel service is installed.  Changing lines 2 thru 5 to use the value INFO (as shown in the next example) will reduce the logging level of logging of the aoocp.log file.

log4j.defaultInitOverride = false
log4j.rootLogger=INFO, aoocp
log4j.logger.com.bmc.ao=INFO
log4j.logger.com.bmc.rba=INFO
log4j.logger.com.realops=INFO
log4j.logger.com.realops.ui.opsconsole.RequestHandler=INFO
 
log4j.appender.aoocp=org.apache.log4j.RollingFileAppender
log4j.appender.aoocp.File=${catalina.home}/logs/aoocp.log
log4j.appender.aoocp.MaxFileSize=10MB
log4j.appender.aoocp.MaxBackupIndex=20
log4j.appender.aoocp.layout=org.apache.log4j.PatternLayout
log4j.appender.aoocp.layout.ConversionPattern=%d [%t] %-5p %c - %m%n