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


10 Managing Devices

This document describes how to manage devices. Topics include:

10.1 Overview and Architecture

As enterprises deploy more and more applications on small devices, managing these devices presents a crucial constraint on enterprise IT solutions. The Oracle Database Lite 10g, Device Management (DM) system provides a solution to administer the deployed devices and remotely manage applications and data in these devices.

The Oracle Database Lite 10g Device Management System consists of a number of Device Management Clients (DMC) that interact with a Device Management Server (DMS). The DMC runs on the target device and the DMS runs on top of the Oracle Database Lite Mobile Server. For the DMS to interact with the remote DMC, the Administrator must enable a compatible networking layer. For example, HTTP, Wake On Ring, and so on. The DMS uses the Mobile Server's user model and provisioning functionality to provide a unified device, software and data management features.

The DMC is a collection of executables that perform various DM tasks. The DMC consists of a Device Management Agent (DMA), Software Management Client (SMC), Software Update Checker and a set of Device Management APIs for applications. The DMA handles basic Device Management functionalities such as command execution and the SMC handles client software management.

10.1.1 Functionality

Oracle Database Lite Device Management supports the following functionality.

  1. Remote inspection of client device hardware and operating system settings.

  2. Remote inspection and modification of application configuration settings.

  3. Client database information retrieval and validation.

  4. Client databases synchronization with the Oracle Database.

  5. Client device lock down, application removal, application data removal.

  6. Client software management.

  7. Device configuration files modification. For example, ODBC.INI.

  8. Remote database integrity verification.

10.1.2 Terms and Definitions

This section familiarizes you with the terms and definitions used during device management.


Database schema in which all DMS objects are recorded. DMS provides APIs to access Repository objects. The Device Management Repository is a part of the Mobile Server Repository.


Person who administers DMS objects using the Mobile Manager.


External implementation of a functionality required by the DMS. For example, the DMS depends on the Network Provider to transmit data to devices. If you have a custom network in your environment, you must create the Network Provider class using the JAVA language and register it with the DMS, so that the DMS can transmit messages to remote devices. A Network Provider must implement the oracle.lite.provider.NetworkProvider interface.

For a complete definition of this interface, refer the corresponding JAVADOC.

This release of the Oracle Database Lite 10g Device Manager ships with the following network providers.

  1. HTTP - DMS uses HTTP protocol to send commands to DMC.

  2. RAPI - Remote API (Microsoft ® ActiveSync API) Network Provider only supports Pocket PC class devices that are connected directly to the computer which is running the Mobile Server.

  3. WOR - Wake on ring based network protocol.

  4. SMTP - E-mail based Network Provider.

INF File

An INF file contains software installation instructions. For every application in the Mobile Server, it is desirable to have a unique INF file. For applications that do not have an INF file associated with it, the DMS generates a default INF file.

Developers are highly encouraged to create their own custom INF file for their applications. For more information about the INF File format, refer Section 10.3, "Software Management Client (SMC)".


Person who uses a device. ACL (access control lists) are assigned on a user basis. Users can be grouped together for administration purposes.

User Policy

The user policy determines a user's activities. For example, if a user policy setting contains device.register=true, the user can automatically register the device with the DMS. If a user's policy reads device.update=false, the user does not receive new software updates.


Platform is a logical operating environment in which the Oracle Database Lite 10g client runs. Each platform has the following set of attributes.

  • Name - Unique name that identifies the platform.

  • Type - Unique type identifier (For example, WIN32_x86_us) consisting of Operating System Type, CPU type, and Locale.

  • INF File name - Installation and configuration file name.

  • BOOTSTRAP Commands - Commands to be executed during the platform and device initialization.

  • General flags:

    1. Enabled - Indicates if the platform is enabled or not.

    2. Update - Indicates if the platform software is upgradable.

    3. Update apps - Indicates if the application software written for this platform is upgradable.

Listed below are some platforms that are shipped with this release.

  1. Oracle Lite WIN32

  2. Oracle Lite WEB

  3. Oracle Lite PPC2003 ARMV4x


Logical collection of executable code, settings (registry, INI, and so on) and installation actions (creating folder links, executing processes, and so on). Once an application is developed and tested by developers, the Administrator must publish the application to the Mobile Server. To properly install the Software Management Client on the client device, Oracle recommends that the developer also create a custom INF file.

