Jump to: navigation, search


iWD Manager and iWD Runtime Node support creation of their own log files for troubleshooting purposes. In addition, iWD Manager supports centralized logging through Genesys Message Server (optional). The following procedures explains how to configure the required parameters.

Write the pathnames using either a single forward ( / ) slash or a double backwards slash ( \\ ) as a separator.

Configuring Logging for iWD Manager


  • iWD Manager is installed.
  • For centralized logging, Genesys Message Server is installed.

Refer to the Framework 8.1 Management Layer User’s Guide for more information about Message Server.

  1. For centralized logging, add the connection from iWD Manager Server to MessageServer.
  2. Find the log4j.properties file in application installation directory and open it in a text editor. The exact path for iWD Manager is <iWD_Manager_install_dir>/config/log4j.properties.
  3. For centralized logging, update the very first row of the log4j.properties file to include centralized_manager at the end:
    log4j.rootLogger=INFO, runtime, centralized_manager
  4. Configure the parameter to specify the level of logging to send to Message Server:
  5. log4j.appender.centralized_manager.Threshold=INFO
    Threshold can be set to any of the following values:
    • TRACE
    • DEBUG
    • INFO
    • WARN
    • ERROR
  6. For information about various settings for the root logger, refer to log4j framework docs, such as http://logging.apache.org/log4j/1.2/manual.html.
  7. You can change the directory where the logs will be written by changing the value of this line:
  8. log4j.appender.runtime.File=C:/GCTI/iWD/iwd_manager.log
    It is strongly recommended that you only set the file path to a directory on a local machine, not a remote location such as a shared network drive. Logging to a remote location can severely impact performance
  9. You can change the logging level by changing this line (sample is from an iWD Manager log4j.properties file):
  10. log4j.appender.manager.Threshold=INFO

    Possible values are Off, Warning, Error, Debug, Info, and Trace.

  11. You can change the maximum file size of the logs by changing this line:
  12. log4j.appender.manager.MaxFileSize=256MB
  13. Save your changes.

The following is a sample iWD Manager log4j.properties file configured for logging:

#info, rolling 256MB each (2 GB max)
log4j.rootLogger=INFO, manager, centralized_manager
log4j.appender.manager.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss}|%t|%p|%c|%m%n

If you enable centralized_manager appender then make sure you change rootLogger to:

log4j.rootLogger=INFO, manager, centralized_manager

Configuring Logging for iWD Runtime Node

The process of startup logging contains two stages:

  1. Initial Phase.
    1. When Data Mart starts, initial logging configuration is read from the yaml configuration file (<RUNTIMENODE_FOLDER>/config/iwd_dm.yaml).
    2. One log file will be created — <RUNTIMENODE_FOLDER>/datamart-startup.log.
  2. Data Mart retrieves the configuration from Configuration Server.
    1. If logging configuration is missing in Configuration Server, Data Mart will exit with an error.
    2. If logging configuration is incorrect, Data Mart will exit with an error.
    3. If logging configuration is correct, Data Mart will reconfigure itself to log according to configuration stored in Configuration Server.
    4. All log files are created (see Log Files below).

For information about configuring IWD Runtime Node Logging, refer to the iWD Genesys Administrator Extension Plug-in Help.

Log Files

  • datamart.log—Main log.
  • datamart-startup.log—Initial phase log.
  • datamart-access.log - Data Mart API log.

Log files for corresponding Data Mart services:

  • aggregate-historical.log
  • aggregate-intraday.log
  • aggregate-stats.log
  • configuration-monitor.log
  • conf-server-connector.log
  • initialize.log
  • load-config.log
  • load-historical.log
  • load-intraday.log
  • maintain.log
  • stat-adapter.log

Hiding or Tagging Sensitive Data in Logs

Hiding All Sensitive Data

To hide all sensitive data in logs, you must create the following in the application options:

  • Section—[log-filter]
  • Option name—default-filter-type with the value set to hide.

Hiding Specific Data

To hide specific data (for example, password) in logs, you must create the following in the application options:

  • Section—[log-filter-data]
  • Option name—password with the value set to hide.

Common Settings

The settings described at the links below are common for most Genesys applications.


Comment on this article:

blog comments powered by Disqus
This page was last modified on June 22, 2018, at 09:07.