Installing the MFT stand-alone database logger
Complete these steps to install and configure the stand-alone database logger.
For more information about the stand-alone database logger, see Configure an MFT logger.Note: We cannot run more than one database logger (stand-alone or
Java EE) against the same schema in a database at any
one time. Attempting to do so would result in clashes when attempting to write transfer log data to
the database.
Procedure
- Install your database software using the documentation for the database. If JDBC support is an optional component for the database, we must install this component.
- Run the fteCreateLogger command setting the parameter -loggerType to DATABASE to create your stand-alone database logger. For more information, see fteCreateLogger. The default schema name is FTELOG. If we use a schema name other than FTELOG, we must edit the provided SQL file appropriate to your database, ftelog_tables_db2.sql or ftelog_tables_oracle.sql, to reflect this schema name before proceeding to the next step. For more information, see wmqfte.database.schema in MFT logger configuration properties.
-
Create the required database tables using your database's tools.
On Multiplatforms, the files ftelog_tables_db2.sql and ftelog_tables_oracle.sql contain SQL commands that we can run to create the tables.
On z/OS, the file that we need to run depends on the version of Db2 for z/OS that we are using:- For Db2 for z/OS V9.0 and earlier, run the file ftelog_tables_zos.sql to create the tables. This file creates the tables using an INTEGER data type for fields which denote the sizes of files that are transferred and the table ID associated with each transfer.
- For Db2 for z/OS V9.1 and later, run the file ftelog_tables_zos_bigint.sql to create the tables. This file creates the tables using a BIGINT data type for fields which denote the sizes of files that are transferred and the table ID associated with each transfer.
- Run the MQSC commands, provided by the fteCreateLogger command, against your logger command queue manager to create the logger queues. The stand-alone database logger uses two queues on the coordination queue manager. The first queue is a command queue where messages to control the operation of the stand-alone database logger are placed. The default name of this command queue is SYSTEM.FTE.LOG.CMD.logger_name. The second queue is a reject queue. Because the stand-alone database logger never discards log messages, if the logger encounters a message that it cannot handle, it places the message on the reject queue for examination, and possible reprocessing. You are not recommended to use the queue manager's dead letter queue for this purpose, because rejected messages do not have a DLH header and because rejected messages should not be combined with messages put to the dead letter queue for other reasons. The default name for the reject queue is SYSTEM.FTE.LOG.RJCT.logger_name. These two queues are defined in the MQSC script files generated by the fteCreateLogger command.
- Choose a user and configure permissions
- Optional: We can configure the stand-alone database logger further by editing the logger.properties file created by the fteCreateLogger command in step 2. This file is a Java properties file that consists of key-value pairs. The logger.properties file is in the MQ_DATA_PATH/mqft/config/coordination_qmgr_name/loggers/logger_name directory. For more information about available properties and their effects, see MFT logger configuration properties.
- Optional: If we are using a Windows system, we can run the stand-alone database logger as a Windows service. Run the fteModifyLogger command with the -s parameter. For more information, see fteModifyLogger.
- Optional: If the database being used is Oracle or we are connecting to a Db2 database remotely, we will need to specify a user name and password that the logger will use to authenticate with your database server. This user name and password is specified in a credentials file that conforms to the format defined by the MQMFTCredentials.xsd schema. For more information, see MFT credentials file format. After creating the credential file, we must specify the location of the credentials file in the logger.properties file using the wmqfte.database.credentials.file property.
- Start the stand-alone database logger using the fteStartLogger command. By
default, the stand-alone database logger runs in the background and
the stand-alone database logger places output into a file in the logs directory.
To run the stand-alone database logger in the foreground
and produce output to the console as well as to the log file, add
the -F parameter to the fteStartLogger command.
If you carried out the previous step and used the fteModifyLogger command with the -s parameter on Windows, the stand-alone database logger starts as a Windows service.
- Use MFT with a remote database
We can use the Managed File Transfer logger to communicate with a database on a remote system. - Configure user access for an MFT stand-alone database logger
In a test environment, we can add any new privileges needed to your normal user account. In a production environment, we are recommended to create a new user with the minimum permissions required to do the job.
Parent topic: Configure an MFT logger
Related tasks
Related information