Chapter 7. Refining the browser interface 147
7.5 WebFacing properties
A set of properties is stored with the WebFacing project in the Web.xml file within the directory
WebContent\Web-INF. These properties control several aspects of the entire Web application
created by the IBM WebFacing Tool.
To edit the properties for a WebFacing project, in the WebFacing Projects view, right-click the
icon for your Project, CL commands, DDS, User Interface Manager (UIM) Help, or Style
folder, and select Properties. You can edit three types of properties, each of which are
explained in the sections that follow:
Conversion properties (page 147)
– Command key recognition patterns (page 147)
– Command key button labels (page 149)
– Edit code options (page 150)
– MNUDDS options (page 151)
– XML Record Metadata (page 152)
– Custom Tags (page 152)
Run-time properties (page 153)
– Project properties (page 153)
• CL command properties (page 156)
– DDS object mappings (page 157)
– UIM object mappings (page 157)
– Web (choosing the Java 2 Platform, Enterprise Edition (J2EE) specification level)
– Command key actions (page 158)
Style properties (page 159)
– DDS field color (page 160)
– DDS field display attributes (page 161)
– Window (page 162)
– Subfile (page 163)
– Command keys (page 164)
7.5.1 Conversion time properties
As the title Conversion time implies, the properties in this group are used when WebFacing
performs a conversion of your DDS into a Web application. This means that you need to
convert your project every time after changing any of the Conversion time properties
described in the following sections. The values for conversion properties are stored in the
conversion.rules file under the config directory of the WebFacing project.
Command key recognition patterns
An important part of WebFacing is the capability to implement the function of one or more of
the command keys F1 through F24 as buttons on your Web pages. Users click these buttons
to launch an event defined in your DDS source.
WebFacing uses text constants in your DDS to build the labels for those buttons. You can use
the Command Key Recognition Patterns pane to specify how to detect the text for command
key buttons to be displayed in a Web browser (see Figure 7-38).
You can define recognition patterns to control how command keys are detected. 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.
148 Mastering the IBM WebFacing Tool
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 change the placement
of recognition patterns in the table so that they appear in the order that you prefer.
Figure 7-38 Command key recognition patterns
In addition, you can choose one of the following options:
Remove text: This is the default. After recognizing the description for a command key and
using it as a button label, WebFacing removes the constant from the Web page.
Keep text: If a button label is generated, the same text appears on the Web page where it
was defined in DDS.
Replace text with button for all records: This is a special function for WebFacing styles
which do not provide a separate area for command key buttons. The button appears on
that position where the DDS defined the descriptive text constant to be. This capability is
used with the predefined WebFacing style
textbuttons as described in “textbuttons” on
Replace text with button for all window records: This is the same as “Replace text with
button for all records”, but it applies only to DDS panels using the WINDOW keyword,
which are implemented by WebFacing as an additional browser window.