Oracle® Fusion Middleware Administrator's Guide for Oracle Application Development Framework 11g Release 1 (11.1.1.5.0) Part Number E15470-05 |
|
|
View PDF |
This chapter explains how to deploy ADF Mobile client applications to BlackBerry smartphones and Windows Mobile devices during production and later-stage testing. For information about deploying the mobile client applications for development, see Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
This chapter includes the following sections:
Section 5.1, "Introduction to Deploying ADF Mobile Client Applications"
Section 5.2, "Deploying Applications to BlackBerry Smartphones"
Section 5.3, "Deploying Applications to Windows Mobile Devices"
Section 5.4, "Configuring Applications for Client Database Connection"
After the mobile client application has been developed using Oracle JDeveloper, you can deploy this application to the production environment. You use the following tools for production-level deployment:
Oracle Database (Standard or Enterprise Edition) with administrative login credentials.
Oracle Database Lite Mobile Server (Mobile Server) with administrative login credentials, configured with the mobile client application database synchronization.
Mobile Sync Client (mSync)
Packaged mobile client application to be deployed
Windows Mobile device or BlackBerry smartphone
For information about deploying the mobile client applications for development and testing purposes using JDeveloper, see the following:
"Deploying ADF Mobile Client Components" chapter of Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
You use one of the following to deploy a mobile client application as a packaged COD file that includes platform-specific deployment profiles:
BlackBerry Desktop Manager (see Section 5.2.1, "How to Deploy Using BlackBerry Desktop Manager")
BlackBerry Enterprise Server (see Section 5.2.2, "How to Deploy Using BlackBerry Enterprise Server")
Web server (see Section 5.2.3, "How to Deploy Using a Web Server")
The packaged application files are located in directories that were specified at development time during the deployment phase. For more information on the packaged files and their locations, see the following:
Section 5.2.5, "What You May Need to Know About BlackBerry Deployment Files"
"Deploying BlackBerry Applications" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
For more information and details on production deployment to BlackBerry smartphones, see How to Deploy and Distribute Applications tutorial on BlackBerry forums.
You use BlackBerry Desktop Manager to deploy a packaged mobile client application to a single smartphone.
BlackBerry Desktop Manager uses BlackBerry ALX loader program to load COD files.
Note:
BlackBerry Desktop Manager is included in the BlackBerry Desktop Software installation. For more information, see "How to Install BlackBerry Desktop Software" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.To deploy the application using BlackBerry Desktop Manager:
Ensure that you have both the application COD and ALX files available. These files were placed by JDeveloper in the deploy
directory of your application during the deployment stage of development.
Connect the smartphone to the PC with the USB cable or Bluetooth.
Open BlackBerry Desktop Manager.
Click Applications tab. All applications installed on the smartphone are listed in the Applications pane.
To add an application, click Import Files.
In the dialog that appears, browse and select the ALX file of the mobile client application, and then click OK.
Click Apply to complete the deployment.
You can use BlackBerry Enterprise Server to deploy a packaged mobile client application (COD file) to a smartphone (see How to Deploy and Distribute Applications BlackBerry tutorial).
For more information on BlackBerry Enterprise Server and its usage, see the following BlackBerry Enterprise Server documentation:
A packaged mobile client application can be distributed to the production environment using a Web server. This deployment method enables the end users to download the application from the provided URL and install it on their smartphone.
The process of uploading the application to the Web server varies depending on the following:
The type of the Web server
Access configurations
Typically, you distribute the application as follows:
Place both the JAD file that references the application COD file, as well as the COD file, on the Web server.
Point the BlackBerry smartphone to the location of the JAD file.
For more information, see BlackBerry documentation.
After successful deployment, the mobile client application appears on the BlackBerry smartphone as an application, or an icon to run the application. To run the application, you would require ALX application loader file to load COD files.
For more information about COD and ALX files, see BlackBerry support forums at http://us.blackberry.com/support
.
To run the Application on BlackBerry Smartphone:
Install the client database for the BlackBerry smartphone. For more information, see "About Using a Client Database" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
Open the smartphone and load the application. The application would be available in the Downloads folder:
In the Mobile Sync page, enter the required details.
Navigate the selection to the Sync button.
Press Enter to run the application.
Table 5-1 lists files that you deploy to a BlackBerry smartphone.
Table 5-1 BlackBerry Deployment Files
File Name | Location | Description | Used with |
---|---|---|---|
COD |
Specified during deployment phase at development time. |
A generic executable file that contains all application artifacts, including platform-specific deployment profiles. Can be uploaded through a USB link or wirelessly. Appears on the smartphone as an application or icon. |
|
ALX |
The location of the COD file. |
The Application Loader XML file that communicates the location (on your computer) of the application to be installed. |
BlackBerry Desktop Manager |
JAD |
There is no default location |
Java Application Descriptor file that contains information about the application and the location of the application's COD file. |
Web server |
Deploying a packaged mobile client application to a Windows Mobile device is different from deploying to a BlackBerry smartphone: applications developed for Windows Mobile platform are packaged as CAB (cabinet) files and require usage of Windows Mobile-specific tools to enable deployment.
The CAB file includes the application JAR file, the launcher executable file, the options file, and platform-specific deployment profiles. For more information, see the following:
"About the Launcher Executable File" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
Section 5.3.4, "What You May Need to Know About Windows Mobile Deployment Files"
For information on how to create an application package at development time, see "Deploying a Windows Mobile Application" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
You use one of the following to deploy a packaged mobile client application:
Microsoft ActiveSync (see Section 5.3.1, "How to Deploy Using Microsoft ActiveSync")
Oracle Database Lite Mobile Server (the Mobile Server) (see Section 5.3.2, "How to Deploy Using the Mobile Server")
You can use Microsoft ActiveSync 4.5 or Microsoft Windows Mobile Device Center 6.1 or later to deploy a packaged mobile client application.
For more information on Microsoft ActiveSync 4.5 and Microsoft Windows Mobile Device Center 6.1, see "How to Connect the Mobile Device or Emulator" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
Before you begin, ensure that you have deployed the Java Virtual Machine to the Windows Mobile device. For more information, see "Deploying the ADF Mobile Client Runtime" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
To deploy the application using Microsoft ActiveSync:
Connect the Windows Mobile device to the PC with the USB cable or Bluetooth.
Open Microsoft ActiveSync or Microsoft Windows Mobile Device Center.
Click Explore to open the Mobile Device directory.
Copy the application's CAB file to the Mobile Device directory, and then close the window.
Navigate to the CAB file on the device and click on it to trigger the execution, and then follow the installer prompts.
You can deploy a packaged mobile client application to the Mobile Server. For more information, see "Publishing Applications to the Mobile Server Repository" section in Oracle Database Lite Administration and Deployment Guide.
For additional information, see the following:
Once the application is deployed to the Mobile Server, it is available for download from a specific URL (see "Selecting Application Files for Public Use" section in Oracle Database Lite Administration and Deployment Guide).
Once the application is installed on the user device, you can perform a variety of administrative tasks, such as the following:
Trigger the Mobile Server's device management function to push a new version of the application or a patch to the device. For more information, see "Managing Device Software Updates" section in Oracle Database Lite Administration and Deployment Guide.
Introduce the device management functionality in the synchronization client and use the synchronization client running on the device. For more information, see "Managing Your SQLite Mobile Client" chapter of Oracle Database Lite SQLite Mobile Client Guide.
Troubleshoot and tune the application. For more information, see Oracle Database Lite Administration and Deployment Guide.
After successful deployment, the mobile client application is ready to run on the Windows Mobile device.
To run the application on a Windows Mobile device:
Install the client database for the Windows Mobile device. For more information, see "About Using a Client Database" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework.
In the Windows Mobile device, open File Explorer, and then run the application as follows:
In the Mobile Sync page, enter the required details.
Navigate the selection to the Sync button.
Press Enter to run the application.
Table 5-2 lists files that you deploy to a Windows Mobile device.
Table 5-2 Windows Mobile Deployment Files
File Name | Location | Description | Used with |
---|---|---|---|
CAB |
Specified during deployment phase at development time. |
The cabinet file is a library of compressed files stored as a single file. Cabinet files are used to organize installation files that are copied to the user's system. This file includes an application JAR file, a launcher executable file, and an options file. |
|
For information, see the following:
"About Synchronizing Data with Oracle Mobile Server" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
"Specifying the Client Database Location for an Application" section in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
"Working Directly with the Database" chapter in Oracle Fusion Middleware Mobile Client Developer's Guide for Oracle Application Development Framework
When the end user synchronizes data from the mobile device or smartphone, all changes made by this user are updated on Oracle Database Lite Mobile Server (the Mobile Server). The Mobile Server also updates itself with any changes made on the base database server by the base ADF application. For more information, see Oracle Database Lite Administration and Deployment Guide.