Generic service client binary call details
In the generic service client, binary calls are specialized calls for sending binary messages. The transport information refers to the information that is required to send and receive and answer depending on the selected protocol.
- Update node name automatically
- Select this option to automatically rename the request in the Test Contents view.
- Do not wait for response
- Select this option to skip directly to the next request in the test after the current request is sent.
- 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 binary response element or to update the existing response element.
Message
- Source
- This page presents the binary contents of the request and provides access to data correlation. The same contents are presented in Binary and Raw ASCII views.
- Attachments
- This page lists the MIME or DIME attachments that are attached to the request. The contents of this view conform to the Multipurpose Internet Mail Extensions (MIME) or Direct Internet Message Encapsulation (DIME) specification. You can use this page to add workbench resources as MIME or DIME attachments and change properties.
- Transport
- This page covers the transport protocol used to send the request.
The transport protocol can be either HTTP, Java™ Message Service (JMS), or WebSphere® MQ. You can create several configurations
for each protocol so that you can easily switch protocols or variants
of protocols. Note: If you are using IBM® Security AppScan®,only the HTTP transport protocol is available.
Attachments
This page lists the MIME or DIME attachments that are attached to the request. The contents of this view conform to the Multipurpose Internet Mail Extensions (MIME) or Direct Internet Message Encapsulation (DIME) specification. You can use this page to add workbench resources as MIME or DIME attachments and change properties.
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.
- MIME or DIME
- Select whether the attachment conforms to the Multipurpose Internet Mail Extensions (MIME) or Direct Internet Message Encapsulation (DIME) specification
- Use MTOM transmission mechanism
- By default, the request uses SOAP Messages with Attachments (SwA) to handle attachments. Select this option to handle attachments with the SOAP Message Transmission Optimization Mechanism (MTOM).