Skip Headers
Oracle® Database Lite Getting Started Guide
Release 10.3
Part Number E12080-02
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

4 Installation of Oracle Database Lite

This chapter describes all of the details for you to install Oracle Database Lite, including the following:

4.1 Oracle Database Lite Installation Considerations

Note the following issues before you start your installation:

4.1.1 Installing Multiple Languages on a Single Solaris Machine

With Oracle Database Lite installed in a Solaris environment, you cannot install multiple languages on a single Solaris machine. Instead, you must perform a separate installation for each language.

4.1.2 National Language Support for Chinese, Japanese, and Korean (CJK)

The Mobile Server and Mobile Development kit have full National Language Support for Simplified Chinese, Japanese, and Korean (CJK). Only the client database component in the MDK supports the Traditional Chinese language.

4.1.3 Mobile Server on a DHCP Server is Not Supported

Mobile Server can only be installed on a server with a static IP address; thus, the Mobile Server does not function correctly if installed on a DHCP server.

4.2 Starting Oracle Universal Installer

Oracle Database Lite uses Oracle Universal Installer to guide you through each step of the installation process. The Oracle Universal Installer provides the following features:

The Oracle Universal Installer automatically checks your computer prior to installation to verify that your system meets operational requirements. Table 4-1 lists the prerequisite checks that are performed.

Table 4-1 Oracle Universal Installer Automatic Prerequisite Checks

Prerequisite Checks See Also

Check for enough disk space for Oracle Home installation

Section 3.7, "Recommended System Configuration For UNIX"

On UNIX systems, checks for TMP and TMPDIR variable and sufficient swap space

Section 3.7, "Recommended System Configuration For UNIX"

You start the Oracle Universal Installer using different methods for each type of operating system, as detailed in the following steps:

4.2.1 Starting the Oracle Universal Installer on Windows

Insert the CD-ROM labeled Oracle Database Lite and double-click setup.exe. The Welcome screen appears.

4.2.2 Starting Oracle Universal Installer on UNIX

Follow these steps to start Oracle Universal Installer and install Oracle Database Lite:

  1. Insert the CD into the CD-ROM drive.

  2. Mount the installation CD-ROM. For information on mounting the installation CD-ROM for your platform, see Section 3.10, "Mounting the Installation CD-ROM For UNIX Systems".

  3. Run Oracle Universal Installer from the CD-ROM:

    Note:

    Ensure you are not logged in as the root user when you start the Oracle Universal Installer.

    1. Log in as the oracle user.

    2. Start the installer by entering the following command:

      prompt> mount_point/disk1/runInstaller

    This launches Oracle Universal Installer, which installs Database Lite.

4.2.2.1 Using the oraInventory Directory

The Oracle Universal Installer creates the oraInventory directory the first time it is run on a computer. The oraInventory directory keeps an inventory of products that the Oracle Universal Installer installs on your computer, as well as other installation information. If you have previously installed Oracle products, then you may already have an oraInventory directory.

When a UNIX group name is created and specified, the Oracle Universal Installer grants the specified group the permission to write to the oraInventory directory. If another group attempts to run the installer, then they must have permission to write to the oraInventory directory. If they do not have permission, then the installation will fail.

The location of oraInventory is defined in the oraInst.loc file. See Table 4-1 for the location of the orainst.loc file for your system.

The latest installation log file is stored in:

/your_base_directory/oraInventory/logs/installActiontodays_date_time.log

The your_base_directory identifier is the location for your installation files and todays_date_time is the date and time of installation. Log file names of previous installation sessions take the form installActionstodays_date_time.log.

Do not delete or manually alter the oraInventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your system.

4.2.2.2 Location of Files on UNIX

The following table lists the location of the oratab and oraInst.loc file for each platform:

Table 4-2 File Locations for Each Platform

Platform oratab and emtab oraInst.loc

AIX

/etc

/etc

HP

/etc

/var/opt/oracle

Linux

/etc

/etc

