Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Log File Rolling

Log File Rolling

When an application server log file reaches the maximum size defined in the MaxFileSize parameter in the
log4j.xml
configuration, the Enterprise Manager performs a log rolling procedure to archive the existing log information and to prevent log files from being overridden with new application server information:
  1. Define the following application server log configuration settings in the
    log4j.xml
    file for Hub Server and
    Process Server
    located at
    <
    infamdm_install_dir
    >\hub\server\conf
    and
    <
    infamdm_install_dir
    >\cleanse\server\conf
    respectively:
    • File. Name of the log file such as
      C:\infamdm\hub\server\logs\cmxserver.log
      .
      On WebLogic and WebSphere, use the following file names as a best practice to gather logs in the same location while making them distinguishable from each other:
      Hub Server:
      C:\<
      infamdm_install_dir
      >\hub\server\logs\cmxserver.log
      Process Server
      :
      C:\<
      infamdm_install_dir
      >\hub\server\logs\cmxcleanse.log
    • MaxFileSize. Maximum file size of the application server log file.
    • MaxBackupIndex. Maximum number of files.
    • Threshold. The threshold logging level, which overrides any logging level that is higher than the threshold level.
  2. The log files used for the Hub Server and
    Process Server
    appends the various application server messages to the application server log files.
  3. When the physical log file size exceeds the MaxFileSize, the Hub activates the log rolling procedure:
    1. The active log file is renamed to <filename>.hold.
    2. For every file named
      <
      filename
      >.(n)
      , the file is renamed to
      <
      filename
      >.(n+1)
      .
    3. If n+1 is larger than MaxBackupIndex, the file is deleted.
    4. When rolling over goes beyond the maximum number of application server files, the MDM Hub renames the original log file. For example, the MDM Hub renames
      cmxserver.log
      to
      cmxserver.log.1
      , and
      cmxserver.log.1
      to
      cmxserver.log.2
      . The Hub then overwrites
      cmxserver.log
      with the new log information.
    5. The
      <
      filename
      >.hold
      file is renamed to
      <
      filename
      >.1
      .
The Hub also creates a
log.rolling
file prior to executing a rollover. If your log files are not rolling as expected, check your log file directory and remove the
log.rolling
file so that the log rolling can continue.

0 COMMENTS

We’d like to hear from you!