6 Configuring the IBM HTTP Server

This section includes general instructions for configuring ports on an IBM i IBM HTTP Server for WebSphere 7.0 and 8.5.x, as well as setting up the correct virtual host. Complete these steps only once, then all subsequent installations of JD Edwards HTML Web Server will use the same webserver name that you created using the procedures in this section.

This section describes these tasks:

• Configuring the IBM HTTP Server

• Starting the IBM HTTP Server for the IBM i Instance

• Testing the WebSphere Application Server

• Stopping the IBM HTTP Server for the IBM i Instance

6.1 Configuring the IBM HTTP Server

To configure the new HTTP Server instance:

1. Open a browser and enter this URL to start the IBM HTTP Server Web Administration console:

   http://server_name:2001/HTTPAdmin

2. Click the Manage tab.

3. Select the HTTP Server you created in Creating a New HTTP Server Instance, for example HTTPSVR.

4. In the left pane, scroll down and select Tools > Edit Configuration File.

   The configuration file includes a port listen command for the port number you specified when you created the HTTP Server port in Creating a New HTTP Server Instance. This port number might not be the same as the port you specified when you installed the HTML Server. For example, if you selected port 81 as the HTTP Server port, the command in the configuration file should be:

   Listen *:81

5. When an instance is installed with JD Edwards EnterpriseOne Server Manager an entry is added into the httpd.conf file to include the contents of the scf_<INSTANCE_NAME>.conf file. You can verify this by checking for the following line in the httpd.conf file (usually at the end of the file):

   Include /www/HTTPSVR81/conf/scf_<INSTANCE_NAME>.conf

   Where <INSTANCE_NAME> is the name of the created JD Edwards HTML Web Server (HTML Server) instance (for example, EA_JS_101 and so on).

   Refer to the sample screenshot below showing the include directive in the httpd.conf file.

   
   

6. Click the Apply button.

7. Click the OK button.

8. In the Configuration file, add this directive to the end of the file:

   <Directory "/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/default/
   installedApps/DENPBAS2/EA_JS_202.ear/webclient.war/WEB_INF">
   

   This directive allows access to the webclient.war directory.

9. To secure your configuration file, deny access to the WEB-INF directory by adding following to the configuration file, after the above directive.

   <Directory "/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/default/
   installedApps/DENPBAS2/EA_JS_202.ear/webclient.war/WEB_INF">
   Order Deny,Allow
   Deny from All
   </Directory>
   

10. Click the Apply button.

11. Click the OK button.

    Tip:

    You can click on Display configuration file to look and review the contents of the configuration file. An example screen shot is shown below.

    Click the Close button.

    
    

12. Click the Close button.

6.2 Starting the IBM HTTP Server for the IBM i Instance

The IBM HTTP Server for IBM i runs in the QHTTPSVR subsystem, and each HTTP server instance starts multiple jobs. The WebSphere Application Server code that plugs into IBM HTTP Server for IBM i runs in the HTTP server job that communicates with the administrative server and one or more application servers.

There are two ways to start the IBM HTTP Server for IBM i instance:

• Starting the IBM HTTP Server for IBM i Instance from the Command Line

• Starting the IBM HTTP Server for IBM i Instance from the IBM i Configuration and Administration Forms

6.2.1 Starting the IBM HTTP Server for IBM i Instance from the Command Line

To start the IBM HTTP Server for IBM i Instance from the command line:

1. On the IBM i command line, enter this command:

   STRTCPSVR SERVER(*HTTP) HTTPSVR(MYINSTANCE)

   where MYINSTANCE is the name of your HTTP server instance. The syntax of this name should correspond with the recommended naming conventions specified in this guide. For example:

   HTTPSVR

2. If you change your HTTP server instance configuration, stop and then start your HTTP server instance.

6.2.2 Starting the IBM HTTP Server for IBM i Instance from the IBM i Configuration and Administration Forms

The Configuration and Administration forms also allow you the option of restarting your HTTP server instance. When restarting, the HTTP server will recognize all configuration changes except for changes to the Basic and Security configuration forms.

1. Start your JavaScript-enabled browser.

2. Enter this URL in the URL location or address window:

   http://<server_name>:2001/HTTPAdmin

   where <server_name> is the host name of your IBM i system.

3. Press Enter to navigate to the URL.

   The IBM i Tasks page appears.

4. Click the link for IBM HTTP Server for IBM i.

   The IBM HTTP Server for IBM i page appears.

5. Click the Manage tab.

   The Manage page appears.

6. In the right pane, click Manage All Servers.

7. Click the radio button to the left of the server you created.

8. Click the Start button.

   This message appears in the Message box at the bottom of the screen:

   HTTP server starting.

   A sample screen shot is provided below.

   
   

6.3 Testing the WebSphere Application Server

You can test WebSphere by accessing a default application, but a default application requires that Port 80 be configured with WebSphere. You can configure Port 80 with WebSphere using the previous tasks in this chapter.

To test the WebSphere Application Server:

1. Ensure that the IBM HTTP Server is started (as explained in the above section: Starting the IBM HTTP Server for the IBM i Instance).

2. If it is not already started, start WebSphere default server (server1) using the instructions in the chapter: Starting WebSphere.

3. Access the default snoop servlet using this URL:

   http://MachineName/snoop

   where MachineName is the name of the server where you installed the HTTP Server.

   Tip:

   If your Web Server is not on the same machine as WebSphere, you might need to copy the plug-in configuration file from the WebSphere machine to the Web Server machine.

6.4 Stopping the IBM HTTP Server for the IBM i Instance

If you change your HTTP server instance configuration, stop and then start your HTTP server instance.

There are two ways to stop the IBM HTTP Server for the IBM i instance:

• Stopping the IBM HTTP Server for IBM i Instance from the Command Line

• Stopping the IBM HTTP Server for IBM i Instance from the IBM i Configuration and Administration Forms

6.4.1 Stopping the IBM HTTP Server for IBM i Instance from the Command Line

To stop the IBM HTTP Server for IBM i instance from the command line:

1. Enter this command on the IBM i command line:

   ENDTCPSVR SERVER(*HTTP) HTTPSVR(MYINSTANCE)

   where MYINSTANCE is the of name your HTTP server instance.

6.4.2 Stopping the IBM HTTP Server for IBM i Instance from the IBM i Configuration and Administration Forms

To stop the IBM HTTP Server for IBM i instance from the IBM i configuration and administration forms:

1. Start your JavaScript-enabled browser.

2. Enter this command in the URL location or address window:

   http://<server_name>:2001/HTTPAdmin

   where <server_name> is the host name of your IBM i system.

3. Press the Enter button.

   You are prompted for an IBM i user ID and password; your IBM i user ID must have *ALLOBJ authority.

   The IBM i Tasks page appears.

4. Click IBM HTTP Server for IBM i.

   The IBM HTTP Server for IBM i page appears.

5. In the top pane, click Administration.

   The Administration page appears.

6. Click Manage HTTP Servers in the left-hand frame.

7. Click the radio button to the left of the server you created.

8. Click the Stop button.

   This message appears in the Message box at the bottom of the screen:

   HTTP server ended.

   A sample screen shot is shown below.