+

Search Tips   |   Advanced Search


Service call details

Service call elements contain the contents of the call and the transport information for this call. The contents are made of the SOAP envelope. The transport information refers to the information that is required to send and receive and answer depending on the selected protocol.


Call Settings

Update request name automatically

Automatically rename the request in the Test Contents view.

Do not wait for response

Skip directly to the next request in the test after the current request is sent.

Operation and WSDL Name

These identify the WSDL name and operation to which the service request is binded.

WSDL Resource

This is the name of the WSDL resource in the workbench. Click the link to edit the WSDL file. If the WSDL file is missing, click the link to bind the request to a WSDL in the workspace or to import a WSDL.

Time Out (ms)

This is the timeout value in milliseconds. If no response is received after the specified time, an error is produced.

Think Time (ms)

This specifies the programmatically calculated time delay that is observed for each user when this test is run with multiple virtual users. Think time is a statistical emulation of the amount of time actual users spend reading or thinking before performing an action.

Update Response

Click this button to invoke the request with the current settings and to use the response to create a service response element or to update the existing response element.


Message

This page presents the XML contents of the request and provides access to data correlation. The same contents are presented in three different manners.

Form

This view provides a simplified view of the message focused on editing the values of the XML content.

Tree

This view provides a hierarchical view of the XML structure of the message, including elements, namespaces, and the associated values. You can use Add, Insert, Remove, Up, and Down to edit the XML elements and namespaces in the tree.

Click Filter to hide or show namespace, attribute, or text nodes, depending on requirements.

Click Allow only valid modifications to enable smart editing, based on a specified XML schema document (XSD).

To specify a set of XSD documents for the workbench, in the test navigator, right-click the project and select Properties and Schema Catalog. Disable Allow only valid modifications if you do not have an XSD or to bypass the schema.

You can right-click an XML element to convert it to an XML fragment. This enables you to perform data correlation (use datapools and create references) on the entire XML fragment instead of only on the value.

Source

This view displays the source XML content of the message or plain text content.

In the Source view, do not edit the tags that start with SoaTag. If you delete or change these tags, any references and substitutions in the test will be broken. You cannot recreate these tags after you delete them.


Attachments

This page lists the MIME attachments that are attached to the request. The contents of this view correspond to the specification of Multipurpose Internet Mail Extensions (MIME). You can use this page to add workbench resources as MIME attachments and change properties.

To use Web service attachments, add a set of Java™ libraries to the Java Runtime Environment (JRE) that the workbench uses. See Configure the environment for handling file attachments for more information. The Content ID is the identifier that the request uses to refer to the attachments. The method for using this identifier depends on your server requirements.

Use MTOM transmission mechanism

By default, the request uses SOAP Messages with Attachments (SwA) to handle attachments. Handle attachments with the SOAP MTOM.


Transport

This page covers the transport settings used to send the request. The transport protocol settings apply to a transport configuration, which can be either HTTP, Java Message Service (JMS), or WebSphere MQ. You can create several configurations for each protocol so that you can switch protocols or variants of protocols.

HTTP

Select HTTP to use the HTTP transport for the request. At the request level, you can update a URL or SOAP action and the reference to the global configuration of a test.

Protocol configuration

Click Change to specify a predefined transport configuration or to create a configuration. HTTP transport configurations contain proxy and authentication settings that can be reused.

Method and Version

Specify the HTTP method and version to be used to invoke the service request.

URL

Specify the URL end point of the service request.

Headers

Specify the names and values of any custom HTTP headers that are required by the service. Click Add, Edit or Remove to modify the headers list.

Cookies

Specify the names and values of any cookies required by the service. Click Add, Edit or Remove to modify the cookies list.

JMS

Select JMS to use the Java Messaging Service transport for the request. This page enables you to add string properties that are attached to the request for a JMS configuration. These will be sent as message properties through JMS.

Protocol configuration

Click Change to specify a predefined transport configuration or to create a configuration. JMS transport configurations contain generic end point, reception point, and adapter settings that can be reused.

Properties

Specify the names and values of any string properties that are required by the request for the current JMS transport configuration. These are sent as message properties through JMS. Click Add, Edit or Remove to modify the properties list.

WebSphere MQ

Select MQ to use the IBM WebSphere MQ transport for the request. This page enables you to specify the SOAP action and override the settings for the WebSphere MQ configuration selected at the test level.

Protocol configuration

Click Change to specify a predefined transport configuration or to create a configuration. MQ transport configurations contain generic queue, header, and SSL settings that can be reused.

SOAP Action

Specifies the SOAP action to be used to invoke the MQ request.

Override MQ protocol configuration values

Configure the fields of the MQ message. You can replace a subset of an MQ message descriptor with a custom format for use with other server types, specifically when using an XML message request. Refer to WebSphere MQ documentation for details about message descriptors. These settings replace the message descriptor and header settings of the MQ protocol configuration.

Use custom header

Specify custom headers for the transport for the SOAP over MQ feature that is provided by WebSphere MQ. This feature uses a predetermined MQ message format (RFH2), therefore, when selected, other Message Descriptor options are disabled.


Related reference

  • Service test details
  • XML call details
  • Service message return details
  • Service verification point details
  • Service callback details
  • Service timeout details
  • Service parallel details
  • Service receive details