HTTPTransport policy and binding properties
Use the -attributes parameter for the setPolicyType and setBinding commands to specify additional configuration information for the HTTPTransport policy and policy set binding. Application and system policy sets can use the HTTPTransport policy and binding.
Use the following commands and parameters in the PolicySetManagement group of the AdminTask object to customize your policy set configuration.
- Use the -attributes parameter for the getPolicyType
and getBinding commands to view the properties for the policy and binding configuration. To get an attribute, pass the property name to the getPolicyType or getBinding command.
- Use the -attributes parameter for the setPolicyType and setBinding commands to add, update, or remove properties from your policy and binding configurations. To add or update an attribute, specify the property name and value. The setPolicyType and setBinding commands update the value if the attribute exists, or adds the attribute and value if the attribute does not exist. To remove an attribute, specify the value as an empty string (""). The -attributes parameter accepts a properties object.
If a property name or value supplied with the -attributes parameter is not valid, then the setPolicyType and setBinding commands fail with an exception. The property that is not valid is logged as an error or warning in the SystemOut.log file. However, the command exception might not contain the detailed information for the property that caused the exception. When the setPolicyType and setBinding commands fail, examine the SystemOut.log file for any error and warning messages that indicate that the input for the -attributes parameter contains one or multiple properties that are not valid.
This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
For transitioning users: In WAS v7 and later, the security model was enhanced to a domain-centric security model instead of a server-based security model. The configuration of the default global security (cell) level and default server level bindings has also changed in this version of the product. In the WAS v6.1 Feature Pack for Web Services, we can configure one set of default bindings for the cell and optionally configure one set of default bindings for each server. In Version 7.0 and later, we can configure one or more general service provider bindings and one or more general service client bindings. After we have configured general bindings, we can specify which of these bindings is the global default binding. We can also optionally specify general binding used as the default for an application server or a security domain. trns
To support a mixed-cell environment, WebSphere Application Server supports Version 7.0 and Version 6.1 bindings. General cell-level bindings are specific to Version 7.0 and later Application-specific bindings remain at the version that the application requires. When the user creates an application-specific binding, the application server determines the required binding version to use for application.
The following sections explain the policy and binding properties to configure:
HTTPTransport policy properties
The HTTPTransport policy set can be used for HTTPS, basic authorization, compression, and binary encoding transport methods.
Configure the HTTPTransport policy by specifying the following attributes with the setPolicyType command:
- protocolVersion
- Version of HTTP to use. The valid version values are HTTP/1.1 and HTTP/1.0.
- maintainSession
- Whether the HTTP session is enabled when a message is sent. The valid values are yes or no.
- chunkTransferEnc
- Whether to enable chunked transfer encoding. The valid values are yes or no.
- sendExpectHeader
- Whether to send an expect 100-request header. The valid values are yes or no.
- compressRequest:name
- Whether to compress the request. The valid values are gzip, x-gzip, deflate, or none.
- compressResponse:name
- Whether to compress the response. The valid values are gzip, x-gzip, deflate, or none.
- acceptRedirectionURL
- Whether to accept URL redirection automatically. The valid values are yes or no.
- messageResendOnce
- Specifies if a message can be sent more than once. The valid values are yes or no.
- connectTimeout
- Amount of time, in seconds, before a connection times out when sending a message. Specify an integer value that is greater than zero. If a value of zero or less is specified, the connectTimeout property is set to the default value of 180 seconds. No maximum value is set for this property.
- writeTimeout
- Amount of time, in seconds, before the write time out occurs. Specify an integer value. Specify an integer value that is greater than zero. If a value of zero or less is specified, the connectTimeout property is set to the default value of 300 seconds. No maximum value is set for this property.
- readTimeout
- Amount of time, in seconds, before the read time out occurs. Specify an integer value. Specify an integer value that is greater than zero. If a value of zero or less is specified, the connectTimeout property is set to the default value of 300 seconds. No maximum value is set for this property.
- persistConnection
- Whether to use a persistent connection when sending messages. Valid values are yes or no.
The following setPolicyType example command sets values for each HTTPTransport binding property:
AdminTask.setPolicyType('[-policySet "WSHTTPS custom" -policyType HTTPTransport -attributes "[[protocolVersion HTTP/1.1]
[sessionEnable yes][chunkTransferEnc yes][sendExpectHeader yes]
[compressRequest:name gzip][compressResponse:name
gzip][acceptRedirectionURL yes][messageResendOnce no][connectTimeout 300][writeTimeout 300]
[readTimeout 300][persistConnection yes]]"]')
HTTPTransport binding properties
Configure the HTTPTransport binding by specifying the following attributes with the setBinding command:
- outAsyncResponseBasicAuth:userid
- User name for basic authentication of outbound asynchronous responses.
- outAsyncResponseBasicAuth:password
- Password for basic authentication of outbound asynchronous responses.
- outAsyncResponseProxy:userid
- User name for the outbound asynchronous service responses proxy.
- outAsyncResponseProxy:password
- Password for the outbound asynchronous service responses proxy.
- outAsyncResponseProxy:port
- Port number for the outbound asynchronous service responses proxy.
- outAsyncResponseProxy:host
- Host name for the outbound asynchronous service responses proxy.
- outRequestBasicAuth:userid
- User name or basic authentication of outbound service requests.
- outRequestBasicAuth:password
- Password for basic authentication of outbound service requests.
- outRequestProxy:userid
- User name for the outbound service request proxy.
- outRequestProxy:password
- Password for the outbound service request proxy.
- outRequestProxy:port
- Port number for the outbound service request proxy.
- outRequestProxy:host
- Host name for the outbound service request proxy.
The following setBinding example command sets values for each HTTPTransport binding property:
AdminTask.setBinding('[-bindingLocation "" -bindingName generalCellWideBind1 -policyType HTTPTransport -attributes "[[outAsyncResponseBasicAuth:userid myID][outAsyncResponseBasicAuth:password myPW][outAsyncResponseProxy:host hostname]
[outAsyncResponseProxy:port 9060][outAsyncResponseProxy:userid myID]
[outAsyncResponseProxy:password myPW]
[outRequestBasicAuth:userid myID][outRequestBasicAuth:password myPW]
[outRequestProxy:userid myID]
[outRequestProxy:password myPW][outRequestProxy:port 9061][outRequestProxy:host
hostname]]"]')
Related concepts
Related tasks