Connect To MQ Queue

Overview

The Connect to MQ Queue Advanced action is used to connect to a IBM WebSphere MQ queue. It can be used with NeoLoad JMS Advanced actions Queue – Send, Queue – Receive and Disconnect.

Supported JMS API versions: 1.1 and 2.0.

Important: NeoLoad does not include MQ implementation jars (like mqcontext.jar). These jars, which can be found in the WebSphere Application Server installation directory (for example: C:\Program Files\IBM\WebSphere MQ\java\lib), need to be put in the extlib directory of your NeoLoad installation.

Type Advanced Action
Version 2.0.3
Maturity Stable
Author Neotys Professional Services
License BSD Simplified
NeoLoad 5.1 (Ultimate, Enterprise or Professional Edition w/ Integration & Advanced Usage option required)
NeoSense Compatible
Requirements MQ implementation jars
Bundled in NeoLoad No
Download Jar, Sources

Parameters

  • QueueManager (required): The fully qualified class name of the factory class that will create the initial context.
  • HostName (required): The name of the host.
  • Port (required): The port for client connection.
  • Channel (required): The name of the channel – Only applies to client transport mode.
  • QueueName (required): The name of the queue.
  • QueueSessionTransacted (optional): A boolean to indicate whether the session is transacted.
  • QueueSessionAcknowledgeMode (optional): An integer to indicate whether the consumer or the client will acknowledge any messages it receives; ignored if the session is transacted. Legal values are 1 for AUTO_ACKNOWLEDGE, 2 for CLIENT_ACKNOWLEDGE or 3 for DUPS_OK_ACKNOWLEDGE.
  • Username (optional): The username used to create the connection.
  • Password (optional): The password used to create the connection.

Changelog

  • 2.0.3 – Add the possibility to specify the username and password used to create the connection.

Status Codes

  • NL-CONNECTTOMQQUEUE-ACTION-01: There was an issue parsing the parameters.
  • NL-CONNECTTOMQQUEUE-ACTION-02: There was an error while creating the connection to the queue.

Examples

An example of connecting to a IBM WebSphere MQ queue:

  • QueueManager: myQueueManager
  • HostName: 10.0.0.52
  • Port: 1414
  • Channel: myChannel
  • QueueName: myQueueName

An example of connecting to a IBM WebSphere MQ queue with no JMS headers.

  • QueueManager: myQueueManager
  • HostName: 10.0.0.52
  • Port: 1414
  • Channel: myChannel
  • QueueName: queue:///myQueueName?targetClient=1
Entdecken
Folge uns