4.3 Installing Oracle Database Lite

Oracle Database Lite consists of two main components: Mobile Server and Mobile Development Kit. Each is installed separately from the Oracle Database Lite CD-ROM. The following sections describe all of your installation options:

Note:

For instructions on how to install Branch Office, see Chapter 9, "Manage Your Branch Office," in the Oracle Database Lite Administration and Deployment Guide. For instructions on how to create a Mobile Client and download an application, see Chapter 6, "Quick Start for Oracle Database Lite".

4.3.1 GUI Install of the Mobile Server and MDK Components

Once the Oracle Universal Installer is initiated, perform the following steps to install Oracle Database Lite:

Note:

If you install multiple standalone Mobile Servers on a single machine or if you install Web-to-Go client for OC4J with the standalone Mobile Server on a single machine, change the RMI and JMS ports in the rmi.xml and the jms.xml files located in the <ORACLE_HOME>\mobile_oc4j\j2ee\mobileserver\config directory. The port numbers must not be used by another other process.

  1. On the Welcome screen, click Next.

  2. On the File Locations screen, enter the following:

    • In the Source field, either accept or enter a new location of the Oracle Database Lite products.xml file.

    • In the Destination field, enter the name and path of Oracle Home. The Oracle Home name and path CANNOT include spaces. Important: Read the following bulleted list for the appropriate Oracle Home.

      This is the Oracle Home where you want to install Oracle Database Lite. You may choose to install Oracle Database Lite into a new (standalone mode) or existing (OracleAS mode) Oracle Home. Take the following into consideration:

      • If you use Mobile Server in standalone mode for your middle-tier, do not use an Oracle Home that has any version of OracleAS installed.

      • If you use OracleAS as your middle-tier, then you must install Oracle Database Lite into the same Oracle Home where the application server is installed.

    Click Next .

  3. On the Installation Types screen, choose the type of installation to execute. Your options are as follows:

    • Mobile Server

    • Mobile Development Kit

    • Custom

    The first two are the main components of Oracle Database Lite. The custom option is for advanced users only. Each of these Install options are discussed in the following sections:

4.3.1.1 Installation of Mobile Development Kit

Install Mobile Development Kit from the Installation Types screen by choosing the Mobile Development Kit and clicking Next. On the Summary screen, click Install. Click Exit to return to the installation screen.

You have now installed the Mobile Development Kit.

4.3.1.2 Installation of Mobile Server

Install the Mobile Server from the Installation Types screen, as follows:

Note:

When you install the Mobile Server on the OracleAS as the middle-tier, some default values are chosen for you. If you install the Mobile Server without OracleAS, this is referred to as standalone Mobile Server and you will be prompted for additional information. Any screen that mentions standalone Mobile Server only appears when installing in an environment that does not include OracleAS.

  1. Choose Mobile Server and click Next.

  2. Select Yes or No if you want to use SSL for a standalone Mobile Server. Click Next.

  3. Enter the TCP/IP listener port for OC4J for a standalone Mobile Server. The default values are as follows:

    • Windows platform: Port 80 for an HTTP connection; port 443 for an HTTPS connection.

    • UNIX platform: Port 8888 for an HTTP connection; port 4443 for an HTTPS connection.

    If you are using OracleAS, the ports defined in OracleAS are used. Click Next.

    Note:

    If, after installation, you have port conflicts and need to change the port number for OC4J standalone, edit the appropriate XML file to modify the alternate port number.

    • For HTTP, edit the default-web-site.xml file.

    • For HTTPS, edit the secure-web-site.xml file.

    These are located in the ORACLE_HOME\mobile_oc4j\j2ee\mobileserver\config\ directory.

    Modify the port number as follows:

    <web-site port="80" display-name="OracleAS Containers for J2EE HTTP Web Site">

  4. Click Yes to install the Mobile Server Repository. For this option, always click Yes to install the repository—even if one has already been created. If you are installing a Mobile Server on another host that shares an existing repository, selecting yes updates the repository with the shared Mobile Server information. You only select No if instructed to for a certain environment. Click Next.

  5. Click Yes or No indicating if you want the demo applications installed on the server. Click Next.

  6. On the Summary page, click Install to start the installation of Mobile Server, which is installed in your Oracle Home.

    Note:

    If you previously clicked Yes to installing the Mobile Server Repository, then the Repository Wizard is now launched to create and populate the repository with the Mobile Server schema.

  7. Provide the URL for the back-end Oracle database for the Mobile Server Repository, as follows:

    • If you are connecting to a single Oracle database, provide the hostname, port and SID or service name.

    • If you are connecting to an Oracle RAC database, select the Enter Custom JDBC URL checkbox and enter the JDBC URL for this database. This is shown in Figure 4-1.

      An Oracle RAC database URL takes the following format:

      jdbc:oracle:thin:@(DESCRIPTION=
 (ADDRESS_LIST=
   (ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))
   (ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521))
 )
 (CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME)))

    Figure 4-1 Enter JDBC URL for Back-End Database in Repository Wizard

    JDBC URL for database
    Description of "Figure 4-1 Enter JDBC URL for Back-End Database in Repository Wizard"

    The Mobile Server installs its meta-data in the back-end database. If you are not sure of the values to enter for the URL, then you can query the data dictionary to obtain these values. Connect as SYSTEM and run the following queries.

    To retrieve the SID, execute:

    select instance_name from v$instance;

    If you need to retrieve the port number, check the listener.ora file on the back-end database.

    Click Next.

  8. The Repository Wizard asks for a user name and password, which will be used to connect to the back-end database, create the schema and assign database privileges for the Mobile Server. When the Mobile Server accesses the Mobile repository, it uses the repository username/password. This defaults to the user MOBILEADMIN and the password is set during install.

    Before you provide the username, this user has to have the following privileges to create the Mobile Server repository in the back-end database:

    • CREATE TABLESPACE, CREATE USER

    • The following privileges are required with the Admin option:

      ALTER ANY TABLE, ALTER SESSION, ALTER SYSTEM, ANALYZE ANY, CREATE SESSION, CREATE ANY SEQUENCE, CREATE ANY VIEW, CREATE ANY TRIGGER, CREATE ANY INDEX, CREATE ANY TABLE, CREATE ANY SYNONYM, CREATE ANY PROCEDURE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SYNONYM, CREATE TABLE, CREATE VIEW, CREATE INDEXTYPE, DELETE ANY TABLE, DROP ANY SEQUENCE, DROP ANY PROCEDURE, DROP ANY VIEW, DROP ANY SYNONYM, DROP ANY TRIGGER, DROP ANY INDEX, DROP ANY TABLE, INSERT ANY TABLE, SELECT ANY TABLE, SELECT ANY DICTIONARY, SELECT_CATALOG_ROLE, UPDATE ANY TABLE

    Note:

    You can set the Mobile Server privileges independently through an API. See Section 2.17, "Set DBA or Operational Privileges for the Mobile Server" in the Oracle Database Lite Developer's Guide.

    Click Next.

  9. If this is a new Repository, the following message is displayed:

    No existing Repository found. A new Repository will be installed.

    Click Next.

  10. Enter the username and password for the Mobile Server Repository. The default name is MOBILEADMIN. This schema contains all database objects used by the Mobile Server. Also, check whether you want to install sample applications or not. Click Next.

    Note:

    If you choose to install the samples, then the following Mobile Server user accounts will be created: S11U1, JOHN, JANE, JACK, and JUNE. These user accounts have default passwords; thus, after the installation completes, you should immediately modify the passwords through Mobile Manager.

    You should install the samples only on a development system; you should NEVER install the samples on a production Mobile Server. Doing so creates a security risk on your production environment. The default user accounts that are created as part of the samples may cause a security risk, as they could provide unauthorized access to your production system.

  11. Enter the Mobile Server administrator username and password that you will use to log into the Mobile Manager.

  12. Enter the client schema username and password for the schema where the demo applications are installed. When the user accesses the user data in the Mobile Server repository, the Mobile Server authenticates the schema username and password before access is provided to the user data.

  13. A summary screen appears informing you if a repository is installed or not. Click Next.

  14. The installation screen appears. Wait until the install is completed. Click Next.

  15. Once the repository wizard is finished, click Finish to leave the wizard.

  16. Click Exit to complete the installation.

  17. Review the installation log files for any errors, which are located in ORACLE_HOME\mobile\server. The repository.log file contains the log file of all general installation errors; the samples.log file contains a log of the sample installation errors.

  18. When you configure multiple Mobile Servers against a single repository, this is known as a farm. You must enable the Device Manager, Mobile Manager and Mobile client to work properly in a farm environment. For information on configuring all Mobile Servers to act properly in a farm, see Section 1.2.1.2, "Manage Mobile Server Farms" in the Oracle Database Lite Administration and Deployment Guide.

  19. If you are installing on top of any version of the application server, then restart the application server.

4.3.2 Silent Install of Mobile Server and MDK Components

You can execute a command-line tool that runs the installer in silent mode. That is, it installs either the Mobile Development Kit or the Mobile Server for you without having to use the Installation GUI. The following sections describe how to silently install these components on either the Windows or UNIX platforms:

4.3.2.1 Silent Install for Mobile Server or Mobile Development Kit on Windows

The setup.exe command can be executed to run the installer in silent mode for Windows, as follows:

setup.exe  -responseFile 
/full_directory_path/stage/Response/oracle.lite.install_type_2.rsp 
-silent -nowelcome

There are two response files that contain variables that define how the Mobile Server or the MDK are installed. The following sections describe the response files:

4.3.2.1.1 Response File for Mobile Server Install

Variables to be filled for silent install in the response file oracle.lite.install_type_2.rsp to install Oracle Database Lite are as follows:

  • Define the ORACLE_HOME destination directory, as follows:

    ORACLE_HOME="\private\olite\orahome

  • Define the name for your Oracle Home, as follows:

    ORACLE_HOME_NAME="OLITE"

  • Provide the hostname, port, and user for the back-end database, where the repository is to be installed, as follows:

    s_repo_jdbc_url=("jdbc:oracle:thin:@<host>:<port>:<sid>")

  • Specify true or false if the repository is to be created on the back-end database, as follows:

    b_repository=false

  • Provide the Mobile Server port number, where incoming clients connect to it, as follows:

    s_mobile_port="80"

  • Provide the database system username and password, as follows:

    s_olite_sysdb_username="myuser"
s_olite_sysdb_pwd="mypwd"

  • Provide the Mobile Server schema name and password, as follows:

    s_olite_mb_user="myschema"
s_olite_mb_pwd="myschemapwd"

  • Provide the demo schema user name and password, as follows:

    s_olite_demoschema_username="demoschema"
s_olite_demoschema_pwd="demoschemapwd"

  • Provide the Mobile Server administrator user name and password, as follows:

    s_olite_admin_username="adminuser"
s_olite_admin_pwd="adminpwd"

  • If the Mobile Server is standalone—that is, not installed on top of OracleAS— then set the following variables:

    b_ssl=false
b_repository=true
b_olite_samples=true
s_rmi_ssl_port="23943"
s_rmi_port="23791"
s_jms_port="9127"
s_mobile_port="80"
s_mobile_port_nssl="80"
s_mobile_port_ssl="443"

    For an SSL-enabled Mobile Server:

    b_ssl=true
b_repository=true
b_olite_samples=true
s_rmi_ssl_port="23943"
s_rmi_port="23791"
s_jms_port="9127"
s_mobile_port="443"
s_mobile_port_nssl="80"
s_mobile_port_ssl="443"
4.3.2.1.2 Response File for MDK Install

Variables in the oracle.lite.install_type_1.rsp response file to install MDK, are as follows:

