Install and configure the Web Server Plug-ins to allow the application server to communicate with the web server.
The remote web server configuration is recommended for production environments.
The remote installation installs the web server plug-in on the web server machine when the application server is on a separate machine, such as shown in the following graphic:
Step | Machine | Task |
---|---|---|
1 | A | Install your WebSphere® Application Server product. |
2 | A | Create an application server profile. |
3 | B | If you plan to run IBM® HTTP
Server on IBM i, it
is already installed as product 5761-DG1 or 5770-DG1. You can also
use a Domino® Web Server on IBM i. Refer to the Domino documentation for installation
instructions. For either scenario, you must install the Web Server Plug-ins component of the WebSphere Application Server product. |
4 | B | Run the manageprofiles Qshell command
to create an http profile. For example, run this command from Qshell:
The myHttpProfile variable is the name of the profile. |
5 | B | Configure the IBM HTTP Server with your http profile myHttpProfile. As a result of the above, an IBM i qshell script called configureIHS_MyWebServer will be created in the myHttpProfile_profile_root/config/IHS_myWebServer directory on Machine B. For the default WebSphere Application Server install, themyHttpProfile_profile_root of the profile myHttpProfile is /QIBM/UserData/WebSphere/AppServer/V61/Base/profiles/myHttpProfile. Note: In
the remainder of this example, webServerName refers to IHS_myWebServer.
If you choose to configure a DOMINO web server as listed below, then
webServerName refers to DOMSRV01.
The following steps apply to DOMINO web servers only:
|
6 | A | Copy the configurewebServerName script from Machine B to Machine A. The script is found in the myHttpProfile_profile_root/config/webServerName directory described above |
7 | A | Place the file you copied from the previous step into the profile_root/bin directory on Machine A, where profile_root is the directory where your application server profile is located. |
8 | A | Start the application server and then run the
script that you copied in the previous step. For example,
run these commands from Qshell:
Note: wasAdminUserId and wasAdminPassword are
optional and only needed when the application server of myProfile is
running in secure mode.
|
9 | A | If you use IBM HTTP
Server on IBM i, verify
that the application server is running. Open the administrative console
(ISC) and do the following:
|
10 | A | Configure a virtual host alias for the web server machine (B) and web server port of MyWebServer. |
11 | A | Stop and restart your application server. |
12 | A | In the administrative console (ISC) do the following:
|
13 | B | If you use IBM HTTP
Server on IBM i, start
the web server. Open the administrative console (ISC) and do the following:
|
14 | B | Run the Snoop servlet. Access the following
URL in your browser:
If you get an error, retrace your steps. Add a virtual host to Machine A before restarting the application server on Machine A. |
Regeneration of the plugin-cfg.xml file
The web server plug-in configuration service regenerates the plugin-cfg.xml file automatically.
Propagation of the plugin-cfg.xml file
The plugin-cfg.xml file can
be propagated manually. Manual propagation of the plugin-cfg.xml file
is required for DOMINO web servers. Copy the plugin-cfg.xml file
from the application server machine to the myHttpProfile_profile_root/config/IHS_MyWebServer directory
on the web server Machine B. The plugin-cfg.xml file
is generated in the directory named profile_root/config/cells/cell_name/nodes/host_name_of_machine_B-node/servers/IHS_myWebServer on
the application server Machine A.
The local web server configuration is recommended for a development or test environment.
A local installation includes the web server plug-in, the web server, and the Application Server on the same machine:
Step | Machine | Task |
---|---|---|
1 | A | Install your WebSphere Application Server product. |
2 | A | Create an application server profile. |
3 | A | IBM HTTP Server on IBM i is already installed as product 5761-DG1 or 5770-DG1. Alternatively, you can also run Domino Web Server on IBM i. Refer to the Domino documentation for installation instructions. |
4 | A | Configure the IBM HTTP
Server with your WebSphere Application
Server profile. The following steps apply to DOMINO web servers
only. For these steps, assume your web server's name is MyWebServer.
|
5 | A | Stop and restart the application server. |
6 | A | If you use IBM HTTP
Server on IBM i, open
the administrative console (ISC) do the following:
|
7 | A | In the administrative console (ISC) do the following:
|
8 | A | If you use IBM HTTP
Server on IBM i, start
the web server. Open the administrative console (ISC) and do the following:
|
9 | A | Run the Snoop servlet. Access the following
URL in your browser:
If you get an error, retrace your steps. Add a virtual host to Machine A before restarting the application server on Machine A. |
Regeneration of the plugin-cfg.xml file
The web server plug-in configuration service regenerates the plugin-cfg.xml file automatically.
Propagation of the plugin-cfg.xml file
The local file does not require propagation.
See Installing and configuring web server plug-ins for information about
other installation scenarios for installing Web Server Plug-ins.