The Messaging Client tool is similar to the SOAP Client tool in that it sends payloads over HTTP to the server. However, this tool is very useful for non-SOAP clients, such as XML servlets and proprietary web services that have their own specifications.It can be used to test a service, test the communication between the client and server, and check the content of the HTTP messages.
In addition, the Messaging Client can be used for REST style services.For more information, see Testing RESTful Services.The REST Client tool can also be used to send messages to RESTful services. For more details, see REST Client.
To send a message using the Messaging Client tool, you need to tell SOAtest or Virtualize what message to send and how to send it. This is done by specifying the following parameters in the tool’s configuration panel.
This topic explains how to configure and apply the Messaging Client tool that sends HTTP messages to servers. Sections include:
Specifying options at the top of the configuration panel allows SOAtest and/or Virtualize to populate the Request tab with items that make it easier for you to specify the request message. You can specify the following schema settings:
- Schema URL: Describes the Schema URL where this service can be accessed. You can either enter a value or click the Browse button. If you do not have a schema, you can leave this field empty.
- Constrain to Schema: Determines whether certain parameters of the messaging tool obtain their values from the Schema rather than from manual entry. If this option is enabled, certain parameters (e.g. router endpoint, SOAP action, SOAP body and header parameters) are disabled and get their values from the WSDL. If this option is disabled, the Refresh Schema button will also be disabled.
- Refresh Schema: Refreshes the schema from the given location URL and reparses it.
From the Request tab of the Messaging Client tool, you can select input modes from the Input Mode drop-down list. The Messaging Client tool shares Input Mode options with the SOAP Client tool and Message Stub tool. For more information on these shared options, see Message Tool and Responder Options.
Note that in addition to the usual options, you can also use a table view, which is designed for posting form parameters. For details, see Table Input Options.
The Transport options allow you to determine whether the client sends requests using HTTP 1.0, HTTP 1.1, JMS, SonicMQ, WebSphere MQ, RMI, SMTP, or TIBCO protocols—or a custom protocol (To select a custom method, choose CUSTOM then enter the name of your custom method in the Value field that displays). To configure the properties of each protocol, select the appropriate protocol from the Transport drop-down list.
For more information, see the following sections:
Success Criteria Options
The following options are available in the Success Criteria tab of the Messaging Client tool:
- Valid HTTP Response Codes: Allows you to customize the tool behavior so that it succeeds with HTTP response codes outside the
2xxrange. Specify single codes and/or code ranges as a comma-separated list. For example, if you use "
302, 500-599", a
302code or any code in the 5xx range will be accepted. If you're using a parameterized value, be sure that the value in the data source uses this same format (e.g., "
Timeout after (milliseconds): Specifies the length of delay (in milliseconds) after which your FTP, telnet, or HTTP requests should time out. The Default setting corresponds to the timeout set in the Preferences panel. The Custom setting allows you to enter a timeout. A non-positive timeout value can be entered to specify an infinite timeout.
- Fail the test on timeout: Select this option to fail the tool on the specified timeout.
- Pass the test only if a timeout occurred: Select this option to pass the tool if the specified timeout occurred (i.e. tool did not finish execution within the specified time).
The following tutorial lesson demonstrates how to use this tool: