oracle forms lookandfeel

There are 2 parameters in formsweb.cfg responible for how an oracle forms looks:

lookAndFeel       Optional, determines the applications look-and-feel. Legal
                  values: Oracle or Generic (Windows 95 look-and-feel)
colorScheme       Optional, determines the application's color scheme. Legal
                  values: Teal, Titanium, Red, Khaki, Blue, Olive, or Purple.
                  Note: colorScheme is ignored if lookAndFeel is set to Generic

Webforms Parameter Overview [ID 118632.1]
    
        
    
        
 
        
Modified 01-DEC-2010     Type BULLETIN     Status PUBLISHED
        
 
    

Applies to:

Oracle Forms - Version: 6.0.8 to 10.1.2 - Release: 6.0.8 to 10.1.2

Purpose

This document describes all possible parameters which can be used in the html file for webforms.

Scope and Application

The intent of this document is to provide a list and the use of the available parameters.

NOTE: Not all of the parameters listed in this document are available with all versions of forms. See the "Deploying Forms Applications to the Web" On-line Help manual for the details relavent to your version of forms.

Webforms Parameter Overview

Webforms HTML File Parameters
-----------------------------

The HTML File
=============
The html file contains two sections, one for use with Microsoft Internet
Explorer, the other for use with Netscape Navigator. In both sections the same
parameters can be used, however, the syntax may be slightly different.

For Microsoft Internet Explorer, the section in the static html file is
specified using this syntax:

<OBJECT
<parameter>="<value>"
...
>

This first section specifies parameters used by Internet Explorer browser
define the characteristic for the browser. Forexample, as classid, codebase,
WIDTH, HEIGHT, HSPACE and VSPACE.

<PARAM NAME="<parameter>" VALUE="<value>">
...

The second set of tags are used to define the parameters for the Forms Applet
rather than the charateristics for the browser. The syntax for these tags is:

<PARAM NAME="<parameter>" VALUE="<value>">


For Netscape Navigator, the same syntax is used for all parameters:
<COMMENT>
<EMBED
<parameter>="<value>"
...
<NOEMBED>

The parameters are specified in 'n' lines of
<parameter>="<value>"


The Parameters
==============

Note that the parameter name is case sensitive. The following parameters are
available at this writing:

Parameter name Usage
-------------------------------------------------------------------------------
classid Required, Internet Explorer Object tag only. Specifies the
Jinitiator version used. If the classid is not found in the
registry, the form will not run or Jinitiator will be
downloaded again.
codebase (1) Optional, Internet Explorer Object tag only. Specifies the
jnintiator version to be used for the form called from the
html file and the location from where to automatically
download the appropriate version.
CODEBASE/ Required, virtual directory you defined to point to the
java_CODEBASE physical directory <ORACLE_HOME>\forms60\java
In the Netscape Navigator section called java_CODEBASE
CODE/ Required, do not remove or modify the code parameter.
java_CODE Its value should always be: oracle.forms.engine.Main
In the Netscape Navigator section the parameter is java_CODE.
connectMode Required for HTTP and HTTPS connections; optional for socket
connection.
Specifies to the client the type of connection protocol to
use with the Forms Server. Valid values are socket, http, and
https. The default is socket. When using the Listener Servlet,
this parameter is ignored and the value taken from the
calling URL.
pluginspage Optional, Netscape Navigator section only, specifies the url
to activate in order to download the required Jinitiator
version if not available on the web client. The Internet
Explorer equivalent parameter for downloading Jinitator is
codebase.
pluginurl Optional, like pluginspage, but will activate the download
immediately. For Netscape only.
ARCHIVE/ Optional, comma-separated list of archive files to preload.
java_ARCHIVE Paths, if not absolute, are relative to codebase.
In the Netscape Navigator section called java_ARCHIVE
cabBase Optional, needed when using IE5 native mode. This has to point
to the cabinet file (f60all.cab) on the application server.
WIDTH Required, Object tag for Internet Explorer. Specifies the
width of the Form, in pixels
HEIGHT Required, Object tag for Internet Explorer. Specifies the
height of the Form, in pixels
align Optional, left|center|right|top|middle|bottom
alt Optional, text displayed instead of applet (if browser does
not support applets)
hspace Optional, horizontal gutter, in pixels
vspace Optional, vertical gutter, in pixels
type Required, hard coded value ("application/x-jinit-applet" for
JIniniator; no value required for AppletViewer)
name Optional, applet instance name
title Optional, advisory title string
border Optional, border to display
standby Optional, text to display when loading
codetype Optional Defaults to type
serverHost Optional, host on which the Forms Server runs. Defaults to
Web listener machine
serverPort Required, port on which the Forms Server listens. In most
cases, the port number will remain 9000 or 9001, the default.
When using the Listener Servlet, this parameter is ignored.
serverURL Required for the Listner Servlet. This specifies the location
of the ListenerServlet class file used for this configuration.
If this parameter is specified, then the parameters serverHost,
serverPort and connectMode are ignored.
Example: /servlet/oracle.forms.servlet.ListenerServlet