ORACLE_HOME="c:\olite"
ORACLE_HOME_NAME="OLITE"

4.3.2.2 Silent Install Mobile Server or the Mobile Development Kit on UNIX

You can install the Mobile Server and/or the Mobile Development Kit by using the runInstaller command, which is on the top level of the CD or the downloaded ZIP file for the product.

There are two response files that contain variables that define how the Mobile Server or the MDK are installed, which are located in the stage/Response folder of the CD or ZIP file.

Note:

  • If you use Mobile Server in standalone mode for your middle-tier, do not use an Oracle Home that has any version of OracleAS installed.

  • If you use OracleAS as your middle-tier, then you must install Oracle Database Lite into the same Oracle Home where the application server is installed.

4.3.2.2.1 Response File for Mobile Server Install

The response file for installing the Mobile Server is oracle.lite.install_type_2.rsp. The variables that you can modify in this file for defining your install are as follows:

  • Define the ORACLE_HOME destination directory, as follows:

    ORACLE_HOME="\private\olite\orahome\10g"

  • Define the name for your Oracle Home, as follows:

    ORACLE_HOME_NAME="OLITE10g"

  • Provide the hostname, port, and user for the back-end database, where the repository is to be installed, as follows:

    s_repo_jdbc_url=("jdbc:oracle:thin:@<host>:<port>:<sid>")

  • Specify true or false if the repository is to be created on the back-end database, as follows:

    b_repository=false

  • Provide the Mobile Server port number, where incoming clients connect to it, as follows:

    s_mobile_port="80"

  • Provide the database SYSTEM username and password, as follows:

    s_olite_sysdb_username="myuser"
s_olite_sysdb_pwd="mypwd"

  • Provide the Mobile Server schema name and password, as follows:

    s_olite_mb_user="myschema"
s_olite_mb_pwd="myschemapwd"

  • Provide the Mobile Server demo schema user name and password, as follows:

    s_olite_demoschema_username="demoschema"
s_olite_demoschema_pwd="demoschemapwd"

  • Provide the Mobile Server admin user name and password, as follows:

    s_olite_admin_username="adminuser"
s_olite_admin_pwd="adminpwd"

  • If the Mobile Server is standalone—that is, not installed on top of OracleAS— then set the following variables:

    b_ssl=false
b_repository=true
b_olite_samples=true
s_rmi_ssl_port="23943"
s_rmi_port="23791"
s_jms_port="9127"
s_mobile_port="80"
s_mobile_port_nssl="80"
s_mobile_port_ssl="443"

    For an SSL-enabled Mobile Server:

    b_ssl=true
b_repository=true
b_olite_samples=true
s_rmi_ssl_port="23943"
s_rmi_port="23791"
s_jms_port="9127"
s_mobile_port="443"
s_mobile_port_nssl="80"
s_mobile_port_ssl="443"
4.3.2.2.2 Response File for MDK Install

The response file for installing the MDK is oracle.lite.install_type_1.rsp. You can define two variables in this file for your install—the Oracle Home and the name for the Oracle Home—as follows:

ORACLE_HOME="c:\olite10g"
ORACLE_HOME_NAME="OLITE10g"
4.3.2.2.3 Execute Silent Install of Mobile Server and MDK on UNIX

After modifying the response files, if you want to install both the Mobile Server and the MDK, then execute the runInstaller command twice. Each execution is provided a different response file. The following installs the Mobile Server, as follows:

./runInstaller  -responseFile 
    /full_directory_path_to_response_file/oracle.lite.install_type_2.rsp 
    -silent -nowelcome

where the options for this command are as follows:

Table 4-3 The runInstaller Command Options

Command Option Description

responseFile

Provide the path and name of the response file for the component that you are installing. There are two response files: one for installing the Mobile Server and one for installing the MDK.

silent

Always use this option, as it defines that this is a silent installation.

nowelcome

Stops the GUI from displaying.

4.3.3 Providing High Availability with a Farm of Multiple Mobile Servers

