Oracle9i Lite Developer's Guide for Palm
Part No. A97669-01
This document discusses configuring the environment for developing handheld applications. Topics include:
See Section 2.2, "Configuring the Development Environment" for platform-specific software requirements.
Note:Be sure to add the Mobile Development Kit classes to the CLASSPATH.
You need to configure the development environment for each of your target platforms. You should install an emulator for each of these platforms. Use the emulator to test your application before you test the application on the handheld device.
This section describes the components of the Mobile Development Kit for Palm on your development system.
You must install the Mobile Development Kit on your development system using the Oracle Universal Installer. See the Oracle9i Lite Installation and Configuration Guide for Windows NT/2000/XP for more information.
Once installed, the Mobile Development Kit components reside in the <ORACLE_HOME>\Mobile\SDK\Palm directory. This directory contains the subdirectories listed in Table 2-1:
Table 2-1 Directory Structure
|Runtime\shlib||odbc.prc: Shared library version of ODBC with SQL runtime
okapi.prc: Shared OKAPI library
olLibC.prc: Standard C library
ocHttpTransport.prc: Standard HTTP transport driver (used by the Mobile Sync Client module)
ocCompressTransport: Compression transport driver. (used by the Mobile Sync Client module)
|Runtime\bin||msync_Static.prc: Static version of Mobile Sync Client, does not require any shared libraries.
msync.prc: Requires okapi.prc, okindex.prc, odbc.prc
msql.prc: Shared version of the Oracle Lite Mobile SQL application
msql_static.prc: Statically linked version of the Oracle Lite Mobile SQL application
|SDK\lib||ocapi.lib: Mobile Sync API to allow the application to instantiate replication
odbc.lib: Static ODBC and SQL engine library
okapi.lib: Static OKAPI library
okindex.lib: Static index engine library
okapi_stub.lib: Stub for shared library - requires okapi.prc and/or okindex.prc
odbc_stub.lib: Stub for shared library - requires okapi.prc, okindex.prc, and odbc.prc
okapi_noddl.lib: Static OKAPI library without Data Definition Language
okrepex*.lib, olcrypt.lib, pslim.lib, zlib.lib, olrl.lib: Internal use only
|SDK\conduit||conshttp.dll: Them mSync conduit library.
conshttp_reg.exe: Executable you need to run to register the hotsync conduit.
|SDK\examples\cw||msql: This folder contains Mobile SQL source code.
mSync: This folder contains mSync program source code.
okDemo: This folder contains okDemo source code. These are OKAPI demo files.
okTest: Another OKAPI sample.
|SDK||fake31: Header files to support PalmOS 3.1
include: Header files.
lib: Linkable library files.
Note:<ORACLE_HOME>is used throughout this guide as a variable placeholder for the Oracle installation directory name.
Static libraries (*.lib) are best used for development since they statically linked in at compile time and simplify the debugging process. Shared libraries (.prc) are dynamically linked at runtime. Stub libraries are small statically linked libraries that are proxies for shared library files.
The Palm OS Emulator is an application that emulates the hardware for most Palm Computing Hardware devices, for example, PalmPilot, Palm III, Palm V, Palm VII and various other models. The emulator runs on most standard desktop computers running Windows 98/NT/2000/XP. Developers should use the Palm OS Emulator to help develop, test, and debug their Palm OS application. Because the Palm OS Emulator is a machine level emulation of the Palm Computing platform, it eliminates the need to download applications to an actual device for testing. Instead, the developer can install their application into the emulated environment and test it on the same desktop computer containing the development tools.
The most recent released version of Palm OS Emulator for Windows is always posted on the Internet in the Palm developer zone:
Follow the links from the developer zone main page to the emulator page to retrieve the released version of the emulator.
Since the Palm OS Emulator emulates the Palm Computing Platform hardware, all components of the hardware must be present. This includes a ROM image file, which is not shipped with the emulator. To download a debug ROM image from Palm, go to the Palm developer zone web site.
The ROM image files are found in the Palm Provider Pavilion. Consult Palm OS Emulator documentation for more information on how to configure and use Palm OS Emulator.
To configure Palm OS Emulator for TCP/IP execute the following steps:
Launch Palm OS Emulator from Windows.
Select the appropriate ROM image (only required for the first session).
Right click on the Palm OS Emulator Image and select 'Settings-> Properties'.
Select check box 'Redirect NetLib calls to host TCP/IP'.
Select the 'OK' button.