IBM Support

How to Associate an IBM HTTP Server with an IBM WebSphere Application Server Profile on the IBM i OS

Question & Answer


Question

This document will address the question of how to associate an IBM HTTP Server with an IBM WebSphere Application Server (WAS) profile on the IBM i OS.

Answer

Pre-requisites


1) A currently supported version of the IBM WebSphere Application Server software product must already be installed and updated to a recent Fix Pack version. Refer to the following hyperlinks for the list of currently supported IBM WebSphere Application Server products at specific IBM i OS VRMs and how to install WAS v8.0 and later on the IBM i OS.
2) An IBM HTTP Server instance and IBM WebSphere Application Server Profile MUST already exist on your IBM i server. You will need to create one or both of them before proceeding with this document.  

Steps To Associate an IBM HTTP Server with an IBM WAS Profile on the IBM i OS

 
1) Open a web browser and go to the URL, http://<server>:2001/HTTPAdmin or https://<server>:2010/HTTPAdmin, to display the IBM Web Administration for i console web application.

If you are not prompted for a userID and password or receive an error in the browser, ensure the ADMIN jobs are started in the QHTTPSVR subsystem using the WRKACTJOB SBS(QHTTPSVR) CL command. If the ADMIN jobs are not started, execute the following CL command to start the ADMIN server:

STRTCPSVR *HTTP HTTPSVR(*ADMIN)

If you continue to experience issues accessing the IBM Web Administration for i console, please open a Service Request (PMR) with IBM here or call 1-800-IBM-SERV.
2) Click on the "Manage -> HTTP Servers" tabs in the top,left-hand corner of the IBM Web Administration for i GUI.
3) Select the IBM HTTP Server instance you wish to associate with your WAS Profile from the drop-down box next to "Server."
4) Click on the "WebSphere Application Server" link on the left-hand, vertical toolbar just above the "Tools" section.
5) You will then be presented with a screen to select the IBM WebSphere Application Server installation version and edition you would like to associate your IBM HTTP Server with. Select the radio button next to the WAS version and edition your WAS Profile was created under.
6) After selecting the radio button next to the WAS installation, you will be presented with an additional field to select the WAS Profile you wish to associate your IBM HTTP Server with. Select your WAS Profile from the drop-down list.
7) After selecting your WebSphere profile, additional options will be presented asking the following:

- Indicate which installed applications should be mapped to the selected Web server:
IBM Recommends this option be set to "All Applications".

- Start all WebSphere application server(s) for the associated WAS instance when this HTTP server is started :
IBM Recommends this option be set to "Yes". If this option is set to "Yes", you will be presented with a third option.

- Stop all WebSphere application server(s) for the associated WAS instance when this HTTP server is stopped :
IBM Recommends this option be set to "No" so your WebSphere application servers are not automatically stopped when you stop your HTTP Server.
8) After setting the additional options to the values you desire, click on the "OK" button at the bottom of the screen to begin the HTTP Server -> WAS Profile association process. The screen will refresh back to the main "Manage Apache server" screen when the association process has completed.
9) After the association process completes, you might need to change your WAS Profile's virtual host entries. To do this, click on Manage -> Application Servers and then select your WebSphere application server from the list.
10) Click on the "Manage Virtual Hosts" link under "Resource Configuration" on the left-hand, vertical menu.
11) Select the radio button next to the virtual host used by your application(s) and then click on the "Properties" button. By default, the "default_host" virtual host is used by deployed web applications.
12) Select the radio button next to the HTTP Server Port at the bottom of the list. Edit the "IP address or hostname" field and change the value to "*" (star character). Then, click the "Continue" button and then "OK" button to save your changes.

BEFORE:


AFTER:
13) NOTE:  Ensure your WebSphere application server is started.  If it is not, select the server under Manage -> Application Servers. Then, click on the green, , button to start both your HTTP Server and WebSphere Application server instances. Then, click on the "Start" button at the bottom of the page to confirm the start request. Finally, wait for the status of the servers to change to "Started".  You can then click the "Launch Administrative Console" link under Tools to launch the ISC web application.

In the IBM WebSphere Application Server Integrated Solutions Console, click the web server name under Servers -> Server Types -> Web Server. 
Click Plug-in properties under Additional Properties.
Click the Copy to Web server key store directory button under Repository copy of Web server plug-in files as shown below to copy the plugin-key.kdb and plugin-key.sth files to the profile_root/config/<webserver>/ directory.  This will enable TLS to initialize for the web server plugin.
image-20190612150506-1
14) Restart your IBM HTTP Server and WebSphere application server for the changes to take affect.

If your IBM HTTP Server and WebSphere Application Server are currently started....
Ensure your WebSphere application server is selected under Manage -> Application Servers. Then, click on the red, , button to stop both your HTTP Server and WebSphere Application server instances. Then, click on the "Stop" button at the bottom of the page to confirm the stop request. Finally, wait for the status of the servers to change to "Stopped".





To restart your IBM HTTP and WebSphere Application Servers....
Ensure your WebSphere application server is selected under Manage -> Application Servers. Then, click on the green, , button to start both your HTTP Server and WebSphere Application server instances. Then, click on the "Start" button at the bottom of the page to confirm the start request. Finally, wait for the status of the servers to change to "Started".
15) Once you have confirmed your IBM HTTP Server and WebSphere Application Server (WAS) are started, you are now ready to access your WAS web application(s) using your IBM HTTP Server port(s).

non-TLS: http://<server>:<httpPort>/<applicationURL>
TLS: https://<server>:<httpsPort>/<applicationURL>

If you experience issues accessing your WAS web application(s) using your IBM HTTP Server port(s), please open an IBM Support Case with IBM here or call 1-800-IBM-SERV.
16) Congratulations! You have successfully associated an IBM HTTP Server with an IBM WebSphere Application Server Profile using the IBM Web Administration for i Console.

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHUAA2","label":"WebSphere Application Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Document Information

More support for:
IBM i

Component:
WebSphere Application Server

Software version:
All Versions

Operating system(s):
IBM i

Document number:
667039

Modified date:
30 April 2025

UID

nas8N1021306

Manage My Notification Subscriptions

Page Feedback