Troubleshooting WebFacing applications

The information in this section can help you troubleshoot problems that occur in WebFacing applications. You may also refer to the following links to learn more.

• WebFacing Troubleshooting Tips
• WebFacing Tool PTFs
• Configuring the WebFacing Server
• WebFacing Tool -- current DDS keyword support
• Considerations for linked HATS/WebFacing applications
• Web Settings

For additional information on troubleshooting, as well as helpful tips and updates, refer to WebFacing-specific Support Documents online.

Before contacting IBM® Support, please read the Collecting data for IBM i WebFacing applications section.

• WebFacing error messages

  This section lists error messages that you might encounter when using WebFacing. Refer to the following different times of messages when troubleshooting.

• Collecting data for WebFacing applications

  If a problem with WebFacing is suspected, please first read through the WebFacing troubleshooting section and the links it references.

• I cannot run my WebFacing application from a previous release

  In this situation, the WebFacing application from an early release does not function. You need to migrate it to the current release.

• Application does not start

  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.

• Problem with using limited-capability user IDs

  A limited-capability user ID on IBM i is one that has the LIMIT CAPABILITIES (LMTCPB) parameter set to *YES or *PARTIAL. WebFacing only supports limited-capability users on IBM i V6R1 and later.

• WebFacing server does not start

  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.

• Page cannot be displayed

  This error is most likely caused by an application server problem, or an incorrectly entered URL.

• Page cannot be found

  When this error displays, the WebFacing project might be corrupted, the WebFacing project has not been installed correctly, or the URL is being used incorrectly.

• Invalid session

  The Web environment is not based on persistent connections between the browser and the HTTP server. When you run the WebFacing application and leave the browser for an extended period of time, the application will eventually time out.

• DDS and WebFacing are out of sync

  If you change the display file DDS source member and recompile your program to work with the changed display file, you will also have to reconvert this DDS source member to create the corresponding JSPs and XML files in the WebFacing project.

• WAS Test Environment fails initialization for WebFacing application if long workspace path is used

  You may experience a problem with WebFacing projects not running in the WebSphere® Test Environment with an error in the console similar to: 6cb33777 SystemOut O Exception in generateFieldAttributes : java.io.FileNotFoundException: (The system cannot find the path specified)

• Context root with space does not run on WAS Test Environment

  A space is not allowed in context roots because it does not conform to Java™ EE specifications.

• Application does not work properly with RSTDSP(*NO) specified

  WebFacing applications do not work properly when display files have RSTDSP(*NO) specified.

• Absolutely positioned elements appear in unexpected locations in WebFacing

  Elements previously customized with an absolute position property show up in unexpected locations after migration.

• Common Base Event logging support for WebFacing applications

• TFRJOB or RRTJOB with WebFacing ends user job

  If a user job is being run in the WebFacing environment, do not use the TFRJOB or RRTJOB commands and do not apply RTGDTA.

• Cannot access extended help on dynamically rendered WebFacing screens

  By default, extended help cannot be accessed on WebFacing screens that are rendered dynamically because cursor positioning is not turned on for protected fields.