HTTP transport settings

 

+

Search Tips   |   Advanced Search

 

 

Overview

Use this page to view and configure an HTTP transport. The name of the page might be that of an SSL setting such as DefaultSSLSettings.

On a distributed platform, if, when migrating from V5, you indicate that you want to continue using an HTTP transport to handle your HTTP requests, your V5 transports are migrated for you. If you are not migrating from WAS V5, set up an HTTP transport channel to handle your HTTP requests.

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

To view the HTTP Transport panel on the administrative console, click...

Servers | Application Servers | servername | Web Container Settings | Web Container | HTTP Transports | host_name

 

Configuration tab

Host

Specifies the host IP address to bind for transport.

If the application server is on a local machine, the host name might be localhost.

Data type String

Port

Specifies the port to bind for transport. Specify a port number between 1 and 65535. The port number must be unique for each application server on a given machine.

Data type Integer
Range 1 to 65535

SSL Enabled

Specifies whether to protect connections between the WAS plug-in and application server with Secure Sockets Layer (SSL). The default is not to use SSL.

Data type Boolean
Default false

SSL

Specifies the SSL settings type for connections between the WAS plug-in and application server. The options include one or more SSL settings defined in the Security Center; for example, DefaultSSLSettings, ORBSSLSettings, or LDAPSSLSettings.

Data type String
Default An SSL setting defined in the Security Center


 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.