Versions Compared

Old Version 2

changes.mady.by.user Robert Andelin

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 SVC2024.1

This topic explains how to record HTTP, JMS, and IBM MQ traffic for test generation purposes.

...

If you do not have Parasoft Virtualize, you can use SOAtest’s recording proxies to monitor and capture live HTTP, JMS, or IBM MQ traffic from a service as an application is exercised. These proxies can concurrently capture traffic that passes through multiple endpoints.

The recording proxy monitors traffic over the specified transport(s) as an application is exercised. SOAtest "listens" to traffic requests and responses, then builds a traffic file of legitimate request/response pairs. This traffic is then used to generate a test suite that represents the captured behavior in preconfigured test client tools.

JMS, IBM MQ, HTTP, HTTPS (SSL), Basic, Digest, and Kerberos authentication are supported; NTLM is not.

...

  1. Go to File > New > Other > SOAtest > Traffic > Record Traffic.
  2. For each endpoint where you want to record traffic, do the following:
    1. In the Configure Proxies for Recording Traffic dialog, click Add.

      The wizard that opens will be pre-populated with any connections you have already configured.
    2. Under Proxy Type, select the desired transport (HTTP, JMS, IBM MQ).
    3. Complete the proxy settings for the selected transport. See Customizing Grouping Criteria SOAtest, JMS Recording Configuration, or MQ Recording Configuration for details.
    4. In the Traffic file field, specify where you want to save the traffic file that will be created to capture this traffic. You can later use this traffic file to generate tests that represent the live traffic captured.
    5. Specify how you want traffic data recorded in traffic files:
      • Append new session data adds new traffic data to an existing traffic file (the one specified in the Traffic file field). If the specified file does not already exist, a new file will be created.
      • Overwrite session data overwrites the traffic data in an existing traffic file (the one specified in the Traffic file field). If the specified file does not already exist, a new file will be created.
  3. Click OK.
  4. In the main wizard panel, click Next.
  5. Set the host and port of the application under test to the location specified in the wizard.
  6. From the application under test, generate the traffic that you want to record.
  7. Click Finish.

...

This section explains how to configure recording proxies that send and receive messages over the IBM MQ transport.

Sections include:

...

Prerequisites
Anchor
MQ Prerequisites
MQ Prerequisites

Jar Files

SeeAdding Necessary Jar Files to the Classpath.

...

Specifying MQ Settings
Anchor
Specifying MQ Settings
Specifying MQ Settings

Specify your IBM MQ settings as follows:

  1. In the Proxy (Client) and Target Application (Server) Connection Settings dialog, choose MQ for Proxy Type.
  2. Specify the MQ IBM MQ settings in the available fields. See below for more configuration details.

Info
iconfalse
titleUse replyToQueueName for Response

This option specifies whether to use the message’s replyToQueueName header to determine where the proxy sends the response. It impacts responses to MQ IBM MQ messages of type MQMT_REQUEST.

If Use replyToQueueName for Response is enabled, values from the incoming request will be used to determine where to send the response. If it is not enabled, the response will be sent to the queue specified in the UI. More specifically:

  • If Use replyToQueueName for Response is enabled and values for both MQMD.replyTo-QueueManagerName and MQMD.replyToQueueName have been specified, those values will determine both the queue manager and the queue name to send the response to.
  • If Use replyToQueueName for Response is enabled and either MQMD.replyToQueueM-anagerName or MQMD.replyToQueueName is missing from the request, the values specified in the UI will be used in place of the missing value.
  • If Use replyToQueueName for Response is disabled, the replyToQueueName and reply-ToQueueManagerName fields in the IBM MQ request message will be ignored. The UI settings will determine where the message is sent.

...

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

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

...

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

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

...