Deploy the IBM® HTTP
Server plug-in and configure connection requests to forward connections
over Secure Sockets Layer (SSL) to the WebSphere® Application Server.
Before you begin
- If
the server is newly installed on a computer that has no previous versions
of the server, you can use the default values for the ports. To check
whether a port is already in use, use a utility like netstat.
For example: netstat -na -p tcp -o.
- If there are other applications listening to port 80,
shut down the applications before you install the IBM HTTP Server.
- Ensure that the following software is started:
- Review the planning worksheet for the configuration settings.
See Planning worksheet.
About this task
Configuring IBM HTTP Server is a three-stage process.
- Grant remote server administration rights to the IBM HTTP Server configuration to simplify web
server administration from the WebSphere administrative
console.
- Secure the connection between the IBM HTTP
Server and WebSphere Application
Server with a trusted SSL connection.
- Centralize the connection points for each web server.
The following example steps apply
to IBM HTTP Server Version 7.0.
For specific steps that apply to IBM HTTP
Server Version 8.5, search for Implementing a web server
plug-in in the IBM HTTP Server,
Version 8.5 product documentation.
Procedure
- Define the web server configuration for the WebSphere Application Server.
- If the IBM HTTP Server and WebSphere Application Server
are on the same computer:
- Log on to the WebSphere administrative
console, for example https://localhost:9043/ibm/console.
- In the navigation pane, click .
- Click New.
- Follow the instructions in the wizard to create a definition of
the web server.
Tip: To learn more about each field,
on the page, see the field descriptions in the Help pane.
For
guidance, consider the following notes:
- If the IBM HTTP Server and WebSphere Application Server
are not on the same computer, run the web server plug-in configuration
script.
- From <ihs_home>\Plugins\bin,
on the IBM HTTP Server host,
copy the configure<web_server_definition_name>.bat file.
For example: configurewebserver1.bat.
- On the application server, paste the configure<web_server_definition_name>.bat file
to the <was_home>\bin folder.
For example: C:\Program Files\IBM\WebSphere\AppServer\bin
- From a command prompt, on the application server, run the following
command.
configure<web_server_definition_name>.bat
-profileName <profile_name>
-user <was_admin_name>
-password <was_admin_password>
For
example:
configurewebserver1.bat -profileName AppSrv01 -user wasadmin -password p@ssw0rd
- Close the command prompt after the command completes with the
following line:
Configuration save is complete.
You successfully configured a web
server definition on the WebSphere administrative
console. For example: webserver1.
- In the WebSphere administrative
console, click .
Verify that the web server definition is displayed. For example: webserver1.
- Grant remote server
management rights to the WebSphere Application
Server administrator by supplying the IBM HTTP
Server administrator account.
- In the administrator console, click .
- Click the <Web_server_name>. For example: webserver1.
- In the Additional Properties section
on the Configuration tab, click Remote
Web Server Management.
- Enter the IBM HTTP
Server administration server authentication user ID and password. For example: ihsadmin.
- Clear the Use SSL check box.
- Click OK.
- In the Messages box, click Save.
- (Complete
this step only if the IBM HTTP
Server and WebSphere Application
Server are not on the same computer; or if you are using a load balancer.)
Set up the SSL certificates signed by the WebSphere Application Server certificate
authority.
Note: The certificate uses the IBM HTTP Server computer name as the Common Name
(CN). The purpose is to facilitate communication between the client
and the IBM HTTP Server.
- On the IBM Integrated
Solutions Console navigation pane, click .
- Select the certificate named default.
- Click Delete.
- Click .
- Specify default as the alias
for the certificate.
- In Key size, specify
the certificate key size. If the root CA for WebSphere Application Server is a 2048
bits certificate, you can specify a 2048 bits key size. The default
is 1024 bits.
Important: Do not select 2048 bits if you
did not re-create the root CA with a 2048 bits key size.
- In the Common Name field, you
can enter one of the following names:
- The fully qualified domain name of the computer where the IBM HTTP Server is installed. For
example: webserver1.example.com.
- The fully qualified host name of the load balancer if a load
balancer is used.
- Optional: Enter the remaining optional information.
- Click OK.
- In the Messages box,
click Save.
- If you have more than one IBM HTTP
Server, for each IBM HTTP Server,
repeat steps a to j.
The Personal Certificates section
displays the new certificate.
- Synchronize the WebSphere Application Server keystore with
the IBM HTTP Server keystore.
- On the IBM Integrated
Solutions Console navigation pane, click .
- Click the <Web server name>. For
example: webserver1.
- In the Additional Properties section
on the Configuration tab, click Plug-in
properties.
- Click Copy to Web Server key store directory.
- Click OK.
- In the Messages box, click Save.
Results
You defined a web server in the WebSphere Application Server configuration.
The web server routes requests received from client workstations to
the application server.