Skip Headers

Oracle9i Lite Installation and Configuration Guide for Windows NT
Release 5.0.1

Part No. A95945-01


Copyright © 2001, 2002, Oracle Corporation


Oracle is a registered trademark, and Oracle7, Oracle8, Oracle8i, Oracle9i, PL/SQL, SQL*Net, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

Oracle9i Lite Installation and Configuration Guide for Windows NT

Release 5.0.1

January 2002

Part No. A95945-01

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

1. System Requirements

This section describes the system requirements for Oracle9i Lite 5.0.1.

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 Mobile Client 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. Install Oracle9i Lite 5.0.1 in a different Oracle_Home directory than the one where the Oracle9i database is installed.
  2. 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. Note that Oracle 8.1.7 or higher is required for Oracle9i Lite.
  3. If the client software of Oracle 8.1.7 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.
  4. 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 box appears.


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

  2. The File Locations dialog box appears.


    Enter the name of your Oracle Home directory (the directory for your Oracle9i Lite installation) in the Name field under Destination, then enter the desired location of your Oracle Home directory in the Path field, or accept the defaults. Click Next.

  3. The Installation Types dialog box appears.


    Select the Mobile Server option, then click Next:

  4. The Mobile Server Repository Database Information dialog box appears. Enter the information in the Hostname, Port, and Net Service Name fields regarding the existing Oracle database (Oracle 8.1.7 or higher) which will be used as the Mobile Server Repository. The Net Service Name is your Global Database Name and is not the "SID". Contact your system administrator if you do not have any of this information.


    Click Next after entering the required information.

  5. The Do you Want to Install the Mobile Server Repository dialog box appears. Select Yes, then Click Next.

  6. The Oracle Protocol Support dialog box appears, indicating the network protocol support that is preselected for native network protocols that are required for your platform. Click Next.

  7. The Summary dialog box appears showing the global settings and space requirements for the Mobile Server on your system. Check the Space Requirements to make sure that the required space for installing the Oracle9i Lite Mobile Server is actually available on the machine that you are installing the Mobile Server on. Click Install.

  8. The Install dialog appears and provides visual indication of the installation progress.


  9. When the installation of the Mobile Server and all the support files is completed, the Mobile Server Repository Wizard dialog box 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.

  10. 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 manually, see Section 3.4 Migrating the Mobile Server Repository Manually.

  11. Enter the information in the Schema Name and the Password fields for the Mobile Server Repository. You can either use the name of an existing schema in your Oracle database or you can enter a new schema name and a new password, and Oracle9i Lite will create that schema for you. Enter the password again in the Re-enter the password field. Click Next.

  12. The Summary dialog box appears displaying the name of the schema, that no existing repositories are found, and that the Mobile Server Repository will be installed. Click Next.


  13. In this step, 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 for each step in terms of whether it is completed or in progress. When the installation of the Mobile Server Repository is completed, the Next button becomes activated. Click Next.

  14. The Mobile Server 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 Mobile Server Repository installation and to return to the Mobile Server installation process.

  15. The End of Installation dialog box for installing the Mobile Server appears displaying the message "The installation of Oracle9i Lite was successful." 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 the Next Install button after installing the Mobile Server, the File Locations dialog box 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 of your Oracle Home directory (the directory for your Oracle9i Lite installation) in the Name field under Destination, then enter the desired location of your Oracle Home directory in the Path field, or accept the defaults. The directory name must be eight characters or less.

    Note: If you have the Oracle database installed on your machine, or any other Oracle product which uses the Oracle Universal Installer, enter DEFAULT_HOME as the Oracle Home name in the Name field under Destination. Then enter the desired directory location for your Oracle9i Lite installation in the Path field.

    Click Next.

  2. The Installation Types dialog appears.


    Select
    Mobile Development Kit. Click Next.

  3. The Summary dialog box appears showing the global settings and space requirements for the Mobile Development Kit on your system. Check the Space Requirements to make sure that the required space for installing the Mobile Development Kit is actually available on the machine that you are installing the Mobile Development Kit on. Click Install.

  4. The Install dialog box appears and provides visual indication of the installation progress. No action is required.

  5. When the installation of the Mobile Development Kit is completed, the End of Installation panel automatically appears with the message "The installation of Oracle9i Lite was successful."


    Click
    Exit to exit the installation process.

2.3 Additional Installation Options

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

3. Migration and Upgrade Path for Oracle9i Lite 5.0

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

3.1 Definition of Terms

Migration: Conversion of data and replication objects from a previous version of Oracle8i Lite to Oracle9i Lite 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.

3.2 Entities to Migrate/Upgrade

The entities to migrate and/or upgrade are:

  1. Software Libraries: Oracle-produced and Oracle-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

3.3 Supported Migration/Upgrade

