Wednesday, March 22, 2000

Wednesday, March 22, 2000 4:26pmPage 1

1.11.21.322.12.22.32.42.52.62.6.12.6.22.6.32.72.82.92.102.112.122.132.142.152.162.172.182.192.202.212.222.232.24

Purpose Of This DocumentRestricted Rights LegendServer LicensingG e n e r a l C o n s i d e r a t i o n sName and Packaging ChangesRelationship of Release 6i to Release 6.0Release NumberingRSF Components Include Additional Bug FixesDate HandlingKnown LimitationsCo-existence in the same $ORACLE_HOME with Previous ReleasesPLL File Upgrade Requires .PLL Extension on Command LineNon-Alphanumeric Characters in Database Objects NamesMotif Patch on SolarisPrecompilers Compatible With This ReleaseORAINFONAV_DOCPATH Environment Variable on UnixOracle File Packager Not IncludedSequence of Installing in the Same ORACLE_HOMEPath Requirement for Multiple ORACLE_HOMEsMisleading Installation Message: Acrobat Reader AvailableMisleading Installation Message: Folder MovedDatabase Admin Scripts Require OTMAdditional Step Required for Installation on UnixModule MFC42.DLL Lost After Install and RebootTEMPLATES Directory Is MissingForms Requires WebDB Release 2.2WebDB Listener Can Be Installed Only Once per MachineProblem Connecting to Oracle 8.1.6 ServerProblem Connecting to Oracle 8.0.6 Server for Forms-GraphicsUpgrading Your Database Server AgentCustom Install of Wallet Manager Requires Net8 Assistant

Copyright (c) Oracle Corporation 1998, 1999, 2000. All rights reserved,worldwide.

ORACLE FORMS DEVELOPER AND FORMS SERVER 6i RELEASE NOTES

This doc addendum is accurate to the best of our knowledge at the time of going to press. Information that is discovered subsequent topublication will be available through normal support channels.

-------------------------- Table of Contents --------------------------


2.252.262.272.282.29344.14.24.2.14.2.24.2.34.34.44.4.14.4.24.4.34.54.64.74.84.94.104.114.124.134.144.14.14.14.24.14.34.14.44.154.15.14.15.24.15.34.15.44.15.54.15.64.15.74.15.74.164.16.14.16.2

Integration with Oracle RepositoryClient Platform CertificationsSet the Doc60 Environment VariableOracle Forms Server and Firewall/Proxy ServersUse Caution If Deinstalling Intersolve DriversP r o j e c t B u i l d e rF o r m B u i l d e rEffect of Fill Patterns on PerformanceUndocumented Error Messages(FRM-99999)Error Messages 1412 and 1413Error Messages 10905-10909Error Messages 18114-18121Forms Environment Variable AddedJava Keybindings API ProvidedFormAction.javaKeyBinder.java -- Using the APIExample of KeyBinder.java APIOn Windows, Forms Server and Web Previewer Require NTServer Does Not Work If Host and Machine Name DifferRequirements for Using Run_Product on the WebDatabase Commands Available on Separate Start MenuUsing Index-Only TablesForms Server Needs to Access the Wallet FileNetscape Users Prompted to Save Report HTML FileForms-Reports Integration Requires that TMPDIR Not Be SetChanging Font Causes Problem in FormsPerformance Collection Services Now AvailableHow to Use Performance Collection ServicesEvents Collected by Performance ServicesAnalyzing the Performance DataDefault EventsUsing Oracle Trace Instead of PECS for Performance AnalysisInitiating Trace Data CollectionUsing the Oracle Trace Command-Line InterfaceOracle Trace Collection FilesEvents Collected by TraceUsing the Oracle Trace Statistics Reporting UtilityViewing the Trace DataTrace TablesTrace Tables -- continuedHow to Deploy a Certificate from a Non-Trusted AuthorityCreate a Wallet Using the Oracle Wallet ManagerCreate a Certificate Request


4.16.34.16.44.16.54.17566.16.1.16.1.26.27891011121313.113.1.113.1.213.1.313.1.413.1.513.1.613.1.713.1.813.213.2.113.313.3.113.3.213.3.313.3.413.3.513.3.613.3.713.3.813.413.4.1

Install the Trial CA Root Certificate Replace the certdb.txt of Jinitiator with the New VersionImport the User CertificateInstalling OEM: Clarification to InstructionsR e p o r t B u i l d e r G r a p h i c s B u i l d e rAdditional Steps Required for CartridgeAdditional Cartridge Installation Steps for NTAdditional Cartridge Installation Steps for SolarisEnvironment Variables Must Be Set on UnixQ u e r y B u i l d e rS c h e m a B u i l d e rT r a n s l a t i o n B u i l d e rP r o c e d u r e B u i l d e rD e m o sO p e n C l i e n t A d a p t e rN a t i o n a l L a n g u a g e S u p p o r tKnown Problems for All LanguagesForm Builder User Interface May Not Be Fully TranslatedEuro Currency Symbol Has Limited SupportSome Wizard Buttons Have Untranslated TextRestore Icons During Installation Creates Invalid MenusMenu Action Not Available Via Keyboard After Print CancelFMRWEB.RES Must Be Configured ManuallyInformation About NLS_LANG Parameter ValuesWallet Manager User Interface Is in EnglishKnown Problems for Double-Byte LanguagesEditing with Single-Byte FontKnown Problems for JapaneseCannot Save Modules If Character Set Is JA16EUCLength Limit Moving From Windows to SolarisPL/SQL Editor Display ProblemsUTF8 LimitationMultibyte Characters Cannot Be Used for PL/SQL Library NameDifferent prefs.ora Files May Be NeededMessage Texts from PL/SQL Interpreter Are MixedStorage Requirement for Installing Cue Cards on UnixKnown Problems for ArabicLimitations for Displaying Charts on Solaris


1.1

1.2

1.3

2

2.1

Purpose Of This Document

Restricted Rights Legend

Server Licensing

G e n e r a l C o n s i d e r a t i o n s

Name and Packaging Changes

This document notes differences between Oracle Forms Developer andForms Server and their documented functionality.

This software contains proprietary information of OracleCorporation; it is provided under a license agreement containingrestrictions on use and disclosure and is also protected bycopyright law. Reverse engineering of software is prohibited.

If this software/documentation is delivered to a U.S. GovernmentAgency of the Department of Defense, then it is delivered withRestricted Rights and the following legend is applicable:

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure of thePrograms by the Government is subject to restrictions as set forthin subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights inTechnical Data and Computer Software (October 1988). OracleCorporation, 500 Oracle Parkway, Redwood Shores, CA 94065.

If this software/documentation is delivered to a U.S. GovernmentAgency not within the Department of Defense, then it is deliveredwith Restricted Rights as defined in FAR 52.227-14, Rights in Data-General including Alternate II (June 1987).

The information in this document is subject to change withoutnotice. If you find any problems in the documentation, pleasereport them to us in writing. Oracle Corporation does not warrantthat this document is error free.

Please note that if you want to deploy your Forms or Graphics to theInternet, you need the Oracle Forms Server, and its associateddeployment license.

Forms Server is included on the general Forms Developer CD-ROM fordemonstration and test purposes, but is licensed separately.

Please contact your Oracle Sales Representative to get additionalinformation on Forms Server pricing.


2.2

2.3

Relationship of Release 6i to Release 6.0

Release Numbering

In this release, Oracle Developer has become two separate products:Oracle Forms Developer and Oracle Reports Developer. Each containsmultiple Builders.

Similarly, Oracle Developer Server has become two separate products: Oracle Forms Server and Oracle Reports Server.

Release 6i is a "drop-in upgrade" to Release 6.0. This means Release6i is patch-compatible with Release 6.0.

With Release 6i, providing you are not implementing new 6i-specificfunctionality, you get the same benefits as when you take a patchset. Benefits include no required regeneration of fmx files, a drop-in installation, and QA certification. You should still schedulepatch-set-level testing, as is recommended when any patch-set isapplied. (Note that this may require upgrading to the latestcertified client and middle-tier stack.)

The initial release of 6i includes all the fixes in 6.0 throughpatch set 4, and most of the fixes in patch sets 5 and 6 (only bugs892177, 995498, 1086525, and 1120902 are not included).

The first Release 6i patch set (slated for 16 weeks afterproduction) will be a cumulative patch that will roll forward theremaining items from Release 6.0 patch sets 5 and 6, and all of 7,as well as providing any additional 6i-specific fixes. The finalRelease 6.0 patch set (patch set 7) is slated for mid-April 2000.

For customers with production systems on these latest patch sets forRelease 6.0 (patch set 5 or 6) or who are waiting for fixes in thefinal Release 6.0 patch set 7, it is recommended that you remain onRelease 6.0 and plan to upgrade to Release 6i in the timeframe ofthe first 6i patch set. Release 6.0 customers who (a) do not intend to take advantage of any6i features, (b) do not have any bugs they consider serious, and (c)do not intend to upgrade their stack in any way, are not required toupgrade to 6i. Customers who plan to build new applications or are using Release6.0 with a patch set prior to patch set 5 are recommended to utilizeproduction Release 6i.

In this initial 6i release of Oracle Forms Developer, most of themajor components (Form Builder, Graphics Builder, etc.) have a 6.0.8version number. Most of the subcomponents (Toolkit,for example)


2.4

2.5

2.6

2.6.1

2.6.2

2.6.3

RSF Components Include Additional Bug Fixes

Date Handling

Known Limitations

Co-existence in the same $ORACLE_HOME with Previous Releases

PLL File Upgrade Requires .PLL Extension on Command Line

Non-Alphanumeric Characters in Database Objects Names

have a 6.0.5 version number. These are the appropriate versions ofthe subcomponents for this initial release.

It is expected that in the first patch release for 6i, thesubcomponents will be renumbered to a 6.0.8 level.

This release of this product includes some RSF components thatcontain code fixes beyond those in the formal, numbered patches tothe component. (These fixes or patch-levels of a component aresometimes referred to as "one-offs.")

Specifically, this release includes fixes for bugs 1063571, 1063104,1028960, 1049171, and 1040536. These bug fixes affect the followingcomponents: sqlnet, rdbms, nls and plsql.

For important information about date handling in Oracle FormsDeveloper, please refer to http://www.oracle.com/year2000/ andfollow the link to White Papers and Resources.

Oracle Developer 1.6.1 and Oracle Forms Developer 6i can co-exist inthe same $ORACLE_HOME.

Oracle Developer 2.1 and Oracle Forms Developer 6i can co-exist inthe same $ORACLE_HOME.

Oracle Developer 1.6.1 and Oracle Developer 2.1 CANNOT co-exist inthe same $ORACLE_HOME.

Oracle Developer 6.0 and Oracle Forms Developer 6i CANNOT co-existin the same $ORACLE_HOME.

If you are using a batch file to upgrade .PLL files, then you haveto provide extension .pll in the batch file. Otherwise you get anerror "FRM-10043: Could not open file".


2.7

2.8

2.9

2.10

2.11

2.12

Motif Patch on Solaris

Precompilers Compatible With This Release

ORAINFONAV_DOCPATH Environment Variable on Unix

Oracle File Packager Not Included

Sequence of Installing in the Same ORACLE_HOME

Path Requirement for Multiple ORACLE_HOMEs

Oracle Forms Developer 6i cannot support Tables, or Columns namesthat contain non-alphanumeric ASCII characters.

Motif 1.2 runtime library patch 105284-20 is the minimum patch levelfor Oracle Forms Developer and Forms Server 6i on Solaris 2.6.

If you are developing user-exits for Oracle Forms Developer 6i usingthe Oracle Precompilers, please use the versions of the Precompilersthat are bundled with the Oracle 8.0.6 release.

On Unix platforms, the ORAINFONAV_DOCPATH environment variableshould be set to the location of the online manuals. The defaultvalue for this environment variable is set to the location of theAmerican English version of the online manuals($ORACLE_HOME/doc60/admin/manuals/US). If you are interested in theJapanese version of the online manuals, you should set theORAINFODOC_DOCPATH environment variable to:$ORACLE_HOME/doc60/admin/manuals/JA

The Oracle File Packager (mentioned in the Forms Developerdocumentation) is not included as part of this 6i product.

If you choose to install both Forms Developer R6i and the DatabaseServer 8.0.6 in the same ORACLE_HOME, you should install theDatabase Server first, and then install Forms Developer. Thissequence will prevent library linking conflicts.

In order for the Forms CGIs (ifcgi60.exe or rwcgi60.exerespectively) to run successfully on NT when there are multipleORACLE_HOMEs, it is imperative that the %ORACLE_HOME%\bin directoryfor Forms be in the machine's PATH environment setting, ahead of anyother <ORACLE_HOME>\bin directories.

This path setting has to have been in effect WHEN THE MACHINE WAS LAST BOOTED, in order for it to be "seen" by the CGI (assuming thatwhatever Web Listener the user is using is being run as an NTservice, which will usually be the case).


2.13 Misleading Installation Message: Acrobat Reader Available

If these conditions are not met, there are two possibleconsequences:

1. The CGI's may fail to run because one or more DLLs on which theydepend, such as core40.dll, cannot be found. This occurs if the%ORACLE_HOME%\bin directory is not present in the PATH. 2. The CGI's may crash, because an incompatible version ofcore40.dll is being used. This can occur in the case of multipleORACLE_HOMEs, if an ORACLE_HOME other than that into which Forms orReports was installed appears in the PATH before the Forms orReports ORACLE_HOME).

Of these, situation #1 should not normally be a problem, because theinstallation process always adds %ORACLE_HOME%\bin to the PATH andinstructs the user to reboot the machine if one of the CGI's wasinstalled.

Situation #2 is known to occur if you install Forms into oneORACLE_HOME, then install OEM into a separate ORACLE_HOME (which isin fact mandatory). This second ORACLE_HOME's bin directory will beadded into the machine's PATH environment setting, by theinstallation process, ahead of the first one (giving for example c:\orant2\bin;c:\orant1\bin;c:\winNT\system32;...etc). Once theuser reboots, this will cause the Forms CGIs to fail.

Workarounds: 1. Install OEM (into its own separate ORACLE_HOME) BEFORE installingForms (into a different ORACLE_HOME). Then reboot. This worksbecause the "last" ORACLE_HOME installed into is left as the DEFAULTORACLE_HOME.

2. Use the "ORACLE HOME SELECTOR" to ensure that the ORACLE_HOMEwhere Forms was installed is the DEFAULT ORACLE_ HOME. The "ORACLEHOME SELECTOR" may be found in the Oracle for Windows NT programfolder).

3. Manually correct the PATH setting and reboot.

After installing components from the asset manager, you may see thefollowing message:

"Installation Successful. Some of the products you have installedrequire the Adobe Acrobat Reader. If you do not already have thisinstalled on your machine, you should select it from the 'Products


2.14

2.15

2.16

2.17

2.18

Misleading Installation Message: Folder Moved

Database Admin Scripts Require OTM

Additional Step Required for Installation on Unix

Module MFC42.DLL Lost After Install and Reboot

TEMPLATES Directory Is Missing

available' list."

However, the Acrobat Reader is not in this particular list.

Acrobat can be obtained from http://www.adobe.com.

When Release 6i is installed, the following message may appear:

Oracle Developer 6.0D:\winnt\Profiles\All Users\Start Menu\Programs\oracle\OracleDeveloper 6.0 is not accessible. The folder was moved or removed.

Ignore this message. Press OK. There is no impact on the productfunctionality.

The Database Admin build/drop scripts will fail if they do not findOracle Translation Manager SQL scripts.

This problem can be avoided by first explicitly installing OracleTranslation Manager from the product CD.

In order for the Forms Developer help system to work properly on aUnix system, you must set the ORACLE_AUTOREG variable to the value$ORACLE_HOME/guicommon6/tk60/admin. (The help system requires theautoprefs.oar file, which is the toolkit automation registry.)

Problem: On Windows 95, after installing and rebooting, module MFC42.DLL is missing.

