Configure an MFT logger

When Managed File Transfer transfers files, it publishes information about its actions to a topic on the coordination queue manager. The database logger is an optional component of Managed File Transfer used to copy this information into a database for analysis and auditing purposes.

• stand-alone file logger (available in Version 7.5 and later)
• stand-alone database logger
• Java Platform, Enterprise Edition (Java EE) logger

Stand-alone file logger

The stand-alone file logger is a Java process that either runs on the system that hosts the coordination queue manager, or on a system which hosts a queue manager with connectivity to the coordination queue manager. The stand-alone file logger uses IBM MQ bindings to connect to its associated queue manager. The stand-alone logger is created using the fteCreateLogger command.

For Version 7.5 and later, we can run the stand-alone file logger as a Windows service to ensure that the file logger continues running when you log off from your Windows session, and it can be configured to start automatically when a system restarts. For more information, see Installing the MFT stand-alone file logger.

• z/OS
• IBM i

Stand-alone database logger

The stand-alone database logger is a Java application that you install on a system that hosts a queue manager and a database. The stand-alone database logger is often installed on the same system as the coordination queue manager, however it can also be installed on the same system as any queue manager which has connectivity to the coordination queue manager. The stand-alone database logger uses IBM MQ bindings to connect to its associated queue manager, and a type 2 or type 4 JDBC driver to connect to a Db2 or Oracle database. These types of connection are required because the stand-alone database logger uses the queue manager's XA support to coordinate a global transaction over both the queue manager and database, protecting the data.

If we are using a Windows system, we can run the stand-alone loggers as Windows services to ensure that the loggers continue running when you log off from your Windows session. For more information, see Installing the MFT stand-alone database logger for a stand-alone database logger.

Java EE database logger

The Java EE database logger is provided as an EAR file, which you install into an application server. This can be more convenient than using the stand-alone database logger if you have an existing Java EE application server environment available because the Java EE database logger can be managed alongside your other enterprise applications. We can also install the Java EE database logger on a separate system to the systems hosting the IBM MQ server and database. The Java EE database logger is supported for use with Db2 and Oracle databases. The Java EE database logger also supports Oracle Real Application Clusters when installed on WebSphere Application Server Version 7.0.

• Installing the MFT stand-alone file logger
  The stand-alone file logger is a Java process that must connect to a coordination queue manager using IBM MQ bindings. To define a stand-alone file logger use the fteCreateLogger command and follow the steps in this topic.
• Installing the MFT stand-alone database logger
  Complete these steps to install and configure the stand-alone database logger.
• Alternative configurations for an MFT stand-alone logger
  Typically a Managed File Transfer stand-alone logger, whether it is a file or a database type, is on the same system as the coordination queue manager and is connected to the coordination queue manager in IBM MQ bindings mode. However, it can also be installed on the same system as any queue manager which has connectivity to the coordination queue manager. The stand-alone logger receives messages using a subscription, which the stand-alone logger creates automatically. This is the configuration described in the installation instructions.
• Installing the Java EE database logger for MFT
  Follow these instructions to install and configure the JEE database logger for use with Managed File Transfer.
• Migrating from the stand-alone database logger to the Java EE database logger for MFT
  We can migrate from the stand-alone database logger to the Java EE database logger. We must stop the stand-alone database logger and install the JEE database logger. To avoid losing or duplicating log entries we must stop messages being published to the SYSTEM.FTE topic before stopping the stand-alone database logger, and restart it after you have installed the Java EE database logger. Back up your database before migration.

Parent topic: Configure Managed File Transfer

Related tasks

• Use MFT with a remote database

Related information

• Migrating the database tables on Db2 on z/OS to MQ V8.0 or later
• Migrating MFT: Increasing the log db page size for Db2 on UNIX, Linux, and Windows
• MFT logger error handling and rejection
• MFT logger configuration properties