Skip Headers
Oracle® Database Lite Administration and Deployment Guide
10g (10.0.0)
Part No. B12262-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

14 Deployment: Using the Mobile Client for Web-to-Go

This document enables end users of mobile applications to install and use the Mobile Client for Web-to-Go. Topics include:

14.1 Overview

After the mobile application developer packages a web based mobile application and the administrator publishes it, you, as the end user, are ready to use the mobile application. But, before you can use the application, you must first install the Mobile Client for Web-to-Go on your Windows 32 client machine. At this stage, you must familiarize yourself with the Web-to-Go Workspace.

14.2 Installing the Mobile Client for Web-to-Go

This section enables you to install the Mobile Client for Web-to-Go. Topics include:

You can install the Mobile Client for Web-to-Go by running the Web-to-Go setup program in your web browser. Before you install the Mobile Client for Web-to-Go, you must ensure that your environment contains the requisite hardware and software components.

14.2.1 Hardware Requirements

The Mobile Client for Web-to-Go requires the following hardware.

  1. Pentium III

  2. 12 MB Application RAM (Web-to-Go: 1.5 MB, Java: 10 MB)

  3. 10 MB Hard Disk Space

  4. 800 x 600 Display

14.2.2 Software Requirements

The Mobile Client for Web-to-Go requires the following software.

  1. Microsoft Windows 95, 98, NT 4.0 (service pack 3 recommended), or 2000.

  2. Netscape 4.0.6 or Microsoft Internet Explorer 4.0 with JavaScript enabled.

14.2.3 Installation

To install the Mobile Client for Web-to-Go, perform the following steps.

  1. To connect to the Mobile Server, open a browser and enter the following URL.

    http://<mobile_server>:<port_number>/webtogo/setup


    Note:

    You must replace the <mobile_server_name> variable with the host name of your Mobile Server. If the Mobile Server is not accessible after specifying its name, you may need to enter the port number.

    The default port number for the Mobile Server is 443. If your Mobile Server is running on port number 443, you do not have to specify the Mobile Server port number in the URL. If your Mobile Server is running on a port number other than 443, you must specify the Mobile Server port number in the URL as follows. https://<mobile_server_name>:<port_number>/setup


    The Setup page lists Mobile Client programs that are available for downloading.

    Figure 14-1 displays the Mobile Client Setup page.

    Figure 14-1 Mobile Client Setup Page

    This image displays the Mobile Client Setup page.
  2. Click the required Mobile Client link from the list displayed.

  3. If your browser is Netscape, choose a location to download the setup program, and click OK. In Windows Explorer, double-click setup.exe to run the setup program.

    OR

    If your browser is Internet Explorer, run the setup program from your browser window. Once started, the setup program prompts you to provide an install directory. Choose a directory, for example, D:\Mobile Client, and click OK.

    The setup program downloads all the required components and starts the Mobile Client for Web-to-Go on your machine. Upon completion of the installation, the Web-to-Go screen appears.

14.3 Client-Side Configuration for Secure Socket Layer (SSL)

As the end user, you can configure the Mobile Client for Web-to-Go to establish an SSL connection between the Mobile Client and the Mobile Server. Oracle Database Lite 10g does not, however, support SSL connection between the browser and the Mobile Client for Web-to-Go. Topics include:

14.3.1 Communication between the Mobile Client and the Mobile Server

Based on whether or not you download the Mobile Client for Web-to-Go from the Mobile Server running in SSL, you can choose to configure communication between the Mobile Client for Web-to-Go and the Mobile Server. The following sections provide a description of configuring communication between the Mobile Client and the Mobile Server.

Mobile Client Download from a Mobile Server which is Running in SSL Mode

The Mobile Client for Web-to-Go which is downloaded from the following URL is automatically configured for SSL and does not require manual configuration on the part of the end user. This download enables the Mobile Client to communicate with the Mobile Server in SSL mode.

https://<mobile_server>:<port>/setup

Mobile Client Download from a Mobile Server which is not Running in SSL Mode

If you have downloaded the Mobile Client for Web-to-Go from a Mobile Server, which, is not running in SSL mode, you must modify the SERVER_URL parameter in the configuration file webtogo.ora as follows.

SERVER_URL=https://<mobile_server>:<port>/webtogo/setup


Note:

in the location bar, you must type https, to specify and indicate the SSL Mode, and not http.

14.3.2 Connection between the Browser and the Mobile Client for Web-to-Go

While trying to connect to the Mobile Client for Web-to-Go in SSL mode, you will not be able to connect to the Mobile Client, even if the following conditions exist.

  1. The Mobile Server is running in SSL mode, as a module of Oracle9iAS.

  2. The Mobile Client for Web-to-Go is also running in SSL mode.

To connect to the Mobile Client for Web-to-Go using a browser, you must specify HTTP and not HTTPS in the client URL, although the communication between the client and the server is through the HTTPS protocol.

For example, http://<client_machine>/webtogo

14.4 Support for Non-SSL Mobile Clients

Mobile Servers running in SSL mode possess the ability to synchronize with any Mobile Client which is running in SSL or non-SSL mode. But, in the case of the Mobile Client for Web-to-Go, the client also runs in SSL mode to synchronize with the Mobile Server, which is running in SSL mode.

As SSL is not supported on many Mobile Clients, the Mobile Server, which, is running in SSL mode, still supports Mobile Clients that are running in non-SSL mode.


Note:

Inside Oracle9iAS, the Mobile Server runs on both SSL and non-SSL ports, to support SSL and non-SSL clients. The Oracle9iAS must be configured to run on both SSL and non-SSL ports, as a default function.