Enableing SSL between a browser and the internal Web server
 Technote (troubleshooting)
 
Problem(Abstract)
How to enable Secure Sockets Layer (SSL) between a browser and the internal HTTP transport (Web server).
 
Cause
You do not need to use a separate Web server to allow HTTP requests to be routed to IBM® WebSphere® Application Server.

The internal HTTP transport allows HTTP requests to be routed to the
application server directly through a Web server plug-in.

Beginning with Version 5.0.2, HTTP transport functionality is a supported internal
Web server.

This document describes how to enable SSL between a browser client and the internal Web server (HTTP transport).

 
Resolving the problem
To enable SSL between the browser and the internal HTTP transport in
WebSphere Application Server V6, go here and follow steps 6, 9, and 10a.
Perform step 11 if client-side certification is required. You can ignore all other steps because there is no external web server.

To enable SSL between the browser and the internal HTTP transport in WebSphere Application Server V5.1, go here and follow steps 7 and 8. Perform step 9 if client-side certification is required. You can ignore all other steps because there is no external web server.

To enable SSL between the browser and the internal HTTP transport in WebSphere Application Server V5.0, go here and follow steps 7 and 8. Perform step 9 if client-side certification is required. You can ignore all other steps because there is no external web server.
 
Related information
The internal transport
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server
Operating system(s): Windows
Software version: 6.0.2
Software edition:
Reference #: 1234364
IBM Group: Software Group
Modified date: Apr 18, 2006