Wednesday, March 22, 2000

Page 1

Wednesday, March 22, 2000

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

4:26pm

All rights reserved,

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 to publication will be available through normal support channels.

-------------------------- Table of Contents -------------------------1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 2.5 2.6 2.6.1 2.6.2 2.6.3 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24

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 Relationship of Release 6i to Release 6.0 Release Numbering 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 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 Misleading Installation Message: Acrobat Reader Available 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 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 Custom Install of Wallet Manager Requires Net8 Assistant

Page 2

2.25 2.26 2.27 2.28 2.29 3 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 4.4.1 4.4.2 4.4.3 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.14.1 4.14.2 4.14.3 4.14.4 4.15 4.15.1 4.15.2 4.15.3 4.15.4 4.15.5 4.15.6 4.15.7 4.15.7 4.16 4.16.1 4.16.2

Wednesday, March 22, 2000

Integration with Oracle Repository Client Platform Certifications 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 Undocumented Error Messages(FRM-99999) Error Messages 1412 and 1413 Error Messages 10905-10909 Error Messages 18114-18121 Forms Environment Variable Added Java Keybindings API Provided FormAction.java KeyBinder.java -- Using the API Example of KeyBinder.java API 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 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 How to Use Performance Collection Services Events Collected by Performance Services Analyzing the Performance Data Default Events Using Oracle Trace Instead of PECS for Performance Analysis Initiating Trace Data Collection Using the Oracle Trace Command-Line Interface Oracle Trace Collection Files Events Collected by Trace Using the Oracle Trace Statistics Reporting Utility Viewing the Trace Data Trace Tables Trace Tables -- continued How to Deploy a Certificate from a Non-Trusted Authority Create a Wallet Using the Oracle Wallet Manager Create a Certificate Request

4:26pm

Page 3

4.16.3 4.16.4 4.16.5 4.17 5 6 6.1 6.1.1 6.1.2 6.2 7 8 9 10 11 12 13 13.1 13.1.1 13.1.2 13.1.3 13.1.4 13.1.5 13.1.6 13.1.7 13.1.8 13.2 13.2.1 13.3 13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 13.3.6 13.3.7 13.3.8 13.4 13.4.1

Wednesday, March 22, 2000

Install the Trial CA Root Certificate Replace the certdb.txt of Jinitiator with the New Version Import the User Certificate 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 Additional Cartridge Installation Steps for Solaris 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 Euro Currency Symbol Has Limited Support Some Wizard Buttons Have Untranslated Text Restore Icons During Installation Creates Invalid Menus Menu Action Not Available Via Keyboard After Print Cancel FMRWEB.RES Must Be Configured Manually Information About NLS_LANG Parameter Values 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 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 Storage Requirement for Installing Cue Cards on Unix Known Problems for Arabic Limitations for Displaying Charts on Solaris

4:26pm

Page 4

1.1

Wednesday, March 22, 2000

4:26pm

Purpose Of This Document This document notes differences between Oracle Forms Developer and Forms Server and their documented functionality.

1.2

Restricted Rights Legend This software contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of software is prohibited. If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable: RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure of the Programs by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988). Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065. If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with Restricted Rights as defined in FAR 52.227-14, Rights in DataGeneral including Alternate II (June 1987). The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.

1.3

Server Licensing Please note that if you want to deploy your Forms or Graphics to the Internet, you need the Oracle Forms Server, and its associated deployment license. Forms Server is included on the general Forms Developer CD-ROM for demonstration and test purposes, but is licensed separately. Please contact your Oracle Sales Representative to get additional information on Forms Server pricing.

2

G e n e r a l

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

2.1

Name and Packaging Changes

Page 5

Wednesday, March 22, 2000

4:26pm

In this release, Oracle Developer has become two separate products: Oracle Forms Developer and Oracle Reports Developer. Each contains multiple Builders. Similarly, Oracle Developer Server has become two separate products: Oracle Forms Server and Oracle Reports Server. 2.2

Relationship of Release 6i to Release 6.0 Release 6i is a "drop-in upgrade" to Release 6.0. This means Release 6i is patch-compatible with Release 6.0. With Release 6i, providing you are not implementing new 6i-specific functionality, you get the same benefits as when you take a patch set. Benefits include no required regeneration of fmx files, a dropin installation, and QA certification. You should still schedule patch-set-level testing, as is recommended when any patch-set is applied. (Note that this may require upgrading to the latest certified client and middle-tier stack.) The initial release of 6i includes all the fixes in 6.0 through patch set 4, and most of the fixes in patch sets 5 and 6 (only bugs 892177, 995498, 1086525, and 1120902 are not included). The first Release 6i patch set (slated for 16 weeks after production) will be a cumulative patch that will roll forward the remaining items from Release 6.0 patch sets 5 and 6, and all of 7, as well as providing any additional 6i-specific fixes. The final Release 6.0 patch set (patch set 7) is slated for mid-April 2000. For customers with production systems on these latest patch sets for Release 6.0 (patch set 5 or 6) or who are waiting for fixes in the final Release 6.0 patch set 7, it is recommended that you remain on Release 6.0 and plan to upgrade to Release 6i in the timeframe of the first 6i patch set. Release 6.0 customers who (a) do not intend to take advantage of any 6i 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 to upgrade to 6i. Customers who plan to build new applications or are using Release 6.0 with a patch set prior to patch set 5 are recommended to utilize production Release 6i.

2.3

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

Page 6

Wednesday, March 22, 2000

4:26pm

have a 6.0.5 version number. These are the appropriate versions of the subcomponents for this initial release. It is expected that in the first patch release for 6i, the subcomponents will be renumbered to a 6.0.8 level. 2.4

RSF Components Include Additional Bug Fixes This release of this product includes some RSF components that contain code fixes beyond those in the formal, numbered patches to the component. (These fixes or patch-levels of a component are sometimes referred to as "one-offs.") Specifically, this release includes fixes for bugs 1063571, 1063104, 1028960, 1049171, and 1040536. These bug fixes affect the following components: sqlnet, rdbms, nls and plsql.

2.5

Date Handling For important information about date handling in Oracle Forms Developer, please refer to http://www.oracle.com/year2000/ and follow the link to White Papers and Resources.

2.6

Known Limitations

2.6.1

Co-existence in the same $ORACLE_HOME with Previous Releases Oracle Developer 1.6.1 and Oracle Forms Developer 6i can co-exist in the same $ORACLE_HOME. Oracle Developer 2.1 and Oracle Forms Developer 6i can co-exist in the same $ORACLE_HOME. Oracle Developer 1.6.1 and Oracle Developer 2.1 CANNOT co-exist in the same $ORACLE_HOME. Oracle Developer 6.0 and Oracle Forms Developer 6i CANNOT co-exist in the same $ORACLE_HOME.

2.6.2

PLL File Upgrade Requires .PLL Extension on Command Line If you are using a batch file to upgrade .PLL files, then you have to provide extension .pll in the batch file. Otherwise you get an error "FRM-10043: Could not open file".

2.6.3

Non-Alphanumeric Characters in Database Objects Names

Page 7

Wednesday, March 22, 2000

4:26pm

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

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

2.8

Precompilers Compatible With This Release If you are developing user-exits for Oracle Forms Developer 6i using the Oracle Precompilers, please use the versions of the Precompilers that are bundled with the Oracle 8.0.6 release.

2.9

ORAINFONAV_DOCPATH Environment Variable on Unix On Unix platforms, the ORAINFONAV_DOCPATH environment variable should be set to the location of the online manuals. The default value for this environment variable is set to the location of the American English version of the online manuals ($ORACLE_HOME/doc60/admin/manuals/US). If you are interested in the Japanese version of the online manuals, you should set the ORAINFODOC_DOCPATH environment variable to: $ORACLE_HOME/doc60/admin/manuals/JA

2.10

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

2.11

Sequence of Installing in the Same ORACLE_HOME If you choose to install both Forms Developer R6i and the Database Server 8.0.6 in the same ORACLE_HOME, you should install the Database Server first, and then install Forms Developer. This sequence will prevent library linking conflicts.

2.12

Path Requirement for Multiple ORACLE_HOMEs In order for the Forms CGIs (ifcgi60.exe or rwcgi60.exe respectively) to run successfully on NT when there are multiple ORACLE_HOMEs, it is imperative that the %ORACLE_HOME%\bin directory for Forms be in the machine's PATH environment setting, ahead of any other \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 that whatever Web Listener the user is using is being run as an NT service, which will usually be the case).

Page 8

Wednesday, March 22, 2000

4:26pm

If these conditions are not met, there are two possible consequences: 1. The CGI's may fail to run because one or more DLLs on which they depend, 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 of core40.dll is being used. This can occur in the case of multiple ORACLE_HOMEs, if an ORACLE_HOME other than that into which Forms or Reports was installed appears in the PATH before the Forms or Reports ORACLE_HOME). Of these, situation #1 should not normally be a problem, because the installation process always adds %ORACLE_HOME%\bin to the PATH and instructs the user to reboot the machine if one of the CGI's was installed. Situation #2 is known to occur if you install Forms into one ORACLE_HOME, then install OEM into a separate ORACLE_HOME (which is in fact mandatory). This second ORACLE_HOME's bin directory will be added into the machine's PATH environment setting, by the installation process, ahead of the first one (giving for example c:\orant2\bin;c:\orant1\bin;c:\winNT\system32;...etc). Once the user reboots, this will cause the Forms CGIs to fail. Workarounds: 1. Install OEM (into its own separate ORACLE_HOME) BEFORE installing Forms (into a different ORACLE_HOME). Then reboot. This works because the "last" ORACLE_HOME installed into is left as the DEFAULT ORACLE_HOME. 2. Use the "ORACLE HOME SELECTOR" to ensure that the ORACLE_HOME where Forms was installed is the DEFAULT ORACLE_ HOME. The "ORACLE HOME SELECTOR" may be found in the Oracle for Windows NT program folder). 3. Manually correct the PATH setting and reboot.

2.13

Misleading Installation Message: Acrobat Reader Available After installing components from the asset manager, you may see the following message: "Installation Successful. Some of the products you have installed require the Adobe Acrobat Reader. If you do not already have this installed on your machine, you should select it from the 'Products

Page 9

Wednesday, March 22, 2000

4:26pm

available' list." However, the Acrobat Reader is not in this particular list. Acrobat can be obtained from http://www.adobe.com. 2.14

Misleading Installation Message: Folder Moved When Release 6i is installed, the following message may appear: Oracle Developer 6.0 D:\winnt\Profiles\All Users\Start Menu\Programs\oracle\Oracle Developer 6.0 is not accessible. The folder was moved or removed. Ignore this message. functionality.

2.15

Press OK.

There is no impact on the product

Database Admin Scripts Require OTM The Database Admin build/drop scripts will fail if they do not find Oracle Translation Manager SQL scripts. This problem can be avoided by first explicitly installing Oracle Translation Manager from the product CD.

2.16

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

2.17

Module MFC42.DLL Lost After Install and Reboot Problem: On Windows 95, after installing and rebooting, module MFC42.DLL is missing. Workaround:

2.18

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

TEMPLATES Directory Is Missing In the manual Oracle Forms Developer and Reports Developer: Guidelines for Building Applications, references are made to TEMPLATES/.... However, the TEMPLATES directory is not included with the product.

Page 10

Wednesday, March 22, 2000

4:26pm

Use a different method to invoke the Oracle Installer. 2.19

Forms Requires WebDB Release 2.2 If you are going to use WebDB with the Forms Server, WebDB 2.2 or higher is required.

2.20

WebDB Listener Can Be Installed Only Once per Machine Only one copy of WebDB Listener can be installed on a machine. If you try to install a second copy in another Oracle_Home on that same machine, the first copy may stop working.

2.21

Problem Connecting to Oracle 8.1.6 Server Customers may not be able to connect to the 8.1.6 database from any of the Oracle Forms Developer products using operating system authentication. (This problem is due to bug 1139334 in the database server.)

2.22

Problem Connecting to Oracle 8.0.6 Server for Forms-Graphics 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:

2.23

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.)

Upgrading Your Database Server Agent Forms Developer 6i comes with an 8.0.6 agent with a Forms extension in the same Oracle_Home as Forms. If you already have an existing agent installed, or you want to upgrade to a later version of the agent, a manual step is necessary to install the Forms extension to your agent. Please note that any agent other than 8.0.6 cannot be installed in the same Oracle_Home as Forms, and only one agent should be used at a time. Also, we highly recommend staying with the 8.0.6 agent. These installation steps, below, are the same for both Windows NT and UNIX. (Please note that the files are platform-specific, and you should not copy files across platforms.)

Page 11

Wednesday, March 22, 2000

4:26pm

