Oracle9i TM Lite Installation and Configuration Guide
Release 5.0

May 2001

Part Number: A90112-01

Copyright © 2001, Oracle Corporation.
All Rights Reserved.

 


This document provides information regarding the system requirements for Oracle9i Lite 5.0 as well as detailed instructions on how to install, upgrade to, and configure Oracle9i Lite 5.0. It includes discussions of the following topics:

1. System Requirements

This section describes the system requirements for Oracle9i Lite 5.0.

1.1 Hardware Requirements

1.1.1 The Mobile Server

1.1.2 The Mobile Client for Windows 32 and Web-to-Go & the Mobile Development Kit on Windows 32

1.1.3 The Mobile Client on Palm

1.1.4 The Mobile Client on Windows CE/PocketPC

1.1.5 The MobilenClient on EPOC

1.2 Software Requirements

1.2.1 The Mobile Server

1.2.2 The Mobile Client on Windows 32 and Web-to-Go & the Mobile Development Kit on Windows 32

1.2.3 The Mobile Client on Palm

1.2.4 The Mobile Client on Windows CE/PocketPC

1.2.5 The Mobile Client on EPOC

1.2.6 Branch Office

1.3 Required Oracle Components

2. Installation

This section contains the instructions to install the Mobile Server and the Mobile Development Kit.

Note:

  1. If Oracle 8.1.6 client software is already installed on your machine, do not install Oracle9i Lite in the same directory. In this case, you must install Oracle9i Lite in a different directory.

  2. If the client software of Oracle 8.1.7 or a later version is already installed on your machine, it is recommended that you install the Mobile Server in the same Oracle_Home directory where the Oracle data server client software is already installed. This will avoid having duplicate copies of the required support files installed on your machine.

  3. If the Oracle9i Application Server 1.0.2.1 or a later version is already installed on your machine, it is recommended that you install the Mobile Server in the same Oracle_Home directory where the Oracle9i Application Server is already installed. This will avoid having duplicate copies of the required support files installed on your machine.

2.1 Installing the Mobile Server

  1. Insert the Oracle9i Lite CD-ROM into your CD-ROM drive. The install program (setup.exe) starts automatically. The Welcome dialog appears.


    To see the Oracle products that are installed on your system, click Installed Products. To continue, click Next.

  2. The File Locations dialog appears.


    Click Next.

  3. Enter the name and location of your Oracle Home directory, or accept the defaults. The directory name must be eight characters or less. Click Next.

    Note: If you have Oracle8i installed on your machine, or any other Oracle product which uses the Oracle Universal Installer, enter "DEFAULT_HOME" as the Oracle Home name. Then enter the desired directory location for your Oracle9i Lite installation.

  4. The Installation Types dialog appears.


    Select the Mobile Server, then click Next:

  5. The Available Product Components dialog appears.


    Select the components that you want to install. Click Next.

  6. The Mobile Server Repository Database Information appears. Enter the Host Name, Port, and Net Service Name for the Oracle8 or Oracle8i server to be used as the repository. The Net Service Name is your Global Database Name and is not the "SID".


    Contact your system administrator if you do not know your Host Name, Port, or Net Service Name. Click Next.

  7. The "Do you want to install the Mobile Server repository" dialog appears. Select Yes. Click Next.

  8. The Oracle Protocol Support dialog appears. Click Next.

  9. The Summary dialog appears showing the global settings and space requirements for the Mobile Server on your system. Click Install.

  10. The Install dialog appears and indicates the installation progress.


  11. When the installation of the Mobile Server and all the support files is completed, the Mobile Server Repository Wizard dialog appears. On some machines, the Mobile Server Repository Wizard may appear at this point in a minimized window, which can be accessed from the task bar.

    Enter the password for the user SYSTEM for the Oracle database server. If you do not have the password for the user SYSTEM, contact your system administrator. Click Next.

  12. The Mobile Server Repository Wizard indicates that no existing repository is found and that a new repository will be installed. Click Next.

    Note: The Mobile Server Repository Wizard queries against the database for the previously installed components of Web-to-Go and Consolidator. If it finds any of the previous versions of Web-to-Go and Consolidator, it will migrate the previous version of Web-to-Go and Consolidator Repository to the latest version of the Mobile Server Repository. If it does not find a previous version, it will install a new Mobile Server Repository. For information on using the Mobile Server Repository Wizard for migrating your repository, see Section 2.4 Migrating the Mobile Server Repository.

  13. Enter the Schema Name and the password for the Mobile Server Repository. Click Next.

  14. The Summary dialog appears. Click Next.


  15. The Mobile Server Repository is in the process of being installed. A progress panel appears indicating the installation steps and the status of the installation process. When the installation is completed, click Next.

  16. The Repository Wizard indicates that the installation of the Mobile Server Repository is completed. It displays the path of the Repository.log file, which you should check for any errors. Click Finish to exit the Repository installation.

  17. The End of Installation dialog appears. Click Exit to exit the installation process, or click Next Install to install the Mobile Development Kit.