serverArgs Required, command-line parameters for Runform on the web.
Replace forms_param with any valid Form Runtime command-line
parameter. Replace user_param with any valid user-defined
parameter. For example,
<paramname="serverArgs" VALUE="module=order.fmx">
Notes:
You can provide multiple Form Runtime command-line and
user-defined parameters.
You must provide a physical directory path for the .FMX file
by including a directory path by defining the FORMS60_PATH
environment variable.
The .FMX suffix is optional
serverUserParams Optional, accepts NLS environment settings, and in the future
may accept arbitrary environment settings.
Its format is similar to the existing serverArgs parameter;
it takes a space separated list of token=value pairs. An
example of how it might appear in a jinitiator document is:
serverUserParams="NLS_NUMERIC_CHARACTERS='.,'
NLS_LANG=DUTCH_THE NETHERLANDS.WE8ISO1859P1"
networkStats Optional, can be used for monitoring the network traffic.
Setting this parameter to TRUE will display two numbers in
the status bar. These numbers represent the total number of
bytes and round-trips that have occurred thus far.
networkRetries Optional, can be used to set the number of retires when
connect to the server not possible. Details see:
Note:332942.1 Understanding How networkRetries Works

splashScreen Optional, specifies the .GIF file that should appear before
the applet appears. Set to NO for no splash. Leave empty to
use the default splash
background Optional, specifies the .GIF file that should appear in the
background. Set to NO for no background. Leave empty to use
the default background
clientDPI Optional, specifies the dots per inch (DPI) and overrides the
DPI setting returned by the JVM, allowing you to manage
varying DPI settings per platform. For example, a form
developed on the Win32 platform may not display properly on
the UNIX platform due to varying DPI values. The clientDPI
value can be any positive integer. Oracle recommends that you
use an integer between 50 and 200.
<param name="clientDPI" value="200">
separateFrame Optional, determines whether the applet appears within a
separate frame. Legal values: True or False
lookAndFeel Optional, determines the applications look-and-feel. Legal
values: Oracle or Generic (Windows 95 look-and-feel)
colorScheme Optional, determines the application's color scheme. Legal
values: Teal, Titanium, Red, Khaki, Blue, Olive, or Purple.
Note: colorScheme is ignored if lookAndFeel is set to Generic
darkLook Optional, accepts either true or false. If set to true the
components in the form takes the background and foreground
color based on the colorScheme.
Note: darkLook is ignored if lookAndFeel is set to Generic
See bug:1394076 for availability
logo Optional, specifies the .GIF file that should appear at the
forms menu bar. Set to NO for no logo. Leave empty to
use the default Oracle logo
readOnlyBackground Optional, specifies the background color of read only items.
Setting it to True, gives a grey background (the Oracle look
and feel. False gives a white background and Automatic will
set the background to gray for read-only fields unless the
colour is set to a non-default value. The colour will revert
back to gray if it is set back to default.
serverApp Optional, replace default with the name of your application
class (if any). Use application classes for creating
application-specific font mapping and icon path settings
heartBeat Optional, use this parameter to set the frequency at which a
client sends a packet to the server to indicate that it is
still running. Define this integer value in minutes. The
default is two minutes
imageBase Optional, use this parameter to indicate where icon files are
stored. Choose between:
- codeBase, which indicates that the icon search path is
relative to the directory that contains the Java classes.
Use this value if you store your icons in a JAR file
(recommended).
- documentBase, which is the default. In deployments that
make use of the Forms Server CGI, you must specify the icon
path in a custom application file.
registryPath Optional, use this parameter to list the virtal directory
where the application file named in the serverApp parameter
is located
webformsTitle Optional, use this parameter to change the title that appears
in the top border of the forms display window.
clientBrowser Optional, this parameter is relevant when you use run_product
or run_report_object (output to screen and preview) to
display the generated HTML or PDF report and you start your
application using the Appletviewer. Because the Appletviewer
cannot display HTML or PDF you will need a Browser to perform
this task. Set the clientBrowser to netscape or iexplore for
use with Windows Clients.
You have to make sure that the browser you specify is in the
search path on the client
proxyHost Optional, this parameter is used when you use connectMode
HTTP or HTTPS and your forms Server should be reached via a
proxy Server. When no Proxy Server is used the parameter can
be set to the ServerHost or can be omited.
proxyPort Optional, used when you use connectMode HTTP or HTTPS and
your forms Server should be reached via a proxy Server in
which case this parameter is used to specify the port number
of the proxy server. When no Proxy Server is used the
parameter can be set to the ServerPort or can be omited.
dontTruncateTabs Optional, this is a boolean option to turn on/off truncation
of tab labels when the tab panel is not wide enough to
display all the labels
java_showprogress Optional, setting this parameter to "true" enables a progress
dialog during the initial download of the JAR files used by
the forms applet
java_appletname Optional, specifies the name of the product. Defaults to
"Applet". The product name is used in the titlebar of the
progress dialog and is preceded by the word "Starting".
Therefore by default the progress dialog title is
"Starting Applet"
java_progressimage Optional, specifies the URL to a splash screen image. The
image can be either GIF or JPG format. The image can be any
size, and can be animated. Note that the dialog will not be
shown until the image is downloaded, so the file size of the
image will affect the speed with which the dialog comes up.
The image will be shown at the top of the dialog. If the
image is not as wide as the other components in the dialog,
it will be centered in the dialog and blank space will appear
to the sides of the image
java_progressjars Optional, lists the JAR files that the progress dialog should
track. If this parameter is not specified,all JAR files in
the applet tag will be tracked by the progress dialog.
This parameter is useful if you have JAR files on your
archive tag that are not loaded at startup (that is,
on-demand JAR files). Uses the same format as the ARCHIVE tag
to specify the list of the JAR files.
jinit_appletcache Optional, controls how applet caching is handled by the
Jinitiator. Valid values are 'off' and 'on', with on as the
default.
to the documents location.
MetricsDomainName Required for cartridge load balancing only and is obsolete.
For load balancing. Specifies the domain of your Load
Balancer Client server machine. This is a load balancing
parameter that must be used with the LEASTLOADEDHOST
parameter. In your HTML file, the metricsDomainName parameter
must immediately follow the LEASTLOADEDHOST parameter. For
example,
ARCHIVE="http://%LEASTLOADEDHOST%%metricsDomainName%/forms60java"
LEASTLOADEDHOST Required for cartridge load balancing only.
During load balancing, this fixed-name place holder is
replaced dynamically by the cartridge with the name of the
least-loaded system. The cartridge gets this information from
the Metrics Server at runtime. This parameter is obsolete.
latencyCheck Optional. The forms Network Latency Meter tests the network
in a mode that is similar to the way Forms server will use the
network by simulating typical messages between the applet and
the Forms Server. The latency meter measures the response time
of the network and reports the average response time.
This is a new feature in Forms 6.i. When you set this
parameter to value true, double clicking the status bar will
start the latency meter and reports the network latency.

Parameters no longer working with Forms 6.0 and higher:
helpBookName Optional, specifies the name of a help book
helpBookPath Optional, specifies the help book URL, absolute or relative

References

BUG:1366851 - WEBFORMS: NO DOCUMENT FOR 'HELPBOOKNAME' AND 'HELPBOOKPATH' IN BASE HTML
NOTE:118515.1 - How To Show The Download Progress Dialog Using Jinitiator
NOTE:166486.1 - Browser Refresh or Reload Does not Work in Webforms Using Jinitiator
NOTE:197268.1 - JInitiator Applet Caching Behaviour in Jinit 1.3.x
NOTE:276651.1 - How To Change or Disable Logo, Background and SplashScreen
NOTE:332942.1 - Understanding How networkRetries Works
NOTE:556614.1 - How To Center Application Form