Migrating Agent or extension logging configuration

MVMM 9.1 Agent Fix Pack C has updated the logging provider for the following MVMM components:

•    MVMM Configuration Agent (bmmtm_agent)
•    MVMM Monitoring Extension for IBM IIB/ACE (qpwmb)
•    MVMM Monitoring Extension for IBM DataPower (bmmpa_datapower)

Related topics

Release-notes-and-notices

Installing-Server-and-Agent-Fix-Packs

These components have been updated to use a LogBack logging provider. This replaces the obsolete Log4jv1 logging provider that was used previously.

After the Agent Fix Pack C is installed, the above components will use a LogBack logging configuration by default. The LogBack logging configuration is defined in the configuration/logback.xml file present in the installation directories of the MVMM components.

(Default) Changes made to the logging configuration in the logback.xml file will take effect within thirty seconds.

Important

Backup the org.ops4j.pax.logging.properties file before installing the new MVMM components.


You can migrate a previously installed custom log4j configuration to a LogBack configuration by performing the following steps:

  • Extract the custom log4j configuration from the previous configuration/services/org.ops4j.pax.logging.properties file. 
  • Use the following tool to translate the log4j configuration to a LogBack configuration file: https://logback.qos.ch/translator/. In MVMM, we use the org.ops4j.pax.logging.properties file, which is a type of log4j.properties file. So, you can use the translator to convert org.ops4j.pax.logging.properties file to a LogBack configuration file
  • Create a backup copy of the default LogBack configuration file in configuration/logback.xml.
  • Save the custom LogBack configuration to configuration/logback.xml.
  • Restart the Agent or Extension.
  • Verify that the log output is processing as per the specifications you have provided.

 

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