Workaround: Invoke the Installer again. Get to the first dialog. Then exit. Installer will install mfc42.dll if it is not present in the machine.

In the manual Oracle Forms Developer and Reports Developer:Guidelines for Building Applications, references are made toTEMPLATES/.... However, the TEMPLATES directory is not includedwith the product.


2.19

2.20

2.21

2.22

2.23

Forms Requires WebDB Release 2.2

WebDB Listener Can Be Installed Only Once per Machine

Problem Connecting to Oracle 8.1.6 Server

Problem Connecting to Oracle 8.0.6 Server for Forms-Graphics

Upgrading Your Database Server Agent

Use a different method to invoke the Oracle Installer.

If you are going to use WebDB with the Forms Server, WebDB 2.2 orhigher is required.

Only one copy of WebDB Listener can be installed on a machine. Ifyou try to install a second copy in another Oracle_Home on that samemachine, the first copy may stop working.

Customers may not be able to connect to the 8.1.6 database from anyof the Oracle Forms Developer products using operating systemauthentication. (This problem is due to bug 1139334 in the databaseserver.)

Problem: Forms-Graphics integration does not work correctly when the connection to a local Oracle 8.0.6 database server is made with only a userid and password (for example, scott/tiger).

Workaround: Define the local database in the tnsnames.ora file. Then provide a complete connect string when connecting to the database. (For example, scott/tiger@local806.)

Forms Developer 6i comes with an 8.0.6 agent with a Forms extensionin the same Oracle_Home as Forms. If you already have an existingagent installed, or you want to upgrade to a later version of theagent, a manual step is necessary to install the Forms extension toyour agent.

Please note that any agent other than 8.0.6 cannot be installed inthe same Oracle_Home as Forms, and only one agent should be used ata time. Also, we highly recommend staying with the 8.0.6 agent.

These installation steps, below, are the same for both Windows NTand UNIX. (Please note that the files are platform-specific, and youshould not copy files across platforms.)


2.24

2.25

2.26

Custom Install of Wallet Manager Requires Net8 Assistant

Integration with Oracle Repository

Client Platform Certifications

Follow the steps below to manually install Forms support for youragent. (Currently 8.0.6, 8.1.5, and 8.1.6 are supported). Theseparticular instructions assume that an agent with the Formsextension is installed in Oracle_Home $OH, and you want to copy theForms extension from $OH to an agent installed in Oracle_Home $OH2.

1. Copy $OH/network/agent/Jobs/Oracle/forms/general/* to thecorresponding directory (create one if necessary) in $OH2. 2. Copy $OH/network/agent/Events/Oracle/forms/fault/* to thecorresponding directory (create one if necessary) in $OH2. 3. Copy $OH/network/agent/Tcl/frminit.tcl to the correspondingdirectory in $OH2. 4. Copy $OH/network/agent/config/nmiforms.tcl to the correspondingdirectory in $OH2. 5. Append this entry "nmiforms.tcl" to the end of nmiconf.lst,located in $OH2/network/agent/config. (nmiconf.lst is a text file).

Wallet Manager requires Net8 Assistant in order to launchsuccessfully.

In the typical, default install of Forms Developer, both thesecomponents will be installed for you.

However, if you choose a custom install, where you select specificcomponents, and you install Wallet Manager, then you also need toinstall Net8 Assistant.

Oracle Forms Developer can be integrated with Oracle Repository.

This 6i release is shipped with a d2sc plug-in (similar to thoseprovided for PVCS, Clearcase, and other products) that allowsintegration with Repository for source control management. Userswill be able to check in and check out FMBs, MMBs, and so forth, andcan then use Repository's dependency tracking and other advancedfunctionality. (See the Repository documentation for moreinformation.)

This initial feature establishes the potential for enhanced levelsof integration in future Forms Developer releases.

Oracle JInitiator is the only supported client platform for theinitial release of Oracle Forms Server R6i.


2.27

2.28

2.29

3

4

4.1

Set the Doc60 Environment Variable

Oracle Forms Server and Firewall/Proxy Servers

Use Caution If Deinstalling Intersolve Drivers

P r o j e c t B u i l d e r

F o r m B u i l d e r

Effect of Fill Patterns on Performance

Additional client platforms such as Internet Explorer R5.0 using thenative JVM, Sun Solaris JDK 1.1.7B, or Apple MRJ have not yet beencertified with the initial release of Oracle Forms Server R6i.

It is expected that the certification on these additional platformswill be complete and supported with the first patch release to R6i.

For the latest information regarding supported client platforms andtheir support level, consult the current version of the ClientPlatform SOD, available from the Oracle Technology Network(http://technet.oracle.com) website or your Oracle supportrepresentative.

In order for users to be able to access the online documentation(help topics, Quick Tour, etc.) via a browser, you must first setthe Doc60 environment variable to identify the installed location ofthat documentation.

The Oracle Forms Server has been tested and certified against theEagle Raptor Firewall/Proxy Server when running in HTTP and HTTPSmodes. The use of firewalls and proxy servers other than EagleRaptor is supported. Additional testing and certification of theForms Server 6i HTTP and HTTPS modes with other vendors' firewalland proxy server products will be performed in the months followingthe production release of Forms Server 6i.

Do not deinstall Intersolve drivers (ODBC) from an Oracle_Home ifother products on another Oracle_Home on that machine use them.Deinstalling the drivers from one Oracle_Home will remove them fromthe entire system.

No known problems.

Assigning a fill pattern to a large Forms object may degrade runtimeperformance on the web. Objects are filled in 64x64 pixel


4.2

4.2.1

4.2.2

Undocumented Error Messages(FRM-99999)

Error Messages 1412 and 1413

Error Messages 10905-10909

increments. Thus, objects larger than 64x64 require multipleoperations. (For example, painting a window of size 800x600 wouldrequire 120 such operations.)

Recommendations: Avoid using fill patterns for large objects unlessdoing so is a significant user requirement. Also, minimize thenumber of different patterns. (Each pattern used requires 4K ofmemory.)

Any Forms error message not documented in the online help willdisplay a generic message:

FRM-99999 Error FRM-nnnnn occurred, please consult the release notes.

The details of these error messages are documented in the followingsubsections.

FRM-99999, Error 1412. An attempt was made to set scrollbar position on a block that has no scrollbar.

FRM-99999, Error 1413. An attempt was made to get scrollbar position on a block that has no scrollbar.

FRM-10905: The following return values are invalid.Cause: The invalid return values must be corrected before you can leave this page of the wizard.Action: Enter a valid return value. Return values must be one of the following: 1. A fully qualified Item name (<BLOCK_NAME>.<ITEM_NAME>). 2. A Form Parameter (PARAMETER.<PARAMETER_NAME>). 3. A global PL/SQL variable (GLOBAL.<VARIABLE_NAME>).

FRM-10906: One or more LOV columns has a negative width.Cause: One or more of the columns in the table has a negative width.Action: Ensure that no columns in the table have a negative width.

FRM-10907: The LOV size or position has a negative value.


4.2.3 Error Messages 18114-18121

Cause: One or more of the attributes of the LOV size and position is negative.Action: Ensure that none of the LOV size or position attributes is negative.

FRM-10908: Number of rows retrieved is less than or equal to zero.Cause: The number of rows retrieved is less than or equal to zero.Action: Enter a value greater than zero for the number of records retrieved.

FRM-10909: Old Style LOVs cannot be modified using the LOV wizard.Cause: The LOV Wizard was invoked on an Old-Style LOV.Action: Create a new LOV based on a Record Group.

FRM-18114: FORMS60_JAVADIR not set.Cause: For Web Preview from the Builder to work the Registry variable FORMS60_JAVADIR must point to the location that contains the Forms Java files. This variable should have been set by the Oracle Installer when Oracle Forms Developer was installed. A typical value for this variable is c:\orant\forms60\java.Action: Create or update the registry variable on NT, FORMS60_JAVADIR, and set its value to the location that contains the Forms Java files.

FRM-18115: CLASSPATH variable not set.Cause: For forms to run on the Web the environment variable CLASSPATH must point to the location that contains a valid Java installation. This variable should have been set by the Oracle Installer when Oracle Forms Developer was installed.Action: Create or update the environment variable CLASSPATH and set its value to the location that contains a valid Java installation.

FRM-18116: The CLASSPATH does not contain a reference to Forms.Cause: For Forms Server to work, the environment variable CLASSPATH must include an entry that points to a location containing the Java files required by Oracle


Forms. An entry should have been added to the existing CLASSPATH variable by the Oracle Installer when Oracle Forms Developer was installed. A typical value for this variable is c:\orant\forms60\java.Action: Create or update the environment variable CLASSPATH and set its value to the location that contains the Java files required by Oracle Forms.

FRM-18117: The preferences contains a reference to a non-existent HTML file.Cause: In the 'Runtime' Preferences dialog an HTML file has been specified, but that HTML file does not exist, or the location specified does not exist.Action: In the 'Runtime' Preferences dialog either remove the reference to the offending HTML file, so that the default HTML file is used, or specify an HTML file that exists. Alternatively place the HTML file in the location specified.

FRM-18118: Javai.DLL does not exist.Cause: For Forms Server to work in the Microsoft Windows environment, e.g. Windows NT, the DLL 'javai.dll' must exist and be in the %ORACLE_JDK%\bin directory, where %ORACLE_JDK% contains a valid Java installation.Action: Determine whether javai.dll exists in the %ORACLE_JDK%\bin directory, and if necessary, reinstall the Oracle JDK.

FRM-18119: ORACLE_JDK variable not set Cause: For Forms Server to work, the environment variable ORACLE_JDK must point to the location that contains a valid Java installation. This variable should have been set by the Oracle Installer when Oracle Forms was installed. Action: Create or update the environment variable ORACLE_JDK and set its value to the location that contains a valid Java installation.

FRM-18120: libjava.so does not exist. Cause: For Forms Server to work in the Solaris environment, a valid JDK installation must exist and be in the path. Action: Determine whether a valid JDK exists in the path, and if necessary, reinstall the JDK.

FRM-18121: The JavaBean does not implement the IView interface.Cause: For Forms to use this JavaBean, it must implement Oracle Forms IView interface.Action: Implement Oracle Forms oracle.forms.ui.IView


4.3

4.4

4.4.1

Forms Environment Variable Added

Java Keybindings API Provided

FormAction.java

Interface.

A new environment variable is available:

FORMS60_WEB_CONFIG_FILE

You can use it to specify the full path and name of the Forms CGIconfiguration file.

For example: FORMS60_WEB_CONFIG_FILE=c:\temp\myfile.cfg

The default value is <ORACLE_HOME>\forms60\server\formsweb.cfg

To provide consistent, configurable, and performant keybindingsin Forms, a keybinding API is provided. This API first downloadskeybindings to the client. The API can then query the keysequence and return the corresponding form action or querythe form action and return the corresponding key sequence.

See the following subsections for details.

Standard form actions are defined in FormAction.java. Theseform actions are static instances of the class FormAction.For example, the Next Field form action can be addressed asFormAction.FA_NEXT_FIELD.

The constants for the various form actions in FormAction.javaare obtained from frmweb.res. The following shows the beginningof the keybinding constants in FormAction.java.

public class FormAction extends Property{ /* ** The constants (or id's) for various forms actions have ** been obtained from frmweb.res. These id's will not change. ** New forms actions will be assigned new id's. */ public static final FormAction FA_NEXT_FIELD = new FormAction(1); public static final FormAction FA_PREVIOUS_FIELD = new


