...
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 | ||
---|---|---|
| ||
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:
|
...
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 Queue | PROXY_REQUEST_QUEUE |
Reply to/Get Queue | PROXY_RESPONSE_QUEUE |
Server Queues | |
Destination/Put Queue | REQUEST_QUEUE |
Reply to/Get Queue | RESPONSE_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 Queue | REQUEST_QUEUE |
Reply to/Get Queue | RESPONSE_QUEUE |
Server Queues | |
Destination/Put Queue | PROXY_REQUEST_QUEUE |
Reply to/Get Queue | PROXY_RESPONSE_QUEUE |