Each application belongs to an Oracle Database Lite platform. To start using an application after publishing, the Administrator must perform the following tasks.

  • Assign an Oracle Database Lite platform to the application.

  • Assign access rights to users.

  • Create publication subscription values to publication items. For more information, refer Chapter 8, "Managing Synchronization".


Logical representation of a physical device. Only one platform can be installed on a device. Each device has the following set of attributes.

  • Name - Unique name to identify the device

  • Owner - Owner of the device (User Object)

  • Type - Unique type identifier consisting of the Operating System type, CPU type, and Locale. For example, WIN32_x86_US.

  • General Flags:

    1. Enabled - Indicates if the Device is enabled or not.

    2. Update - Indicates if the device has the capability for software or data updates.

The software management client installs applications written for the device.


Unique network identifier of a device. The device address must have a corresponding Network Provider associated with it. To transmit data to a device, the DMS uses the Network Provider associated with the address object.

To enable a communication link between the DMS and the DMC, the Administrator must create a proper device address for all devices.


An instruction to the DMC to perform specified actions. These actions can be specified using the OTL scripting language. The first step in creating a custom command is to create an OTL file. Subsequently, you must register the command with the DMS.

The Oracle Database Lite 10g release ships with a set of pre-defined commands and their associated OTL files. A command can be sent to a device in three different ways.

  1. Using the registered address of the device.

  2. Scheduled to be sent at a later time.

  3. Queuing in the device queue. A device pulls these commands later.


Process of initializing the device so that it can be managed by the DMS. During the bootstrap process, the device registers itself with the DMS. Upon successful registration, the device executes (bootstrap) commands sent by the DMS.

When a device bootstraps with the DMS, it automatically registers its default address with the DMS. For example, a Microsoft Windows based Laptop or Desktop registers its IP Address with the DMS. Whereas, a Pocket PC based device registers RAPI (Active Sync). It is imperative that the Administrator change these default address values to the correct value.

10.1.3 Architecture

As Figure 10-1 displays, the DM System operations are based on the Command and Response paradigm. An Administrator can create device specific commands and send them to the DMC. Upon receiving the commands, the DMC processes them and sends the results to DMS.

The DMS then sends the commands using one of the Network Providers defined by the administrator. The Oracle Database Lite Device Manager ships with a set of Network providers - HTTP, RAPI and Wake-on-Ring. If your company uses any other messaging mechanism, you must implement your own Network Provider implementation and must register it with the DMS.

Figure 10-1 Oracle Database Lite 10g Device Management Architecture

Oracle Database Lite Device Management architecture.

10.1.4 Security

High-level security is one of the main design requisites of the DMS. The main aspects of DM security are summarized below. Topics include: Database Security

The Oracle Database Lite software enforces security between a client, device, and the database. To connect to the database, applications require the User name and Password combination. For a higher degree of security, the entire database can be encrypted. Communication Security

There are two kinds of messages that are sent between the DM Client and the DM Server.

  1. Commands sent from the DMS to the DMC.

  2. Messages sent from the DMC to the DMS.

The Oracle Database Lite 10g software enforces the communication security process in the following sequence.

  1. All the messages exchanged between the DMS and the DMC are encrypted using the AES algorithm.

  2. Before the DMC can send messages to the DMS, it must authenticate with the DMS. DMS authentication is based on the HMAC protocol. Command Execution

DM commands are written in the OTL scripting language. The DM provides a sand box style environment for script execution. This prevents a malicious OTL script file from doing irreparable damage to the device.

The OTL scripting engine provides a highly secure environment for command execution. Script files are restricted within the scope of device management functionality and cannot perform any other operation on the client device. Database Synchronization Security

The DM uses the Consolidator client's security features to provide secure database synchronization. To achieve a high-level of security, administrators must configure the DM client to use SSL as the transportation protocol.

10.2 Device Management Client

When you install the required Mobile Client on a device (Windows Desktop/Laptop or Pocket PC based devices), the corresponding Device Management Client is installed. However, DM features may not be enabled at the time of Mobile Client Installation. To enable the DM feature in the device, it must be bootstrapped with the DMS. The Bootstrap process depends on the device's ability to connect to the Mobile Server, where the DMS is running.

