HTTP transport custom properties

You can use the administrative console to set custom properties for an HTTP transport. The HTTP transport custom properties administrative console page only appears if you have an HTTP transport defined for your system.

Important: You can use HTTP transports only on a V5.1 node in a mixed WebSphere Application Server environment. This panel shows if you are using nodes from Version 5.1 and have the script compatibility mode enabled. You must use HTTP transport channels instead of HTTP transports to handle your HTTP requests on all of your other nodes. See HTTP transport channel custom properties for a description of the custom properties that you can specify for an HTTP transport channel.

The use of IPv6 (Internet Protocol Version 6) and WS-AT (Web Services Atomic Transactions) are not supported on HTTP transports; they are only supported on HTTP transport channel chains.

If you are using HTTP transports, you can set the following custom properties on either the Web Container or HTTP Transport Custom Properties page on the administrative console. When you set custom properties on the Web container Custom Properties page, all transports inherit the properties. Setting the same properties on a transport overrides similar settings for a Web container. For more information, see the Web container custom properties documentation.

To specify custom properties for a specific transport on the HTTP Transport, complete the following steps through the administrative console unless otherwise indicated:

  1. Click Servers > Application Servers > server_name
  2. Under Container Settings, expand Web Container Settings and click Web Container.
  3. Under Additional Properties, click Web container transport chains.
  4. Click the name of the Web transport and then the name of the transport channel for which you want to set the custom property.
  5. Click Custom properties > New to add a new custom property.
  6. On the settings page, enter the property you want to configure in the Name field and the value you want to set it to in the Value field.
  7. Click Apply or OK.
  8. Click Save on the console task bar to save your configuration changes.
  9. Restart the server.

Following is a list of custom properties provided with the Application Server. These properties are not shown on the settings page for an HTTP transport.

ConnectionIOTimeOut

Use the ConnectionIOTimeOut property to specify how long the J2EE server waits for an I/O operation to complete. Set this variable for each of the HTTP transport definitions on the server. You will need to set this variable for both SSL transport and non-SSL transport. Specifying a value of zero disables the time out function.

Data type Integer
Default

120 seconds for the z/OS platform

ConnectionKeepAliveTimeout

Use the ConnectionKeepAliveTimeout property to specify the maximum number of seconds to wait for the next request on a keep alive connection.

Data type Integer
Default

30 seconds for the z/OS platform

ConnectionResponseTimeout

Use the ConnectionResponseTimeout property to set the maximum amount of time, in seconds, that the server will wait for an application component to respond to an HTTP request. Set this variable for each of the HTTP transport definitions on the server. You will need to set this variable for both SSL transport and non-SSL transport. If the response is not received within the specified length of time, the servant (region) might fail with ABEND EC3 and RSN=04130007. Setting this timer prevents client applications from waiting for a response from an application component that might be deadlocked, looping, or encountering other processing problems that cause the application component to hang.

[Updated in August 2012] To set this property in the administrative console, click Servers > Application Servers > server_name , and then under Web Container Settings, click Web container transport chains > chain_name > HTTP Inbound Channel. [Updated in August 2012]

aug2012

This property can be set for both HTTP transports and HTTP transport channels.

Use the server custom properties protocol_http_timeout_output_recovery and protocol_https_timeout_output_recovery to indicate the recovery action that you want taken on timeouts for requests received over the HTTP and HTTPS transports.

Data type Integer
Default 300 seconds

MaxKeepAliveRequests

Use the MaxKeepAliveRequests property to specify the maximum number of requests which can be processed on a single keep alive connection. This parameter can help prevent denial of service attacks when a client tries to hold on to a keep-alive connection. The Web server plug-in keeps connections open to the application server as long as it can, providing optimum performance.

On the z/OS platform, when this property is set to 0 (zero), the connection is closed after every request.

Data type Integer
Default

50 requests for the z/OS platform

MutualAuthCBindCheck

This property is only valid on the z/OS platform. Use the MutualAuthCBindCheck property to specify whether or not a client certificate should be resolved to a SAF principal. If this property is set to true, all SSL connections from a browser must have a client certificate, and the user ID associated with that client certificate must have RACF CONTROL authority for CB.BIND.servername. If these conditions are not met, the connection will be closed. Issue the following RACF command to give the user ID associated with that client certificate RACF CONTROL authority:

PERMIT CB.BIND.<optional SAF profile prefix>.clustername CLASS(CBIND) ID(clientCertUserid) ACCESS(CONTROL)
Data type String
Value true or false
Default false
Important: If you set MutualAuthCBindCheck as a HTTP Transport Custom Property, it does not come into effect for the transport channels. To have MutualAuthCBindCheck come into effect for the transport channels, you have to define it as a Web container custom property. See Web container custom properties for information on defining MutualAuthCBindCheck as a Web container custom property.

RemoveServerHeader

Use this property to specify whether an existing server header is removed before a response message is sent. If this property is set to true, the value specified for the ServerHeaderValue property is ignored.

Data type String
Value true or false
Default false
Attention: This custom property takes effect on the Web container level only. You cannot set it on the transport level. To set this custom property, see Modifying the default Web container configuration.

ResponseBufferSize

This property is used to specify, in bytes, the default size of the initial buffer allocation for the response buffer. When the buffer fills up, a flush for this buffer space will automatically occur. If a value is not specified for this property, the default response buffer size of 32K bytes is used.

The setBufferSize() API method can be used to override the value specified for this custom property at the individual servlet level.

Data type Integer
Default 32000 bytes

ServerHeader

This property is only valid for the z/OS platform. Use the ServerHeader property to suppress the server HTTP header (Server:) in responses. When the server header custom property is not specified, the default is equal to a setting of true and the server header is included in the HTTP response. Set this property to false if you want to prevent the inclusion of the server header.

Data type String
Value true or false
Default true

ServerHeaderValue

Use this property to specify a server header this is added to outgoing response messages if server header is not already provided. This property is ignored if the RemoveServerHeader property is set to true.

Data type string
Default WebSphere Application Server/x.x

x.x is the version of WebSphere Application Server that you are using.

Attention: This custom property takes effect on the Web container level only. You cannot set it on the transport level. To set this custom property, see Modifying the default Web container configuration.

SoLingerValue

Use this property to specify, in seconds, the amount, that the socket close operation waits for data contained in the TCP/IP send buffer to be sent. This property is ignored if the UseSoLinger property is set to false.

Data type Integer
Default 20 seconds

TcpNoDelay

Use this property to set the socket TCP_NODELAY option which enables and disables the use of the TCP Nagle algorithm for connections received on this transport. When this property is set to true, use of the Nagle algorithm is disabled.

Data type String
Value true or false
Default true

Trusted

Use the Trusted property to indicate that the application server can use the private headers that the Web server plug-in adds to requests.

Data type String
Value true or false
Default false
Important: This property must be set to false for Secure Sockets Layer (SSL) client certificate authentication to work.

UseSoLinger

Use this property to set the socket SO_LINGER option. This property configures whether the socket close operation waits until all of the data contained in the TCP/IP send buffer is sent before closing a connection. If this property is set to true, and the time expires before the all of the content of the send buffer sent, any data remaining in the send buffer is lost.

The SoLingerValue property is ignored if this property is set to false.

Data type String
Value true or false
Default true



Related tasks
Modifying the default Web container configuration
Tuning the application serving environment
Related reference
Administrative console page features
HTTP transport settings
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=xrun_transport
File name: xrun_transport.html