Receiving Data from a JMS Queue

The following example demonstrates how to receive data from a JMS queue.

Prerequisites

Ensure that you have completed the following tasks:

  • Both TIBCO MFT Command Center and TIBCO MFT Internet Server are installed.
  • The JMS service in TIBCO MFT Command Center is configured and started. See TIBCO Managed File Transfer Command Center User 's Guide for more information about configuring and starting the JMS service.
  • A JMS queue named MFT.Queue1 is created in JMS.
To receive data from a JMS queue, you have to perform the following operations:
  1. Adding a JMS Server
  2. Adding a Transfer Definition
  3. Receiving Data from the JMS Queue to a Client

Adding a JMS Server

Click Servers > Add Server to open the Add Server page, and configure the following parameters in the Required Server Information section:
Field Description
Server Name Defines the name for the server that you add.
IP Address or fully qualified IP Name Defines the IP address or IP name for the server you add.
Type the address 127.0.0.1.
Note: This parameter is required for adding a server but is ignored for JMS because the JMS connectivity information is defined on the Configure JMS Service page.
Server Type Defines the type of the server that TIBCO MFT Command Center will be communicating with.

Select JMS.

OverrideJMSServiceConfiguration

Defines whether to override the URL defined in the Configure JMS Server parameter.

When the value is Yes, the URL defined in the IPAddress or fully qualified IP Name parameter overrides the URL defined in the Configure JMS Server parameter. When the value is No, the URL defined in the Configure JMS Server parameter is used, and the URL defined in the IP Address or fully qualified IP Name parameter is ignored.

Adding a Transfer Definition

Click Transfers > Add Transfer to open the Add Transfer page, and configure the following parameters in the Required Transfer Information section:
Field Description
Client File Name Defines the name for the client file.
Server File Name Defines the name for the queue that you want to write.

In this example, enter MFT.Queue1.

Directory Transfer Defines whether the transfer is a directory transfer.

Select No. Downloads require transfers to be file transfer not directory transfer.

Description Defines a short description for the transfer that you add.
Authorized User Id Defines the ID of the authorized user.
Choose the user ID from the drop-down list that will be used to make this file transfer.
Note: You must have TransferRight assigned to your account.
Server Name Defines the name for the server.
Transfer Direction Defines the direction of the transfer: Upload to Server or Download to Client.

Select Download to Client.

Client Protocols Allowed Defines whether all client protocols are supported.

Select ALL.

Department Defines the department to which this transfer is assigned.

If you have one, set it here; if not , leave it blank.

Virtual Alias Defines the alias that the client uses for transfers.

For this example, JMSPlatform is used.

Configure the following parameters in the Additional Transfer Properties section:
Field Description
Data Type Defines which data type the system uses to write to JMS.

This parameter is ignored when reading from a JMS queue.

Delimiter Defines the system how to handle record delimiter.
The following fields are available:
  • No: all message will be read from JMS and written as a single record.
  • CRLF: CRLF delimiters will be added at the end of each JMS message read.
  • LF: LF delimiters will be added at the end of each JMS message read.
Configure the following parameters in the JMS Properties section:
Field Description
Input Selector Defines the selector that is used to filter JMS messages when reading data from a JMS queue .
Note: This parameter is ignored when writing data to a JMS queue.
By default, all data in a queue will be read.
Output JMSType Property Defines the JMSType output property that is written when the file is sent to the JMS queue.
Note: This parameter is ignored on download requests and can be left blank.
Output Property Defines the output property that is set when writing data to a JMS queue.
Note: This parameter is ignored on download requests and can be left blank.
Max Message Size Defines a maximum message size.
Note: This parameter is ignored on a download requests.
Write EOF Message

Defines whether MFT will write an empty JMS message at End Of File. This message will indicate that the entire file has been written and will not contain any message data. Supported values are:

Yes - Write an empty message indicating end of file. JMS header property "LastMessage" will be "true" for the empty message and "false" for messages that contain data.

No - Do not write an empty message indicating end of file

Click Add after you finish the configurations.

Receiving Data from the JMS Queue to a Client

Go to the client from which the data will be sent.

The following example assumes a JMS queue named MFT.Queue1 is defined in JMS. In this example, the FTP Command Line client is used; however, any client can be used. 

FTP to MFT Internet Server and authenticate with the JMS user credentials get /
JMSDOWN/MFT.Queue1 c:\test.txt