F2Q (File to Queue)

The F2Q product is a companion product and the reciprocal of the Q2F product that is referenced in the site.

The purpose of the F2Q application is to provide a reliable mechanism for reading files in a directory and writing the files as WebSphere MessageQ messages onto a WMQ queue for later processing by some other service. Care is being taken in the development of this product to ensure that the outgoing message data is not lost in the event of a system failure by automatically archiving the files that have been successfully sent. The diagram shown below, illustrates a typical use of the F2Q application:

The F2Q application is delivered in two versions on the disc; it can be included with the WMQ Client and WMQ Server bindings. This enables the user to deploy the product to a machine that has the WMQ Message Service already installed or to a machine where WMQ is not installed; and the WMQ Remote Client connection will be used to provide the messaging service. The following are a few of the main features of the F2Q application:

  • The specified directory is scanned for files and the oldest files that meets the selection mask criteria is opened for sending. When the file is successfully written to the WMQ queue, a log entry will be made and the file will be transferred to an archive directory location.
  • If a file cannot be written to the WMQ queue, a log entry will be made, the files will be closed and the F2Q application will sleep for a predetermined interval before attempting to send the file. This sequence will be repeated until the queue has sufficient space to enable the file to be written message or the queue has become available.
  • F2Q_c uses a WebSphere MessageQ Client connection to access its single input queue, while F2Q utilizes the local WMQ Server.
  • F2Q runs as a daemon and is started by as a system service.
  • F2Q has been tested on Windows, Linux, HP_UX11i, Solaris 8 and Solaris 9 with WebSphere MessageQ V5.3-V6.0

The Q2F application is supplied in two forms:

  1. Using the WebSphere MessageQ Client facility
  2. Using the local binding to the WebSphere MessageQ Server

Certified for HP_UX11i on Itanium: