HTTP transport settings

To configure HTTP transport settings using the console, go to:

Servers | Application Servers | server_name | Web Container | HTTP Transports | host_name

Here are sample settings for six servers, running on two UNIX hosts, Chicago and Seattle:

   
ChicagoA and SeattleA 

Host   Port   SSL Enabled   
 *     9080     false   


ChicagoB and marsB 

Host   Port   SSL Enabled   
 *     9081     false   


ChicagoC and marsC 

Host   Port   SSL Enabled   
 *     9082     false   

Because the *A, *B, and *C servers are hosted on different ports, an application installed on one set of servers will run independently of the others, with the URLs resembling something like:

http://ChicagoA:9080/appname
http://ChicagoB:9081/appname
http://ChicagoC:9082/appname

 

Host

Host IP address to bind for transport.

If the appserver 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 WebSphere plug-in and appserver with SSL . The default is not to use SSL.

Data type Boolean
Default false

 

SSL

Specifies the SSL settings type for connections between the WebSphere plug-in and appserver. The options include one or more SSL settings defined in the Security Center; for example, DefaultSSLSet, ORBSSLSet, or LDAPSSLSettings.

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


See also:

  1. Administrative console buttons
  2. Administrative console page features
  3. Custom Properties
  4. SSL configuration repertoire settings
  5. SSL.

 

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.