Forum Discussion
I have the same problem.
Were you able to find a solution?
I have a project setup that uses MQTT/JMS to connect to a Websphere IBM MQ instance.
This wasn't super easy to set up.
You will need the following:
- bindings file (used by JNDI fscontext)
- additional jars in lib folder
- update to ready-api.bat file
- configuration within ReadyAPI
In your ready-api.bat file you need to add the following JVM parameter:
-Dcom.ibm.mq.cfg.useIBMCipherMappings=false
The additional jars you need:
- fscontext
- jms
- providerutil
- com.ibm.mq.allclient
The bindings file was created by the team that manages the WebSphere MQ software and provided to us. It has information regarding the queues including the connection factory name (which you need for setting up in ReadyAPI).
You'll need to open ReadyAPI with the .bat file so it uses the JVM parameter.
In JMS settings, you need to set the Initial Context Factory class, Provider URL (path to the bindings file) and connection factory name.
In my test cases, I publish a MQTT message which is routed to the QM.
I then use a JMS Request to consume the message off the queue. You need to use an existing request or create a new request. I used the petstore GET. From there, you can create an existing JMS endpoint or create a new one.
- Bailoze6 months agoNew Contributor
Thank you for your answer
Related Content
- 2 years ago
- 4 years ago
Recent Discussions
- 20 days ago