Use these screens to view and edit conversion properties. Conversion properties control how selected DSPF and UIM files are being converted for WebFacing use. Values for conversion properties are stored in the file conversion.rules under the config directory of the WebFacing project.
Use the Command Key Recognition Patterns to specify how to detect the text for command key buttons to be displayed in a Web browser. When converted, command keys are displayed as buttons on your Web pages. Clicking these buttons is the same as pressing the corresponding command key.
You can define recognition patterns to control how command keys will be displayed. To define a recognition pattern, specify a prefix value in the Prefix field and a separator value in the Separator field, and then click Add. The pattern is added to the list of recognition patterns. When a pattern is recognized during conversion, the value for the text on the Web page button is taken from what is listed after the separator in your DDS source. For example, a recognition pattern with a prefix F and separator = converts the source F4=Prompt to a button with the text Prompt and the source F5=Refresh to a button with the text Refresh. To delete a recognition pattern, select the pattern from the list of recognition patterns and click Delete. You can also use the Move Up and Move Down buttons to alter the placement of recognition patterns in the table so that they appear in the order that you prefer.
Use the Key Button Labels to specify the default text for keys identified during conversion that do not match a defined recognition pattern. For example, if no recognition pattern has been defined that would match F1=Help, you could specify the value for the Key field as F1 and the value for Button label as Help. When converted, keys are displayed as 'Help' buttons on your Web pages. Users click these buttons to launch an event defined in your DDS source such as to refresh their page or to get online help.
Use the Key and Button label fields to specify the default text for keys and then click Add. The key and its label will then be added to the key list. If you want to delete a key label, select it from the key list and select Delete.
There are several ways you can define the label for a function key in your WebFacing applications. If more than one label is defined for a key, WebFacing conversion and run time will use the following priority table to determine which label will appear in the browser. The key label that will be used is the one with higher priority.
Priority | Source of key label text | Scope of setting |
---|---|---|
1 (highest) | Command Key Actions in WebFacing project Run Time properties | Project |
2 | Dynamic key labels Web Setting | Field |
3 | Key labels Web Setting | Record |
4 | Key labels Web Setting | File |
5 | Command Key Recognition Patterns in WebFacing project Conversion properties Note: Function keys labels cannot be obtained using this method. Only command key text constants can be recognized in this way during conversion. | Record |
6 | DDS-defined "text" parameter for keyword | Record |
7 | DDS-defined "text" parameter for keyword | File |
8 (lowest) | Key Button Labels in the WebFacing project Conversion properties | Project |
Select the edit codes to map for conversion. Click Add. The mapping appears in the list. Click OK when you have made your selection.
If you have selected DDS members of type MNUDDS for conversion, use the MNUDDS Options to convert the menu options into hypertext links. The command option number and any text included in the same field where that number is found will be converted into a hypertext link. The option of automatically converting commands into hypertext links is selected by default. In the Separator drop-down list, specify a separator to identify the menu options. The default separator is the period (.). The other separators available for selection are the equal sign (=), colon (:), and dash (-).
Click OK when you have made your selection.
The WebFacing conversion generates XML files that describe the data associated with each record format. By default, these files are archived in JAR files. Archiving the XML in JAR files can make deployment more efficient because when your project's EAR or WAR file is installed on an application server, only a single JAR file is deployed for your DDS data. Some large projects can have thousands of XML files and deploying these as un-archived files increases the time required to install your application.
Depending on your project, though, you may not want the XML stored in a JAR file. Working with un-archived XML files can facilitate change management. A scenario where this might apply would be if more than one developer was working on a WebFacing project. For example, you might convert part of your application's DDS while another developer converts the rest and the overall project is stored in a repository like CVS. If the generated XML was stored in JAR files, one JAR file would overwrite the other in your repository.
Use these screens to view and edit runtime properties. Runtime properties determine the behavior of the converted Web application when it is being used by an end user.
Values for project properties are stored in the deployment descriptor file web.xml. The following properties appear under the General tab.
The following properties appear under the Authentication tab.
For each CL command of your WebFacing project, an entry is created in the invocations.jsp file, which is included in the index.jsp file. A corresponding section in the deployment descriptor file web.xml is also created for each link.
Values for DDS object mapping are stored in the file DSPFObjectMapping.properties, which is located under the \conf\ path in your Java™ source directory. Information about object mappings is available in the comments area of the corresponding screen. Mapping information is displayed in the editable text area of the screen.
Values for UIM object mapping are stored in the file UIMObjectMapping.properties. Information about UIM object mappings is available in the comments area of the UIM Object Mappings screen, and the actual mapping information is displayed in the editable text area of the screen.
This option displays the J2EE (Java 2 Platform, Enterprise Edition) specification level for your WebFacing application. To change the J2EE level, right-click the project and select Migrate > J2EE Migration Wizard.
See Extending your WebFacing application with command key actions in the Developing i5/OS WebFacing applications > Customizing your WebFacing applications section of the WebFacing online help.
If you select the check box, all system screens are rendered at run time by dynamic data stream transformation (or by HATS for linked HATS/WebFacing projects), allowing all system screens to share the same look and feel. If you deselect the check box, WebFacing uses built-in Web pages for system screens like DSPSPLF (to display a spool file), which may provide faster response times.
Built in system screens include the following:
Use the Style properties screens to customize the appearance of your converted pages. You can customize the look of the application area and the command keys using the Style properties.
For the classic WebFacing syles, if you want to change the look of the layout and frame surrounding these areas, you must use a CSS editor to update the style files stored in the chrome directory. For more information on how to edit the layout or frame, see the related topic Creating and modifying styles.
For the Web Site Designer style, if you want to change the look of the layout and frame surrounding these areas, right-click the .websit-config icon and select under the Navigator tab of the IDE. Then you can select the Index icon and edit the page template to change the look and layout. For more information on how to use the Web Site Designer tools, see the related topic Using the Web Site Designer style.
Changes to the styles made through the property pages or by direct editing apply only to the current project.
Use the DDS field color screen to indicate how you want DDS field colors to be treated when they are converted for Web use. For example, you can specify that a blue DDS field be displayed as some other color on the Web. You can also control the text and background color for your fields when you use the reverse image display attribute.
Use the DDS field display attributes screen to indicate how you want DDS field display attributes to be treated when they are converted for Web use. For example, you can specify that a blinking DDS field be displayed as italic font on the Web.