Configuring Atrium Integrator logs

You can customize the logging settings for Atrium Integrator for troubleshooting scenarios. Atrium Integrator logs all activities that it performs. A log file for a job is created each time the Atrium Integrator runs a job. The default log level for Atrium Integrator is set to WARN.

Change the AR Pentaho plug-in log level from the AR Pentaho User-defined AI level property. For Atrium Pentaho plug-in and AR Pentaho plug-in, you can change the log level at run time, which does not require you to restart your system or open any file. You can use the Pentaho plug-in to run and monitor Atrium Integrator jobs and transformations from AR System vendor forms. Using this plug-in, an AR System or BMC Helix ITSM application user creates a comprehensive AR form-based data management user interface.

For information about log entry details, see Contents-of-the-logs.

To change the Atrium Integrator plug-in server log level at run time

  1. In the Action Request System Administration Console, select AR System Administration > AR System Administration Console > System > General > Plugin Server Configuration.
    The Plugin Server Configuration window opens.
  2. From the Plugin Server Instance list, select the plugin server with port number 9999.
    This is the port used for the shared Atrium Integrator plug-in.
  3. To view the server configurations, click the Plugin Server Configurations tab.

  4. Modify the following settings:

    Setting

    Description

    Enable Plugin Log

    Enables logging for the plug-in server.

    Log level

    Defines the type of information saved in the log file.

    Log file

    Defines the path on the server where the log file is saved.

    Maximum Log File Size

    When the log file reaches the file size limit, a new log file is created with a different file name. The older files are not automatically deleted.

    Log History

    Specifies the number of log files to be maintained as a backup.

  5. Click Apply and then Close.

Atrium Integrator log file locations

The following table lists the locations where the Atrium Integrator components save logs:

Log file

Purpose

Log file location

Mid Tier logs


The Mid Tier logs are located in the following directory:
midtierInstallationDirectory/Log.

If you are running the Tomcat web server, the Atrium Integrator console log files are located in the following directory on the computer where you installed Mid Tier: <Tomcat installation directory>/logs/stdout_currentDate.log

arcarte.log

For information about job execution related issues.

The logs are located in the following directory:

Windows: <AR Home>/Arserver/db/

UNIX: <AR Home>/db/

See the following files:

  • arcarte.log
  • arcarte-stdout-YYYY-MM-DD.log
  • arcarte-stderr-YYYY-MM-DD.log

For setting the log for arcarte.log, perform the following steps:

  1. Open the file carte_log4j.properties from this location: /opt/bmc/ars/diserver/data-integration/pwd/carte_log4j.properties
    carte.log.rollover_size=20971520
    carte.log.max_backup_index=30
    logger.1.name = com.bmc
  2. Set the logger.1.level property to  DEBUG.
  3. Restart the Carte Server after making this change. 

arjavaplugin.log

ai_ardbc_plugins.log

arjavaplugin: For information about all errors and exceptions.

ai_ardbc_plugins: For information about Atrium Pentaho and Atrium plug-in related issues.

These plug-in log files are present in the db folder of every installation at:

<AR Home>/db/ai_ardbc_plugins.log and <AR Home>/db/arjavaplugin.log

cmdb_services.log


The bundle logs are found at:

<AR Home>/Arserver/db/cmdb_services.log

ARSYS.ARDBC.PENTAHO plug-in logs

For information about the error messages related to the ARSYS.ARDBC.PENTAHO plug-in.

Logs are located at:

ARInstallationDirectory/ARServer/db/arjavaplugin.log

Atrium Integrator Spoon logs


Log file for Atrium Integrator Spoon is located at:

%temp%/Spoon.log

Development-to-production utility logs

For logging information about migration of jobs and transformation from one computer to another. This log is generated when you execute the development-to-production utility.

Development-to-production utility log location:

ARInstallationDirectory/diserver/data-integration/ngie/log

See the following files:

  • devtoprodout.txt
  • devtoproderror.txt

Atrium Integrator Maintenance tool logs

For logging information about jobs you import using the tool.

Atrium Integrator Maintenance utility log location:

Windows: TEMP

UNIX: /var/tmp

See the atriumintegrator_configuration_log.txt file.

aiexport utility logs

For logging information about backup jobs created by using the aiexport utility.

aiexport utility log location:ARInstallationDirectory/diserver/data-integration

See the atriumintegrator_install_log.txt file.

To change the file location for the Mid Tier log

For better debugging, you can configure the Mid Tier log location to a different file.

  1. Open the log4j.properties file from the following location:
    ARInstallationDirectory\midtier\WEB-INF\classes\log4j.properties

  2. Add the following information in the log4j.properties file:

    log4j.rootLogger=DEBUG, atrium
    log4j.appender.atrium=org.apache.log4j.RollingFileAppender
    log4j.appender.atrium.File=_ARInstallation Directory_/midtier/logs/<filename>.log
    log4j.appender.atrium.MaxFileSize=25MB
    log4j.appender.atrium.MaxBackupIndex=10
    log4j.appender.atrium.layout=org.apache.log4j.PatternLayout
    log4j.appender.atrium.layout.ConversionPattern=%p %t %c - %m%n
  3. Save the file.
  4. Open the services-config.xml file from the following location:
    ARInstallationDirectory\midtier\WEB-INF\AtriumIntegrator\flex\services-config.xml
  5. Change the target level=WARN parameter to DEBUG.
  6. Restart the Mid Tier web server.

Related topics

Contents-of-the-logs

Enabling-logs-for-the-plug-ins-server

Troubleshooting-Atrium-Integrator-issues

Transferring-data-from-external-data-stores-to-BMC-Helix-CMDB



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*