10 1 Troubleshooting Checklist

10.1 Troubleshooting Checklist

Before you contact your local LANSA vendor for support, please complete the following checklist and have the answers available.

IBM i Servers with LANSA for the Web

• Do you have TCP/IP (STRTCP) running?

• Do you have the HTTP Web Server configured and running?

• Are you able to display the index or home page for the Web Server by entering the IP address of the Web Server into a browser?

• If you are using the IBM HTTP Server for the IBM i and you are using the default user profiles for the IBM HTTP Server configuration, have you checked that both the QTMHHTTP and QTMHHTP1 user profiles are enabled?

• Do you have a LANSA Listener running?

• Have you used WRKACTJOB to confirm that Web Server instances and the LANSA Listener jobs are running?

• Have you used NETSTAT to confirm the Listener port is being listened on?
  (For example, NETSTAT *CNN  - followed by F13, select local port, F14 - normally port 4545.)

• Do you have a LANSA for i and LANSA for the Web development license installed?

• Have you installed the LANSA for the Web PC-based Administrator?

• Is the partition Web enabled?
  Have you web enabled the partition using Partition Initialization or have you imported the LWEBSF save file into the partition? You must import LWEBSF before you Web Enable a partition using the LANSA for the Web Administrator.

• Have you created a Default User (DFTUSR) to allow anonymous user access (from the LANSA for the Web Administrator)?

• Have you confirmed that the IBM i user profile associated with the Default User exists and has the correct library list and authority? (For example, QTEMP, QGPL, DCXPGMLIB should be in the library list and the user should have *JOBCTL authority.)

• Have you set the user profile(s) used to run the LISTENER, TP, LWEB_MON, LWEB_JOB  so that they have a JOBD with its message logging set to *SECLVL.

• Have you Web enabled the test process you are using? (To do this, select option 28 (Work with Processes) on the Advanced Work with menu.)

• Have you recompiled the functions after Web enabling the process? (See step above.)

• Have you configured LANSA for the Web to access your LANSA system correctly using the LANSA for the Web Administrator? Specifically, have you configured LANSA for the Web, including the file location, the working library and the Transaction Server settings, other than the defaults?

• If you have pre-started your transaction monitor, have you used WRKACTJOB to confirm that LWEB_MON and the LWEB_JOBS are active?

• Have you checked the Maintain System definitions using the LANSA for the Web Administrator to ensure that you have complete details for the system? For example, do you know the port being used with your system or partition? Initially, and before you change the basic defaults, test this with System Name set to "*DEFAULT"; PORT set to your port number i.e. 80; LANSA Library set to DCXPGMLIB or your PGM library and Partition left blank.)