Ensuring that WebSphere MQ File Transfer Edition log messages are retained
WebSphere® MQ File Transfer Edition sends file transfer progress and log information to the coordination queue manager. The coordination queue manager publishes this information to any matching subscriptions to the SYSTEM.FTE topic. If there are no subscriptions, this information is not retained.
- Use the WebSphere MQ File Transfer Edition database logger to copy messages published to the SYSTEM.FTE/Log topic to an Oracle or DB2® database.
- Define a subscription to the SYSTEM.FTE topic, which stores publications on a WebSphere MQ queue. Define this subscription before transferring any file transfers to ensure that all progress and log messages are retained on the queue.
- Write an application that uses the message queue interface (MQI) or WebSphere MQ JMS to create a durable subscription and process the publications that are delivered to the subscription. This application must be in operation before any files are transferred to ensure that the application receives all progress and log messages.
Do not rely on the WebSphere MQ File Transfer Edition WebSphere MQ Explorer plug-in to retain log information.
Using the WebSphere MQ File Transfer Edition database logger to retain log messages
The database logger is an optional component of WebSphere MQ File Transfer Edition that you can use to copy log information in to a database for analysis and auditing purposes. The database logger is a stand-alone Java™ application that you install on a system that hosts the coordination queue manager and the database. For more information about the database logger, see Configuring a WebSphere MQ File Transfer Edition logger.
Retaining progress and log messages by using the WebSphere MQ File Transfer Edition MQ Explorer plug-in
When an instance of the WebSphere MQ File Transfer Edition WebSphere MQ Explorer plug-in is first started, the instance creates a durable subscription on the coordination queue manager. This durable subscription is used to collect the information displayed in the Transfer Log and Current Transfer Progress views. The name of the durable subscription is prefixed with the host name of the system running the associated instance of WebSphere MQ Explorer. This prefix is added in case an administrator wants to delete a durable subscription that is no longer in active use by an instance of the WebSphere MQ Explorer plug-in.
Using a durable subscription on the coordination queue manager can cause messages to build up on the SYSTEM.MANAGED.DURABLE queues. If you have a high-volume WebSphere MQ File Transfer Edition network, use the WebSphere MQ Explorer plug-in infrequently, or this message data can fill the local file system.
- Select
- From the Transfer Log subscriber type list, choose NON_DURABLE.
Storing publications on a WebSphere MQ queue
define sub(MY.SUB) TOPICSTR('Log/#') TOPICOBJ(SYSTEM.FTE) DEST(LOG.QUEUE)
After the log messages have been forwarded to a WebSphere MQ queue, they are persisted on the queue until they are processed by a WebSphere MQ application that uses the queue.
Writing applications that manage a durable subscription to the SYSTEM.FTE topic
You can write applications that manage their own durable subscriptions to the SYSTEM.FTE topic by using one of the application programming interfaces supported by WebSphere MQ. These applications can receive WebSphere MQ queue or log messages and act on them appropriately for your business needs.
For more information about the available application programming interfaces, see the following WebSphere MQ information:WebSphere MQ Application Programming Reference (SC34-6940-00) or WebSphere MQ Using Java (SC34-6935-00).