The current implementation of the DMC communicates with the DMS using HTTP (or HTTP over SSL) protocol only. Once the device has been bootstrapped with the DMS, it is ready to accept device commands from the DMS.

Figure 10-2 illustrates the Device Management Client architecture.

Figure 10-2 Device Management Client Architecture

Device Management Client Architecture.

10.2.1 Device Management Agent

The Device Management Agent (DMA) executes commands and transmits results to the DMS. As DM commands are not a fixed set, users can create their own customized commands. All commands are mapped to OTL script pages. For more information about OTL, refer the Oracle Tag Language Reference. When a command originator (SMS Client or Wake On Ring Handler) invokes the DMA to execute a command, the DMA searches for the OTL script file represented by the command and executes the script file.

Command execution is queue driven. Therefore, a command sent by the server may not be executed immediately. However, the DMC guarantees command execution and discards duplicate commands.

The following sections describe the bootstrap process, configuration parameters, and the user interface. Topics include: Bootstrap Process

All devices must be registered (bootstrapped) with the DMS before it can be managed by the DMS. Bootstrap process involves registering the device with the DMS and executing a set of BOOTSTRAP commands sent by the DMS.

Bootstrapping Windows CE/Pocket PC Based Devices

To bootstrap Windows CE based devices, install Oracle Database Lite on your device and later execute the dmagent.exe program which is located in the \OraCE directory. If the device is not bootstrapped already, the DMAGENT displays the Bootstrap dialog.

To bootstrap the device, enter the appropriate values and press OK. Ensure that your Pocket PC device is connected to the network (using ActiveSync version 3.7 or later) or Ethernet/dialup/wireless connectivity. Oracle strongly recommends using the IP Address instead of the HOST NAME for the Server URL.

Once the bootstrap process is completed, the device executes bootstrap commands received from the server.

Bootstrapping Windows based Desktops/Laptops

If you have installed your Oracle Database Lite client using the setup.exe program provided by Oracle Corporation, your device is bootstrapped automatically. However, if you have installed the Oracle Database Lite client using other methods, you must bootstrap your Desktop or Laptop by invoking dmagent.exe program before using it. Configuration Parameters

Configuration parameters of the DMA are located in the devmgr.txt file, which is located in the OLITE_HOME directory. All the Boolean values must be set to 1 (true) or 0 (false). Main configuration items are located under the Section [OMC]. Table 10-1 describes each configuration item.

Table 10-1 Configuration Item Description

Parameter Name Description
DEVICE_ID The Device_ID parameter may be pre-configured by the Administrator. If the ID is not pre-defined, the DMS automatically generates an ID during the Bootstrap process.
SERVER_ID Unique system generated Server ID.
SERVER_URL HTTP URL of the Device Management Server.
APPS_DIR Directory in which all applications are installed.
SHOW_UI Display DM Client's UI (default:1)
MAX_RETRY Maximum number of attempts to execute a command.
UPDATE_DAY Day on which the automatic update is scheduled.
UPDATE_TIME Time at which the automatic update is scheduled.
DISABLE_PROMPT Disable user confirmation prompting (I/O).
PROMPT_PASSWORD Prompt for a user's password when DMAGENT is launched (default:1).


Remote access (RAS) related configuration parameters are under the section [Network]. These values may not be valid for all devices. Table 10-2 describes remote access related configuration parameters.

Table 10-2 Remote Access Configuration Parameters

Parameter Name Description
NAME Remote Access Service Name. For example, USB, WOR, and so on.
DISCONNECT Disconnect RAS connection when idling (true/false).

To store data that is needed, the DMA relies on the following two sub-directories under the OLITE_HOME directory.

  1. APPS\DM - This directory holds all DM commands.

  2. USERNAME - Command queue directory. User Interface

The DMA displays the following three dialog boxes.

  1. BOOTSTRAP - This dialog box is displayed when the user invokes a DMA on non-bootstrapped devices.

  2. Device Management Agent - This is the main dialog. This dialog box is hidden until the SHOW_UI parameter is set to TRUE in the devmgr.txt file. On a Microsoft Windows based desktop or laptop, a tray icon is displayed when the DMA is running. To invoke the DMA user interface, end users can double-click this icon. To invoke the user interface on Pocket PC based devices, users can click the DMAGENT.EXE program, which is available under the following directory.


    This user interface enables users to accomplish the following tasks.

    1. Check versions of all files.

    2. Set or reset DMA options.

  3. Password Dialog - The DMA displays this dialog box when invoked by double-clicking the DMAGENT.EXE program. Using this dialog, users can change their password. If the PROMPT_PASSWORD parameter in the devmgr.txt file is set to 0 and a valid password is already available, the DMA does not display this dialog.

