Creating an HTTP transport configuration

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

  1. Click the Generic service client Open the generic service client toolbar button to open the generic service client and click the Transport tab. This opens the Transport Configurations page.
  2. On the Transport Configurations page, click Create an HTTP configuration (Create an HTTP configuration) to create a new HTTP transport configuration.
  3. Type a Name for the new transport configuration.
  4. Specify the following options for the HTTP transport:
    HTTP/2
    Note: Testing HTTP/2 service is in the Beta mode. For more information, see Preparing to record a HTTP/2 service.
    To test a service that uses the HTTP/2 protocol, select the Activate check box. This check box is automatically selected when you record a service by using a browser. If you use the Generic Service Client component to create a HTTP/2 test, you have to manually select the check box.
    HTTP/2 client connection timeout
    Specifies the time limit for the HTTP/2 client to connect to the HTTP/2 server.
    Time out for the HTTP/2 session creations
    Specifies the time limit to create the HTTP/2 session. This time starts after the connection is established.
    Enable HTTP/2 Push
    The Push functionality of HTTP/2 automatically identifies and passes the related objects or requests to the client when a request is sent to the server. Clear the check box to not use the functionality.
    Initial session window
    Specifies the buffer size on the sessions.
    Initial stream window
    Specifies the window size for buffer on each stream after the connection is established.
    HTTP/2 Client Input Buffer Size
    Specifies the buffer size that is used to read the network traffic.
    Maximum Quantity of Messages that can be queued
    Specifies the maximum number of messages that can be queued for the HTTP/2 client on a thread.
    Maximum Quantity of HTTP/2 thread pool
    Specifies the maximum number of thread pools that will be used by the HTTP/2 client to distribute the workload.
    Minimum Quantity of HTTP/2 thread pool
    Specifies the minimum number of thread pools that will be used by the HTTP/2 client to distribute the workload.
    HTTP/2 client bytebuffer pool size
    Specifies the buffer size to receive the unciphered values.
    Server Name Indication
    Note: Not applicable for HTTP/2.
    Clear this check box if you do not want to connect to the host computer by using the Server Name Indication protocol. If the host computer is already configured with Server Name Indication protocol, you should keep this check box selected.
    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
    Note: Not applicable for HTTP/2.
    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
    Note: Not applicable for HTTP/2.
    Select this option to use the Kerberos authentication protocol between the client and server.
    Connect through proxy server
    Note: Not applicable for HTTP/2.
    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
    Note: Not applicable for HTTP/2.
    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.
  5. 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.
Feedback