If you receive an application error after clicking the hyperlink
to invoke the WebFacing application, check the error message just below it.
The error message contains details about the cause of the error. One of the
more frequent messages is that the WebFacing server is not started.
Use the Start TCP/IP server command to start the WebFacing server.
STRTCPSVR *WEBFACING
Note: Make sure that the i5/OS® system value QAUTVRT is higher
than 0. Because the WebFacing server relies on Virtual Terminal jobs, you
should check to make sure that this system value is set so that all WebFacing
sessions are supported.
You will receive the same message
if the i5/OS server
you have specified to connect to does not exist, so use the WebFacing project
properties to ensure that the server name is correct.
Scroll
down the rest of the error page to see which i5/OS host the application attempted to
access and which port number was used to connect to the WebFacing server.
Check that these values are correct. The default port for the WebFacing server
is 4004. Use the following command to check the ports:
NETSTAT *CNN
Press
F14 to show the port numbers, and use option 8 to check the jobs using port
4004.
There should be
one job listed (QQFWFSVR). That means the WebFacing server is using port 4004.
If the job listed is not QQFWFSVR, then it is not the WebFacing server listening
on port 4004. If this is the case:
- Check the port the WebFacing server is using by entering the Work with
Service Table (WRKSRVTBLE) command.
- Look for an "as-WebFacing" service entry in the list. If there is an entry,
use the display option to see what port is being used.
Note: If the default port 4004 is not in use by some other service,
there is no need to change the port number to something else.
If
there are QQF jobs:
- Check the job logs in both of them.
- In case of any errors, check the PTF level. If your system has the current
WebFacing PTFs applied, this is most likely a problem and should be reported
to IBM® support.
Determining whether or not the WebFacing server responded
to a request
You can easily check to determine whether
or not the WebFacing server on the i5/OS host has been responding to a request
by checking the idle time in the Work with TCP Connections Status list.
If
the idle time is close to zero and you are the only user running WebFacing
applications, then your last request has been received by the WebFacing server
and the job logs should help you find the problem.
If the
idle time is high, then the request did not make it to the WebFacing server.
Check the i5/OS server
name you specified in the WebFacing project, and check the authentication.
You can try removing the automatic authentication in the WebFacing project
properties to force a signon dialog. If the signon dialog appears, you know
that you reached the i5/OS server and you can check the WebFacing server
environment as described before.