C
AppletViewer

C.1 Introduction

This appendix describes the AppletViewer, an alternative to using Oracle JInitiator. The AppletViewer is a JDK component and an Oracle-supported product that client machines use to view applications running on the Forms Server. Upgraded versions are available for download from the Forms Developer Web site.

Note:

The AppletViewer is only supported on Windows 95 and Windows NT 4.0.

C.2 Running Application in the AppletViewer

To run applications in the AppletViewer, you must complete the following steps:

• Prepare to run your application with the AppletViewer.

• Add the clientBrowser parameter to your base HTML file.

• Set the clientBrowser parameter.

When running your application in the AppletViewer, requests to show a URL (for example, web.showDocument and RUN_PRODUCT) will be ignored by the AppletViewer. If this is the case, you will need to follow the process to trust the Forms applet, as described later in this chapter in Section C.3.1, "Trusting the Forms Applet by Registering Its Signature".

C.2.1 Preparing to Run Your Application with the AppletViewer

In order to prepare to run your application within the AppletViewer, make the AppletViewer available for download and inform your users that they will have to install the AppletViewer on their client machines. Complete the following:

1. Customize JDK_DOWNLOAD.HTM.
   JDK_DOWNLOAD.HTM is the template HTML file that allows your users to download the AppletViewer.

2. Copy JDK.EXE to your Web server.
   You must copy JDK.EXE to the location specified within JDK_DOWNLOAD.HTM.

3. Copy JDK_DOWNLOAD.HTM to your Web server.
   You must copy JDK_DOWNLOAD.HTM to the location specified within JDK_DOWNLOAD.HTM.

C.2.2 Adding the clientBrowser Parameter to your Base HTML File

To use the clientBrowser parameter, you must have security permissions to issue a system call that executes the named application. In general, when loading Java class files, the Forms applet is not trusted and, as such, cannot issue such system calls. However, when the Forms applet is trusted, it is able to issue these calls. The Forms applet is considered trusted when one of the following is true:

• The Forms applet signature is "registered" on the client machine as described in Section C.3.1, "Trusting the Forms Applet by Registering Its Signature".

• The Forms Java class files are installed locally on the client system and the CLASSPATH environment variable is set as described in Section C.3.2, "Trusting the Forms Applet by Installing the Forms Java Class Files Locally".

These HTML file examples assume that you trusted the Forms applet by registering its signature on your machine. If you trusted the Forms applet by locally installing the Forms Java class files instead, you should not download the F60ALL.JAR file. Therefore, remove the ARCHIVE="/.../f60all.jar" applet tag from your HTML file.

C.2.3 Setting the clientBrowser Parameter

To set the clientBrowser parameter, do one of the following:

• Add the clientBrowser parameter to your HTML file.

• Add the clientBrowser parameter to your HTML file, and have each client modify their JDK_SETUP.BAT file.

Add the clientBrowser Parameter to Your HTML File.

This option assumes that every client has its browser executable installed into the same physical directory because the physical path of the browser is hard-coded in the HTML file. For example:

<APPLET CODEBASE="/forms60code/" 
     CODE="oracle.forms.engine.Main" 
     ARCHIVE="/forms60code/f60all.jar" 
     HEIGHT=480 
     WIDTH=640> 
     <PARAM NAME="serverArgs" VALUE="module=start.fmx userid=scott/tiger"> 
     <PARAM NAME="clientBrowser"
     VALUE="c:\programfiles\netscape\communicator\program\netscape.exe"> 
</APPLET> 

Add the clientBrowser Parameter to Your HTML File and Have Each Client Modify Their JDK_SETUP.BAT File.

This option is best if there is a possibility that clients have installed their browser executables into different physical directories. It does assume, however, that all clients are using the same browser. For example, the HTML file might look like this:

<APPLET CODEBASE="/forms60code/" 
     CODE="oracle.forms.engine.Main" 
     ARCHIVE="/forms60code/f60all.jar" 
     HEIGHT=480 
     WIDTH=640> 
     <PARAM NAME="serverArgs" VALUE="module=start.fmx userid=scott/tiger"> 
     <PARAM NAME="clientBrowser" VALUE="netscape"> 
