MQ

 View Only
Expand all | Collapse all

Migrate from stand-alone file logger to stand-alone DB logger

  • 1.  Migrate from stand-alone file logger to stand-alone DB logger

    Posted Mon February 22, 2021 10:56 AM
    Hi all, 
    We're considering switching from an MFT stand-alone file logger to a DB logger either stand-alone or J2EE DB logger.  I can see you can you can migrate from a stand-alone database logger to the Java™ EE database logger. However what about from a stand-alone file logger to a DB logger, preferably on a separate server running MQ that is connected to the MFT Coordination QM.   Is this simply a matter of stopping traffic, deleting the current logger and recreating it and optionally deleting the current logger files?  Any pros/cons to this approach would also be appreciated.

    Thanks,
    Guy

    ------------------------------
    Guy Petty
    ------------------------------


  • 2.  RE: Migrate from stand-alone file logger to stand-alone DB logger

    Posted Mon February 22, 2021 09:22 PM
    Hi Guy,

    The DB logger connects to coordination queue manager in bindings mode. Hence DB Logger must be run the same machine as the coordination queue manager. If it's not possible, then you can use the alternative approaches described here - https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.2.0/com.ibm.mq.con.doc/logger_alt_config.html

    There is no direct migration from file to db logger.  Since logger is a Pub/Sub application consuming publications from SYSTEM.FTE topic, you can simply fire up new a DB logger while the file logger is still running. Once the DB logger is running, you can stop and delete the file logger and delete the related queues, *REJECT* and *COMMAND*, in the coordination queue manager.

    Hope this helps.
    Shashi

    ------------------------------
    Shashikanth Rao Thambrahalli
    IBM
    ------------------------------

    Original Message