Operator Guide

10.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1

Back Next

MQ MFT Connection Properties

Create an MQ MFT Connection to define communications using the MQ protocol for an MFT Remote endpoint. Informatica Managed File Transfer can connect to enterprise messaging systems using JMS (Java Message Service) to send and receive messages from queues and topics.

The following table describes the properties in the

Basic

tab:

Property	Description
Name	Name of the MFT Connection.
Description	Provide a description for the MFT Connection.
Connection Type	The connection type for the MQ server. The MQ server can use the JMS Standard (Java Message Service) or a connection type specific to the MQ Provider. When connecting to Websphere MQ, SonicMQ or ActiveMQ use the MQ Provider Specific type and use JNDI (JMS Standard) for others.
URL	The connection string to an MQ Provider Specific server uses the following syntax: providerCode:[transportProtocol:]//host[:port][?key1=value1&key2=value2] . The connection string to a JNDI (JMS Standard) server is supplied by the MQ server administrator.
JNDI Initial Context Factory	The JNDI (Java Name and Directory Interface) context factory is the fully qualified name of the class used to look up the JMS connection factory object. For example, the class might be com.sun.jndi.fscontext.RefFSContextFactory or com.sun.jndi.ldap.LdapCtxFactory . This is required when the connection type is set to use the JMS Standard.
JNDI Name	The name of the JMS connection factory object to use. This is required when the connection type uses the JMS Standard.
JNDI Properties	The optional JNDI properties are specified using key=value pairs. Each pair is defined on a separate line.
User	The user name to use for connecting to the server.
Password	The password to use for connecting to the server.

Rename Saved Search

Table of Contents

Operator Guide

Operator Guide

MQ MFT Connection Properties

MQ MFT Connection Properties