This topic provides information to help you troubleshoot issues that you might encounter with the BMC Change Management and Infrastructure Management integration.
Ensure that the
pronet.jserver.ruleconfigurator.enable flag in the pronet.conf file is set to
true. If a blackout policy is not created, check if the
pronet.jserver.ruleconfigurator.eventcollectiondowntime.enable flag is set to
true. If the problem persists even after the flag is set to true, check the JServer logs for any errors. Some of the possible error conditions are:
Check the web services logs for any change notifications. If change notifications are present, check the web services logs for any error conditions. Some of the possible error conditions are:
Perform the following steps to verify that the Infrastructure Management - BMC Change Management integration is active:
Perform the following steps if events still do not appear on the operator console:
By default all logs are located at: installationDirectory/pw/pronto/logs/<logfolder>. The following table lists the location of logs of specific components:
installationDirectory/pw/pronto/logs/debug/eventws.debug.log and installationDirectory/pw/pronto/logs/debug/jserver.log
To enable debug logging, run the
The following table lists error codes, messages, and description of some common errors that can occur while integrating BMC Change Management with Infrastructure Management.
You can activate the integration on a Infrastructure Management standalone server or on a Central Server in multiserver deployments. You cannot activate this integration from a Child Server.
Error code and message
An internal server error can occur due to several reasons. Check the error log for the exact reason why this error has occurred. Some of the possible reasons are: