Configure IBM MQ
Use the service port type IBM MQ to connect to IBM MQ queues or topics and to push and pull messages.
For information on IBM MQ, see the IBM MQ documentation.
Prerequisites
To use an IBM MQ connection, you have to install IBM MQ Client Library 9.1.0.4 or later.
If you use an earlier version, you can create a redirect as described in the Tricentis Knowledge Base.
Configure your service port
Once you have created your service port, you can configure the general service port details:
Attribute |
Description |
---|---|
General - Name |
Enter the name of the service port. |
General - Type |
Select your service port technology. |
Read / Write / Read & Write |
Select what your service port should do with messages:
|
Real Service |
Select if you want to connect to a real service. |
Allow OSV to forward requests to the real service. To use this option, you need to select Real Service. |
|
Allow OSV to store forwarded messages in the Recorder tab. To use this option, you need to enable Forwarding. |
|
Active |
Select if you want your service port to be active, deselect to set it to inactive. |
To connect to IBM MQ, specify the following attributes:
Attribute |
Description |
---|---|
Name |
Enter the name of the queue or topic you want to connect to. |
Type |
Select Queue or Topic. What you select depends on how you push and pull your messages with ActiveMQ. Queues represent a one-to-one messaging pattern, topics allow one-to-many messaging. |
Name |
Enter the name of the queue or topic you want to connect to. |
Host |
Enter the name or IP address of the host. |
Manager |
Specify the name of the manager that manages the queue or topic. |
Channel |
Enter the name of the channel that transfers the messages. |
Username |
If your connection requires authentication, enter your user name. |
Password |
If your connection requires authentication, enter your password. |
MessageType |
Specify what type of message you want to send and receive: JmsTextMessage or JmsBytesMessage. |
JMS Support |
Define the client type: IBM MQ with JMS or IBM MQ with Native WMQ. |
Selector |
Define a selector to filter the headers and properties of incoming JMS messages. This enables you to receive only JMS messages that match your filter criteria. For detailed information on the predefined selectors for this technology, see the IBM MQ documentation. |
Cipher Spec |
To enable encrypted communication (SSL), enter your combination of encryption algorithm and message authentication code algorithm. Example: ECDHE_ECDSA_AES_128_CBC_SHA256. |
Cipher Suite |
To enable encrypted communication (SSL), enter your suite of cryptographic algorithms. Example: SSL_RSA_WITH_RC4_128_MD5. |
Peer Name |
To enable encrypted communication (SSL), enter a string that contains the peer name. The peer name is the distinguished name of the certificate from the peer queue manager or client. |
Key Repository |
To enable encrypted communication (SSL), enter the file path to your key repository without file extension. Example: C:\Data\ssl_certificate |
Certificate Stores |
To enable encrypted communication (SSL), enter the URL of the certificate store server. If you use multiple certificate store servers, enter the URLs separated by comma. |
Port |
Specify the port to access the broker. |
UnprocessableMessages |
Define how to handle messages in a queue that a client can no longer process:
This applies only to queues, not to topics. |
IBM MQ service port
To save your changes, click Apply. To discard your changes, click Reset.
Once you have configured your service port, you can use your IBM MQ connection for testing. For information on how to edit JMS messages for your OSV Scenarios, see chapter "Edit JMS messages".
Work with dynamic queues
In IBM MQ, you can work with dynamic queues that are created during run-time. This applies for outbound queues and real service outbound queues. For detailed information on dynamic queues, see the IBM MQ documentation.
To work with dynamic queues in OSV, follow the steps below:
-
Go to the Outbound section of the IBM MQ service port. To see this section, you need to set your service port to Write or Read & Write.
-
Leave the Name field empty. In this case, OSV assumes that you use a dynamic queue and sends responses to the destination specified in the ReplyTo field of the actual request message.
-
In Tosca Commander, configure your OSV Scenario to ensure that OSV matches the correct response to the correct request.
This means that the MessageID of the request message has to be the same as the CorrelationID of the response message. You have to set the following ActionModes:
-
In the request message, set the MessageID ActionMode to Buffer.
-
In the response message, set the CorrelationID ActionMode to Insert.
-