2.2 Installing the Mobile Development Kit

  1. If you click Next Install, the File Locations dialog appears again to enable you to specify the location for your next installation. Enter a name for your Oracle Home and a directory path.




    Enter the name and location of your Oracle Home directory, or accept the defaults. The directory name must be eight characters or less. Click Next.


    Note: If you have Oracle8i installed on your machine, or any other Oracle product which uses the Oracle Universal Installer, enter "DEFAULT_HOME" as the Oracle Home name. Then enter the desired directory location for your Oracle9i Lite installation.

  2. The Installation Types dialog appears.


    Select Mobile Development Kit. Click Next.

  3. The Summary dialog appears showing the global settings and space requirements for the Oracle Mobile Server on your system. Click Install.

  4. The Install dialog appears and indicates the installation progress. No action is required.

  5. When the installation is completed, the End of Installation automatically appears.


    Click Exit to exit the installation.

2.3 Additional Installation Options

To develop Java applications for the Oracle Lite database, you must install the Java Development Kit (JDK) version 1.2.2 (or higher).

3. Manual Installation of the Branch Office Database

You can install the Branch Office Database manually. As the following diagram shows, the Branch Office Database occupies the third tier in the four-tier architecture of the Branch Office system. Oracle8i provides the first tier in this architecture. The Oracle9i Lite Mobile Server provides the second tier. The Branch Office Database is the third tier, and the Branch Office Client is the fourth tier.


To install the Branch Office Database manually, perform the tasks that are described in the following sections.

3.1 Install the Mobile Development Kit

Install the Mobile Development Kit (if you have not already installed it). See Section 2 "Installation," for instructions on installing the Mobile Development Kit.

3.2 Deploy Manually the Branch Office Database

To manually deploy the Branch Office Database, follow these steps:

  1. Create the following directories:

    C:\orant [This is the home directory, which is referred to as ORACLE_HOME.]

    C:\orant\bin [This is the binary subdirectory.]

    C:\orant\classes [This is the subdirectory for the Java class files.]

    C:\orant\oldb40 [This is the database subdirectory.]

  2. Copy files

    A. Copy into the subdirectory C:\orant\bin the following files:

    File Name

    Description

    Olobj40.dll Oracle Lite object kernel
    Olod2040.dll ODBC interface
    Olsql40.dll SQL engine
    Oljdbc40.dll JDBC native code
    Createdb.exe database creation utility
    Olsv2040.exe Branch Office listener process
    Olcl2040.dll ODBC Client driver
    Olite40.msg Oracle Lite message file
    Oladcl2040.dll ODBC Client driver setup
    Olad2040.dll ODBC driver setup


    B. Copy the file
    Polite.ini into the Windows NT directory.

    For example, your Windows NT directory may be C\:winnt

    C. Copy the file
    Polite.odb into the directory C:\orant\oldb40

    D. Copy the file
    olite40.jar into the directory C:\orant\classes

  3. Set C:\orant\classes\olite40.jar to the system classpath.

  4. Make sure of the following:

    - The Java runtime is installed.
    - The
    rt.jar file is in the SYSTEM classpath.
    - The jre\bin\classic directory that contains jvm.dll is on the system path.
    - The C:\orant\bin directory is on the system path.

  5. Run the following command:

    olsv2040.exe -install

    This command will install the Branch Office service as a Windows service on your Windows client. The file olsv2040.exe is located in the BIN subdirectory.

  6. Start the Branch Office service.

    To start the Branch Office service, use the Windows service applet from the Services menu. From the Start menu, select Start->Settings->Control Panel. Click Services in the Control Panel window. The Services dialog box appears. Select olite service and click Startup.

