Hello CA Community,
we have a PoC running, where we need to create an MQ-Virtualization by RR Pairs. (MQ Native as Transport Protocol)
1. Do you need a queue manager for the RR Pairs virtualization and how can you install or use the queue manager.
2. Is it necessary to have an MQ Explorer or MQ jar files to create a RR Pairs MQ-Virtualization?
3. Due to connection restrictions by Firewall, we can't use the full functionality of the Workstation via remote. Is it possible to export the MQ VS to MAR and to deploy it to the Portal?
4. Is it possible to use any XML RR Pairs for the virtualization or do they have to follow some rules?
Thank you in advance
All valid questions and the right kind of questions that will propel you forward using the product for the right use. Let me take a stab at it. I am sure there are lot of very experienced people in the community who will chip in further and refine the answers and bring more clarity.
[Answer] Yes, if your intent is to do IBM MQ virtualization, you definitely need the queue managers. There is lot of information in the product documentation. Besides, I suggest you to have a look at this document that was posted in communities on the IBM MQ - Devtest topic: https://communities.ca.com/servlet/JiveServlet/download/242147004-1-198603/CA-DevTest-IBMMQ.pdf
[Answer] Given the fact that you would need the queue manager set up, you need the IBM MQ jars put in right place. For more details please refer to https://docops.ca.com/devtest-solutions/10-4/en/administering/general-administration/third-party-file-requirements#Third-PartyFileRequirements-WebSphereMQFileRequirements
Btw, Devtest doesnt need MQ Explorer. You may use it for your own administration activities with IBM MQ Broker.
[Answer] Yes you can deploy the MAR file from Portal. For more details please refer to section titled "To upload the contents of a MAR file into a project:" in https://docops.ca.com/devtest-solutions/10-4/en/getting-started/devtest-portal
[Answer] Very good question. Yes, there are certain file naming conventions to follow. More details can be had from: https://docops.ca.com/devtest-solutions/10-4/en/using/using-ca-service-virtualization/ca-service-virtualization-concepts/request-response-pairs
Re. 1 - Maybe the question should be: Why is it necessary that the queue manager already exists, is up and running, and must be accesible when you are creating virtual services from RR pairs? Your answer is obvious for when you are creating a virtual service through recording but the prerequisite of needing an accessible up-and-running queue manager for RR pairs is cutting into our abilities of agility and properly supporting test-driven development.
Now, that being said the work-around is to have one "dummy" queue manager and dummy queues up-and-running and available in your test engineering environment. You use the same queues for whatever MQ service you want to virtualize. If you give proper meaningful but generic names for your queues, channels and queue manager assets then it is just a matter of providing the proper config with the real names when deploying to the actual test environment?
Thank you very much, Sankar and Danny. I appreciate your support.
You are most welcome !! Happy to be of help.