Setting up the IBM WebFacing Tool

The WebFacing Tool provides a GUI environment for selecting, converting, and testing the converted user interfaces of your original application.

Setting up your systems for the WebFacing Tool involves the following activities:

  • Setting up WebSphere® Application Server on your IBM® i server
  • Installing the WebFacing server PTFs on your IBM i server
  • Starting the WebFacing server on the IBM i server
  • Transferring converted applications to the IBM i server.

Setting up WebSphere Application Server on your IBM i server

WebSphere Application Server handles executing the JavaServer Pages and JavaBeans™ that are generated as part of the DDS conversion process. Set up WebSphere Application Server for IBM i using the documentation resources on the following Web site:

IBM WebSphere Application Server - Express V7.0 for IBM i
http://www.ibm.com/software/webservers/appserv/was/library/v70/e-ibmi/index.html

Minimally you will need to carry out the installation steps. Becoming familiar with the IBM WebSphere Application Server documentation, in particular the sections on installation and creating application server instances, is highly recommended.

You can optionally set up individual instances for the WebSphere Application server. If your system is to be used for test and production work, it can be helpful to create instances for testing and development and separate instances for production. As well, if more than one developer is doing development work, their work can be developed and tested separately by creating additional instances. The default HTTP port for WebSphere Application Server is port 9080. The default port for the administrative server is port 9060. The administrative servers are accessed through a browser-based console. If you want to create additional instances, please refer to the Web site links above.

Test the WebSphere Application Server setup. Use the links at the above sites to locate the appropriate Information Center. In the Information Center search on Verify the installation for information about testing your application server setup.

Setting up WebSphere Portal on your IBM i server

WebSphere Portal handles the execution of the portlets you create from your projects. Set up WebSphere Portal for IBM i using the documentation resources on the following Web site:

Minimally you will need to carry out the installation steps. Becoming familiar with the IBM WebSphere Portal documentation, in particular the sections on installation, is highly recommended.

Installing the WebFacing server PTFs on your IBM i server

The WebFacing server acts as a gateway between WebSphere Application Server and your original IBM i application. Information about the WebFacing server PTFs can be found in Troubleshooting WebFacing applications.

The WebFacing server PTFs must be installed on the IBM i server where your application will be running. Except on some later-model IBM i servers, the WebFacing Tool consumes interactive cycles. Although WebSphere Application Server can run on the same system, it is not necessary for it to be running on the same system on which your application is running. The converted interface to your application is deployed as a WebSphere application; you can deploy the WebFacing WebSphere application to one IBM i server while the IBM i application is installed on another.

Starting the WebFacing runtime server on the IBM i server

  1. Start the WebFacing runtime server on your IBM i server. For OS/400® V5R2 and later, enter STRTCPSVR SERVER(*WEBFACING) from the command line. To stop the WebFacing server, enter ENDTCPSVR SERVER(*WEBFACING) from the command line.
  2. To ensure that the server is running, enter WRKACTJOB from the command line.
    1. From a command line enter WRKACTJOB JOB(QQF*) to list all WebFacing jobs:
      • QQFWFSVR -- the WebFacing runtime server AND
      • QQFVTSVR -- the WebFacing virtual terminal server (More than one QQFVTSVR job may be running, which is normal)
    Note: Check the system value QAUTOVRT. If this value is 0 then no browser sessions can be launched in place of VT (virtual terminal) jobs. The WebFacing runtime server relies on VT jobs. The value for QAUTOVRT determines the number of virtual terminal jobs that can be auto started. If necessary, set QAUTOVRT to *NOMAX or some value greater than 0. To change the value for QAUTOVRT, use the WRKSYSVAL IBM i server command to work with system values.

Transferring converted applications to the IBM i server

Application development is done on a workstation. Artifacts generated by the application must later be transferred to an IBM i server so they can be deployed by WebSphere Application Server. Set up a method for transferring your converted applications to your IBM i server. When you are deploying your converted applications to your IBM i server, you will need a method to transfer them to your server. Applications are transferred as .ear files, which are archived Web application packages created through the Export wizard. They facilitate deploying and installing new WebFacing Web applications to WebSphere Application Server. These are the primary methods for transferring files:
  • Remote System Explorer perspective in the Rational® Developer for IBM i workbench
  • IBM i NetServer™ file sharing -- With file sharing, files can be transferred using the Export wizard.
  • FTP -- With FTP, files are transferred manually.

NetServer file sharing allows you to map an IFS folder on your IBM i server to a drive letter on your workstation. This allows you to use the Export wizard to transfer files to your server in the same way that you can copy files from one folder to another on your workstation. To transfer your files by FTP, the FTP server must be running on your IBM i server. If FTP is not running, it can be started by entering the command STRTCPSVR *FTP.


Feedback