</APPLET> 

And JDK_SETUP.BAT would look like this:

     SET CLASSPATH=C:\ORANT\JDK1.1\JDK\LIB\CLASSES.ZIP 
     PATH C:\PROGRAM FILES\NETSCAPE\COMMUNICATOR\PROGRAM; 
     C:\ORANT\JDK1.1\JDK\BIN;%PATH% 

C.3 Registering the Forms Applet Signature

A signature allows client machines to verify that a file has been downloaded from a valid and trusted entity (a signer). This allows client machines to protect themselves from malicious or malfunctioning Java archive (JAR) files. In order for a JAR file to be validated by a client, the signature of that file must be registered on the client machine. Javakey is a Sun Microsystems command-line tool that generates digital signatures for JAR files.

The Forms applet is itself a signed JAR file. You have two options for registering the Forms applet signature. Choose one of the following:

• Register the signature on your client machine(s) using the Forms applet signature we provide.

• Re-sign the Forms applet with your own signature and register that signature on your client machine(s). If you choose this method, please refer to http://java.sun.com/security/usingJavakey.html for instructions on creating and signing JAR files.

C.3.1 Trusting the Forms Applet by Registering Its Signature

To trust the Forms applet by registering its signature:

1. Copy the Forms Developer certificate to \ORACLE_HOME\FORMS60\JAVA on the client machine.
   The certificate is a file named Dev.x509. It is located in \ORACLE_HOME\FORMS60\JAVA on the server.

2. Open a DOS Command Prompt, and navigate to \ORACLE_HOME\FORMS60\JAVA.

3. Type: javakey -c Developer true
   This command creates a trusted identity for the AppletViewer on the client's identity database using the exact name of the certificate provider.

4. Press Enter.

5. Type javakey -ic Developer Dev.x509
   This command imports the Dev.x509 certificate into the client's JDK identity database and associates the certificate with the trusted identity created in step 3.

6. Press Enter.

C.3.2 Trusting the Forms Applet by Installing the Forms Java Class Files Locally

To trust the Forms applet by installing the Java class files locally:

1. Copy the \ORACLE_HOME\FORMS60\JAVA directory to a new directory on the client machine.
   Copy this directory exactly; do not change the directory structure in any way.

2. Modify JDK_SETUP.BAT in your ORACLE_HOME directory:
   1. Open JDK_SETUP.BAT in a text editor.

   2. Modify the CLASSPATH environment variable to reference the new directory.

   3. Save your changes to JDK_SETUP.BAT.

   C.4 Instructions for the User

   To run an application from within the AppletViewer, complete the following steps:

   • Install the AppletViewer.

   • Run the AppletViewer.

   • Invoke a Web browser from within the AppletViewer.

   C.4.1 Installing the AppletViewer

   To install the AppletViewer, use the Oracle Installer to install the JDK AppletViewer:

   1. Shut down any active Windows applications.

   2. From the taskbar, choose StartRun.

   3. In the Run dialog, type the following (where D: is your CD-ROM drive letter): D:\setup.exe and click OK.

   4. In the Oracle Installation Settings dialog, check the default values for your company name and your ORACLE_HOME directory.

   5. Click Oracle Forms Server.

   6. Click Custom.

   7. From the list of Available Products, select JDK AppletViewer.

   8. Click Install.

   C.4.2 Running the AppletViewer

   To run the AppletViewer:

   1. From a DOS command, navigate to the AppletViewer executable (appletviewer.exe).

   2. Run the AppletViewer executable, specifying the host name, HTML file virtual directory, and HTML file.
      For example, type: appletviewer http://myhost.com/web_html/start.html
   3. Press Enter.

   C.4.3 Invoking a Web Browser From Within the AppletViewer

   To invoke a Web browser from within the AppletViewer:

   1. Trust the Forms using one of two methods:
      • Register the Forms applet signature.

      • Install the Forms Java class files locally.

   2. Add the clientBrowser parameter to your base HTML file.