Troubleshootings

  Topics in this section:
1 - HTTP server
2 - Application JOB
3 - JAVA enable
4 - FireWall
 

1 - HTTP server

iWeb can use both the original HTTP server or the Apache HTTP server. In either case the HTTP server will open several HTTP instances.
You can list the HTTP instances with the command WRKACTJOB or WRKACTJOB SBS(QHTTPSVR):

__   QHTTPSVR      QSYS        SBS     0,0                  DEQW
__     IWEBRUN     QTMHHTTP    BCH     0,0  PGM-QZHBMAIN    SELW
__     IWEBRUN     QTMHHTTP    BCI     0,0  PGM-QZSRHTTP    SIGW
__     IWEBRUN     QTMHHTTP    BCI     0,0  PGM-QZSRCGI     TIMW
__     IWEBRUN     QTMHHTTP    BCI     0,0  PGM-QZSRCGI     TIMW
__     IWEBRUN     QTMHHTTP    BCI     0,0  PGM-QZSRCGI     TIMW
5_     IWEBRUN     QTMHHTTP    BCI     0,0  PGM-QZSRCGI     TIMW

When an instance of iWeb is running, one of these HTTP instances is invocated (and it could be any of them). If an error occurs at the HTTP server level, you will have to find out an error message in one of this instance:
do opt5, then opt10 to see the log until you see a relevant message.  

2 - Application JOB

After a LOGIN (manual or automated) has been accepted by the HTTP server, a JOB is submited in QSYSWRK to run the application.

  • If any error occurs, the JOB end and a JOBLOG is created in the queue QEZJOBLOG. To see the LOG use the command:
    WRKOUTQ QEZJOBLOG and look for the last log.

You can list the iWeb JOBs with the command WRKACTJOB or WRKACTJOB SBS(QSYSWRK): 

__   QSYSWRK       QSYS        SBS     0,0                  DEQW
__     IWEB000001  USER01      BCH     0,0  PGM-SESSION     DEQW
__     IWEB000002  USER32      BCH     0,0  PGM-SESSION     DEQW

To DEBUG an iWeb JOB you have to do the same as debuging a batch JOB, which is:

  • 1. SRTSRVJOB jobNbr/jobUser/jobName
  • 2. STRDBG lib/pgm
  • . . .
  • 3. ENDDBG
  • 4. ENDSRVJOB
2.a Converted application structure overview
When iWeb does a conversion the following happens:

Original library: yourLib
Target library for converted pgm: yourLibW (which is a new library)

For programs:
All converted program are recompiled in the library yourLibW (the originals pgm are not altered)

For Display files:
XML document are created in /iwebdata/fmts/yourLib/dspName/fmtName.xml for each display format.
Note that the reference library is the original library, nothing is recompiled here.

For Menus:
XML document are created in /iwebdata/menus/yourLib/menuName.xml for each menu.
Note that the reference library is the original library, nothing is recompiled here.

For Help panel groups:
XML document are created in /iwebdata/uim/yourLib/helpName.xml for each help.
Note that the reference library is the original library, nothing is recompiled here.

Therefore, to run a converted application the only point to remind is to put the Target library for converted pgm (yourLibW) on the top of the library list. In that way when a program is called, that the converted version which will run (unless your application uses qualified call, specifiyng the lib name, in that case you have to change it). A last point to check out, for converted application, is when the INLPGM (initial program) of a user profil is directly a program using a display file, in that case you will have to change the library name to the Target library for converted pgm (yourLibW).

Only converted programs are within the library Target library yourLibW (yourLib2W, yourLib3W) !
All other object are dinamically referenced to the original library they belong to (yourLib, yourLib2, yourLib3, yourLib4...)

At runtime, iWeb uses dinamically the object library upon the library list to get the reference library (as the same way the 5250 use to run). Therefore, never add objects different than converted programs within a Target library yourLibW.
  

3 - JAVA enable

iWeb uses, for the client interface, a Web JAVA applet

  • the browser has to enable the Java (sun), which is the default setting. Check in through your browser menu: Tools > internet option > advanced.
3.a Java error
Within the browser you can see the JAVA console, usually you can acces it through the browser menu. The Java console will display the Java version currently used and a LOG if any errors occured.
  • With Internet Explorer browser menu: Tools > Sun Java Console
  • With Mozzilla Firefox browser menu - Download the extension "Open Java Console" - then: Tools > Java Console
 

4 - FireWall

iWeb uses a JAVA applet, an URL connection to your System i and a port number usually different than 80.

  • Check your FireWall enables JAVA
  • Check your FireWall accepts connection with the URL of your Sistem i
  • Check your FireWall accepts connection with the HTTP port number used by iWeb (usually :8008 or :8010)