10.2.2 Software Update Client

The client UPDATE program named update.exe in Microsoft Windows based devices checks for software updates in the Mobile Server. Software updates include both the Oracle Database Lite system software updates as well as client application updates. Normally, the DMAGENT or MSYNC programs (Oracle Database Lite Synchronization Client) invokes the UPDATE program to check for software updates. However, end users can manually launch the UPDATE program by clicking on the update.exe.

To turn off the automatic update feature, navigate to the Device Properties page and choose 'Yes' from the 'Upgradable' list. This action sets the DISABLE_UPDATE flag in the devmgr.txt file to '1'.

When software updates are available in the Mobile Server, the update program invokes a dialog where end users can choose the application(s) that they wish to install. Users can remove the applications that they do not wish to install immediately. The Administrator can disable the user confirmation dialog by setting the DISABLE_PROMPT parameter in the devmgr.txt file to '0'.

To install applications, click the 'Install' button. The Update program launches the Software Management Client (SMC).

10.2.3 Software Version Checker

This program displays information such as the current version of the platform, application, and files. To view the platform version, navigate to the Device Management user interface and click on the 'Version' button. Alternatively, users can invoke it by double-clicking on the olver.exe program file.

10.3 Software Management Client (SMC)

This chapter describes the Software Management Client (setup.exe) in detail and explains how to create a custom INF file for an application. The SMC provides the following functionalities.

Oracle highly recommends developers to create custom INF files for their applications. It must be named as setup.inf and must reside in the root directory of your application. When the Administrator publishes the application to the Mobile Server, the INF file is copied to the repository.

10.3.1 Software Installation

Software Installation involves copying files, updating registry settings, modifying configuration files, creating ODBC DSN, and so on. All these operations are achieved by interpreting the installation configuration file by the SMC. To start the installation process, the SMC sends the application name and current version number to the DMS. The DMS in turn locates the current INF file for such applications. If an update is available, the DMS sends the INF file to the SMC.

A typical software installation comprises the following steps.

  1. Software Management Client - Logon to the Oracle Database Lite 10g Mobile Server.

  2. Software Management Client - Requests application installation configuration file (INF file).

  3. Device Management Server - Sends the INF file to the SMC.

  4. Software Management Client - Interprets the INF file.

10.3.2 Installation Configuration (INF) File

The SMC relies on an Installation Configuration file to complete software installation, upgrade, and de-installation. This file contains all the instructions required to install or de-install client software. The Oracle Database Lite Device Management's INF file format is based on XML. The INF file contains a set of ACTIONS and each action may have multiple items. The SMC parses INF files and performs the necessary actions for each action element in the INF file.

The SMC supports a set of keywords that can be used in any INF file. As Table 10-3 describes, a keyword name starts with a '$' character and ends with a '$' symbol.

Table 10-3 Software Management Client Keyword Description

Keyword Description
$APP_DIR$ Application directory of the application
$APP_NAME$ Application name
$OS_DIR$ Operating system directory
$OS_TYPE$ Operating system type. For example, WIN32, WINCE, LINUX, PALM, and so on.
$OS_VER$ Operating system version. For example, NT, 95, XP, 3.0, and so on.
$OS_LANG$ Language or Location name. For example, EN for English, JP for Japanese.
$DESKTOP$ Folder name of the Windows desktop.
$CPU$ Device processor type. For example, x86, ARM, XSCALE, MIPS, and so on.
$HOST_NAME$ Host name of the client device.
$USER_NAME$ User name
$HTTP_PROXY$ HTTP Proxy Server name, if any.
$SERVER_URL$ Oracle Mobile Server URL. Setup Information

All Software Management actions are enclosed within the SETUP XML tag. The SETUP consists of a set of PROPERTIES, INITIALIZATION, INCLUSION of other INF files and INSTALLATION actions. All the four items must be child elements of the SETUP element. A sample INF file is given below.

