You can create an HTTP transport configuration that describes
the transport settings for a service call. Transport and security
settings can be associated with any service call.
Before you begin
If you are using Secure Sockets Layer (SSL) authentication,
ensure that you have valid key files in your workspace.
If you
are using SOAP security, ensure that you have configured the environment
with the correct libraries and configuration files.
About this task
To create an HTTP transport configuration:
Procedure
- Click the Generic service client
toolbar button to open the generic service client and click the Transport tab. This opens the Transport Configurations page.
- On the Transport Configurations page,
click Create an HTTP configuration (
) to create a new HTTP transport
configuration.
- Type a Name for the new transport
configuration.
- Specify the following options for the HTTP transport:
- Keep alive
- Select this option to keep the connection open after the request.
- SSL certificate
- Select this option to use an SSL configuration. Click Open
SSL Editor to create an SSL configuration or select an
existing configuration.
- Server authentication
- In this section, specify the type of authentication that is required
to access the service. Select None if no authentication
is required.
- Basic authentication
- Select this option to specify the User Name and Password that
are used for basic authentication.
- NTLM authentication
- Select this option to use the Microsoft® NT
LAN Manager (NTLM) authentication protocol. NTLM uses challenge-response
authentication. This view lists what is negotiated (supported by the
client and requested of the server) and what is authenticated (the
client reply to the challenge from the server).
- Kerberos authentication
- Select this option to use the Kerberos authentication protocol
between the client and server.
- Configure proxy
- If the HTTP connection needs to go through a proxy server or a
corporate firewall, specify the Address and Port of
the proxy server. If the proxy requires authentication, select Basic
proxy authentication.
- Proxy authentication
- In this section, specify the type of authentication that is required
to access the proxy. Select None if no authentication
is required.
- Basic proxy authentication
- Select this option to specify the User Name and Password that
are used for basic authentication.
- NTLM proxy authentication
- Select this option to use the Microsoft NT
LAN Manager (NTLM) authentication protocol. NTLM uses challenge-response
authentication. This view lists what is negotiated (supported by the
client and requested of the server) and what is authenticated (the
client reply to the challenge from the server).
- Custom class
- Select this option if the communication protocol requires complex,
low-level processing with a custom Java™ code
to transform incoming or outgoing messages. Click Browse to
select a Java class that uses
the corresponding API. See Extending Rational® Performance Tester for
more information about using the custom code API.
See Creating an SSL configuration for more
information about SSL authentication.
- Click OK to create the new configuration.
What to do next
Once created, you can use your new configuration with any
service call that uses the HTTP transport protocol. You can use the
Configurations list
in the generic service client to edit existing configurations or to
create duplicate configurations.