The WebFaced Application Does Not Start


When you click the link on the index.html page, the application does not start. The index.html page stays in the browser, no error message displays, and the application invocation seems to hang. This might be a problem with one of the following:

  • The library list

  • The invocation command you have specified in the WebFacing project

  • The iSeries host setup itself

    • The use of limited capabilities user IDs

    • WebFacing PTF levels not in sync with the WebFacing runtime level

Check the application server console. If you do not see the Pagebuilder.jsp being invoked (see Figure 18.1), this is a good indication that the program on the iSeries host cannot be found.

click to expand
Figure 18.1: WebSphere application server console without the Pagebuilder.jsp being invoked
Note  

If you run an initial program at job startup to set up the library list, be aware that this program will not be run in the WebFacing environment. You will need to modify the job description to apply the correct library list or set up the environment to explicitly call a program during startup.

The first course of action is to check whether the command that you specified in the WebFacing project, in combination with the user ID that you used to log on for the WebFaced 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 WebFaced 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 the WebFaced application.

If you need to change the user ID and password in the WebFacing project, use the WebFacing project Properties option in the WebFacing Perspective to change them.

If you need to change the invocation command, you have two options:

  1. Use the WebFacing Project Wizard to delete the current entry and add a new, changed one.

  2. Directly edit the file that contains the information.

To use the WebFacing Project Wizard (option 1):

  • Switch to the WebFacing Project view.

  • Expand the WebFacing project .

  • Right-click the CL commands node.

  • Select the Add option from the pop-up menu.

  • The Specify CL commands wizard page displays.

  • Select the flawed invocation command entry in the list and delete it.

  • Specify a new correct invocation command and add it to the list.

  • Click the Finish push button.

  • Restart the WAS Test environment server to pick up the new invocation file content.

  • Run your application.

To edit the file directly (option 2):

  • Go to the Navigator view in the workbench.

  • Look for the .invocation file in the WebFacing project structure under Project Web content WEB-INF classes conf.

  • Edit the .invocation file to correct the command invocation.

  • Save the file.

  • Close the editor.

  • Restart the WAS test environment server to pick up the new invocation file.

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 iSeries jobs node, or you can use a 5250 and issue a Work Active Job (WRKACTJOB) command.

  • Look for a QQF job starting with the user ID you are using and then check the job log. Figure 18.2 shows the Remote System Explorer with a QQF job selected and the job log displayed.

    click to expand
    Figure 18.2: Using the RSE to display a job log

In Figure 18.2, the problem is an error in the command you are using to invoke the application.

If you cannot find a QQF job, that job might have ended:

  • Use the Work Spool File (WRKSPLF) command for the User ID you used in the WebFaced application to check if 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 iSeries host. Check the WebSphere Development Studio Web page for WebFacing Tool information. If you have a mismatch, load and apply the PTFs, then End the WebFacing server and Start it again:

  • In V5R1 or higher, use the End TCP/IP Server (ENDTCPSVR) *WEBFACING command, then the Start TCP/IP Server (STRTCPSVR) * WEBFACING command.

  • In V4R5, use the End WebFacing Server (ENDWFSVR) command, then the Start WebFacing Server (STRWFSVR) command.

Run the WebFaced application again.




Understanding the IBM WebFacing Tool. A Guided Tour
Understanding the IBM WebFacing Tool: A Guided Tour (IBM Illustrated Guide series)
ISBN: 1931182094
EAN: 2147483647
Year: 2003
Pages: 153

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net