<setup name="Oracle Lite" version="" type='WIN32_XP_x86'>
<property>…. </property>
        <install> …..</install>

Setup may have the following attributes specified as XML tag attributes.

  1. NAME - Application name (Mandatory).

  2. VERSION - Application version number (Mandatory).

  3. PACKAGE - Package Type. For example, cab - Windows CAB format. Properties

All the SETUP properties must be the child element of the PROPERTY tag. Setup may have following properties.

  • STORAGE - Estimated disk (storage) space (in MB) required for an application. For example,


  • MEMORY - Minimum amount of system memory (in MB) required. For example,


  • LOCATION - Location or directory name of the application. For example,

    <location default='olite' type='WIN32'></location>

  • PORT - This is an optional value and is only used when installing Oracle Database Lite clients.

  • PROMPT - All the pre-setup user prompt actions such as terminating running instances of applications are placed in this section. For example,

    <prompt><item type='WINCE' file='olobj40.dll'/>Would you like to terminate Oracle Lite Application?</prompt>

    In the above example, SETUP prompts user confirmation when it detects an application using the OLOBJ40.DLL running in the device. For example,

    <setup name="Oracle Lite" version="" type='WIN32_XP_x86'>
                            <item'>Would you like to install App1?</item>
                            <item file='olobj40.dll'>Would you like to close Oracle Lite Applications></item>

Initialization includes setting environment variables.

<init> <item type='WIN32' name='DMC_DIR'>$APP_DIR$/bin</item> </init> Including Other INF Files

The following syntax allows an INF file to include other INF files.


The value of this tag can be an application name or a fully qualified INF file name. If the value is an application name, the DMS includes the INF file of the application. INSTALL Element

This section lists all the installation steps necessary to perform Software Installation. Each of the steps (actions) must correspond to another child entry or tag. Each action element has a set of ITEMS and two optional caption strings. The caption string is displayed on the SMC's user interface. For example,

<action msg_i='Creating directories' msg_u='Removing directories'>directory</action>

When the SMC interprets the above tag, it looks for a child element by the name DIRECTORY and processes all the child items of this element. At this stage, the Device Manager UI indicates that directories are being created.

Table 10-4 describes INSTALL actions that are supported by the SMC.

Table 10-4 INSTALL Actions Supported by the SMC

Action Description
directory Lists all directories to be created.
file Lists all the files to be copied.
env Lists all the environment variables to be added to the Operating System.
registry Registry keys and values to be added to the Windows Registry.
odbc ODBC driver and DSN to be created.
java JRE to be installed in the computer.
link Folder links to be created. For example, desktop, menu, and so on.
ini INI (configuration files) to be updated.
registry DLL (or COM objects) to be registered with Windows.
execute Executable files to be launched during the installation process.
finish Installation completion messages.


The directory named ACTION contains names of all the directories to be created or removed during the installation or removal process. Entries in this section are fully qualified directory names. For example,


The SMC creates OLDB40 and CRM directories in the ROOT of the application directory.


This section lists all the files to be copied or removed during the software installation or removal process. Each item contains a target file name and source file name. For example,

        <src> win32/crm/crm.dll </src>
        <des>$APP_DIR$\crm\crm.dll </des>


This section contains all environment variables to be added to the Operating System.

   <item name='PATH'>$APP_DIR$\WEBTOGO</item>
</env >

The above example adds the APPLICATION_ROOT\WEBTOGO directory to the PATH environment variable.


This section modifies or removes Windows Registry values. All the entries in this section must be a fully qualified registry key name. Sub key names and values must be specified as a sub section. For example,

                <item name="Count" type="DWORD">400</item>
                <item name="Test" type="STRING">ABCDE</item>

The SMC adds the Windows Registry key named Test in the directory named HKEY_CURRENT_USER\Software\Oracle branch and creates a String value named Test and a DWORD value named Count inside the key. If the same script is used in UNINSTALL mode, the SMC removes the key from the Registry.


This section creates the ODBC driver and DSNs in the client device. For example,

            <item name="driver:Oracle Lite 40 ODBC Driver" dll='$APP_DIR$\bin\olod2040.dll'>
            <item name="driver:Oracle Lite 40 ODBC Driver (Client)" dll='$APP_DIR$\bin\olcl2040.dll'>
            <item name="dsn:POLITE" driver='Oracle Lite 40 ODBC Driver' dll='$APP_DIR$\bin\olod2040.dll'>


