Configure IBM MQ advanced actions

IBM MQ is a messaging middleware that facilitates communication between applications, devices, and data across cloud, mobile, IoT, and on-premises environments. IBM MQ advanced actions help users connect to an IBM WebSphere MQ queue from within NeoLoad.

For the integration's requirements, check out this table:

Requirements Description
Maturity NeoLoad doesn't support it
Author IBM
License BSD Simplified (opens in new tab)
NeoLoad version NeoLoad 6.5.1 Enterprise and Professional editions with Integration & Advanced Usage
Bundled with NeoLoad No
Download Binaries You can find them in our support hub (opens in new tab)
Supported JMS API versions 1.1 and 2.0

Before you start

Before you set up the IBM MQ advanced actions, follow these steps:

  1. Download the latest version of the advanced actions (opens in new tab) and necessary IBM MQ .jar files.

  2. Add the advanced actions .jar file and the IBM MQ .jar file to the extlib folder of your NeoLoad project directory.

  3. Reopen your NeoLoad project to load the new action.

NeoLoad doesn't include IBM MQ implementation .jar files, such as mqcontext.jar. You must manually add these files from the IBM WebSphere MQ installation directory, such as C:\Program Files\IBM\WebSphere MQ\java\lib to the extlib folder in your NeoLoad installation.

IBM MQ parameters

The following parameters are available for the IBM MQ advanced actions:

Parameter Description Required/Optional
QueueManager Fully qualified class name of the factory class creating the initial context. Required
HostName Name of the host. Required
Port Port for client connection. Required
Channel Channel name, applicable in client transport mode. Required
QueueName Name of the queue. Required
QueueSessionTransacted Boolean indicating whether the session is transacted. Optional
QueueSessionAcknowledgeMode

Integer to define acknowledgment mode:

  • 1 for AUTO_ACKNOWLEDGE

  • 2 for CLIENT_ACKNOWLEDGE

  • 3 for DUPS_OK_ACKNOWLEDGE

 Optional
Username Username to create the connection. Optional
Password Password to create the connection. Optional
CCSID Client or server coded character set identifier. Optional
TransportProperty Transport type, such as MQSeries or MQSeries Client. Optional
Debug Debug mode values: True or False. Optional
SslFipsRequired Boolean to enforce FIPS-certified CipherSpecs for SSL/TLS channels. Optional
UseIBMCipherMappings Boolean to enable IBM CipherMappings. Optional
PreferTLS Boolean to prefer TLS for communication. Optional
SslCipherSuite SSL cipher suite to use. Optional
SslPeerName SSL peer name. Optional
SslProtocol SSL protocol to use, such as TLSv1 or TLSv1.2. Optional
TrustStorePath Path to the truststore file containing CA certificates. Optional
TrustStorePassword Password for the truststore file. Optional
KeyStorePath Path to the keystore file containing the certificate and private key. Optional
KeyStorePassword Password for the keystore file. Optional
QueueOperation Operation type: CREATE to create session and queue, or ACCESS to access an existing queue. Default type is CREATE. Optional
OpenOptions Integer for open options as specified in the Oracle documentation (opens in new tab). Default value is 8240. Optional
tls.insecure Boolean to bypass TLS certificate validation issues. Default is False. Optional

List of error codes

Error code Description
NL-CONNECTTOMQQUEUE-ACTION-01 Issue parsing parameters.
NL-CONNECTTOMQQUEUE-ACTION-02 Error while creating the connection to the queue.

Change log

2.2.1

  • Do not ignore TLS certificate issues for security purposes. Added tls.insecure for backward compatibility.

2.1.8

  • Added support for the OpenOptions parameter.

2.1.7

  • Added support for the QueueOperation parameter.

2.1.6

  • Added support for truststore and keystore parameters.

2.1.5

  • Added TLS support.

2.0.3

  • Added username and password for connection creation.