In some cases, you may want to have multiple Mobile Servers using the same Mobile Server repository on an Oracle database or an Oracle RAC database. For example, as Figure 4-2 shows, if you wanted to load balance your Mobile clients across multiple Mobile Servers, you could add a load balancer—such as Oracle WebCache—before the shared Mobile Servers, and then your clients would be balanced across these Mobile Servers, of which each accesses the same data in the shared repository.

This is the type of configuration that entails an Oracle Database Lite Farm.

Figure 4-2 Multiple Mobile Servers Sharing a Repository

Multiple Mobile Servers sharing a repository
Description of "Figure 4-2 Multiple Mobile Servers Sharing a Repository"

You can install multiple Mobile Servers, each on its own host, that use the same Mobile Server Repository, as follows:

  1. Install the load balancer. Oracle Database Lite only certifies the Oracle Application Server Web Cache as a load balancer. You can use any load balancer as long as the JSESSIONID is used.

  2. Install the first Mobile Server and the Mobile Server Repository following the instructions in Section 4.3.1.2, "Installation of Mobile Server".

    Note:

    Each Mobile Server in the Farm must use the Oracle Application Server.

  3. Install additional Mobile Servers. For each subsequent Mobile Server, follow the instructions in Section 4.3.1.2, "Installation of Mobile Server", supplying the same JDBC URL for the back-end Oracle database where the Mobile Server Repository exists. This URL can be either a regular JDBC URL or an Oracle RAC URL. Select Yes for creating the repository, which registers the shared Mobile Server with the repository.

  4. Configure Mobile Servers with the load balancer URL. Because the Mobile client accesses any of these Mobile Servers through a load balancer, you need to configure each Mobile Server with the load balancer URL. This ensures that when the setup.exe is downloaded by the client, that the client is automatically configured with the load balancer URL, instead of the Mobile Server URL.

    This process is similar to how the Mobile Server is configured to use with a reverse proxy. Configure both the reverse_proxy and DM_AUTO_SYNC_CACHE parameters in the webtogo.ora configuration file, as follows:

    [WEBTOGO]
REVERSE_PROXY=http://<load_balancer_hostname>:<port_number>/webtogo
DM_AUTO_SYNC_CACHE=YES

  5. Configure the load balancer to honor the JSESSIONID cookie. When a user logs into a Mobile Server, an HTTP session is created for that user. An HTTP cookie with the name JSESSIONID is sent back to the Mobile client. Subsequent HTTP requests from the Mobile client will contain the HTTP cookie, which allows the Mobile Server to identify the session for that user.

    In a configuration with multiple Mobile Servers and a load balancer, you must ensure that the load balancer is configured to route HTTP requests within the same HTTP session to the same Mobile Server. To do this, configure the load balancer to honor the JSESSIONID cookie.

    If the load balancer uses a different algorithm to distribute HTTP requests, such as round-robin or server-load based, then the Mobile Server will not work correctly.

  6. Perform additional configuration for device management and data synchronization for all Mobile Servers in the farm as described in Section 1.2.1.2, "Manage Mobile Server Farms" in the Oracle Database Lite Administration and Deployment Guide.

4.3.4 Install Oracle Database Lite on Linux

Oracle Database Lite 10g includes a Mobile Development Kit for Linux.

The following sections provide considerations when installing Oracle Database Lite on a Linux platform:

4.3.4.1 Patch Required if Using Linux Redhat 3.0

If you install Oracle Database Lite 10g on Linux Redhat 3.0 and the following error occurs, apply the 3006854 patch and start the installation again.

Error occurred during initialization of VM Unable to load native library: /tmp/myhost/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference.

4.3.4.2 Providing Enough Swap Space on the Linux Platform

If the swap space is not sufficient on your Linux machine, then modify the value for the SWAP_SPACE variable in the install/linux/oraparam.ini file. The default value is set to SWAP_SPACE=1536. For example, if your machine is not as powerful, decrease the swap space; for example, SWAP_SPACE=1024.

