Service Virtualization

  • 1.  MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Apr 17, 2018 07:02 AM

    Hi ,

     

    We are trying to virtualize MQ service using DevTest 10.1.0. We have placed the below listed IBM Webshpere MQ 9 jar files in the DevTest lib folder.  Can someone please confirm whether DevTest 10.1.0 support MQ V9 and below jar files are sufficient to connect with MQ. It would be really helpful if someone help us to setup the MQ v9 connectivity in DevTest 

    • ibm.mq.commonservices
    • ibm.mq.headers
    • ibm.mq
    • ibm.mq.jmqi
    • ibm.mq.pcf

     

    Thanks in advance

     

    Regards,

    Rjeev



  • 2.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup
    Best Answer

    Broadcom Employee
    Posted Apr 17, 2018 10:05 AM

    Hello Rjeev,

     

             MQ9 support was officially added to DevTest 10.3. Please find more information below on the jar requirements for the same. 

     

    https://docops.ca.com/devtest-solutions/10-3/en/administering/general-administration/third-party-file-requirements 

     

    https://docops.ca.com/devtest-solutions/10-3/en/release-notes/new-features-and-enhancements#NewFeaturesandEnhancements-I… 

     

    Thanks,

    Surya



  • 3.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Apr 17, 2018 01:23 PM

    Hi Surya, 

     

    Thank you for the information shared. Could you please ensure that whether we can use MQ9 in DevTest 10.1.0 itself. If yes, could you please help us to do the MQ v9 connectivity setup in DevTest. 



  • 4.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Apr 17, 2018 02:21 PM

    *Officially*, we do not support IBM MQ 9 until DevTest 10.3.

     

    *Unofficially*, IBM MQ 9 should function with DevTest 10.1.  However, depending on what you are doing there may be a lot of very large and ugly warning messages that show up in the log when you stop a test or virtual service.  You can safely ignore those.

     

    Your jar list looks complete unless you want to use JMS mode.

     

    > If yes, could you please help us to do the MQ v9 connectivity setup in DevTest.

     

    It's officially unsupported in your version of DevTest, so we can't really offer you personalized attention to get set up.  All I can do is point you at the documentation:

    IBM MQ Native Assets - DevTest Solutions - 10.1 - CA Technologies Documentation 

    IBM MQ Native Send Receive Step - DevTest Solutions - 10.1 - CA Technologies Documentation 

    IBM MQ Native Transport Protocol - DevTest Solutions - 10.1 - CA Technologies Documentation 



  • 5.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Apr 17, 2018 02:29 PM

    Hi Kevin, 

     

    Thank you for the clarification and shared information. 



  • 6.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Jul 05, 2018 04:25 AM

    Hi Kevin,

     

    We are using Devtest9.5.1 version and out infrastructure is getting updated to IBM MQ 9. We are basically using IBM MQ depreciated step in devtest 9.5.1

     

    Will it support connectivity with IBM MQ 9. Kindly suggest if there is any alternative path to fix the problem since immediately its not possible for us to migrate to version 10.3. It might take some time but IBM MQ infrastructure is about to migrate pretty soon.

     

    Thanks,

    Vinit Malhotra



  • 7.  Re: MQ Virtualization - Wepshere MQ 9 Connectivity Setup

    Posted Jul 09, 2018 06:58 PM

    Okay.  The *only* problem I'm aware of with MQ 9 and the DevTest MQ Native step/protocol before 10.3, is this:  There are some specific versions of the MQ v9 client jars that have a bug that will cause it to write large block of log output to standard output, and thus to the DevTest process log, when stopping a running test or running VSM that is listening on an MQ Queue. 

     

    There is no functional problem, it's just an ugly log that may appear.  It still works fine.  The entirety of the changes necessary for "MQ 9 support" was to change the way we do things slightly so the large log block no longer appears. 

     

    *Unofficially*: Without this fix we still work just fine MQ 9. 

    "Officially*: If you happen to run into an actual, functional issue that only occurs with MQ 9 then support will ask you to upgrade to 10.3 before helping you.