Versions Compared

Old Version 1

changes.mady.by.user user-50d80

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2023.1

...

The method that Parasoft Virtualize uses for capturing/recording JMS point-to-point messaging and WebSphere MQ requires Virtualize to be a proxy— or, proxy; in other words, an intermediary / man-in-the-middle. 

Assume that there is a client/consumer application (we’ll call this "Client") that sends/puts/pushes a request message on destination queue REQUEST_QUEUE and receives/gets/pulls a response/reply from RESPONSE_QUEUE. Also assume there is a server/provider application (we’ll call this "Server") that receives/gets/pulls messages from REQUEST_QUEUE and sends/puts/pushes responses to RESPONSE_QUEUE. 

 

There are two possible configuration scenarios for recording traffic. In one, you modify the queues that are used on the client application end. In the other, you modify the queues that are used on the server.

...

If the application under test is the client end of the system, then it is likely that the goal is to virtualize the server application. In this case, scenario 1, which involves modifying the client application, is more feasible because it involves modifying the component that is owned by the party interested in virtualization.  

Info
titleUsing Topics Instead of Queues?

If a publish and subscribe scheme is used (using Topics instead of queues), then you don’t need to introduce new topics into the system. That’s why only two destinations need to be provided in the wizard:

  • One for the requests—labeled requests, labeled in the wizard as the "Client Subscribe Topic."
  • One for the response—labeled response, labeled in the wizard as the "Server Publish Topic."

...

The server does not need to have its queues changed in this case. 

 

In the Virtualize MQ or JMS recording wizard, provide the queue names as follows:

 

Client Queues
Destination/Put QueuePROXY_REQUEST_QUEUE
Reply to/Get QueuePROXY_RESPONSE_QUEUE
Server Queues
Destination/Put QueueREQUEST_QUEUE
Reply to/Get QueueRESPONSE_QUEUE

Scenario 2: Modifying the Server Application

...

The client does not need to have its queues changed in this case. 

 

In the Virtualize MQ or JMS recording wizard, provide the queue names as follows: 

Client Queues
Destination/Put QueueREQUEST_QUEUE
Reply to/Get QueueRESPONSE_QUEUE
Server Queues
Destination/Put QueuePROXY_REQUEST_QUEUE
Reply to/Get QueuePROXY_RESPONSE_QUEUE