4.3.5 Install Oracle Database Lite on Symbian Devices

The following sections describe the installation directions for Symbian devices:

4.3.5.1 Prerequisites for Installation

Before installing Oracle Database Lite, perform the following:

  • You must install the SDK for the target device on the development machine. For example, if you are using a Motorola device, go to www.motorola.com and download the M1000 SDK on the development machine.

  • It is recommended, but not mandatory, that for development, you install the target device development suite of either the "PC Suite" or "Desktop Suite".

  • In order to use command-line prompts on your device, you need to install eshell.exe on the device. In addition, we recommend that you purchase a hardware keyboard to connect to your phone to type in the eshell.exe window.

We assume that you have a basic Symbian OS development knowledge to develop your application.

4.3.5.2 Oracle Database Lite 10g Components

The following are the components that you will see when you install the Oracle Database Lite 10g for Symbian devices:

  • OLAES.DLL : AES Encryption Module

  • OLOBJ40.DLL : Core Database Module

  • OLSQL40.DLL : SQL Parser Module

  • OLOD2040.DLL : ODBC 2.0 Driver

  • ZLIB.DLL : zlib Compression Module

  • OCAPI.DLL : Synchronization Module

  • POLITE.INI : System-wide Common Configuration File

  • ODBC.INI : Data-source Name Management File

  • OLITE40.MSB : Message File (English)

  • CREATEDB.EXE : Utility to create a new database

  • REMOVEDB.EXE : Utility to remove an existing database

  • ENCRYPDB.EXE : Utility to encrypt a database

  • DECRYPDB.EXE : Utility to decrypt an encrypted database

  • ODBINFO.EXE : Utility to display/modify database setting

4.3.5.3 Installing Oracle Database Lite on Symbian Devices

To install Oracle Database Lite on Symbian devices, perform the following:

  1. On the development machine, unzip olite_epoc.zip in the EPOCROOT directory. For example, the EPOCROOT directory could be C:\Symbian\8.0a\S60_2nd_FP2_J.

    When you complete the installation, the following files are unzipped:

    • Header files are placed in the epoc32\include\olite directory.

    • ARMI (urel) .lib files are placed in the epoc32\release\armi\urel directory.

    • THUMB (urel) .lib files are place in the epoc32\release\thumb\urel directory.

    • WINS (udeb) binaries and .lib files are copied into the epoc32\release\wins\udeb directory.

    • Initial configuration files are copied into the epoc32\wins\c\System\Data directory.

    • Samples are copied into the OliteEx directory.

  2. On the target device, perform the following:

    1. For most devices, copy the olite_core.sis file to the device using PC Suite, Desktop Suite, or an external memory card. If you are using the Sony Ericsson P910 device, then you must copy the olite_core_uiq2x.sis file to the device.

    2. Install the olite_core.sis file (or the olite_core_uiq2x.sis file, if using the Sony Ericsson P910 device), which causes the following:

      The following files are copied into the target drive, which by default is the !:\System\Libs\ directory: OLAES.DLL, OLOBJ40.DLL, OLSQL40.DLL, OLOD2040.DLL, ZLIB.DLL, and OCAPI.DLL.

      Note:

      You may chose a different target directory during installation.

      If the configuration files do not already exist on the device, then the following files are copied into the C:\System\Data\ directory: polite.ini, odbc.ini, and olite40.msb.

  3. To optionally install the Oracle Database Lite 10g Utility Tools, perform the following:

    Note:

    These utility tools are command line based programs; thus, you need to install and use the eshell.exe program to execute them.

    1. For most devices, copy the olite_tools.sis file to the target device using PC Suite, Desktop Suite, or a memory card. If you are using a Sony Ericsson P910, then copy the olite_tools_uiq2x.sis file.

    2. Install either the olite_tools.sis file or if using the Sony Ericsson P910 device, the olite_tools_uiq2x.sis file. This copies the following files into the target directory (which by default is the !:\System\Programs\ directory): CREATEDB.EXE, REMOVEDB.EXE, ENCRYPDB.EXE, DECRYPDB.EXE, and ODBINFO.EXE.

      Note:

      You may chose a different target directory during installation.