FormAction(2); public static final FormAction FA_CLEAR_FIELD = new FormAction(3); . . .

The following is the list of all the static constants forkeybindings included in the FormAction.java class.

FA_NEXT_FIELDFA_PREVIOUS_FIELDFA_CLEAR_FIELDFA_UPFA_DOWNFA_SCROLL_UPFA_SCROLL_DOWNFA_EDITFA_RETURNFA_LIST_OF_VALUESFA_HELPFA_EXITFA_SHOW_KEYSFA_COMMITFA_NEXT_PRIMARY_KEYFA_CLEAR_RECORDFA_DELETE_RECORDFA_DUPLICATE_RECORDFA_INSERT_RECORDFA_NEXT_SET_OF_RECORDSFA_NEXT_RECORDFA_PREVIOUS_RECORDFA_CLEAR_BLOCKFA_BLOCK_MENUFA_NEXT_BLOCKFA_PREVIOUS_BLOCKFA_DUPLICATE_FIELDFA_CLEAR_FORMFA_ENTER_QUERYFA_EXECUTE_QUERYFA_DISPLAY_ERRORFA_PRINTFA_COUNT_QUERYFA_UPDATE_RECORDFA_FUNCTION_0FA_FUNCTION_1FA_FUNCTION_2FA_FUNCTION_3FA_FUNCTION_4FA_FUNCTION_5


4.4.2 KeyBinder.java -- Using the API

FA_FUNCTION_6FA_FUNCTION_7FA_FUNCTION_8FA_FUNCTION_9FA_LIST_TAB_PAGES

Use the KeyBinder API to download keybindings and get a requestedform action or key sequence. The following is an overview of theprocess:

1. Execute downloadKeyBindings() in your start-up code.

2. Use isKeyBindingsAvailable() to test if the keybindings are available on the client.

3. If the keybindings are available, use getKeySequence(FormAction action) to get the key sequence for the requested form action,

or

use getFormAction(KeyEvent event) to get the form action for the requested key sequence.

Use the following KeyBinder.java API methods:

public synchronized static void downloadKeyBindings()

*If the keybindings have not been created on the client, thismethod requests that the server send the bindings. This is nota blocking call, because we do not want to incur a round-tripfor getting keybindings from the server. The next time a round-tripoccurs, the server will send the necessary information.

public synchronized static Hashtable getKeyBindings()

*This method returns a cloned table of all the keybindings.

public synchronized static boolean isKeyBindingsAvailable()

*This method checks if the keybindings are available on theclient.

public synchronized static KeyEvent getKeySequence(FormActionaction)

*This method gets the key sequence corresponding to a requested form


4.4.3 Example of KeyBinder.java API

action.

public synchronized static FormAction getFormAction(KeyEvent event)

*This method gets the form action corresponding to a requested keysequence.

The following example shows programming pertinent to the use of theKeyBinder.java API to get the form action from the keys pressed.

KeyBinder.downloadKeyBindings(); // get bindings from server

Then in a text field's processKeyEvent(KeyEvent e) implementation,this handles events:

// If we have key bindings, see whether this event maps to // one that we care about. // If it does, record which event it is with the name of // the action that goes with it. // Many actions can be invoked by buttons, key presses, // and/or menu selections...

