Installation Guide

Sections in this chapter:

1.1 Uploading library iWEB

1.2 iWEB contents

1.3 iWEB authorization codes

1.4 Installing the Converter

1.5 Installing the RunTime

1.6 Installing a new iWEB release

1.7 Uninstalling iWEB

1.1 Uploading library iWEB

The iWEB package is a file named iweb.zip that should be downloaded from the iWEB site http://www.iseries-iweb.com.

Once unzipped, this file generates the following files:

File iweb.savf, the V4R5 save file of library IWEB
File readme.pdf, containing the procedure to install library iWEB and some reference to the iWEB manual.

To transport the save file from your pc to the iSeries, you may use the following procedure:

if the library iWEB already exists on the iSeries, rename or delete it
start the FTP server on your iSeries
open a 5250 session on the iSeries and create save file qgpl/iweb

on your PC, open a DOS window, position to the directory containing the savefile qgpl/iweb and run the following FTP session in connection with your iSeries:

ftp n.n.n.n   (n.n.n.n. = ip address of the iSeries)
(enter user_profile_name and password)
bin
quote site namefmt 1
cd /qsys.lib/qgpl.lib
put iweb.savf
quit

Figure 01-01. Uploading IWEB save file

Once the save file qgpl/iweb has been loaded from the FTP session, you may restore library iWEB.
To do this, you need to open a 5250 session with a user profile class SECOFR.
Then enter command rstlib iweb savf(qgpl/iweb).

To complete your iWEB installation, please go through the step 1.4 and 1.5

1.2 iWEB contents

An iWEB installation is made up of the following pieces:

Library IWEB. It mainly contains iWEB programs. Customer data and / or programs should be excluded from this library.
Library IWEBDATA. It mainly contains database files to receive data from the Converter module.
IFS directory /iweb. It contains iWEB objects, such as the Runtime Applet, html scripts, iWEB images. Never add customer files to this iWEB directory.
IFS directory /iwebdata. It contains iWEB files related to the iWEB installation at the customer site, such as iWEB instances, conversion results, etc.
IFS directory /iwebdir.This directory is for customer use, when running the utility iExplore.

iWEB installation sets up those five pieces. While library iWEB and directory /iweb stay static until a subsequent iWEB release is installed, directory /iwebdata is updated any time something is converted to iWEB.

Performing appropriate saves of library iWEB and of /iweb... directories is a customer responsibility.

1.3 iWEB Authorization codes

iWEB Converter and iWEB RunTime, in order to execute, need authorization codes be provided. Two different authorization codes are needed: one for the Converter, one for the Runtime.

Authorization codes are communicated from the iWEB owner any time iWEB licenses are obtained.

iWEB authorization codes are related to the iSeries serial number, model feature, and processor feature. They also account for the license expiration date.

1.4 Installing the Converter

The iWEB Converter module is the one in charge for enabling existing 5250 applications to run also under WEB.
iSeries shops just installing iWEB applications converted elsewhere do not need to install this iWEB module.
iSeries shops willing to enhable their 5250 applications for the WEB, should install this iWEB module.

If you need to install (enable) the Converter module, you should proceed as follow:

Make sure that you have installed the latest iWEB release. This can be done by checking the information available from the iWEB download site and what is available from command iweb/release.
Make sure that you have have received from the iWEB owner the correct Converter authorization code for the serial number, model, and processor feature of your iSeries. The expiration date of the authorization code for Converter should also be checked out.

Open a 5250 session with a user profile class SECOFR and enter command IWEB/INSTALLC:

directory /iweb is restored
library IWEBDATA is created / updated
directory /iwebdata is created / updated with all the needed subdirectories
the following screen appears:

                   Install iWEB Converter

Step 1 - Select one of the national languages
         1=select

         1  English
            Italian

Figure 01.02 - Select national language

the following screen appears:

                   Installing iWEB Converter

Step 2 - To enable the Converter, enter the following data:

         password . . . . . . . . . .                  
         expires on year  . . . . . .      
                     month  . . . . .    
                     day  . . . . . .    
         maximum number of formats  .             number, *NOMAX

Figure 01.03 - Enter authorization code data

enter the authorization code data as you have received from the iWEB owner.
A message tells whether the password is valid.
Should it turn on as no good, please get in touch with the iWEB owner.
Next, an HTTP instance is automatically created.
This instance allows to perform conversion jobs.
If your OS/400 is lower than V5R3, an Original HTTP instance is created, otherwise an Apache HTTP instance is created.

The following screen appears:

                  Installing iWEB Converter

Step 3 - Converter HTTP instance

HTTP instance IWEBCVT was installed for the iWEB Converter.

To start this instance:
        strtcpsvr *http httpsvr(iwebcvt)

To start the iWEB converter:
        http://...:8008/

Figure 01.04 - HTTP instance for the iWEB Converter

Take a note of the instructions for starting and using the Converter HTTP instance and press Enter to end the Converter installation procedure.

1.5 Installing the RunTime

The iWEB RunTime module is the one in charge for running the converted programs under WEB.

To install (enable) the Converter module, you should proceed as follow:

Make sure that you have installed the latest iWEB release. This can be done by checking the information available from the iWEB download site and what is available from command iweb/release.
Make sure that you have have received from the iWEB owner the correct RunTime authorization code for the serial number, model, and processor feature of your iSeries. The expiration date of the authorization code for the RunTime should also be checked out.

Open a 5250 session with a user profile class SECOFR and enter command
IWEB/INSTALLR:

directory /iweb is restored
library IWEBDATA is created /updated
directory /iwebdata is created / updated with all the needed subdirectories
the following screen appears:

                   Install iWEB RunTime

Step 1 - Select one of the national languages
         1=select

         1  English
            Italian

Figure 01.05 - Select national language

The following screen appears:

                  Installing iWEB Runtime

Step2 - Enter the following data:

         password . . . . . . . . . .                        
         this password is independent
           from the processor feature . . .         Y=Yes, N=No
         expires on year  . . . . . .            
         month . . .                           
         day . . . .

Figure 01.06 - Enter authorization code data

Enter the authorization code data as you have received from the iWEB owner.
A message tells whether the password is valid. Should it turn on as no good, please get in touch with the iWEB owner.

Next, a series of screens appear to set up the iWEB runtime HTTP instance:

                    Installing iWEB runtime

Step 3 - Runtime HTTP instance

Select your option and press Enter.

Instance type  . . . . . .     1=an existing instance
                               2=a new instance

Figure 01.07 - Select the type of RunTime instance

For any release update (new release installation) ignore all following screens and Exit with F3.

If in Figure 01.07 you selected an existing instance, you are asked which instance type:

 Update an iWEB Runtime HTTP instance (command HTTPCFG)


Type your choice and press Enter.

Instance type  . . . . . .        1=Original, 2=Apache

Figure 01.08A - Select between type Original and type Apache

Once you have made your selection, a screen shows all the existing instances of that type. As an example, when selecting type Apache, a screen like the following may show up:

 Update an iWEB Runtime HTTP instance (command HTTPCFG)

Select an instance and press Enter.
  1=instance to be updated

  instance   configuration file
  APACHEDFT  /www/apachedft/conf/httpd.conf
  CGIDEV2APA /cgidev/conf/httpd.conf
  HTTP41941  /http/http41941/conf/httpd.conf
  HTTP7777   /http/http7777/conf/httpd.conf
  HTTP80     /http/http80/conf/httpd.conf
  MAMA       /www/mama/conf/httpd.conf

Figure 01.09A - Select an existingTTP instance

Once you select an instance, it is added the proper directives that allow the Runtime to operate.
Warning. The iWEB Converter instance (IWEBCVT) should never be selected for the Runtime.

If in Figure 01.07 you selected a new instance, the following appears:

                        Installing iWEB Runtime

Step 4 - Create an HTTP instance

   Instance name . . . . . .               Name
   Instance type . . . . . .               1=Original, 2=Apache
   Port number . . . . . . .               80, 1024 - 65535

Figure 01.08B - Creating a new HTTP instance for RunTime
Note. Never specify port 8008 for the Runtime HTTP instance.
This port is dedicated to the Converter.

To execute the Runtime, in the command line of your WEB browser enter:
- http://nnn.nnn.nnn.nnn:pppp
  if you created a new HTTP instance for the Runtime
- http://nnn.nnn.nnn.nnn:pppp/runtime
  if you updated an existing HTTP instance for the Runtime
  where
  - nnn.nnn.nnn.nnn is the IP address of the iSeries
  - pppp is the port assigned to the Runtime HTTP instance

1.6 Installing a new iWEB release

From time to time, the iWEB owner would make available a new iWEB release for download. A new release will generally contain some fixes and some enhancements.
If you have a license for iWEB maintenance, you would receive by e-mail the announcement letter of the new release, and you would be enabled to download it.

If you do not remember what is the last iWEB release you have installed on your iSeries, just open a 5250 session and enter command iweb/release.

Installing a new iWEB release is not a trivial job: restoring library iWEB is not enough! To install a new IWEB release, please carefully apply the following procedure:

On the iSeries open a 5250 session with a user profile class *SECOFR

end the iWEB Converter HTTP instance  [endtcpsvr *http httpsvr(name_of_the_Converter_HTTP_Instance)]
end the iWEB Runtime HTTP instance  [endtcpsvr *http httpsvr(name_of_the_Runtime_HTTP_Instance)]
rename or delete library IWEB
Download and install the new release of library iWEB: see Uploading library iWEB
Perform the installation of the Converter: see Installing the Converter but make sure to exit from the INSTALLR procedure (with F3) when appears Figure 01.07. Please note that the authorization code for the Converter will be retrieved from the data saved during the last Converter installation (so that you do not need to key in again those data).
The service programs in library iWEB carry new signature identifiers at every new release. These signature changes will cause all programs already converted to fail during execution. In order to avoid such failures, one should rebind (using command updpgm) every converted program. Command iweb/rebind will do that for you. This command submits a separate rebind job for each converted library.
Start the iWEB Converter HTTP instance  [strtcpsvr *http httpsvr(name_of_the_Converter_HTTP_Instance)]
Start the iWEB Runtime HTTP instance  [strtcpsvr *http httpsvr(name_of_the_Runtime_HTTP_Instance)]

1.7 Uninstalling iWEB

To disinstall iWEB, do the following:

On the iSeries open a 5250 session with a user profile class *SECOFR
end the HTTP instance for iWEB Converter
end the HTTP instance for iWEB Runtime
delete library IWEBDATA
delete library IWEB
remove IFS directory /iwebdir, including all its subdirectories and files
remove IFS directory /iwebdata, including all its subdirectories and files
remove IFS directory /iweb, including all its subdirectories and files
start PDM option 3 over file QUSRSYS/QATMHINSTC and remove the member related to the iWEB Converter HTTP instance
if the iWEB Runtime HTTP instance was a dedicated one, start PDM option 3 over file QUSRSYS/QATMHINSTC and remove the member related to the iWEB Runtime HTTP instance