3.3 Configure the Client

Create a DSN on the client to access the Branch Office. To create a DSN on the client, follow these steps:

  1. From the Windows Start menu, click Start and then point to Settings.

  2. Click Control Panel.

  3. In the Control Panel, double click the ODBC Data Source icon to open it. The ODBC Data Source Administrator dialog box appears.

  4. Select the User DSN tab. Click Add. The Create New Data Source dialog box appears.

  5. From the scroll-down list in the Name panel, scroll down and select Oracle Lite 40 ODBC Driver (Client). Click Finish. The Oracle9i lite ODBC 2.0 (Client) Setup dialog box appears.

  6. Enter the DSN name for the Branch Office server in the Database Host DSN field. Alternatively, you can enter the names for the Database Directory and the Database File Name. Click OK.

    Your manual deployment of the Branch Office Database is now complete.

4. Migration and Upgrade Path for Oracle9i Lite 5.0

You can migrate your data and upgrade your software from previous versions of this product.

4.1 Definition of Terms

Migration: Conversion of data and replication objects from a previous version of Oracle Lite database to Oracle Lite DBMS 5.0

Upgrade: Upgrading of libraries, executable files, DLL files, and other software components from a previous version of Oracle8i Lite to Oracle9i Lite 5.0

4.2 Entities to Migrate/Upgrade

The entities to migrate and/or upgrade are:

  1. Software Libraries: Oracle produced and owned software libraries
  2. Application Libraries: Custom written application code
  3. Application Data: Data used in specific applications, such as, a CUSTOMER table
  4. Replication Objects: Repository objects, such as, RefreshGroup, MasterGroup, PublicationItem, Subscription

4.3 Supported Migration/Upgrade

The following table describes the components that can be migrated or upgraded from Oracle8i Lite 4.0.1.2.0 to Oracle9i Lite 5.0.

Component to Be Migrated

From Oracle8i Lite 4.0.1.2.0

To Oracle9i Lite 5.0

Comment

Web-to-go Server and Web-to-go Repository

1.3.1

2.0.1

The Mobile Server installation scripts install, or upgrade to, Mobile Server 2.0.1 and migrate Web-to-go Repository 1.3.1 (oraclerm) to the new 2.0.1 Repository (mobileadmin). Existing Web applications and replication objects are automatically migrated.
Consolidator Server and Consolidator Repository

4.0.1

2.01

The Mobile Server installation scripts install, or upgrade to, Mobile Server 2.0.1 and migrate Consolidator Repository 4.0.1 (consolidator) to the new 2.0.1 Repository (mobileadmin).
Synchronization Server and Synchronization Server Repository

1.3.1

2.0.1

The Mobile Server installation scripts install, or upgrade to, Mobile Server 2.0.1 and migrate Synchronization Server Repository 1.3.1 (oraclerm) to the new 2.0.1 Repository (mobileadmin). Existing native applications and replication objects are automatically migrated.
Web-to-go Client

1.3.1

2.0.1

The Web-to-go Client 1.3.1 does not work with Mobile Server 2.0.1. To upgrade and migrate, follow these steps:

  1. Delete the 1.3.1 client, using uninst.exe.
  2. Download and install the Mobile Client for Web-to-Go.
  3. Logon to the Mobile Client for Web-to-Go and go offline.
Consolidator Client

4.0.1

EPOC 4.0.1.x

Windows CE/PocketPC 4.0.1.x

Palm Computing 4.0.1.x

Windows 32 4.0.1.x

The Consolidator Client 4.0.1 does not work with Mobile Server 2.0.1. To upgrade and migrate, follow these steps:

  1. Delete the 4.0.1 client.
  2. Download and install the Mobile Client for <platform>.
  3. Execute synchronization using the Mobile Sync Client.
Consolidator Client

4.0.0.5.0

EPOC 4.0.1.x

Windows CE/PocketPC 4.0.1.x

Palm Computing 4.0.1.x

Windows 32 4.0.1.x

Consolidator Client 4.0.0.5.0 coexists with Mobile Server 2.0.1.

The optional upgrade/migration steps are:

  1. Delete the 4.0.0.5.0 client.
  2. Download and install the Mobile Client for <platform>.
  3. Execute synchronization using the Mobile Sync Client.
REPAPI Client

4.0.1

N/A

See the document Introduction to Consolidator for REPAPI Users.
Oracle Lite Database

4.0.1

5.0

Run the Oracle Lite DBMS migration utility, which migrates the older version.

4.4 Migrating the Mobile Server Repository

Use the Mobile Server Repository Wizard to migrate a previous version of the repository to the release 5.0 Repository.

The Repository Wizard is started during the last phase of the installation. After entering the password and clicking the Next button in Step 10 of Section 1 Installation, the Mobile Server Repository Wizard queries against the database for the previously installed components of Web-to-Go and Consolidator. Follow these steps to migrate your repository to the Mobile Server Repository:

  1. If the Repository Wizard finds any of the previous versions of the repository, the following dialog appears, displaying the schema name of the existing repository and the Web-to-go and Consolidator version numbers:

    If the Repository Wizard finds two or more repository schemas, you have the option of selecting the repository schema that you want the Repository Wizard to migrate to the Mobile Server Repository.

    Select the schema that you want to migrate to the Mobile Server Repository, then click Next.

  2. Enter the Schema Name and the Password. Click Next.

  3. A Summary showing the Schema name and the existing repositories appears. The dialog box displays the statement regarding the action that will be taken by the Repository Wizard at this point, namely, that the repositories will be migrated. Click Next.

  4. The repository is migrated. A progress panel appears indicating the installation and migration steps and their status. When the migration is completed, click Next.

  5. The Repository Wizard indicates that the installation of the Mobile Server Repository is completed. It displays the path of the Repository.log file, which you should check for any errors. Click Finish to exit the Repository migration.

4.4.1 Migration of Web-to-Go 2.0.1

If you select the migration of Web-to-Go 2.0.1, then all of the Web-to-Go repository will be migrated to the Mobile Server Repository. The snapshots logs, replication groups, and replication objects will be dropped from the Web-to-Go repository. The user application schema will not be dropped.

4.4.1.1 What Is Weight?

The snapshot weight factor is calculated according to the master detail relation of the tables, so that the referential integrity between the tables is maintained. If you want to change the weight factor, you can change the weight factor manually in the Java file AddPub.java. Compile the Java program and then run the program.

The syntax is as follows:

Consolidator.AddPublicationItem(appsid,snames,null,updateable,"S",null,weight)

You have to change only the last parameter, namely, weight. Do not change any other parameters.

In the master-detail relation, update the master table first and then the detail tables. Taking this into account, calculate the snapshot weight.

If you have two tables, ORD_Master and ORD_detail, and ORD_Master should be updated first, then the weight of ORD_Master should be 1, and the weight of ORD_detail should be 2.

4.4.1.2 Snapshot Parameter Names

In Web-to-Go 2.0.1 and in the Mobile Server 5.0, snapshot parameter names belong to an application, and they should be unique across that application. To achieve this in the Web-to-Go 2.0.1 repository, if the snapshot parameter names have multiple entries in an application (as every snapshot parameter belongs to a snapshot), then the snapshot parameter names are changed as follows: a number is added as a suffix for duplicate snapshot parameters.

4.4.2 Migration of the Consolidator

The Repository Wizard will migrate the existing repository schema. If you choose to upgrade both Web-to-Go and Consolidator, then the Repository Wizard will migrate both of them from the existing repository schema to the Mobile Server Repository.

5. Configuring the Mobile Server

This section provides information for configuring the Mobile Server. Installation alone does not enable you to run the Mobile Server. You must also configure a Web server as a framework to run the Mobile Server. The Mobile Server can run in four configurations:


The remainder of this section decribes in detail how to set up these configurations. When you finish your configuration, you must start the Mobile Server, which is described in
Section 6 "Running the Mobile Server."

5.1 Configuring the Mobile Server Module for Apache on the Apache Server

You can run the Mobile Server as a module on the Apache Server. To accomplish this, you must first install and configure the Apache Server.

Note:

The Apache HTTP Server is a third-party product that is not developed or supported by Oracle Corporation. You can find additional information about the Apache HTTP Server at the Apache Web site:
http://www.apache.org.

