The BlueZone Web-to-Host web server files can be served
up from any web server including the IBM HTTP server that ships with
the AS/400 and iSeries hosts. The IBM HTTP server is based on Apache.
This procedure is written under the assumption that HTTP services
are already configured and running on the iSeries (AS/400) host.
This procedure only covers the transfer of the BlueZone Web-to-Host
web server files to the iSeries HTTP web server. It does not cover
the configuration of BlueZone Web-to-Host.
Step 1: Uploading the Web-to-Host web server files
to the web server
- Create a folder (for example, bluezone) in
the root of the iSeries web server. This will be the top-level folder
for the Web-to-Host web server files.
- On the machine where the Web-to-Host Wizard is installed, locate
the place where your Web-to-Host web server files are stored. This
would be the place where you stored all the sites that you created
with the Web-to-Host Wizard. Keep in mind that you may have only
created one site.
Note: Do not use shared folders to copy files because
some of the BlueZone Web-to-Host web server files do not conform to
the Windows 8.3 naming convention.
- On the iSeries host, upload each site including the entire sub
file structure that was created by the BlueZone Web-to-Host Wizard
to the new folder that you just created. Upload all files as binary
and the .htm files as text.
CAUTION:
You
must not change the file structure of the Web-to-Host web server files.
All folders and subfolders including all their files must be uploaded
to the web server just as they were created by the Web-to-Host Wizard.
If anything is changed, you run the risk of the site becoming inoperable.
For
example, if you created a site called MySite,
upload it to the bluezone older as shown here:
\bluezone\mysite
By
uploading the entire contents of the MySite folder,
you will automatically be uploading all the launch folders that are
associated with this site. In this example, there is a launch folder
called MyFolder Your directory structure should
look something like this:
\bluezone\mysite\myfolder
Step 2: Configuring the web server
Once
all the sites and launch folders have been uploaded to the host, you
must make the following changes to allow access to BlueZone Web-to-Host.
- While logged on with QSECOFR authority, you will need to update
the HTTP configuration file. On the command line execute type:
WRKHTTPCFG
- At the bottom (end) of the existing entries, add a line.
- Add the following entry:
Pass /bluezone/*
/bluezone/mysite/myfolder/*
When the HTTP web server
receives a request with a URL containing /bluezone,
it will send it to the folder /bluezone/mysite/myfolder/ and
execute the default page.
- Refresh the server to recognize the updated configuration file.
On the command line execute type:
STRTCPSVR
Now, when you type in the URL of your iSeries HTTP web
server, followed by /bluezone/mysite/myfolder/,
the launch page associated with the launch folder called myfolder will
start.
Step 3: Testing the uploaded files
- From a Windows workstation, start your browser.
- Type in the URL of your iSeries HTTP web server, followed by /bluezone (or
whatever you called the folder where BlueZone Web-to-Host is installed),
then the site name, and press ENTER. For example:
http://63.69.143.23/bluezone
Or
http://www.myhost.com/bluezone
If
your HTTP web server is set up properly, the default.htm file
will open the correct launch page.
- The Web-to-Host Control Module will download and install. Then, a web page
with a BlueZone launch pad will be displayed. The launch pad will
contain icons for one or more BlueZone emulation clients.
- Continue the test by starting a BlueZone emulation client session
by double clicking one of the icons.
- If you have both Internet Explorer and Netscape users, be sure
to test with both browsers.
Note: When conducting browser tests, it’s
okay to run IE and Netscape at the same time however, you cannot start
a BlueZone display session from one browser then start the same BlueZone
display session from the other. The second session will not start.
You must close the first BlueZone session (not the browser) before
starting the same BlueZone session with the other browser.