You can create an HTTP transport configuration that describes
the transport settings for a service request. Transport and security
settings can be associated with any service request.
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.
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:
- HTTP/2
- To test a service that uses HTTP/2 protocol, select this check box.
- Use HTTP Keep Alive
- Select this option to keep the HTTP connection open after the
request. This option is not available if you are using IBM® Rational® AppScan®.
- Use SSL
- Select this option to use an SSL configuration. Click Configure
SSL to create an SSL configuration or select an existing
configuration.
- Platform Authentication
- In this section, specify the type of authentication that is required
to access the service. Select None if no authentication
is required.
- Basic HTTP 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.
- Connect through proxy server
- 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 either Basic
proxy authentication or NTLM 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. This option is not available in IBM Security AppScan.
See Creating SSL configurations 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 request 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.