5.1.1 The Apache Configuration File

You add the Mobile Server Module for Apache by changing the Apache configuration file. The default location for the Apache configuration file is:

APACHE_DIR\conf\httpd.conf

where APACHE_DIR is the directory where you installed the Apache Server.

For example, if you installed the Apache Server in the location:

C:\Program Files\Apache Group\Apache

then the full path to the configuration file is:

C:\Program Files\Apache Group\Apache\conf\httpd.conf

5.1.2 Loading the Mobile Server Module for Apache

To configure the Mobile Server Module for Apache for the Apache Server:

  1. Add the Mobile Server Module for Apache to the Apache Server by adding the following line to the Apache configuration file:

    include "Oracle_Home\mobile\server\bin\wtgapach.conf"

    This points to the wtgapach.conf file. This file is the configuration file for loading the Mobile Server Module for Apache inside Apache.

  2. Start the Apache Server by typing the following command at a DOS prompt:

    apache -k start

    If the Apache Server is already running, restart it by typing the following command at a DOS prompt:

    apache -k restart

  3. Start the Mobile Server.

Note:

The preceding instructions refer to Apache Server 1.3.14 for Windows NT 4.0. If you are running a different release of the Apache Web Server, some of the steps may vary. See the Apache Web Server documentation for more information.

5.2 Configuring the Mobile Server Module for Oracle9i Application Server on the Oracle9i Application Server

You can run the Mobile Server as a module on the Oracle9i Application Server (Oracle9i AS). To accomplish this, you must first install and configure Oracle9i AS.

5.2.1 The Oracle9i AS Configuration file

You add the Mobile Server Module for Oracle9i Application Server to Oracle9i AS by changing the Oracle9i AS configuration file. The default location for the configuration file is:

Oracle9i AS_DIR\Apache\Apache\conf\httpd.conf

where Oracle9i AS_DIR is the directory where you installed Oracle9i AS.

For example, if you installed Oracle9i AS in the location:

C:\Program Files\Oracle9i AS

then the full path to the configuration file would be:

C:\Program Files\Oracle9i AS\Apache\Apache\conf\httpd.conf

5.2.2 Loading the Mobile Server Module for Oracle9i Application Server

To configure the Mobile Server Module for Oracle9i Application Server for the Oracle9i AS:

  1. Add the Mobile Server Module for Oracle9i Application Server by adding the following line to the Oracle9i AS configuration file:

    include "Oracle_Home\mobile\server\bin\wtgias.conf"

    This points to the
    wtgias.conf file. This file is the configuration file for loading the Mobile Server Module for Oracle9i Application Server inside Oracle9i AS.

  2. Start the Oracle9i AS by typing the following command at a DOS prompt:

    apache -k start

    If the Oracle9i AS is already running, restart it by typing the following command at a DOS prompt:

    apache -k restart

  3. Start the Mobile Server.

5.3 Configuring the Mobile Server Module for Oracle9i Application Server on the Oracle HTTP Server

You can run the Mobile Server as a module on the Oracle HTTP Server. To accomplish this, you must first install and configure the Oracle HTTP Server.

5.3.1 The Oracle HTTP Server Configuration file

You add the Mobile Server Module for Oracle9i Application Server to the Oracle HTTP Server by changing the Oracle HTTP Server configuration file. The default location for the configuration file is:

Oracle_HTTP_DIR\Apache\Apache\conf\httpd.conf

where Oracle_HTTP_DIR is the directory where you installed the Oracle HTTP Server.

For example, if you installed the Oracle HTTP Server in the location:

C:\Program Files\Oracle HTTP

then the full path to the configuration file would be:

C:\Program Files\Oracle HTTP\Apache\Apache\conf\httpd.conf

5.3.2 Loading the Mobile Server Module for Oracle9i Application Server

To configure the Mobile Server Module for Oracle9i Application Server for the Oracle HTTP Server:

  1. Add the Mobile Server Module for Oracle9i Application Server by adding the following line to the Oracle HTTP Server configuration file:

    include "Oracle_Home\mobile\server\bin\wtgias.conf"

    This points to the
    wtgias.conf file. This file is the configuration file for loading the Mobile Server Module for Oracle9i Application Server inside the Oracle HTTP Server.

  2. Start the Oracle HTTP Server by typing the following command at a DOS prompt:

    apache -k start

    If the Oracle HTTP Server is already running, restart it by typing the following command at a DOS prompt:

    apache -k restart

  3. Start the Mobile Server.

