Configure transports
Overview
A transport is the request queue between a WebSphere Application Server plug-in for Web servers and a Web container in which the Web modules of an application reside. To define the characteristics of the connections between that plug-in and the Web container, specify:
- How the transport is to handle a set of connections. For example, specify the number of concurrent requests that is to be allowed.
- Whether to secure the connections with SSL.
- The Host and IP information for the transport participants.
- Create an HTTP transport.
- Ensure that virtual host aliases include port values for the new transport.
- Go to the HTTP Transports page and click New.
- On the settings page for an HTTP transport, specify values such as the transport's host name and port number, then click OK.
- Change the configuration for an existing transport.
- Ensure that virtual host aliases include port values for the transport your are changing.
- Go to the HTTP Transports page and click on the transport under Host whose configuration you want to change.
- On the settings page for an HTTP transport, which might have the page title DefaultSSLSettings, change the specified values as needed, then click OK.
- Custom properties page, add and set any custom properties you want to use.
- Regenerate the WebSphere plug-in for the Web server.
- Stop the Application Server and start it again.You must stop the Application Server and start it again before the configuration changes you made take affect.
What to do next
If the Web server is located on a machine remote from the Application Server, copy the plugin-cfg.xml file to the remote Web server and replace the file that is there. See "Manually configuring supported Web servers" in the information center for the base product for information about copying the plugin-cfg.xml and binary plug-in module to a remote Web server and configuring the Web server to use the files.
Transports
HTTP transport collection
HTTP transport settings
HTTP transport custom properties