How to Duplicate an HTTP Server Instance on Another System

Troubleshooting

Problem

This document includes a procedure that will yield an HTTP server identical to the first, that will be integrated to the point where it will be known and manageable using the Web administrative tools on the system.

Resolving The Problem

The procedure below addresses the two areas common to HTTP servers. The instructions for moving/re-creating an HTTP server instance follow:

Create the member for your HTTP server in the following file:

WRKMBRPDM FILE(QUSRSYS/QATMHINSTC)

Press Enter.

Enter Option 3 next to APACHEDFT, and press F4 to prompt the COPY command.

Change the To member (TOMBR) or label parameter to whatever you would like to name your new HTTP server. This will be defined as <serverName> for use throughout this document.

Note: The name of the HTTP server cannot exceed 10 characters.

Press Enter to accept the changes.

Once the member is created, do the following:

a.	Type 18 next to the member name to edit it in DFU, and press Enter.
b.	Page down once.
c.	Change the Instance Data value from the following: -apache -d /www/apachedft -f conf/httpd.conf -AutoStartN to -apache -d /www/<serverName> -f conf/httpd.conf -AutoStart Y. Where <serverName> is the name of the member you just created. The Y on the end of the string will autostart the HTTP server when the STRTCPSVR HTTP ALL is issued.
d.	To change the HTTP server to not autostart, change the -AutoStart Y value to -AutoStart N if you want.

e. Press F3 to Save/Exit.

Execute the following commands from the 5250 command line:

MKDIR '/www/<serverName>' then
MKDIR '/www/<serverName>/conf'
MKDIR '/www/<serverName>/logs' and
MKDIR 'www'<serverName>/htdocs'

Once again, <serverName> is the name of the member created in Step 3.

Copy the files from the /www/<serverName>/conf directory from the source system:

/www/<serverName>/conf
to
/www/<serverName>/conf.

Copy the files from the /www/<serverName>/htdocs directory from the source system:

/www/<serverName>/htdocs/*
to
/www/<serverName>/htdocs/*.

Now your HTTP server has been created and is ready. If any system unique references to the source system (specific IPs, and so on), it must be changed in the httpd.conf file

Notes:
1. Any referenced CGI library or data files unique to your HTTP server configuration must be re-created.
2. If this HTTP server instance uses SSL, an SSL certificate must be assigned to it prior to starting.
3. Port availability should be verified to avoid contention issues with the ports defined in the HTTP configuration.
4. If the operating system releases of the target system and source system are different special care has to be taken as some of the directives may not work on all releases.
5. If your httpd.conf file has an Include directive you need to make sure to create the referenced path and copy the file over as well.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CGqAAM","label":"IBM i HTTP Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

566080041

Was this topic helpful?

Document Information

More support for:
IBM i

Component:
IBM i HTTP Server

Software version:
All Versions

Operating system(s):
IBM i

Document number:
686343

Modified date:
21 March 2023

UID

nas8N1012162

IBM Support

Tips