Generic service client text call details
In the generic service client, text calls are specialized calls for sending text 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.
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).
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), WebSphere® MQ, or Microsoft .NET. You can create several configurations for each protocol so that you can easily 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.
- URL
- Specify the URL end point of the service request.
- Rest mode
- Use this check box to split the REST URL so that it is easy to understand the different parts of REST URL. When you use this option, the main section of URL is placed in the URL field, the resource part is placed in the Resource field, and the parameters are placed in the Parameters field. Use the Add button to manually add more parameters.
- Method
- Specify the HTTP method to be used to invoke 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 that are 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. WebSphere® 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 WebSphere® MQ request.
- Override MQ protocol configuration values
- Select this option to configure the fields of the WebSphere® 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.
- Customize message header
- Select this option to 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.
- Message descriptor
- These settings replace the message descriptor and header settings of the MQ protocol configuration. Refer to WebSphere® MQ documentation for information about message descriptors.
- Microsoft™ .NET
- Select Microsoft .NET to use the Microsoft
.NET Framework transport for requests based on Windows™ Communication Foundation (WCF). This
page enables you to override the settings for the Microsoft™ .NET configuration selected at
the test level.
- Item
- Click Add to specify the name and value of the WCF actions that are required by the service. This table is automatically generated when you import a Microsoft .NET WSDL file. Refer to the Microsoft™ .NET WCF documentation for more information.
Security for Request
In this page you can edit the security algorithm stacks that the security protocol uses. Security stacks are a set of algorithms that are executed in a given order.- Override stack
- By default, you edit the security algorithm stack attached to a specific WSDL file in the WSDL Security Editor. Select this option to specify a different security algorithm stack only for the current response.
- Show response stack
- Clear the Show response stack option to hide the Response Stack page.
- Security Algorithm Details
- Click Add, Insert, or
Remove to add or remove
security algorithms in the stack. Click
Up and
Down to change the order of
a selected algorithm in the security stack. The
following security algorithms can be added to the
security stack:
- XML Encryption
- The XML encryption security algorithm specifies how the XML document
is encrypted. For details on security algorithms, refer to the web
service security specification.
- Actor / Role name
- Specify the name of the recipient of the algorithm header element, if required.
- Must understand
- Select whether it is mandatory that the algorithm header is processed by the recipient, if required. The recipient is either the Actor name or the server.
- Identifier type
- Select the type of key identifier to be used for the encryption.
The following key identifiers are available, as defined in the Web
Services Security (WSS) specification X509 profile and the OASIS WSS
1.1 specification:
- ISSUER_SERIAL
- BST_DIRECT_REFERENCE
- X509_KEY_IDENTIFIER
- SKI_KEY_IDENTIFIER
- EMBEDDED_KEYNAME
- THUMBPRINT_IDENTIFIER
- ENCRYPTED_KEY_SHA1_IDENTIFIER
- User XPath part selection
- This enables you to specify an XPath query that describes parts of the XML document that can be subjects of the algorithm. By default, the body is the subject.
- Key
- Select the key used for the encryption. The details of each key
vary.
- x509 key: This specifies the name and password of the x509 key and the keystore where it is located.
- Raw key: This specifies the name and the byte value of your SecretKey in hexadecimal.
- Encrypted key: This specifies a reference to an encrypted key that was previously defined in the security stack. Click Insert a new encrypted key to create a new encrypted key definition block.
- Encoding Algorithm Name
- Specify the encryption method to be used as defined in the XML Encryption Syntax and Processing specification.
- Key Encoding Algorithm
- Specify the standard algorithm for encoding the key as defined in the XML Encryption Syntax and Processing specification.
- Encrypted Key
- This block defines an encrypted key that can be used in an XML
signature or XML encryption block. The encrypted key block must be
before a block that uses the encrypted key.
- Actor / Role name
- Specify the name of the recipient of the algorithm header element, if required.
- Must understand
- Select whether it is mandatory that the algorithm header is processed by the recipient, if required. The recipient is either the Actor name or the server.
- Key name
- Specify the name of the encrypted key.
- Identifier type
- Select the type of key identifier to be used for the key. The
following key identifiers are available, as defined in the the Web
Service Security (WSS) specification X509 profile and OASIS WSS 1.1
specification:
- ISSUER_SERIAL
- BST_DIRECT_REFERENCE
- X509_KEY_IDENTIFIER
- THUMBPRINT_IDENTIFIER
- SKI_KEY_IDENTIFIER
- Key size
- Specify the size of the key in bits.
- Key encoding algorithm name
- Specify the algorithm to be used for encoding the key.
- Keystore
- Select a keystore or click Edit Security to define a new keystore or to manage the existing keystores.
- Name
- Select a key contained in the specified keystore.
- Password
- Type the password for the selected key name.
- Custom Security Algorithm
- If you want to use a Java™ class
as a custom security algorithm, then use this stack element to apply
the custom algorithm to the service.
- Java™ Project
- If you have not implemented a custom Java™ class, select Java Project, type a name for the new project, and click Generate to create a new Java™ class with the default structure for custom security implementations.
- Implementation class
- Specify the name of the class that implements the custom security algorithm. Click Browse Class to select an existing Java™ class from the workspace.
- Properties
- Use this table to send any specific properties and associated values to the custom security algorithm.