This section lists the JRE file name and the expected JAVA version. If the expected JAVA version is greater than the version that is already existing in the computer, the SMC installs a new JRE.

        <java version="1.3.1">


This section creates Windows program links (or Program menu items). Each entry must have name, a program file name and a folder name. For example,

            <item name=' Oracle Web-to-go'>


This section creates entries in the INI (configuration) files. Each item must have an INI file name and a set of values to be added to a section. For example,

            <item name=ÓPOLITE.INIÓ section=ÓAll DatabasesÓ>
                    <item name="DatabaseID">200</item>
                    <item name="NLS_LANGUAGE">ENGLISH</item>


This section lists all the programs to be executed during the installation process. Each item must have a program name, wait period, and program arguments. The wait is specified in milliseconds. For example,



This section lists all DLLs (or COM objects) to be registered with the Windows Operating System. For example,

        <register >	

10.4 Device Management Server

This section presents a discussion of the Device Management Server and describes how to manage devices and their corresponding platforms using the Mobile Manager. Topics include:

10.4.1 Overview

The Device Management Server runs on the Oracle Database Lite Mobile Server. It contains a set of Java Servlets and a web based Device Management Application, which is a component of the Mobile Manager. To provide DM functionalities, DMS servlets interact directly with Device Management Clients. Some of the common functionalities of DMS are listed below.

  • Oracle Database Lite Platform Installation

    To install the Oracle Database Lite Client on a device, download the Mobile Client Setup program from the Mobile Server. The Setup program interacts with the DMS to install the Oracle Database Lite Client Platform on the device.

  • Software Installation and Upgrades

    To install, de-install, and upgrade applications, this feature works in conjunction with the Software Management Client.

  • Send device commands.

  • Enable or disable devices.

  • Enable or disable Oracle Database Lite platforms.

  • Create custom Oracle Database Lite platforms.

10.4.2 Mobile Manager

The Mobile Server's Mobile Manager application presents device management functionality. The following sections enable you to manage device platforms, commands, device configuration, and network providers. Topics include:

10.4.3 Managing Device Platforms

To manage device platforms, login to the Mobile Server and click the Mobile Manager link in the workspace. The Mobile Server Farms page appears. Click the Mobile Devices in the top section. As Figure 10-3 displays, the Devices page appears.

Figure 10-3 Devices Page

This image displays the Devices page.

Using the Devices page, you can manage device platforms, commands, configuration, and network providers. Modifying Platform Properties

To modify device platform properties, select the Platform Name and click the Properties button. The View/Edit Properties page appears. Enter the path and file name of the modified Setup INF file and choose the required Bootstrap command from the list displayed. The Device platform is enabled by default. Click the Apply button. The Mobile Manager displays a confirmation message. Creating Custom Platform

The Mobile Manager enables users to create custom device platforms as an extension to the existing platform. To create a custom platform, select the Platform Name and click the Extend button. The Extend Platform page appears. Enter the custom platform name, path and file name of the Setup INF file, and choose the required Bootstrap command. The Device Platform is enabled by default. Click the Extend button. The Mobile Manager displays a confirmation message.

10.4.4 Managing Device Commands

To manage device commands, navigate to the Administration page and click the Command Management link. As Figure 10-4 displays, the Command Management page appears.

Figure 10-4 Command Management Page

This image displays the Command Management page.

Using the Command Management page, you can modify existing device commands and create new device commands. Modifying Existing Commands

To modify existing commands, click the required Command Name link. The chosen Command's Properties page appears. Enter the command name, description, and syntax in the corresponding fields. To check the accuracy of the command syntax, click the Syntax Check button. If no errors are found, the Mobile Manager displays a confirmation message. Click the Apply button. The Mobile Manager displays a confirmation message. Creating New Commands

To create new commands, click the Create Command button. The Create Command page appears. Enter a unique Command ID, Command String, and Description in the corresponding fields. Click the Create button. The Mobile Manager displays a confirmation message. Creating Group Commands

To create group commands, click the Create Group Command button. The Create Group Command page appears. Enter a unique Command ID and description in the corresponding fields and select the required set of commands that you need to group. The Command Weight feature controls the order in which commands must be executed. For example, a command with Weight 1 is executed first and a command with Weight 2 is executed next. Users must specify a weight for all the commands for the chosen group command. Click the Add button. The Mobile Manager displays a confirmation message.

