Oracle9i Lite Administration and Deployment Guide
Part No. A97376-01
This document provides a conceptual framework for understanding Oracle9i Lite features and terminology. Topics include:
The Mobile Server environment is a three-tier Web model that contains a client, a Web application server, and a database server. As Figure 2-1 shows, the architecture of the Mobile Server environment contains the following three tiers:
The Mobile Client (for example, the Mobile Client for Web-to-Go)
The Mobile Server
The database server (for example, the Oracle database)
Figure 2-1 The Mobile Server Environment
The database server makes up the first tier. Here, the Mobile Server Repository data and the application data must reside in the same Oracle database.
The Mobile Server constitutes the second or middle tier. The Mobile Server runs in one of the following two configurations:
Mobile Server running in standalone mode
Mobile Server running as a component of Oracle9iAS
The Mobile Client makes up the third tier.
The Mobile Client tier consists of the Oracle Lite database, Mobile Sync, and a client machine or a handheld device running one of the following compatible operating systems:
Windows NT 4.0 SP6a, Windows 2000, or Windows 95/98
Windows CE/Pocket PC
You can install the Mobile Client for Web-to-Go only on a machine running a Windows 32 operating system.
The Mobile Client for Web-to-Go consists of the Mobile Client Web Server and the Oracle Lite database.
The Mobile Client for Web-to-Go can be accessed from a browser on Microsoft Windows. The browser should be either Netscape 4.5 or higher, or Internet Explorer 5.0 or higher. If you use Internet Explorer, it is recommended that you use Internet Explorer 5.5 and the Internet Explorer 5.5 Service Pack 2. Users and administrators should enable Web cookies in their browsers.
Note:For complete information on the hardware and software system requirements, see Oracle9i Lite Installation and Configuration Guide for Sun SPARC Solaris if you installed the Mobile Server on a Solaris machine, or see Oracle9i Lite Installation and Configuration Guide for Windows NT/2000/XP if you installed the Mobile Server on a Windows machine.
The application server tier contains the Mobile Server, which processes requests from the Mobile Client to replicate data in the database server. The Mobile Server is a module that operates with the Oracle9i Application Server (Oracle9iAS). The Mobile Server runs as a component of Oracle9iAS.
The Mobile Server also runs in the standalone mode.
The database server tier stores the application data and the application and system files. The files are stored in the Mobile Server Repository, a virtual file system that resides on Oracle. It is a persistent resource repository that contains all application files and definitions of the applications.
An application is available to the user after the administrator publishes it to the system and grants access privileges to the user.
The Mobile Clients for the various platforms use Mobile Sync to synchronize the data changes between the local Oracle Lite database and the Oracle database.
During data synchronization, the Mobile Client uploads data changes into the in queues in the Oracle database. The client then downloads the new changes from the out queues and applies these changes to the local Oracle Lite database.
The Consolidator Message Generator and Processor (MGP) is a Java background process that applies the pending transactions from the queues to the Oracle database at set intervals. It also generates new data changes for the Mobile Client to download. These changes are stored in out queues from where the Mobile Client retrieves them the next time it synchronizes. Data changes uploaded by the Mobile Client are not reflected in the Oracle database tables until the MGP has processed the in queue and applied those changes. Similarly, any changes made to the Oracle database tables after the MGP has run are not added to the out queue and are not downloaded when the Mobile Client synchronizes.
As Figure 2-2 illustrates the synchronization process, you can use the Mobile Client to upload changes into the in queue and download updates in your out queue even if the MGP is not running. However, your in queue will not be processed, and your out queue will not receive any new changes.
You can start and stop MGP from within the Mobile Server Control Center.
Figure 2-2 Synchronization Process
When the user synchronizes, the Mobile Server replicates the data changes that the user made locally to the Oracle database. The data changes that the user made to the data in the Oracle database are applied to the data in the Oracle Lite database on the the Mobile Client.
In addition, any application changes are downloaded to the Mobile Client.
In Web-to-Go, data and applications are also synchronized when the user switches from the online mode to the offline mode or from the offline mode to the online mode.
The Mobile Server provides server-side management of all users and applications. Administrators manage mobile users and applications using the Mobile Server Control Center.
The Administrator uses the Mobile Server Control Center to install the application in the production system. After publishing the application, the Administrator can use the Mobile Server Control Center to assign application access privileges to users.
Using the Mobile Server Control Center, the Administrator can create and modify access control on an application by granting or revoking access to individual users or groups. The Administrator can also use the Mobile Server Control Center to perform other administration tasks, such as:
Create users and groups.
View server status.
Start, stop, and review status of MGP, which is the asynchronous replication engine.
View site information.
In addition, the Administrator can use the Mobile Server Control Center to change an application's properties by doing the following:
Modify the number of connections that an application manages in its Web-to-Go connection pool.
Change the Oracle database login user name and password.
Determine which subset of the data is downloaded to the client.
A Web-to-Go role is a privilege level which is specified within the application only in Web-to-Go. The developer creates roles in the application's code. It is an attribute of the user and of the application.
For information on using the Packaging Wizard to define application roles, see Oracle9i Lite Developer's Guide for Web-to-Go.
After the Administrator publishes the Web-to-Go application to the Mobile Server, the Administrator can assign roles to users and groups by using the Mobile Server Control Center. The Administrator determines a user's application access by assigning roles to users and groups. For example, the server has three different applications (Applications A, B, and C) and two users (Jane and John) who both have varying roles. Jane has the role of employee and developer for two different applications. John has the role of manager and employee for two different applications.
A Mobile Client is a physical machine such as a laptop or PC that can be used by one or more users. On the Mobile Client for Web-to-Go, each user has a directory. This directory contains a database file for each of the applications that the user has access to. This directory is called a site. A Mobile Client for Web-to-Go can contain multiple sites, but only one site per user. Users can have multiple sites on different clients.
The Mobile Server administrator can track and manage sites using the Mobile Server Control Center. The Mobile Server automatically collects site properties during client synchronization. Using the Mobile Server Control Center, the administrator can view site properties, such as the following:
|username||The site user name.|
The site host name. For example:
|last mode||The site's last mode. The last mode is either online or offline.|
|created||The date the site was created.|
|last synchronized||The date the site was last synchronized.|
|client operating system, version, and architecture||
The Mobile Client for Web-to-Go operating system, version, and architecture. For example:
Windows NT 4.0 x86
|client Java version||The Mobile Client for Web-to-Go Java version.|
|Web-to-Go version||The Web-to-Go version.|