Table of Contents

Search

  1. Preface
  2. Introduction
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

Websphere MQ Connection Properties

Websphere MQ Connection Properties

Property Name
Description
queueManager
The name of the Queue Manager.
clientID
The ID assigned to
Managed File Transfer
(client). This is used as part of the topic’s subscription ID.
hostName
Name or IP address of the host MQ server. If specified, this value overrides the value in the host portion of the URL.
port
The port number of the MQ server. If specified, this value overrides the value in the port portion of the URL.
transportType
The type of transport (default 1).
channel
Sets the name of the channel - applies to client transport mode only.
localAddress
The local address to be used. The format of a local address is [IP address or Host Name][(low-port[,high-port])]. Most MQ servers use 4-5 ports, but if an application is having difficulty making connections, increase the number of ports in the range. A host name can be specified instead of an IP address. Local address examples:
9.20.4.98 - The channel binds to 9.20.4.98 locally.
9.20.4.98(1000) - The channel binds to 9.20.4.98 locally and uses port 1000.
9.20.4.98(1000,2000) - The channel binds to 9.20.4.98 locally and uses a port in the range 1000 to 2000.
(1000) - The channel binds to port 1000 locally.
(1000,2000) - The channel binds to a port in the range 1000 to 2000 locally.
Considerations:
  • Specify a range of ports to allow for connections that are required internally as well as those explicitly used by an application. The number of ports required depends on the application and the facilities it uses. Typically, this is the number of sessions the application uses plus three or four additional ports. If an application is having difficulty making connections, increase the number of ports in the range.
  • Connection pooling has an effect on how quickly a port can be reused. In JMS, connection pooling is switched on by default and it might be several minutes before a port can be reused. Connection errors might occur in the meantime.
  • For real-time connections, the local address determines which of the local network interfaces is used for multicast connections. When specifying a local address for a real-time connection, do not include a port number. A port number is not valid for multicast and, if specified, causes a failure at connect time.
maxBufferSize
The maximum number of received messages stored in an internal message buffer (default 1000).
proxyHostName
The host name of the proxy server when establishing a real-time connection.
proxyPort
The port number of the proxy server when establishing a real-time connection.

0 COMMENTS

We’d like to hear from you!