The following table describes the migration paths from an Oracle8i Lite version to an Oracle9i Lite version and from a particular Oracle9i Lite version to a higher version:

Table 1: Migration Paths

Migrating from
Oracle8
i Lite or Oracle9i Lite Version

To
Oracle8
i Lite Version 4.0.0.x

To
Oracle8
i Lite Version 4.0.1.x

To
Oracle9
i Lite Version 5.0.0.6

To
Oracle9
i Lite Version 5.0.1.0

4.0.0.x

N/A

No

Yes

Yes

4.0.1.x

N/A

N/A

Yes

Yes

5.0.0.6

N/A

N/A

N/A

Yes

5.0.1.0

N/A

N/A

N/A

N/A


The following table describes the components that can be migrated or upgraded from Oracle8
i Lite 4.0.1.2.0 to Oracle9i Lite 5.0:

Table 2: The Oracle8i Lite Components that Can Be Migrated or Upgraded

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.

3.4 Migrating the Mobile Server Repository Manually

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

The Repository Wizard is started during the last phase of the installation. After entering the password and clicking the Next button in Step 9 of Section 2 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 manually:

  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 appropriate information in the fields for the Schema Name and the Password, then click Next.

  3. A Summary showing the schema name and the existing repositories appears. The dialog box also displays a 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.

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

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

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

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

3.5 Migration Troubleshooting

The migration of JavaServer Pages (JSP) requires troubleshooting. The following section describes the troubleshooting procedure.

3.5.1 Migration of JavaServer Pages (JSP)

The JSP library that ships with Oracle9i Lite is different than the one included in Oracle8i Lite. One of the most visible changes is that the algorithm used to translate
the URL for a JSP page in the underlying servlet class name has changed.

For example:

Oracle8i Lite uses OracleJSP 1.0.6.
The URL
/sample1/page.jsp
maps to the servlet class:
sample1.page.class

Oracle9i Lite uses OracleJSP 1.1.2.
The URL
/sample1/page.jsp
maps to the servlet class:
_sample1._page.class

As a result, after migrating from Oracle8i Lite to Oracle9i Lite, your application may display "ClassNotFound" errors when trying to access JSP pages. There are two options to resolve this issue:

Option 1. Recompile the JSP files and copy the class files to the repository (recommended)

Step 1: Recompile the JSP files with the newer JSP library.

Step 2: Manually copy the files into the Mobile Server Repository using
wsh. See the Oracle9i Lite Administration Guide, Appendix A, for a list of the commands on how to manually manipulate the files in the Mobile Server Repository.

Option 2. Replace the JSP library with the version that shipped with Oracle8i Lite

Step 1: Replace the JSP library used by the Mobile Server. Replace the file
OracleHome\Mobile\classes\ojsp.jar with the previous version, which was installed in the following location:
OracleHome\webtogo\bin

Step 2: Change the version of
ojsp.jar that is deployed for the Mobile Client for Web-to-Go, using the Shell Utility (wsh.exe) as follows:


wsh -o mobileadmin/manager@webtogo.world
cd /setup/webtogo
copy OracleHome\webtogo\bin\ojsp.jar ojsp.jar
sync
exit

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

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

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

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

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

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

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

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

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

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

4.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 program. After you install the Mobile Server, start it by typing the following command:

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

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

> webtogo -d0

4.5 Running the Mobile Server as a Windows NT Service

The necessary executable is called wtgsrv.exe. It is located in the ORACLE_HOME\mobile\server\bin directory. Install the service by launching the service from a DOS prompt:

> wtgsvc -i

The Mobile Server Service will start automatically after rebooting the system.


You can uninstall the service by using the following command:

> wtgsvc -u

5. Running the Mobile Server

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

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

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

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

6. Installing the Demos on the Mobile Server

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

Oracle_Home\Mobile\Server\samples

The command syntax is:

instdemo [SYSTEM_password] [repository_owner] [repository_password]

For example:

instdemo manager mobileadmin manager

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

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

ARM

Sun

SH3

8. Detecting Restart of the Mobile Server Repository

By default, the Mobile Server uses the OCI8 JDBC driver to connect to the Mobile Server Repository.
This driver does not allow the Mobile Server to detect if the Oracle database containing the Mobile
Server Repository has been restarted. As a result, you must manually restart the Mobile Server if the
database is bounced.

If you want the Mobile Server to automatically reconnect to the Oracle database, in case the Oracle
database is restarted, you must configure the Mobile Server to use the thin JDBC driver.

You can do this by changing the
ADMIN_JDBC_URL parameter in the configuration file webtogo.ora.

The location of this file is:
OracleHome\mobile\server\bin\

Set the paramater to:
ADMIN_JDBC_URL=jdbc:oracle:thin:@HOST_NAME:PORT:SID

Go to Top of Document


Oracle Logo
Copyright © 2001, 2002, Oracle Corporation

All rights reserved