In this situation, the application does not start when
you click the link on the index.jsp page. The page remains in the
browser with no error message and the application appears to hang.
There might be a problem with one of the following:
- The library list
- The invocation command you specified in the WebFacing project
- The IBM® i host setup itself
- The use of limited capability user IDs
- WebFacing PTF levels may not be in sync with the WebFacing run-time
level
Check the application server console. If you do not see the Pagebuilder.jsp
being invoked, this is a good indication that the program on the IBM i host cannot be found.
First, check to determine whether or not the command you
specified in the WebFacing project, along with the user ID that you
used to log on for the WebFacing application, works in a 5250 environment:
Start a 5250 emulation session:
- Sign on with the same user ID and password that you used in the
WebFacing project to run the WebFacing application.
- Enter the command that you specified in the WebFacing project
exactly the same way on the 5250 command line.
If the application does not open in the 5250 environment,
something is wrong with the library list or the command:
- Thoroughly check your application to get it running in the 5250
environment.
- With the same settings, start your WebFacing application.
If you need to change the user ID and password in the
WebFacing project, use the WebFacing project Properties to change
them.
If you need to change the invocation command, use
the WebFacing Project wizard to remove the current entry and add a
new one. To use the WebFacing Project wizard:
- Switch to the WebFacing Projects view.
- Expand the WebFacing project.
- Right-click the CL commands node and select Add.
- In the Specify CL Commands page, select the CL command in the CL
Command list and click Delete.
- Specify a new command in the CL command field
and click Add.
- Click Finish.
- Restart the server and run your application.
If the command in the 5250 environment worked fine and
started the application without a problem, check the job log for the
WebFacing job. You can do this in the Remote System Explorer under
the IBM i jobs node, or you
can start a 5250 session and issue a Work Active Job (WRKACTJOB) command.
Look
for a QQF job started with the user ID you are using and then check
the job log. If you cannot find a QQF job, the job might have ended.
Use the Work Spool File (WRKSPLF) command for the user ID you used
in the WebFacing application to determine whether or not there are
any job logs from the terminated job that could give you more information.
Checking the WebFacing PTF level
Make sure
you have the latest PTF level on your IBM i
host. Refer to
WebFacing
Tool PTFs for more information. If you have a mismatch, end
the WebFacing server, load and apply the PTFs, then restart the WebFacing
server:
- End the WebFacing server (ENDTCPSVR *WEBFACING)
- Load and apply the desired PTFs
- Start the WebFacing server (STRTCPSVR *WEBFACING)
Run the WebFacing application again.