5.4 Configuring the Mobile Server to Run in Standalone Mode

In some cases, such as when you run the Mobile Server on a development machine, you may want to start it without using the Apache Server, the Oracle9i AS, or the Oracle HTTP Server. You can start the Mobile Server in standalone mode by running the webtogo.exe utility. After you install the Mobile Server, start it by typing the following command at the DOS prompt:

C:\> webtogo

If you want to start the Mobile Server in servlet debug mode (when experiencing problems with running servlets), type the following command at the DOS prompt:

C:\> webtogo -d


If you want to start the Mobile Server in total debug mode (when experiencing problems with the server and the
webtogo.ora file), type the following command at the DOS prompt:

C:\> webtogo -d0

6. Running the Mobile Server

In order to run the Mobile Server, the administrator must first start the Apache Server, Oracle9i AS, the Oracle HTTP Server, or the webtogo.exe executable (the standalone mode). Starting the Mobile Server depends upon system configuration. There are two configuration scenarios for the Mobile Server:

6.1 Logging into the Mobile Server

The administrator can log into the Mobile Server after starting it by supplying a user name and a password for the Mobile Server Repository. Logging in connects the Mobile Server to the Mobile Server Repository, giving the administrator access to the account information and applications that reside in the Mobile Server Repository. The administrator uses the Mobile Server Repository to deploy such client software as the Mobile Client for Web-to-Go.

6.1.1 User Name and Password Security

The Mobile Server enables administrators to manage their user Mobile Server Repository names and passwords securely by saving them in encrypted form in the webtogo.ora file. In addition, administrators can change their Mobile Server Repository passwords in the webtogo.ora file or remove them from the file.

To log into the Mobile Server:

  1. Start the Mobile Server Listener.
  2. Connect to the following URL:http://Mobile Server_name/webtogo/startup If the Mobile Server is running, then the following login screen appears.If the Mobile Server is not running, then the following login screen appears.


    If the login is successful, then the Menu Option screen appears.

  3. Enter the administratorís user name and password for the Mobile Server Repository.

  4. Click Startup. If the password is invalid, then the Invalid User Name/Password screen appears, which enables the administrator to enter the user name and password a second time followed by clicking Logon.


    If the login is successful, then the Menu Option screen appears.


  5. Select one of the following options:

6.2 Changing a Password for the Mobile Server Repository

To change a password for the Mobile Server Repository:

  1. In the Menu Options screen, select Change. The Change Password screen appears.
  2. Enter the current password in the Old Password field.
  3. Enter the new password in both of the New Password fields.
  4. Click Change Password. If the entries in both the Old Password and the New Password fields match, then the password to the Mobile Server Repository is changed and the old password is overwritten in the webtogo.ora file.

7. Installing the Demos on the Mobile Server

You can install the demos on the Mobile Server by running the batch file instdemo.bat. This batch file is located in:

Oracle_Home\Mobile\Server\samples

The command syntax is:

instdemo.bat [SYSTEM_password] [repository_owner] [repository_password]

For example:

instdemo manager mobileadmin manager

7.1 Install the Web-to-Go SDK Demos

The Web-to-Go SDK demos are installed as follows:

Oracle_Home\Mobile\SDK\wtgsdk\src\sdkdemos.bat

8. The Supported JVM Versions for Windows CE

The following table lists the JVM versions and the associated chipsets that Oracle9i Lite 5.0 supports on Windows CE (versions 2.0 and above).


JVM

Supported Chipsets

Insignia Jeode (JDK 1.1.8)

MIPS

x86

SH3

SH4

Sun (JDK 1.2)

MIPS

x86

SH3

 N/A

Go to the Top


Copyright © 2001, Oracle Corporation.
All Rights Reserved.

 

The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained 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. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.

RESTRICTED RIGHTS NOTICE

If the Programs are delivered to the US Government or anyone licensing or using the Programs on behalf of the US Government, the following notice is applicable:

Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the Programs including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

HAZARDOUS APPLICATIONS

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the Programs.