4.3.6 Mobile Client Install

The Mobile client can use either the SQLite database or the Oracle Lite database.

4.3.7 Custom Install

The custom install option enables a user to install separate components within the Mobile Development Kit and Mobile Server. This is only for the user who is familiar with these components and not for the beginner.

4.4 Post-Installation Configuration Requirements

The following describes any post-installation requirements:

4.4.1 Username and Password for WebLogic Server Domain

When installing the Mobile Server on the WebLogic Server 10g, a new domain is created in the WebLogic Server called mobileserver. You can log into the WebLogic Server console for administration tasks, such as changing the port number or checking traces.

The new WebLogic Server domain is the mobileserver domain. The default administrator username is weblogic. The password is set to the Mobile Repository schema password appended with weblogic123. You should modify this password after your first login.

4.4.2 Setup DISPLAY Variable for UNIX Systems in Oracle Application Server

If you are using a UNIX system, you may have to configure the DISPLAY variable. Mobile Manager uses UIX to create the graphics in its display, which requires access to your XServer. If you have the XServer on the local machine where the Mobile Manager is executing, then you do not have to perform any configuration. However, if the XServer is on another machine, then set the DISPLAY variable in the OPMN component of the Oracle Application Server to point to that machine. In the opmn.xml file, modify the <environment> section and add the following property:

<prop name="DISPLAY" value="hostname:display_number.screen_number"

where the host is the machine where the XServer is available. For example, if the XServer is on myhost, then set the DISPLAY environment variable, as follows:

<environment>
 <prop name="DISPLAY" value="myhost:0.0"
</environment>

4.4.3 Enabling Branch Office on Windows XP Service Pack 2

When you install Windows XP Service Pack 2, the Internet Connection Firewall (ICF) defaults to ON. In order for the Branch Office Server to work properly, you either need to turn the ICF OFF or enable port 1160 within the ICF. To enable port 1160, go to the Windows Firewall control on your Windows machine. Select the Exception tab. Click Add Port. Add port 1160 with any name.

4.5 Starting Mobile Server

You can start the Mobile Server through the Windows All Programs item or automatically when you start the middle-tier. Both options are described below:

4.6 Testing Your Mobile Server Installation

To test whether your Mobile Server was installed correctly, test it in one of the following ways:

For more information on testing your installation using the samples, see Chapter 6, "Quick Start for Oracle Database Lite".

4.7 Removing Demo Applications

Before you use Oracle Database Lite in a production environment, you may wish to remove the demo applications. To remove the demo applications, execute the following batch file:

demoinstaller [-install | -uninstall] <sys_user> <sys_pwd> <mobile_user> <mobile_pwd>

where the options are as follows:

Option Description
-install or -uninstall -install: install the demos

-uninstall: remove the demos
<sys_user> <sys_pwd> Provide the system username and password that are used to drop the schema in which the demos are installed.
<mobile_user> <mobile_pwd> Provide the Mobile Server log on username and password, which is necessary to remove the demos from the repository.

The removal process enables you to delete the schema into which the applications were installed. If you did not use the schema for any other purpose, then allow the batch file to remove the demo application schema.

4.8 How to Uninstall Oracle Database Lite

After you remove the Oracle Database Lite components through the Oracle Universal Installer, also perform the following tasks:

  1. Delete the following directories:

    • ORACLE_HOME\Mobile

    • If you are using Oracle Database Lite Standalone, then delete the ORACLE_HOME\Mobile_oc4j directory; if you are using OracleAS, then delete the ORACLE_HOME\j2ee\home\applications\mobileserver directory.

  2. Drop TABLESPACE SYNCSERVER INCLUDING CONTENTS

  3. Delete the Mobile01.dbf database file from the operating system.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us