Alternative configurations for the database logger

Typically the database logger is on the same system as the coordination queue manager and is connected to the coordination queue manager in WebSphere® MQ bindings mode. The database logger receives messages using a subscription, which the database logger creates automatically. This is the configuration described in the installation instructions.

However, if you have site-specific considerations, you can configure the database logger to receive messages in two other ways, controlled by the wmqfte.message.source.type property. This property is described in Database logger properties.

Administrative subscription

By default, the database logger creates its own subscription to the SYSTEM.FTE/Log/# topic, using the default durable subscription options and a managed subscription (that is, the queue manager controls the backing queue used to hold the messages before they are passed to the application). If other options are required on the subscription or the queue, you can instead create a subscription yourself, set the options that you require, and configure the database logger to use that subscription instead. Remember to add permission for the database logger to use the subscription that you create.

An example of using this configuration is to partition the log space by using two wildcard subscriptions, to send logs from agents whose name begins with FINANCE into one database and logs from agents beginning with ACCOUNTING into another. This type of configuration requires two database logger instances, each with its own databaselogger.properties file referring to the required subscription and its own command queue and reject queue.

To collect log messages only from agents whose names begin with ACCOUNTING, create a subscription object on your coordination queue manager with a topic string of SYSTEM.FTE/Log/ACCOUNTING*. Set the Wildcard usage value to Character level wildcard. You must also add entries to the databaselogger.properties file for your WebSphere MQ File Transfer Edition installation. For example, if you create a subscription object called ACCOUNTING.LOGS with these settings, add the following entries to the databaselogger.properties file:
wmqfte.message.source.type=administrative subscription
wmqfte.message.source.name=ACCOUNTING.LOGS 
If your alternative configuration means that you must use more than one database logger, you need separate command and reject queues defined for each of your database loggers. For example, if you create a command queue called SYSTEM.FTE.DATABASELOGGER.COMMAND.ACCOUNTING and a reject queue called SYSTEM.FTE.DATABASELOGGER.REJECT.ACCOUNTING, add the following entries to the databaselogger.properties file:
wmqfte.command.queue.name=SYSTEM.FTE.DATABASELOGGER.COMMAND.ACCOUNTING
wmqfte.reject.queue.name=SYSTEM.FTE.DATABASELOGGER.REJECT.ACCOUNTING 

The database logger handles log messages that start with the topic string of SYSTEM.FTE/Log/ only. You can specify a more restrictive topic string, but you cannot specify a less restrictive string. If you do specify a less restrictive string in error, all publications that relate to a topic string other than SYSTEM.FTE/Log/ go to the reject queue, and the database logger produces the error message BFGDB0002E. This error message implies that there is a problem with the database logger configuration.

Queue

The typical topology is where the database logger runs on the same system as the coordination queue manager. If this is not possible, you can create a subscription on the coordination queue manager using a queue on another queue manager as the subscription destination (either using a remote queue definition or by using the DESTQMGR property of the subscription). The database logger can then run on the system hosting the second queue manager and read the messages from the queue. To ensure transactional integrity, the database logger must always connect to its queue manager in bindings mode. You must define the reject queue and command queue on the same queue manager that the database logger connects to. The queue managers must be at WebSphere MQ Version 7 or later.

For example, to collect log messages which are being placed on the queue USER.QUEUE by a subscription, add these entries to the databaselogger.properties file:
wmqfte.message.source.type=queue
wmqfte.message.source.name=USER.QUEUE

Reference Reference

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/dl_alt_config.htm