if (KeyBinder.isKeyBindingsAvailable()) { String actionName; FormAction fact = KeyBinder.getFormAction(e);

if (fact == (FormAction) null) { // if no binding found, issue message. system.out.printer("No binding found."); } else if (fact == FormAction.FA_LIST_OF_VALUES) actionName = "LOV"; else if (fact == FormAction.FA_EDIT) actionName = "FLDEDIT"; else if (fact == FormAction.FA_EXIT) actionName = "CANCEL"; else { } . . .


4.5

4.6

4.7

4.8

4.9

4.10

On Windows, Forms Server and Web Previewer Require NT

Server Does Not Work If Host and Machine Name Differ

Requirements for Using Run_Product on the Web

Database Commands Available on Separate Start Menu

Using Index-Only Tables

Forms Server Needs to Access the Wallet File

The Forms Server component will not run on Windows 95 or 98. Itruns only on the NT version of Windows.

Also, because the Forms web-previewing functionality requires theForms Server, the Web Previewer is available only on Windows NT (noton Windows 95 or 98).

Problem: If the TCP/IP host name and the Windows machine name are different, the Forms Server Service will not work.

Workaround: Re-enter your host name by following the path HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> OracleFormsServer-Forms60Server. Then double-click on 'Host' and enter your host name.

If you use Run_Product in a form to run a report and want to displaythe output in the browser window, it is necessary to do thefollowing:

On Windows NT, remove the TMP user environment variable.

On Unix, remove the TMPDIR environment variable.

In this release, the database commands Build, Drop, Grant, andRevoke are listed on their own Start Menu, entitled "Oracle Forms 6iAdmin," which is separate from the Start Menu for the main Formsproduct.

In order to use an index-only table in Forms, the block's Key Modeshould be set to either Updateable or Non-Updateable.Also, a Primary Key should be nominated.

If you register the Forms Server as an NT service and configure it


4.11

4.12

4.13

4.14

Netscape Users Prompted to Save Report HTML File

Forms-Reports Integration Requires that TMPDIR Not Be Set

Changing Font Causes Problem in Forms

Performance Collection Services Now Available

with https as the connect mode, launching Forms applets may failbecause the service is not able to access the wallet file on theserver.

To work around this problem, you should either run the Forms Serverfrom the command line (that is, not as a service), or, if you dowant to run the Forms Server as a service, do the following:

1. In the services dialog, select the Forms Server service and clickthe Startup button. 2. In the "Log On As:" section, select the "This Account" radiobutton.

3. In the "This Account" field, enter the account name under whichForms was installed, and fill in the password information for thataccount. 4. Click the OK button and restart the Forms Server service.

The installation process for Forms Server creates a registry entrynamed FORMS60_REPFORMAT with value of "HTML" (upper case). If a useris running a Forms applet in a Netscape browser that launches areport, rather than having the report open in the browser window,the user will be prompted to save the report HTML file.

You can avoid this situation by setting the FORMS60_REPFORMATregistry entry to "html" (lower case).

In order for Forms-Reports integration to work on the web on a Unixsystem, the variable TMPDIR must not be set. Unset this environmentvariable before starting the Forms listener.

Problem: When using Form Builder, if you draw a text object andsubsequently change its font, then the copy, paste, and delete keyswill stop working.

Workaround: None.

The Forms runtime diagnostics have been enhanced with the additionof Performance Collection Services. These provide you with


4.14.1

4.14.2

4.14.3

How to Use Performance Collection Services

Events Collected by Performance Services

Analyzing the Performance Data

information you can use to better understand and improve yourapplication's runtime performance.

The following subsections provide details.

To activate Performance Collection Services, include‘record=performance’ in the command line argument (for runtime in aclient/server environment), or as a part of ‘serverArgs’ parameterin the HTML file (for web deployment).

For example, if running in the client/server mode, invoke using

ifrun60 module=.. userid=.. record=performance log=yourlogname

The results are written onto file yourlogname. If the file name isnot specified, a file with a unique filename is created. This nameis in the format ‘perf_xxxx’ where ‘xxxx’ is the ProcessId of theruntime process running.

In the HTML file, this invocation will be: <param name= "serverArgs" value = "module=.. userid=.. record=performance log=yourlogname">

Event Meaning___________ _________________________ClientTime Time spent at the ClientLogon Time Time to logon to the Database Server Logoff Time Time to logoff the from the Database ServerDB Time Time for any database operations, such as query APServerTime Processing time at the Forms Server

The data collected by Performance Services is analyzed using PERL scripts ‘f60parse.pl’, which are located in theORACLE_HOME\forms60\perl directory

perl f60parse.pl -input=infile -eventf=’evfile’ -outputf=’ofile’

where:


4.14.4 Default Events

Infile Recorded data while running the application. Evfile Event Description File. Ofile Results file generated by the PERL Script.

Eventf and outputf are optional parameters.

A typical event description file is of the following form:

Client ThinkTime THINK_START THINK_END _______ __________ _______________ ____________ DBLOGON Logon DBLOGON_START DBLOGON_END APServer Logon_Wr DBLOGON_END THINK_START DBPROC DB DB_START DB_END APServer DB_App DB_END DB_START APServer DB_Write DB_END THINK_START APServer DB_Logoff DB_END DBLOGOFF_START DBLOGOFF Logoff DBLOGOFF_START DBLOGOFF_END

If an events file is not specified, the following default events areassumed by Performance Collection Services:

FSPreLogon - Time Spent at the FS Server before Logon DBLOGON - Logon time at the DB Server FSPostLogon - FS processing time after LOGON at the DBServer FSPreDB - User Input processing at the FS before query to DB DBPROC - Processing time at the DB Server FSMidDB - Processing Time at FS between successive DB actions FSPostDB - Processing Time at FS after DB query PreLogoff - Processing Time at FS before Logoff DBLOGOFF - Time to Logoff from the DB Server Client+Net - Time spent at the Client and the Network Client+Net+User - Time spent at the Client, Network and the User while waiting for user interaction.

By default, the output appears in the following HTML files (whichcan be viewed in a browser): 1. index.html - Summary of user action 2. detailed1.html - Detailed events 3. detailed2.html - Detailed event collection 4. event.html - Event definitions

When specified, an XLS output file is created with the given name.

A typical results file has three sections: 1. Summary 2. Detailed Description (Level1)


4.15

4.15.1

4.15.2

Using Oracle Trace Instead of PECS for Performance Analysis

Initiating Trace Data Collection

Using the Oracle Trace Command-Line Interface

3. Detailed Description (Level2)

Although PECS is supported in this 6i release, such support is notplanned for any future Forms releases.

You can use Oracle Trace to provide functionality that is similar toPECS. Integration of Oracle Trace functionality with Forms is a betafeature introduced in Forms Developer 6i.

The Oracle Trace-based Forms implementation supports a subset of theevents defined in PECS. In addition, a few new events are alsodefined and supported. The event definitions reside in the fileORACLE_HOME\otrace80\admin\fdf\oforms.fdf on Windows NT, andORACLE_HOME\otrace\admin\fdf\oforms.fdf on Unix. This file isessential for activating Trace in Forms, and is supplied ascollateral on the Forms Developer 6i CD.

Data collection on the Forms Server needs to be initiated eitherthrough the command line, or through Trace Manager -- which comes aspart of Oracle Enterprise Manager with Diagnostic Pack ver.2.1.

The command line interface requires Oracle Trace CLI version 9,which comes as part of the 8.0.6 components and is supplied ascollateral on the Forms Developer 6i CD.

To enable actual data collection in a web environment, include‘pecs=trace’ as part of the ‘serverArgs’ parameter defined in theHTML file used for running the form.

You invoke this interface by variations of the OTRCCOL command,which provide the following functions:

OTRCCOL START job_id input_parameter_file OTRCCOL CHECK col_name OTRCCOL STOP job_id input_parameter_file OTRCCOL DCF col_name cdf_file [to delete collection file]

The parameter job_id can be any numeric value. The input parameter


4.15.3

4.15.4

Oracle Trace Collection Files

Events Collected by Trace

file contains specific parameter values required for each functionas shown in the following examples. COL_NAME (collection name) andCDF_FILE (collection definition file)are initially defined in the START function input parameter file.

The OTRCCOL START command invokes a collection based upon parametervalues contained in the input parameter file. For example: otrccol start 1234 my_start_input_filewhere my_start_input_file contains the following input parameters: col_name= my_collection dat_file= <usually same as collection name>.dat cdf_file= <usually same as collection name>.cdf fdf_file= <server event set>.fdf regid= 1 192216243 0 0 45 <database SID>

These parameter file records are all required for otrace collection,and the regid record must contain the values shown, including yourSID value.

The OTRCCOL STOP command halts a running collection as follows: otrccol stop 1234 my_stop_input_filewhere my_stop_input_file contains the collection name and cdf_filename. You can use the same otrace input parameter file as used withthe START command.

Running an Oracle Trace collection produces the following collectionfiles located in the directory specified in INIT.ORA or in thedefault collection path:

collection_name.cdf This is the Oracle Trace collection definition file for your collection.

collection_name.dat These files are the Oracle Trace output files containing the data in binary format.

These are the events collected by Trace Collection Services.

Subset of PECS Events: * Application - (a session with the Oracle Forms Server) * Form - (from opening to closing of a form)


4.15.5 Using the Oracle Trace Statistics Reporting Utility

* ExeQuery - (Query Execution) * Trigger - (Trigger) * LOV - (LOV) * MenuCreate - (MenuCreation) * Alert * Timer * Window * Canvas

Additional Events: * DB Logon * DB Logoff * ServerTime * DBTime

You can access the Oracle Trace data contained in the collectionfiles in the following ways:

- Create Oracle Trace reports from the binary file.

- Use Oracle Trace Data Viewer (data must be formatted).

- Format the data to the tables in the Oracle database for SQL access and reporting.

The Oracle Trace statistics reporting utility displays statisticsfor all items associated with each occurrence of a server event.These reports can be quite large. You can control the report outputby using command parameters. Use the following command and optionalparameters to produce a report: otrcrep [optional parameters] collection_name.CDF

The first step you may want to take is to generate a report called“collection_PROCESS.txt.” You can produce this report first to see alisting of specific process identifiers for which you might want torun other reports.

You can manipulate the output of the Oracle Trace reporting utilityby using the following optional report parameters:

output_path Specifies a full output path for the report files. If not specified, the files will be placed in the current directory.-p [<pid>] Organizes event data by process. If you specify a process ID (pid), you will have one file with all the events generated by that process in chronological order. If you omit the process ID, you will have one file for each process that


4.15.6

4.15.7

Viewing the Trace Data

Trace Tables

participated in the collection. The output files are named collection_Ppid.txt.-P Produces a report called collection_PROCESS.txt that lists all processes that participated in the collection. It does not include event data. You could produce this report first to determine the specific processes for which you might want to produce more detailed reports.-w# Sets report width, such as -w132. The default is 80 characters.-l# Sets the number of report lines per page. The default is 63 lines per page.-h Suppresses all event and item report headers, producing a shorter report.-s Used with Net8 data only (or SQL*Net for Oracle7).-a Creates a report containing all the events for all products, in the order they occur in the data collection (.dat) file.

To format the data to the database and inspect it using the TraceDataViewer, use the instructions in the Oracle Trace User's Guide.The DataViewer presents special form views (which are Beta-level).

The DataViewer presents specialized views for viewing the data. Theviews are: * Session Overview - Presents the statistical details of the various sessions for which the data was collected * Form Overview - Presents the statistical details about the various forms opened and closed during the sessions and the events that occur within a form -- for example, Query, Triggers, LOV, Window creations, Canvases, and so forth. * Drill-down views from Forms Overview, which also lead to the statistics about the above events. * Time elapsed in every event, plus the actual CPU clock ticks spent in the event.

You can also create custom views to examine the statistical details. See the Oracle Trace User's Guide for Release 2.1.

In case the Diagnostic Pack is not available, the data uploaded tothe database can be obtained from the tables namedV_192216243_F_45_E_yy_6_0, where yy is the event number.

The various events defined in the 'fdf' file and the associatednumbers and items are as follows:


FORMS DURATION EVENTS AND ITEMS

Event # and Name Description and Items ________________ _____________________________________1. Session Total time spent by the end user in the Forms Session, including login and logout. Specific items = Session Name,IPAddress. Generic items = UCPU, SCPU, INPUT_IO, OUPUT_IO, PAGEFAULTS, PAGEFAULTS_IO, MAXRS_SIZE.2. Form Total time spent by the end user in the specific form and the forms called from this form. Specific item = Form Name. Generic items = UCPU, SCPU, MAXRS_SIZE, CROSS_FAC (Session id).3. Query Total time spent by the end user in a specific query. Specific item = Block Name Generic items = same as for # 2 above.4. Trigger Total time spent by the end user in a specific trigger. Specific items = Block Name, Item Name, Trigger Id. Generic items = same as for # 2 above.5. LOV Total time spent by the end user in a LOV. Specific items = LOV Name, Blockname, Itemname Generic items = same as for # 2 above. 11. Built-In Total time spent by the end user in a built-in Specific items = Built-in Name. Generic items = same as for # 2 above.12. User Exit Total time spent by the end user in a user exit. Specific items = User Exit Name. Generic items = same as for # 2 above. 13. SQL Total time spent by the end user in SQL code. Specific items = SQL Statement. Generic items = same as for # 2 above. 14. Menu Create Total time spent by the end user in creating a menu. Specific items = Menu Name. Generic items = same as for # 2 above.41. ServerTime Time Spent in processing at the Forms Server. Specific items = none. Generic items = same as for # 2 above.42. DBTime Total time spent at database. Specific items = SQL statement. Generic items = same as for # 2 above.43. DBLogon Time spent in logging on to the database. Specific items = none.


4.15.7

4.16

Trace Tables -- continued

How to Deploy a Certificate from a Non-Trusted Authority

Generic items = same as for # 2 above. 44. DBLogoff Time Spent in logging off from the database. Specific items = none. Generic items = same as for # 2 above.

(see also next subsection)

FORMS POINT EVENTS AND ITEMS

Event # and Name Description and Items ________________ _____________________________________31. Alert Instant at which alert occurs. Specific item = Alert Name. Generic items = UCPU, SCPU, CROSS_FAC (Form ID).32. Editor Instant at which editor is invoked. Specific item = Editor Name. Generic items = same as for # 31 above.33. Window Instant at which a window is created. Specific item = Window Name. Generic items = same as for # 31 above.34. Canvas Instant at which a canvas is visited from the user perspective. Specific item = Canvas Name. Generic items = same as for # 31 above.38. Timer Instant at which a timer activates. Specific item = Timer Name. Generic items = same as for # 31 above.39. Dialog Instant at which a dialog activates. Specific item = Dialog Name. Generic items = same as for # 31 above.

The following describes how to deploy a certificate from aCertificate Authority that is not trusted by Oracle Forms bydefault.

The Forms HTTPS feature trusts certificates issued by the followingCertificate Authorities:

Verisign Inc. - Class 1, 2, 3 Public Primary Certification Authority RSA Data Security Inc. - Secure Server Authority GTE CyberTrust Solutions Inc. - CyberTrust Global Root GTE Corporation - CyberTrust Root

The following instructions are based on using the Verisign Trial


4.16.1

4.16.2

Create a Wallet Using the Oracle Wallet Manager

Create a Certificate Request

Certificate (not one of the above, and not trusted by default).However, these instructions are generalized, and could also be usedto deploy a certificate from a CA not listed above.

The instructions follow this general sequence:

· Create a wallet using Oracle Wallet Manager.· Create a certificate request using Oracle Wallet Manager.· Import the Trial CA root certificate into the Internet Explorer browser.· Export the Trial CA root certificate as a Base 64 encoded X.509(.CER).· Import the Base 64 encoded X.509(.CER) Trial CA root certificate into the wallet.· Replace the certdb.txt of Jinitiator with the new version.· Import the user certificate into a wallet.

Details are provided in the following subsections.

On NT, run the Oracle Wallet Manager by clicking on Start->Programs->Oracle for Windows NT->Oracle Wallet Manager.

Create a wallet as follows: 1. Click Wallet->New from the menu bar. The New Wallet dialog box is displayed. 2. Type a password in the Wallet Password field. 3. Retype that password in the Confirm Password field. 4. Click OK to continue. A message appears, and informs you that a new empty wallet has been created, and prompts you to decide whether you want to create a certificate request. 5. Click Yes.

1. Enter the following information in the Certificate Request dialog box:

Common Name: Enter the name of the certificate identity in First name Last name format. For example, you could use the name of the Forms server


administrator.

Organizational Unit: Enter the name of the identity's organizational unit; for example, Finance.

Organization: Enter the name of the identity's organization; for example, XYZ Corp.

Locality/City: Enter a city or locality.

State/Province: Enter a state or province. Do not use abbreviations, such as CA for California.

Country: Click the drop down list to view a list of country abbreviations, and select the country in which the organization is located.

Key Size: Click the drop down box and select the key sizes to use when creating the public/private key pair.

Advanced: Click Advanced to view the Advanced Certificate Request dialog panel. Use this field to edit or customize the identity's distinguished name (DN).

2. Click OK. An Oracle Wallet Manager message box informs you that a certificate request was successfully created. 3. You can save the wallet to the disk now or any other time by clicking on Wallet->Save. You will be prompted for a directory name.

4. There are many ways in which you can send the certificate requestto the certificate authority. The most common way is to cut andpaste the certificate request to the HTML form of the CA. You canalso copy the certificate request text from the body of the messagebox, and paste it into an e-mail message and send the request to acertificate authority which accepts such requests. In theseinstructions, we will use the Trial Server Certificate fromVerisign. Using your browser go to the url www.verisign.com. (Do asearch for ‘Trial Server Certificate’ if such a link is notavailable on the home page.)

Verisign lists five steps : Step 1: Generate CSR. You have already completed this step using OWM. Step 2: Submit CSR. Cut & Paste the Certificate Request from OWM into the "Enter CSR information" HTML field. Step 3: Complete Application. Enter the Technical Contact Information such email address where the certificate should be sent.


4.16.3 Install the Trial CA Root Certificate

Step 4: Install Test CA Root. (We will do this in the next subsection, Installing the Root Certificate.) Step 5: Install your Test Server ID. Refer to the Forms 6i documentation on how to deploy the wallet on the server side. 5. Now, back on your Oracle Wallet Manager screen, click OK. You are returned to the OWM main window. The status of the certificate is changed to Requested.

You need to use Internet Explorer 5.0 to install the CA rootcertificate and export it as a Base 64 encoded X.509(.CER) filethat can be read by Oracle Wallet Manager. (Unfortunately, Netscapecannot be used, since it does not allow you to export the rootcertificates to a file.) 1. Run IE 5.0 and go to the URL http://www.verisign.com/server/trial/welcome/caroot.html. 2. Follow the instructions and download the CA root certificate into your browser.

3. Click on Tools->Internet Options->Content and ‘Certificates’.

4. When you get the Certificate Manager, make sure the ‘Intended Purpose’ is ‘All’ and click on ‘Trusted Root Certification Authorities’.

5. Select the certificate that has the value 'For Verisign authorized testing only…' in the ‘Issued to’ column.

6. Click ‘Export’-> Next and select Base 64 encoded X.509(.CER).

7. Save it into a file; in this example, vrsnca.cer.

8. Go back to your OWM session.

9. Click on Operations->Import Trusted Certificate. Click on ‘Select a file that contains the certificate’ and open the file vrsnca.cer which you saved earlier from IE.

10. Make sure you now see ‘For Verisgn authorized testing only’ listed among the ‘Trusted Certificates’.

11. Export all the trusted certificates by clicking on ‘Operations -> Export All trusted Certificates’.


4.16.4

4.16.5

Replace the certdb.txt of Jinitiator with the New Version

Import the User Certificate

12. Save it into a file; for example, vrsndb.txt.

1. Make a backup copy of C:\Program Files\Oracle\Jinitiator…\lib\security\certdb.txt.

2. Copy the vrsndb.txt onto C:\Program Files\Oracle\Jinitiator…\lib\security\certdb.txt.

After Verisign processes your request, you will receive an emailfrom Verisign containing the certificate which looks something likethis:

-----BEGIN CERTIFICATE-----DzANBgNVBAoTBk9yYWNsZTEoMCYGA1UECxMfRW50ZXJwcmlzZSBBcHBsaWNhdGlvbiBTZXJ2aWNlczEhMB8GA1UEAxMYRUFTUUEgQ2VydGlmaWNhdGUgU2VydmVyMB4XDTk5MDcyNjE3MzkyNloXDTAwMDEyMjE3MzkyNlowPTELMAkGA1UEBhMCVVMxDzABgNVBAoTBm9yYWNsZTEOMAwGA1UECxMFZm9ybXMxDTALBgNVBAMTBGFtYXIw-----END CERTIFICATE-----

After you receive the user certificate that you requested from theCA, you must import it into the wallet that you created. You canimport it in one of two ways: · Paste the user certificate from the email that you receive from the certificate authority. · Import the user certificate from a file.

To paste the user certificate: 1. From the OWM menu bar, click Operations->Import User Certificate.The Import User Certificate dialog box opens. 2. Click the ‘Paste the Certificate’ radio button, and click OK. AnImport User Certificate dialog box opens with the following message:"Please provide a base64 format certificate and paste it below." 3. Copy the user certificate from the body of the email you receivedor the web page. 4. Paste the certificate into the window, and click OK. A message atthe bottom of the window informs you that the user certificate wassuccessfully installed. 5. Click OK. You are returned to the Oracle Wallet Manager mainpanel, and the user certificate is displayed at the bottom of theUser Certificates tree. Remember to save the wallet to the disk.

To import a file that contains the user certificate:


4.17

5

6

6.1

6.1.1

Installing OEM: Clarification to Instructions

R e p o r t B u i l d e r

G r a p h i c s B u i l d e r

Additional Steps Required for Cartridge

Additional Cartridge Installation Steps for NT

1. From the menu bar, click Operations->Import User Certificate. TheImport User Certificate dialog box opens. 2. Type the path or folder name of the user certificate location. 3. Click to select the name of the user certificate file, forexample, cert.txt. 4. Click OK. A message at the bottom of the window informs you thatthe user certificate was successfully imported into the wallet.

Click OK to close the dialog box. You are returned to the OracleWallet Manager main panel, and the user certificate is displayed atthe bottom of the User Certificates tree. Remember to save thewallet to the disk.

In the manual Deploying Forms Applications to the Web, chapter 13,section 13.4.2, "Configuring Forms Support for OEM on NT,"you should omit step 2 if you are using OEM 2.1 or later. This stepis only necessary for a special release of OEM 2.0.4.

(See the separate Release Notes for the Reports Developer product.)

If you are going to use Oracle Application Server (OAS) and theGraphics Cartridge, you need to perform additional steps afterinstalling OAS and Graphics in separate ORACLE_HOMEs.

There are separate instructions for NT and Solaris. See thefollowing subsections.

1. Install Graphics in the default ORACLE_HOME. 2. Install OAS 4.0.8 in a separate ORACLE_HOME. 3. In the OAS ORACLE_HOME, create registry entries that point backto the default ORACLE_HOME (the directory in which Graphics isinstalled). In the following examples, you should replace


6.1.2 Additional Cartridge Installation Steps for Solaris

%ORACLE_HOME% with the actual physical directory for the default(Graphics) ORACLE_HOME, and replace %OAS_HOME% with the actualphysical directory for the OAS ORACLE_HOME.

Using the NT Registry Editor, add the following registry entries tothe OAS ORACLE_HOME registry:

Symbol Value______ ______DE60 %ORACLE_HOME%\TOOLS\COMMON60GRAPHOGD60 %ORACLE_HOME%\GRAPH60\GWIZ_OGDGRAPHICS_WEB_DIR %ORACLE_HOME%\GRAPH60\WEB_OGDMM60 %ORACLE_HOME%\TOOLS\COMMON60OCL60 %ORACLE_HOME%\GRAPH60OWS_IMG_DIR %OAS_HOME%\ows\4.0\admin\imgTK60 %ORACLE_HOME%\TOOLS\COMMON60UI60 %ORACLE_HOME%\TOOLS\COMMON60VGS60 %ORACLE_HOME%\TOOLS\COMMON60

NOTE: Be sure to replace %ORACLE_HOME% and %OAS_HOME% with theactual full directory paths in all of the value entries.

4. Create a sub-directory named WEB_TMPDIR under the directory thatthe OAS's ORACLE_HOME/img_dir/ points to.

After configuring the Graphics Cartridge in OAS as documented, setthe following environmental variables in the OAS environment:

1. ORATOOLS_HOME must be set to point to the ORACLE_HOME ofDeveloper.

2. $ORATOOLS_HOME/lib must be added to the end of theLD_LIBRARY_PATH.

3. GRAPHICS_WEB_DIR must be set to the location of the Graphicsdisplays you wish to run with the cartridge.

4. OWS_IMG_DIR must be set to $ORACLE_HOME/ows/4.0/admin/img.

5. The directory $ORACLE_HOME/ows/4.0/admin/img/web_tmp must becreated.

6. The OAS listener must have a virtual path /ows-img that pointsto the physical directory $ORACLE_HOME/ows/4.0/admin/img.

After you make the above changes, OAS must be restarted to pick upthe changes to the environmental variables.


6.2

7

8

9

10

11

12

13

13.1

13.1.1

Environment Variables Must Be Set on Unix

Q u e r y B u i l d e r

S c h e m a B u i l d e r

T r a n s l a t i o n B u i l d e r

P r o c e d u r e B u i l d e r

D e m o s

O p e n C l i e n t A d a p t e r

N a t i o n a l L a n g u a g e S u p p o r t

Known Problems for All Languages

Form Builder User Interface May Not Be Fully Translated

In order for Graphics integration to work on a Unix system, you mustset the following environment variables:

setenv PRINTER <printer_name> setenv TK2_PRINT_STATUS echo

No known problems.

No known problems.

No known problems.

No known problems.

No known problems.

No known problems.

Customers who install the Forms Builder with a language otherthan English may find that the user interface is a mixture of locallanguage and English. The Forms Builder is not translated fully forsome languages.

For these languages, please use the English language interface.


13.1.2

13.1.3

13.1.4

Euro Currency Symbol Has Limited Support

Some Wizard Buttons Have Untranslated Text

Restore Icons During Installation Creates Invalid Menus

To do this, set

DEVELOPER_NLS_LANG=AMERICAN_AMERICA.<charset>USER_NLS_LANG=< Language>_<Territory>.<charset>

on the workstation that is running the Builder.

Substitute < Language> with the Language you want to run your form in.Substitute < Territory> with the Territory you want to run your form in.Substitute for <charset> the Oracle character set that you wish to use.

There is limited support in this release for the Euro currencysymbol.

To enable a limited use of the Euro symbol in this release, you mustdo the following:

1. If you are using Windows 95 or NT, update that operating system with the appropriate Euro-related patch from Microsoft. (Windows 98 already contains the Euro support.)

2. Install Microsoft TrueType fonts that contain the Euro symbol.

3. Verify that your database and client NLS_LANG character sets both support the Euro symbol. If you will print the Euro symbol, Euro support on the printer is also required.

Microsoft has reserved hexcode 0x80 for the Euro symbol. To enterthe Euro symbol on keyboards without an explicit Euro key, click theNumLock key to enable the Numeric Keypad, then click Alt + 0128.

In the wizards on Unix systems, some buttons appear with their textsin English.

Problem: When using Software Asset Manager during a custom


13.1.5

13.1.6

13.1.7

Menu Action Not Available Via Keyboard After Print Cancel

FMRWEB.RES Must Be Configured Manually

Information About NLS_LANG Parameter Values

installation and selecting the Restore Icons button, invalid menus are created in 'Start -> Program'.

Workaround: Reinstalling the 6i release will correctly reset the icons and menus.

Problem: When accessing a form via keyboard commands, and selecting a print dialog and then cancelling that dialog several times, the print dialog could not be brought up again.

Workaround: Avoid repeated cancelling.

The file "fmrweb.res" contains a keyboard map. This map is used byOracle Forms Server to detect key strokes entered in the user'sbrowser and map them to Forms actions. The map assumes that thekeyboard is similar to a VT100 keyboard. If the user has a PC-style keyboard, we recommend that you copy thefile "fmrpcweb.res" over the original "fmrweb.res". This will makethe server assume that the keyboard is similar to a 101-key "PC"keyboard. By default, the US versions of fmrweb.res and fmrpcweb.res areinstalled, regardless of language. In addition, for aparticular language, the appropriate mapping files for thatlanguage's typical keyboard are installed. They are installed tothe files "fmrweb<lang>.res" and "fmrpcweb<lang>.res", where <lang>is the Oracle language code. For instance, the Oracle language codefor Latin American Spanish is "esa". To use the files for aparticular language instead of the US versions, copy the desiredfile over the file "fmrweb.res". Starting with Oracle Forms Server 6i, the files"fmrweb<lang>_utf8.res" and "fmrpcweb<lang>_utf8.res" are alsoinstalled. These contain the same key mappings as"fmrweb<lang>.res" and "fmrpcweb<lang>.res", but the files areencoded in the UTF8 character set. These files should be used ifthe server is using the UTF8 character set (UTF8 is thecharacter set specified in NLS_LANG).


13.1.8

13.2

13.2.1

13.3

13.3.1

13.3.2

Wallet Manager User Interface Is in English

Known Problems for Double-Byte Languages

Editing with Single-Byte Font

Known Problems for Japanese

Cannot Save Modules If Character Set Is JA16EUC

Length Limit Moving From Windows to Solaris

The manual "Deploying Forms Applications to the Web" refers to afile named \bonus\nls\nlsdrl.wri. However, that file is no longerup-to-date, and is not supplied on the product CD.

For information about parameter values for NLS_LANG, consult thedocumentation for the Oracle8 8.0.6 server. The valid NLS_LANGparameter values are the same for Forms and for that databaseserver.

When you install Wallet Manager from the Forms Developer CD, it willnot have a translated user interface. The user interface will be inEnglish.

Oracle Wallet Manager translations can be obtained if required.Contact your Oracle representative for more details.

Problem: In any double-byte language implementation of the Builders, editing using a single-byte font face (such as Arial) causes characters to become distorted or unreadable. This occurs in any editing field.

Workaround: Use double-byte fonts that display Roman script, instead of using the single-byte font.

Problem: Cannot save modules in an Oracle Database if the character set is JA16EUC.

Workaround: Use the JA16SJIS character set instead.

Problem: Cannot take objects with names over 30 bytes in length (using Hankaku-Katakana) from Windows to Solaris.


13.3.3

13.3.4

13.3.5

13.3.6

13.3.7

PL/SQL Editor Display Problems

UTF8 Limitation

Multibyte Characters Cannot Be Used for PL/SQL Library Name

Different prefs.ora Files May Be Needed

Message Texts from PL/SQL Interpreter Are Mixed

Workaround: No workaround.

Problem: Characters entered on a single line are displayed on multiple lines, overlapping.

Workaround: None.

Problem: If NLS_LANG is set to American_America.UTF8, you can not create fmx files from fmb files that were created in JA16SJIS.

Workaround: None.

Problem: Trying to create a PL/SQL library name using a multibyte character set does not work correctly.

Workaround: None.

Problem: If a customer selects Japanese installation, prefs.ora for theJapanese language in JA16SJIS encoding will be installed. Thiscauses some problems for customers who develop their applicationswith other NLS_LANG settings such as: - American_America.JA16SJIS (a) or - Japanese_Japan.UTF8 (b)

Workarounds: (a) prefs.ora files for the American language are required. They need to be copied from the installation CD.

(b) prefs.ora files in UTF8 encoding are required. Convert the prefs.ora files from JA16SJIS encoding to UTF8 encoding.

When running Procedure Builder, error messages (for example, ORA-04098) from the PL/SQL Interpreter are sometimes displayed inEnglish and sometimes in Japanese.


13.3.8

13.4

13.4.1

Storage Requirement for Installing Cue Cards on Unix

Known Problems for Arabic

Limitations for Displaying Charts on Solaris

If you choose to install the Cue Cards on a Unix system, both theJapanese tar files and the US tar files will be installed. Thetotal storage requirement for these tar files is approximately275Mb.

The Cue Cards are optional. If your storage space is limited, youmay choose to not install the Cue Cards.

Customers using the Solaris version of Forms Developer 6i whogenerate charts should note that the Solaris operating system hasless support for fonts and locales than Windows NT. Specifically,Solaris does not have an official Arabic locale. Forms Developer 6ifor Solaris has only very limited support for the Unicode locale.

As a result, charts generated on Solaris will not display textcorrectly if Arabic or Unicode is used. This will also happen withcharts displayed on any Web Client that is accessing a Solaris-basedserver. This occurs because the chart is rendered into bitmapgraphics on the server. If the server is Solaris-based, then Arabicand Unicode fonts are not available. Other text in forms, reports,and graphics is usually sent directly to the client and rendered inthe client's locale. The recommended workaround is to select a chart text font that isWestern European and not Unicode.

Documents

Wednesday, March 22, 2000