JKL Toy Company creates an HTTP Server (powered by Apache)

 

This scenario discusses how to create an HTTP Server for i5/OS (powered by Apache).

Information for this topic supports the latest PTF levels for HTTP Server for iSeries . IBM recommends that you install the latest PTFs to upgrade to the latest level of the HTTP Server for i5/OS. Some of the topics documented here are not available prior to this update. See IBM Service for more information.

 

Scenario

The JKL Toy Company (a fictitious company) wants to run a Web site with their iSeries™. The examples used in this scenario show the Create New HTTP Server wizard being used to create an HTTP Server (powered by Apache) instance called JKLTEST which will use all IP addresses, port 1975 on an iSeries designated JKL_SERVER.

 

Prerequisites

 

Start the IBM Web Administration for i5/OS interface

Enter your Webmaster user profile username and password when prompted.

  1. Start a Web browser.

  2. Enter http://[iSeries_hostname]:2001 in the location or URL field .

    Example: http://jkl_server:2001

    If you have changed your port number for the Web Administration for i5/OS interface, replace port 2001 with your port number.

  3. Click IBM® HTTP Server for iSeries.

If the Web Administration for i5/OS interface does not start, see Installing and testing the HTTP Server.

 

Create your HTTP Server (powered by Apache)

The Web Administration for i5/OS interface allows you to create, set up, and manage multiple servers.

  1. Click the Setup tab.

  2. Expand Common Tasks and Wizards.

  3. Click Create HTTP Server.

  4. Enter a descriptive, unique name in the Server name field.

    Example: JKLTEST

  5. Click Next.

  6. Accept the default value.

    Example: /www/jkltest

  7. Click Next.

  8. Accept the default value.

    Example: /www/jkltest/htdocs

  9. Click Next.

  10. Accept the default values or replace with your own unique IP address and port.

    Example: IP address All Addresses

    Example: Port 1975

  11. Click Next.

  12. Optional: Select Yes to use an access log.

    Select No if you do not want to create an access log at this time. By default, the log will be created for you.

  13. Click Next.

  14. Accept the default values to specify the length of time to keep the log files or update with your preferences.

  15. Click Next.

  16. Review the displayed information. If any information is incorrect, click Back and correct it.

  17. Click Finish to create your new HTTP Server (powered by Apache).

If the wizard fails and you receive an error message, check your Webmaster user profile authorities.

 

Restart your HTTP Server (powered by Apache)

Select one of the following methods below:

Manage one server

  1. Click the Manage tab.

  2. Click the HTTP Servers subtab.

  3. Select your HTTP Server from the Server list.

  4. Click the Stop icon if the server is running.

  5. Click the Start icon.

Manage all servers

  1. Click the Manage tab.

  2. Click the HTTP Servers subtab.

  3. Select All Servers from the Server list.

  4. Click the All HTTP Servers tab.

  5. Select your HTTP Server name in the table.

    Example: JKLTEST

  6. Click Stop if the server is running.

  7. Click Start.

If your HTTP Server (powered by Apache) does not start, see Troubleshooting.

 

Test your HTTP Server (powered by Apache)

  1. Open a new Web browser.

  2. Enter http://[iSeries_hostname]:[port] in the location or URL field .

    Example: http://jkl_server:1975

Your new HTTP Server (powered by Apache) will display a generic HTML file provided by the Web Administration for i5/OS interface.

 

View your HTTP Server (powered by Apache) configuration

Your configuration will look similar if you used the given example in this and previous examples.

  1. Click the Manage tab.

  2. Click the HTTP Servers subtab.

  3. Select your HTTP Server (powered by Apache) from the Server list.

    Example: JKLTEST

  4. Expand Tools.

  5. Click Display Configuration File. 
Listen *:1975
DocumentRoot /www/jkltest/htdocs ServerRoot /www/jkltest Options -ExecCGI -FollowSymLinks -SymLinksIfOwnerMatch -Includes -IncludesNoExec -Indexes -MultiViews LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%{Cookie}n \"%r\" %t" cookie LogFormat "%{User-agent}i" agent LogFormat "%{Referer}i -> %U" referer LogFormat "%h %l %u %t \"%r\" %>s %b" common CustomLog logs/access_log combined SetEnvIf "User-Agent" "Mozilla/2" nokeepalive SetEnvIf "User-Agent" "JDK/1\.0" force-response-1.0
SetEnvIf "User-Agent" "Java/1\.0" force-response-1.0
SetEnvIf "User-Agent" "RealPlayer 4\.0" force-response-1.0
SetEnvIf "User-Agent" "MSIE 4\.0b2;" nokeepalive SetEnvIf "User-Agent" "MSIE 4\.0b2;" force-response-1.0
<Directory />
	Order Deny,Allow 	Deny From all </Directory>
<Directory /www/jkltest/htdocs>
	Order Allow,Deny 	Allow From all </Directory>

 

Parent topic:

Scenarios for HTTP Server