10.4.5 Managing Device Configuration

Client configuration parameters are used by the software installer to modify client side configuration files such as the devmgr.txt, polite.ini, and the webtogo.ora.

To manage Device Configuration parameters, click the Configuration Management link under the Administration section. As Figure 10-5 displays, the Configuration Management page appears.

Figure 10-5 Configuration Management Page

This image displays the Configuration Management page.

Using the Configuration Management page, you can modify existing configuration parameters or add new parameters. Modifying Client Configuration Items

To modify client configuration items, enter the modified configuration value against the required configuration parameter and click the OK button. The Mobile Manager displays a confirmation message. Creating Configuration Items

To create configuration parameters, select the configuration object name and click the Add button. Enter a unique configuration parameter name and value in the corresponding field and click the Create button. The Mobile Manager displays a confirmation message.

10.4.6 Managing Network Providers

The Network Management page enables you to modify properties of a network provider and register new network providers. To manage network providers, navigate to the Devices page, and click the Network Management link under the Administration section. As Figure 10-6 displays, the Network Management page lists existing client configuration items.

Figure 10-6 Network Management Page

This image displays the Network Management page. Modifying Network Provider Properties

To modify existing network providers, click the Network Provider name. The chosen Network Provider's properties page appears. Enter the modified Class Name and Meta Data in the corresponding fields. Click the Apply button. The Mobile Manager displays a confirmation message. Creating New Network Providers

To register new network providers, click the Create button. The Create Provider page appears. Enter a unique Network Provider ID, class name, and meta data in the corresponding fields, and click the Create button. The Mobile Manager displays a confirmation message.

10.4.7 Administering Devices

This section enables you to modify device properties, create new device addresses, view device information and device application information. Topics include: Modifying Device Properties

Device Properties are comprised of the device address, network provider key, network provider protocol, and options to enable and upgrade a device. Using the Device Properties page, the Administrator can modify properties of a specific device and create a new device address. The Device Properties page provides controls to enable or disable a device and automatically upgrade the device. After disabling the upgrade feature, the device does not receive any software updates.

To modify device properties, navigate to the Devices page and click the Platform Name link. The Mobile Manager displays a list of associated devices for the chosen platform. Click the required Device Name link. The Properties page appears. Enter the modified device address, network provider key, and network provider protocol in the corresponding fields. Click the Apply button. The Mobile Manager displays a confirmation message. Viewing Applications

To view applications on a device, click the Applications link. The Applications page lists applications, version, setup time, and location details. Viewing Device Information

The Mobile Manager displays general and database information for a chosen device. To view device information, click the Information link. The Information page contains general information about the Operating System, Oracle Database Lite platforms, networking, CPU, and storage.

To view database information, click the Database link. The Database information page contains Oracle Database Lite information such as DSN and configuration details on the client device. Information about the ODBC.ini and POLITE.ini is displayed under the Oracle Lite DSN section. Scheduling or Sending Commands

The Commands page enables the Administrator to schedule or send device commands to a specific device. To schedule or send commands, click the Commands link. The Commands page appears.

Scheduling Commands

To schedule commands, click the Schedule button. The Schedule Command page appears. Using the Parameter section of the Command Schedule page, the Administrator can choose the required command, send the command priority, and when required, set extra command parameters. The Schedule section provides controls to set the command schedule start, repeat, and expiry durations. Enter the appropriate command schedule information in the corresponding fields, and click the Add button. The Mobile Manager displays a confirmation message.

Sending Commands

To send commands, choose the required command and click the Send Now button. To send the chosen command, the Mobile Manager seeks your confirmation and displays a confirmation message subsequently. The Mobile Manager displays an argument collection page when a command requires arguments. For example, the Upload File command requires a file name as an argument. To send the command to the device, click the Yes button. Viewing Device Logs

The Mobile Manager displays device logs and synchronization logs. To view device logs, click the Device Logs link. The Device Logs page lists existing device logs. To view synchronization logs, click the Synchronization link. Viewing the Device Command History

To view the Device Command History, click the Command History link. The Command History page lists a history of commands that were implemented for the chosen device.