Follow the steps below to manually install Forms support for your agent. (Currently 8.0.6, 8.1.5, and 8.1.6 are supported). These particular instructions assume that an agent with the Forms extension is installed in Oracle_Home $OH, and you want to copy the Forms extension from $OH to an agent installed in Oracle_Home $OH2. 1. Copy $OH/network/agent/Jobs/Oracle/forms/general/* to the corresponding directory (create one if necessary) in $OH2. 2. Copy $OH/network/agent/Events/Oracle/forms/fault/* to the corresponding directory (create one if necessary) in $OH2. 3. Copy $OH/network/agent/Tcl/frminit.tcl to the corresponding directory in $OH2. 4. Copy $OH/network/agent/config/nmiforms.tcl to the corresponding directory 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). 2.24

Custom Install of Wallet Manager Requires Net8 Assistant Wallet Manager requires Net8 Assistant in order to launch successfully. In the typical, default install of Forms Developer, both these components will be installed for you. However, if you choose a custom install, where you select specific components, and you install Wallet Manager, then you also need to install Net8 Assistant.

2.25

Integration with Oracle Repository Oracle Forms Developer can be integrated with Oracle Repository. This 6i release is shipped with a d2sc plug-in (similar to those provided for PVCS, Clearcase, and other products) that allows integration with Repository for source control management. Users will be able to check in and check out FMBs, MMBs, and so forth, and can then use Repository's dependency tracking and other advanced functionality. (See the Repository documentation for more information.) This initial feature establishes the potential for enhanced levels of integration in future Forms Developer releases.

2.26

Client Platform Certifications Oracle JInitiator is the only supported client platform for the initial release of Oracle Forms Server R6i.

Page 12

Wednesday, March 22, 2000

4:26pm

Additional client platforms such as Internet Explorer R5.0 using the native JVM, Sun Solaris JDK 1.1.7B, or Apple MRJ have not yet been certified with the initial release of Oracle Forms Server R6i. It is expected that the certification on these additional platforms will be complete and supported with the first patch release to R6i. For the latest information regarding supported client platforms and their support level, consult the current version of the Client Platform SOD, available from the Oracle Technology Network (http://technet.oracle.com) website or your Oracle support representative. 2.27

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

2.28

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

2.29

Use Caution If Deinstalling Intersolve Drivers Do not deinstall Intersolve drivers (ODBC) from an Oracle_Home if other products on another Oracle_Home on that machine use them. Deinstalling the drivers from one Oracle_Home will remove them from the entire system.

3

P r o j e c t

B u i l d e r

No known problems. 4

F o r m

B u i l d e r

4.1

Effect of Fill Patterns on Performance Assigning a fill pattern to a large Forms object may degrade runtime performance on the web. Objects are filled in 64x64 pixel

Page 13

Wednesday, March 22, 2000

4:26pm

increments. Thus, objects larger than 64x64 require multiple operations. (For example, painting a window of size 800x600 would require 120 such operations.) Recommendations: Avoid using fill patterns for large objects unless doing so is a significant user requirement. Also, minimize the number of different patterns. (Each pattern used requires 4K of memory.) 4.2

Undocumented Error Messages(FRM-99999) Any Forms error message not documented in the online help will display a generic message: FRM-99999

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

The details of these error messages are documented in the following subsections.

4.2.1

Error Messages 1412 and 1413 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.

4.2.2

Error Messages 10905-10909 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 (.). 2. A Form Parameter (PARAMETER.). 3. A global PL/SQL variable (GLOBAL.). 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.

Page 14

Wednesday, March 22, 2000

Cause: Action:

4:26pm

One or more of the attributes of the LOV size and position is negative. 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.

4.2.3

Error Messages 18114-18121 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. Action:

A typical

value for this variable is c:\orant\forms60\java. 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

Page 15

Wednesday, March 22, 2000

Action:

4:26pm

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. 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

Action:

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. 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

Page 16

Wednesday, March 22, 2000

4:26pm

Interface. 4.3

Forms Environment Variable Added A new environment variable is available: FORMS60_WEB_CONFIG_FILE You can use it to specify the full path and name of the Forms CGI configuration file. For example:

FORMS60_WEB_CONFIG_FILE=c:\temp\myfile.cfg

The default value is \forms60\server\formsweb.cfg 4.4

Java Keybindings API Provided To provide consistent, configurable, and performant keybindings in Forms, a keybinding API is provided. This API first downloads keybindings to the client. The API can then query the key sequence and return the corresponding form action or query the form action and return the corresponding key sequence. See the following subsections for details.

4.4.1

FormAction.java Standard form actions are defined in FormAction.java. These form actions are static instances of the class FormAction. For example, the Next Field form action can be addressed as FormAction.FA_NEXT_FIELD. The constants for the various form actions in FormAction.java are obtained from frmweb.res. The following shows the beginning of 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

Page 17

Wednesday, March 22, 2000

public static final FormAction FA_CLEAR_FIELD

FormAction(2); = new FormAction(3);

. . . The following is the list of all the static constants for keybindings included in the FormAction.java class. FA_NEXT_FIELD FA_PREVIOUS_FIELD FA_CLEAR_FIELD FA_UP FA_DOWN FA_SCROLL_UP FA_SCROLL_DOWN FA_EDIT FA_RETURN FA_LIST_OF_VALUES FA_HELP FA_EXIT FA_SHOW_KEYS FA_COMMIT FA_NEXT_PRIMARY_KEY FA_CLEAR_RECORD FA_DELETE_RECORD FA_DUPLICATE_RECORD FA_INSERT_RECORD FA_NEXT_SET_OF_RECORDS FA_NEXT_RECORD FA_PREVIOUS_RECORD FA_CLEAR_BLOCK FA_BLOCK_MENU FA_NEXT_BLOCK FA_PREVIOUS_BLOCK FA_DUPLICATE_FIELD FA_CLEAR_FORM FA_ENTER_QUERY FA_EXECUTE_QUERY FA_DISPLAY_ERROR FA_PRINT FA_COUNT_QUERY FA_UPDATE_RECORD FA_FUNCTION_0 FA_FUNCTION_1 FA_FUNCTION_2 FA_FUNCTION_3 FA_FUNCTION_4 FA_FUNCTION_5

4:26pm

Page 18

Wednesday, March 22, 2000

4:26pm

FA_FUNCTION_6 FA_FUNCTION_7 FA_FUNCTION_8 FA_FUNCTION_9 FA_LIST_TAB_PAGES 4.4.2

KeyBinder.java -- Using the API Use the KeyBinder API to download keybindings and get a requested form action or key sequence. The following is an overview of the process: 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, this method requests that the server send the bindings. This is not a blocking call, because we do not want to incur a round-trip for getting keybindings from the server. The next time a round-trip occurs, 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 the client. public synchronized static KeyEvent getKeySequence(FormAction action) *This method gets the key sequence corresponding to a requested form

Page 19

Wednesday, March 22, 2000

4:26pm

action. public synchronized static FormAction getFormAction(KeyEvent event) *This method gets the form action corresponding to a requested key sequence.

4.4.3

Example of KeyBinder.java API The following example shows programming pertinent to the use of the KeyBinder.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 { } . . .

Page 20

4.5

Wednesday, March 22, 2000

4:26pm

On Windows, Forms Server and Web Previewer Require NT The Forms Server component will not run on Windows 95 or 98. runs only on the NT version of Windows.

It

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

4.6

Server Does Not Work If Host and Machine Name Differ 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.

4.7

Requirements for Using Run_Product on the Web If you use Run_Product in a form to run a report and want to display the output in the browser window, it is necessary to do the following: On Windows NT, remove the TMP user environment variable. On Unix, remove the TMPDIR environment variable.

4.8

Database Commands Available on Separate Start Menu In this release, the database commands Build, Drop, Grant, and Revoke are listed on their own Start Menu, entitled "Oracle Forms 6i Admin," which is separate from the Start Menu for the main Forms product.

4.9

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

4.10

Forms Server Needs to Access the Wallet File If you register the Forms Server as an NT service and configure it

Page 21

Wednesday, March 22, 2000

4:26pm

with https as the connect mode, launching Forms applets may fail because the service is not able to access the wallet file on the server. To work around this problem, you should either run the Forms Server from the command line (that is, not as a service), or, if you do want to run the Forms Server as a service, do the following: 1. In the services dialog, select the Forms Server service and click the Startup button. 2. In the "Log On As:" section, select the "This Account" radio button. 3. In the "This Account" field, enter the account name under which Forms was installed, and fill in the password information for that account. 4. Click the OK button and restart the Forms Server service. 4.11

Netscape Users Prompted to Save Report HTML File The installation process for Forms Server creates a registry entry named FORMS60_REPFORMAT with value of "HTML" (upper case). If a user is running a Forms applet in a Netscape browser that launches a report, 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_REPFORMAT registry entry to "html" (lower case).

4.12

Forms-Reports Integration Requires that TMPDIR Not Be Set In order for Forms-Reports integration to work on the web on a Unix system, the variable TMPDIR must not be set. Unset this environment variable before starting the Forms listener.

4.13

Changing Font Causes Problem in Forms Problem: When using Form Builder, if you draw a text object and subsequently change its font, then the copy, paste, and delete keys will stop working. Workaround:

4.14

None.

Performance Collection Services Now Available The Forms runtime diagnostics have been enhanced with the addition of Performance Collection Services. These provide you with

Page 22

Wednesday, March 22, 2000

4:26pm

information you can use to better understand and improve your application's runtime performance. The following subsections provide details.

4.14.1

How to Use Performance Collection Services To activate Performance Collection Services, include ‘record=performance’ in the command line argument (for runtime in a client/server environment), or as a part of ‘serverArgs’ parameter in 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 is not specified, a file with a unique filename is created. This name is in the format ‘perf_xxxx’ where ‘xxxx’ is the ProcessId of the runtime process running. In the HTML file, this invocation will be: <param name= "serverArgs" value = "module=.. userid=.. record=performance log=yourlogname">

4.14.2

Events Collected by Performance Services Event ___________ ClientTime Logon Time Logoff Time DB Time APServerTime

4.14.3

Meaning _________________________ Time spent at the Client Time to logon to the Database Server Time to logoff the from the Database Server Time for any database operations, such as query Processing time at the Forms Server

Analyzing the Performance Data The data collected by Performance Services is analyzed using PERL scripts ‘f60parse.pl’, which are located in the ORACLE_HOME\forms60\perl directory perl f60parse.pl -input=infile -eventf=’evfile’ -outputf=’ofile’ where:

Page 23

Wednesday, March 22, 2000

Infile Evfile Ofile

4:26pm

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

Eventf and outputf are optional parameters. A typical event description file is of the following form: Client _______ DBLOGON APServer DBPROC APServer APServer APServer DBLOGOFF

ThinkTime __________ Logon Logon_Wr DB DB_App DB_Write DB_Logoff Logoff

THINK_START _______________ DBLOGON_START DBLOGON_END DB_START DB_END DB_END DB_END DBLOGOFF_START

THINK_END ____________ DBLOGON_END THINK_START DB_END DB_START THINK_START DBLOGOFF_START DBLOGOFF_END

If an events file is not specified, the following default events are assumed 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. 4.14.4

Default Events By default, the output appears in the following HTML files (which can be viewed in a browser): 1. 2. 3. 4.

index.html - Summary of user action detailed1.html - Detailed events detailed2.html - Detailed event collection 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)

Page 24

Wednesday, March 22, 2000

4:26pm

3. Detailed Description (Level2) 4.15

Using Oracle Trace Instead of PECS for Performance Analysis Although PECS is supported in this 6i release, such support is not planned for any future Forms releases. You can use Oracle Trace to provide functionality that is similar to PECS. Integration of Oracle Trace functionality with Forms is a beta feature introduced in Forms Developer 6i. The Oracle Trace-based Forms implementation supports a subset of the events defined in PECS. In addition, a few new events are also defined and supported. The event definitions reside in the file ORACLE_HOME\otrace80\admin\fdf\oforms.fdf on Windows NT, and ORACLE_HOME\otrace\admin\fdf\oforms.fdf on Unix. This file is essential for activating Trace in Forms, and is supplied as collateral on the Forms Developer 6i CD.

4.15.1

Initiating Trace Data Collection Data collection on the Forms Server needs to be initiated either through the command line, or through Trace Manager -- which comes as part 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 as collateral 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 the HTML file used for running the form.

4.15.2

Using the Oracle Trace Command-Line Interface You invoke this interface by variations of the OTRCCOL command, which provide the following functions: OTRCCOL OTRCCOL OTRCCOL OTRCCOL

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

The parameter job_id can be any numeric value.

The input parameter

Page 25

Wednesday, March 22, 2000

4:26pm

file contains specific parameter values required for each function as shown in the following examples. COL_NAME (collection name) and CDF_FILE (collection definition file) are initially defined in the START function input parameter file. The OTRCCOL START command invokes a collection based upon parameter values contained in the input parameter file. For example: otrccol start 1234 my_start_input_file where 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 These parameter file records are all required for otrace collection, and the regid record must contain the values shown, including your SID value. The OTRCCOL STOP command halts a running collection as follows: otrccol stop 1234 my_stop_input_file where my_stop_input_file contains the collection name and cdf_file name. You can use the same otrace input parameter file as used with the START command.

4.15.3

Oracle Trace Collection Files Running an Oracle Trace collection produces the following collection files located in the directory specified in INIT.ORA or in the default collection path:

4.15.4

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.

Events Collected by Trace 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)

Page 26

Wednesday, March 22, 2000

* * * * * * * *

ExeQuery Trigger LOV MenuCreate Alert Timer Window Canvas

-

4:26pm

(Query Execution) (Trigger) (LOV) (MenuCreation)

Additional Events: * DB Logon * DB Logoff * ServerTime * DBTime You can access the Oracle Trace data contained in the collection files 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. 4.15.5

Using the Oracle Trace Statistics Reporting Utility The Oracle Trace statistics reporting utility displays statistics for all items associated with each occurrence of a server event. These reports can be quite large. You can control the report output by using command parameters. Use the following command and optional parameters 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 a listing of specific process identifiers for which you might want to run other reports. You can manipulate the output of the Oracle Trace reporting utility by using the following optional report parameters: output_path -p []

Specifies a full output path for the report files. If not specified, the files will be placed in the current directory. 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

Page 27

Wednesday, March 22, 2000

-P

-w# -l# -h -s -a

4.15.6

4:26pm

participated in the collection. The output files are named collection_Ppid.txt. 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. Sets report width, such as -w132. The default is 80 characters. Sets the number of report lines per page. The default is 63 lines per page. Suppresses all event and item report headers, producing a shorter report. Used with Net8 data only (or SQL*Net for Oracle7). Creates a report containing all the events for all products, in the order they occur in the data collection (.dat) file.

Viewing the Trace Data To format the data to the database and inspect it using the Trace DataViewer, 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. The views 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.

4.15.7

Trace Tables In case the Diagnostic Pack is not available, the data uploaded to the database can be obtained from the tables named V_192216243_F_45_E_yy_6_0, where yy is the event number. The various events defined in the 'fdf' file and the associated numbers and items are as follows:

Page 28

Wednesday, March 22, 2000

4:26pm

FORMS DURATION EVENTS AND ITEMS Event # and Name ________________ 1. Session

Description and Items _____________________________________ 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.

Page 29

Wednesday, March 22, 2000

44. DBLogoff

4:26pm

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

(see also next subsection) 4.15.7

Trace Tables -- continued 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.

4.16

How to Deploy a Certificate from a Non-Trusted Authority The following describes how to deploy a certificate from a Certificate Authority that is not trusted by Oracle Forms by default. The Forms HTTPS feature trusts certificates issued by the following Certificate 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

Page 30

Wednesday, March 22, 2000

4:26pm

Certificate (not one of the above, and not trusted by default). However, these instructions are generalized, and could also be used to 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.

4.16.1

Create a Wallet Using the Oracle Wallet Manager 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.

4.16.2

Create a Certificate Request 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

Page 31

Wednesday, March 22, 2000

4:26pm

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 request to the certificate authority. The most common way is to cut and paste the certificate request to the HTML form of the CA. You can also copy the certificate request text from the body of the message box, and paste it into an e-mail message and send the request to a certificate authority which accepts such requests. In these instructions, we will use the Trial Server Certificate from Verisign. Using your browser go to the url www.verisign.com. (Do a search for ‘Trial Server Certificate’ if such a link is not available 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.

Page 32

Wednesday, March 22, 2000

4:26pm

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. 4.16.3

Install the Trial CA Root Certificate You need to use Internet Explorer 5.0 to install the CA root certificate and export it as a Base 64 encoded X.509(.CER) file that can be read by Oracle Wallet Manager. (Unfortunately, Netscape cannot be used, since it does not allow you to export the root certificates 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’.

Page 33

Wednesday, March 22, 2000

12.

4.16.4

4.16.5

4:26pm

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

Replace the certdb.txt of Jinitiator with the New Version 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.

Import the User Certificate After Verisign processes your request, you will receive an email from Verisign containing the certificate which looks something like this: -----BEGIN CERTIFICATE----DzANBgNVBAoTBk9yYWNsZTEoMCYGA1UECxMfRW50ZXJwcmlzZSBBcHBsaWNhdGlv biBTZXJ2aWNlczEhMB8GA1UEAxMYRUFTUUEgQ2VydGlmaWNhdGUgU2VydmVyMB4X DTk5MDcyNjE3MzkyNloXDTAwMDEyMjE3MzkyNlowPTELMAkGA1UEBhMCVVMxDzA BgNVBAoTBm9yYWNsZTEOMAwGA1UECxMFZm9ybXMxDTALBgNVBAMTBGFtYXIw -----END CERTIFICATE----After you receive the user certificate that you requested from the CA, you must import it into the wallet that you created. You can import 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. An Import 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 received or the web page. 4. Paste the certificate into the window, and click OK. A message at the bottom of the window informs you that the user certificate was successfully installed. 5. Click OK. You are returned to the Oracle Wallet Manager main panel, and the user certificate is displayed at the bottom of the User Certificates tree. Remember to save the wallet to the disk. To import a file that contains the user certificate:

Page 34

Wednesday, March 22, 2000

4:26pm

1. From the menu bar, click Operations->Import User Certificate. The Import 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, for example, cert.txt. 4. Click OK. A message at the bottom of the window informs you that the user certificate was successfully imported into the wallet. Click OK to close the dialog box. You are returned to the Oracle Wallet Manager main panel, and the user certificate is displayed at the bottom of the User Certificates tree. Remember to save the wallet to the disk.

4.17

Installing OEM:

Clarification to Instructions

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 step is only necessary for a special release of OEM 2.0.4. 5

R e p o r t

B u i l d e r

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

G r a p h i c s

B u i l d e r

Additional Steps Required for Cartridge If you are going to use Oracle Application Server (OAS) and the Graphics Cartridge, you need to perform additional steps after installing OAS and Graphics in separate ORACLE_HOMEs. There are separate instructions for NT and Solaris. following subsections.

6.1.1

See the

Additional Cartridge Installation Steps for NT 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 back to the default ORACLE_HOME (the directory in which Graphics is installed). In the following examples, you should replace

Page 35

Wednesday, March 22, 2000

4:26pm

%ORACLE_HOME% with the actual physical directory for the default (Graphics) ORACLE_HOME, and replace %OAS_HOME% with the actual physical directory for the OAS ORACLE_HOME. Using the NT Registry Editor, add the following registry entries to the OAS ORACLE_HOME registry: Symbol Value ______ ______ DE60 %ORACLE_HOME%\TOOLS\COMMON60 GRAPHOGD60 %ORACLE_HOME%\GRAPH60\GWIZ_OGD GRAPHICS_WEB_DIR %ORACLE_HOME%\GRAPH60\WEB_OGD MM60 %ORACLE_HOME%\TOOLS\COMMON60 OCL60 %ORACLE_HOME%\GRAPH60 OWS_IMG_DIR %OAS_HOME%\ows\4.0\admin\img TK60 %ORACLE_HOME%\TOOLS\COMMON60 UI60 %ORACLE_HOME%\TOOLS\COMMON60 VGS60 %ORACLE_HOME%\TOOLS\COMMON60 NOTE: Be sure to replace %ORACLE_HOME% and %OAS_HOME% with the actual full directory paths in all of the value entries. 4. Create a sub-directory named WEB_TMPDIR under the directory that the OAS's ORACLE_HOME/img_dir/ points to.

6.1.2

Additional Cartridge Installation Steps for Solaris After configuring the Graphics Cartridge in OAS as documented, set the following environmental variables in the OAS environment: 1. ORATOOLS_HOME must be set to point to the ORACLE_HOME of Developer. 2. $ORATOOLS_HOME/lib must be added to the end of the LD_LIBRARY_PATH. 3. GRAPHICS_WEB_DIR must be set to the location of the Graphics displays 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 be created. 6. The OAS listener must have a virtual path /ows-img that points to the physical directory $ORACLE_HOME/ows/4.0/admin/img. After you make the above changes, OAS must be restarted to pick up the changes to the environmental variables.

Page 36

6.2

Wednesday, March 22, 2000

4:26pm

Environment Variables Must Be Set on Unix In order for Graphics integration to work on a Unix system, you must set the following environment variables: setenv PRINTER <printer_name> setenv TK2_PRINT_STATUS echo

7

Q u e r y

B u i l d e r

No known problems. 8

S c h e m a

B u i l d e r

No known problems. 9

T r a n s l a t i o n

B u i l d e r

No known problems. 10

P r o c e d u r e

B u i l d e r

No known problems. 11

D e m o s No known problems.

12

O p e n

C l i e n t

A d a p t e r

No known problems. 13

N a t i o n a l

L a n g u a g e

S u p p o r t

13.1

Known Problems for All Languages

13.1.1

Form Builder User Interface May Not Be Fully Translated Customers who install the Forms Builder with a language other than English may find that the user interface is a mixture of local language and English. The Forms Builder is not translated fully for some languages. For these languages, please use the English language interface.

Page 37

Wednesday, March 22, 2000

4:26pm

To do this, set DEVELOPER_NLS_LANG=AMERICAN_AMERICA. USER_NLS_LANG=< Language>_. 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 the Oracle character set that you wish to use.

13.1.2

Euro Currency Symbol Has Limited Support There is limited support in this release for the Euro currency symbol. To enable a limited use of the Euro symbol in this release, you must do 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 enter the Euro symbol on keyboards without an explicit Euro key, click the NumLock key to enable the Numeric Keypad, then click Alt + 0128.

13.1.3

Some Wizard Buttons Have Untranslated Text In the wizards on Unix systems, some buttons appear with their texts in English.

13.1.4

Restore Icons During Installation Creates Invalid Menus Problem:

When using Software Asset Manager during a custom

Page 38

Wednesday, March 22, 2000

4:26pm

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

13.1.5

Menu Action Not Available Via Keyboard After Print Cancel 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: 13.1.6

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

Avoid repeated cancelling.

FMRWEB.RES Must Be Configured Manually The file "fmrweb.res" contains a keyboard map. This map is used by Oracle Forms Server to detect key strokes entered in the user's browser and map them to Forms actions. The map assumes that the keyboard is similar to a VT100 keyboard. If the user has a PC-style keyboard, we recommend that you copy the file "fmrpcweb.res" over the original "fmrweb.res". This will make the server assume that the keyboard is similar to a 101-key "PC" keyboard. By default, the US versions of fmrweb.res and fmrpcweb.res are installed, regardless of language. In addition, for a particular language, the appropriate mapping files for that language's typical keyboard are installed. They are installed to the files "fmrweb.res" and "fmrpcweb.res", where is the Oracle language code. For instance, the Oracle language code for Latin American Spanish is "esa". To use the files for a particular language instead of the US versions, copy the desired file over the file "fmrweb.res". Starting with Oracle Forms Server 6i, the files "fmrweb_utf8.res" and "fmrpcweb_utf8.res" are also installed. These contain the same key mappings as "fmrweb.res" and "fmrpcweb.res", but the files are encoded in the UTF8 character set. These files should be used if the server is using the UTF8 character set (UTF8 is the character set specified in NLS_LANG).

13.1.7

Information About NLS_LANG Parameter Values

Page 39

Wednesday, March 22, 2000

4:26pm

The manual "Deploying Forms Applications to the Web" refers to a file named \bonus\nls\nlsdrl.wri. However, that file is no longer up-to-date, and is not supplied on the product CD. For information about parameter values for NLS_LANG, consult the documentation for the Oracle8 8.0.6 server. The valid NLS_LANG parameter values are the same for Forms and for that database server. 13.1.8

Wallet Manager User Interface Is in English When you install Wallet Manager from the Forms Developer CD, it will not have a translated user interface. The user interface will be in English. Oracle Wallet Manager translations can be obtained if required. Contact your Oracle representative for more details.

13.2

Known Problems for Double-Byte Languages

13.2.1

Editing with Single-Byte Font 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.

13.3

Known Problems for Japanese

13.3.1

Cannot Save Modules If Character Set Is JA16EUC Problem:

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

Workaround: Use the JA16SJIS character set instead. 13.3.2

Length Limit Moving From Windows to Solaris Problem:

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

Page 40

Wednesday, March 22, 2000

4:26pm

Workaround: No workaround. 13.3.3

PL/SQL Editor Display Problems Problem:

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

Workaround: 13.3.4

None.

UTF8 Limitation 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:

13.3.5

Multibyte Characters Cannot Be Used for PL/SQL Library Name Problem:

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

Workaround: 13.3.6

None.

None.

Different prefs.ora Files May Be Needed Problem: If a customer selects Japanese installation, prefs.ora for the Japanese language in JA16SJIS encoding will be installed. This causes some problems for customers who develop their applications with 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.

13.3.7

Message Texts from PL/SQL Interpreter Are Mixed When running Procedure Builder, error messages (for example, ORA04098) from the PL/SQL Interpreter are sometimes displayed in English and sometimes in Japanese.

Page 41

13.3.8

Wednesday, March 22, 2000

4:26pm

Storage Requirement for Installing Cue Cards on Unix If you choose to install the Cue Cards on a Unix system, both the Japanese tar files and the US tar files will be installed. The total storage requirement for these tar files is approximately 275Mb. The Cue Cards are optional. If your storage space is limited, you may choose to not install the Cue Cards.

13.4

Known Problems for Arabic

13.4.1

Limitations for Displaying Charts on Solaris Customers using the Solaris version of Forms Developer 6i who generate charts should note that the Solaris operating system has less support for fonts and locales than Windows NT. Specifically, Solaris does not have an official Arabic locale. Forms Developer 6i for Solaris has only very limited support for the Unicode locale. As a result, charts generated on Solaris will not display text correctly if Arabic or Unicode is used. This will also happen with charts displayed on any Web Client that is accessing a Solaris-based server. This occurs because the chart is rendered into bitmap graphics on the server. If the server is Solaris-based, then Arabic and Unicode fonts are not available. Other text in forms, reports, and graphics is usually sent directly to the client and rendered in the client's locale. The recommended workaround is to select a chart text font that is Western European and not Unicode.