Oracle9i Lite Installation and Configuration Guide for Windows NT 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.
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:
This section describes the system requirements for Oracle9i Lite 5.0.1.
This section contains the instructions to install the Mobile Server and the Mobile Development Kit.
Note:
To see the Oracle products that are installed on your system, click Installed
Products. To continue, click Next.
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.
Select the Mobile Server option,
then click Next:
Click Next after entering the required
information.
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.
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.
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.
Select Mobile Development Kit. Click Next.
Click Exit to exit the installation process.
To develop Java applications for the Oracle Lite database, you must install the Java Development Kit (JDK) version 1.3.1 (or higher).
You can migrate your data and upgrade your software from previous versions of this product.
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.
The entities to migrate and/or upgrade are:
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:
Migrating from |
To |
To |
To |
To |
---|---|---|---|---|
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 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:
|
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:
|
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:
|
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. |
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:
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.
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.
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.
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.
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.
The migration of JavaServer Pages (JSP) requires troubleshooting. The following section describes the troubleshooting procedure.
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
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."
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. |
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
To configure the Mobile Server Module for Apache for the Apache Server:
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.
apache -k start
If the Apache Server is already running, restart it by typing the following command at a DOS prompt:
apache -k restart
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. |
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.
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
To configure the Mobile Server Module for Oracle9i Application Server for the Oracle9i AS:
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.
apache -k start
If the Oracle9i AS is already running, restart it by typing the following command at a DOS prompt:
apache -k restart
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.
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
To configure the Mobile Server Module for Oracle9i Application Server for the Oracle HTTP Server:
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.
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
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
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
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:
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.
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:
If the login is successful, then the Menu Option screen appears.
If the login is successful, then the Menu Option screen appears.
To change a password for the Mobile Server Repository:
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
The Web-to-Go SDK demos are installed as follows:
Oracle_Home\Mobile\SDK\wtgsdk\src\sdkdemos.bat
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
ARM
SH3
Insignia Jeode
Sun
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
All rights reserved