Converting the DDS source

Now that you have created the project, you can convert the DDS display files into JSP files for your Web page. When you convert your DDS display files, the WebFacing Tool generates JSPs and XML files that substitute for the DDS code and make Web access possible. The generated files hold the data for the record format, or control its appearance, display the Web version of the screen, prompt for data, and handle input errors. The wizard also generates an application home page to launch the Web-enabled version of your program.

First, however, you need to alter your source to reference the correct iSeries server. More specifically, you need to perform a modification in one of your DDS display files so that the link for the application will function. You need to change the default name, SV000501, to your project name, Project501:

  1. Switch back to the WebFacing perspective and switch to the WebFacing Projects view if it is not already open by default.
  2. Expand Project501 > DDS.
  3. Double-click the second entry, <iSeriesserver>RETAILSTOR/QDDSSRC(QUERY)
  4. Scroll down to about line 16, where you see the line:
    A*%%WB 12 FLD 1 next ('/SV000501/DetailPage.do?PRODNO=&{PRODNO}')
    
  5. Delete SV000501 and enter Project501.
  6. Save and close the file.
Note:
If at some point you want to run the SV000501 project again, you need to change the Project501 value back to SV000501, since this file exists on the iSeries server and is accessed by both projects.

To convert the DDS source:

  1. In the WebFacing perspective, click the WebFacing Projects tab to switch to the WebFacing Projects view if it is not already open by default.
  2. Expand Project501 > DDS.
  3. Select iSeriesserver > RETAILSTOR/QDDSSRC(ORDERDSP) and iSeriesserver > RETAILSTOR/QDDSSRC(QUERY) by clicking the first one and then holding down the Shift key while clicking the second one.
  4. Right-click and select Convert to begin conversion. You might need to enter your user ID and password if at some point you were disconnected from you iSeries server.

Configuring UTF-8 support in the workbench -- For WAS Version 4.0 users only

IBM WebFacing Tool applications support the display of multiple language on a screen. Because languages use different character sets, data streams between the browser and the WebSphere Application Server are UTF-8 encoded. For the IBM WebFacing Tool to function correctly, you need to configure UTF-8 support in the application's properties file in the workbench.

Note:
This section only applies to WAS 4.0 users. WAS version 5.0 performs this task automatically.

To configure UTF-8 support:

  1. Switch to the Web perspective (you can switch between perspectives by clicking the icons clustered on the left side of the screen).
  2. Click the Project Navigator tab so that you can see your project structures.
  3. Expand Project501 and double-click Web Deployment Descriptor.
  4. Click the Environment tab.
  5. Click the Add button.
  6. Switch to the Server perspective by clicking its icon on the upper left task bar, or click Perspective > Open > Other > Server from the menu bar, and then clicking OK.
  7. In the Navigator view, expand Servers folder.
  8. Double-click defaultInstance.wsi to open it in the default editor.
  9. Click the Environment tab and click the Add button.
  10. An editable value appears, "(New Variable)". Delete this default string and enter: client.encoding.override.
  11. In the Value field, enter UTF-8.
  12. Click the save icon or click File > Save Web Deployment Descriptor.

Configuring UTF-8 support for WebSphere Application Server

(Optional) If you want to deploy your iSeries application to WebSphere Application Server, you also need to configure UTF-8 support in WebSphere Application Server as well as the workbench.

To configure UTF-8 support in WebSphere Application Server 4.0 Advanced Edition
  1. Start the WebSphere Administrative Console.
  2. Expand the Nodes icon and expand Node name > Application servers > Default server.
  3. Select the JVM Settings tab and click the Advanced JVM settings button to open the Advanced JVM settings dialog.
  4. In the Command line arguments field, enter:
    -Dclient.encoding.override=UTF-8
    
  5. Click OK and click Apply under the JVM settings tab.
  6. For this change to go into effect for your WebSphere applications, stop the default server and then restart it. To stop the server, right-click Default server and select Stop. After this process is complete, right-click Default server and select Start.

To configure UTF-8 support in WebSphere Application Server 4.0 Advanced Single Server Edition
  1. Start the WebSphere Administrative Console.
  2. In the browser-based Administrative Console, expand the Nodes icon and expand Node name > Application servers > Default server > Process definition > JVM settings.
  3. Scroll to the Advanced Settings section of the JVM Settings page and click the System Properties link. The System Properties page is displayed.
  4. Click New to add a new System Property.
  5. In the Name field, enter client.encoding.override.
  6. In the Value field, enter UTF-8.
  7. Click OK. If you receive a Configuration needs to be saved message with a link at the top of the JVM settings page, click the link to go to the Save configuration page. Select Save and then click OK.
  8. For this change to go into effect for your WebSphere applications, stop the application server and then restart it. How you stop and start the application server can vary depending on the platform you have installed WebSphere Application Server on. Refer to the WebSphere Application Server documentation for your platform for information on stopping and starting the application server.


[ Top of Page | Previous Page | Next Page | Table of Contents ]