This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

BMC Atrium Impact Simulator logging

BMC Atrium Impact Simulator logs errors in the ais.log and ais_cell.log files. The ais.log file records messages generated by the BMC Atrium Impact Simulator plug-in, such as notifying you that BMC Atrium Impact Simulator is starting up and that the BMC Atrium Impact Simulator receiver started on a specific port number. The ais_cell.log file records errors that are generated by the BMC Atrium Impact Simulator computation cell.

This section contains the following topics:

BMC Atrium Impact Simulator plug-in logging

BMC Atrium Impact Simulator uses the Apache log4j mechanism to log messages. Each entry in the log provides the following details:

  • Thread — The thread that the transaction used when the message was generated.
  • Timestamp — The date and time of the log entry.
  • Log Type — The type of log entry: debug, information, warning, error, or fatal.
  • Message — The message for the log entry.

You can specify additional logging options for BMC Atrium Impact Simulator plug-in in the log4j_pluginsvr.xml configuration file. The debug level parameter specified level of logging that you require for your BMC Atrium Impact Simulator plug-in transactions. To set the debug logging to a different level, add CMDB-Debug-Level: <loggingLevel> to the configuration file and restart the AR System server. The debug levels are:

  • Debug — Logs messages for severe errors, which are used for debugging purposes. This is the highest logging level.
  • Information — Logs informational messages. This is the default logging level.
  • Warning — Logs messages for warnings.
  • Error — Logs messages for errors.
  • Fatal — Logs messages and details for the fatal errors.

For more information about the additional parameters that you can specify for the BMC Atrium Impact Simulator plug-in, see http://logging.apache.org.

To enable BMC Atrium Impact Simulator plug-in logging

  1. From the <AtriumInstallation>/AtriumCore/<hostName>/cmdb/plugins/shared/ directory, open the log4j_pluginsvr.xml file.
  2. In the file, search for the Logger for AIS string.
  3. For the com.bmc.atrium.filterplugin.ais and com.bmc.atrium.ais loggers, set the level value parameter to DEBUG.
    Your changes will take effect shortly or after the next time you restart the AR System server.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Gustavo Del gerbo

    All the below needs to be removed since the ais.cell doesn't exists anymore. Calculation are now done by the Plugin itself.

    To enable BMC Atrium Impact Simulator cell logging

    The BMC Atrium Impact Simulator cell, which is a separate process, is the engine that performs the calculations for the impact simulations in the background.

     

    Note

    The ais.cell also logs internal messages from other BMC Atrium Core components. For this reason, BMC recommends that you do not change any additional configuration settings in the mcell.trace file.

     

    1. From the <AtriumInstallation>/AtriumCore/<hostName>/ais/etc/ directory, open the mcell.trace file.
    2. Search for the ALL ALL entry at the end of the file.
    3. If you find the entry and if it is commented, set it to stderr. Otherwise add the ALL ALL stderr entry.
    4. Restart the BMC Atrium Impact Simulator cell for the value to take effect:
      • On Windows, go to the command prompt and type "net start "BMC Atrium Impact Simulator".
      • On UNIX, at the prompt, type "/etc/rc2.d/S99ais start".
        After you finish logging, add a comment entry character (#) at the beginning of the ALL ALL entry.
    Oct 28, 2013 02:40
  2. Hemant Baliwala

    Thanks, Gustavo. I have removed the section.

    Dec 19, 2013 07:22