Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.4 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Configuration Guide

Configuration Guide

Back Next

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!