OpenCCM

PDA Module
· Module Documentation
· Install Guide
· User guide
· Binary Installation
· Changes History

Project Links
· Home
· Download
· Documentation
· Mailing Lists
· Wiki
· Partners
· License
· History
· Related projects

Developers' Corner
· How to Contribute
· Workplan
· Resources
· CVS Repository
· Bug Tracking
· ObjectWeb Forge Site
· User Mailing List
· Team Mailing List

About
· Team
· Contacts

PDA Module Install Guide

This module requires the following modules to work properly :

• openccm (actually, the pda module requires that you have previously installed the whole OpenCCM platform on desktop.)
• utils (to compile this documentation)

The PDA module and all dependencies can be checked out by using the alias openccm-pda.

• Requirements
• Fully supported configurations
• OpenCCM PDA Distribution Architecture
• Compilation and Configuration Instructions
• Dependencies for the pda module
• Compilation Results
• Uninstall PDA Module

Requirements

As for any other environment, the OpenCCM distribution for PDA needs an installed JVM and ORB to work correctly. In the following distribution, OpenCCM has been succesfully tested with ORBacus-4.1 and JacORB CORBA products, the IBM J9 Java Virtual Machine (Windows CE device) and Blackdown Java Virtual Machine (Familiar Linux device). However you can use any of supported ORBs or JVM for your device by easily editing the build.properties configuration file.

Moreover to run the following provided scripts on a Windows CE device, you need to install PocketConsole v1.3 on your PDA.

Let's note also that if you want to deploy and execute OpenCCM applications on a PDA, you should (or have to) compile your application and build the Java archive of your application (more precisely the archive of the CORBA component that will be installed and instanciated on the device) using the Java compiler provided with the JVM installed in your device (for example the IBM j9c Java compiler if you use the IBM J9 JVM).

Fully supported configurations

OpenCCM has been succesfully tested for the following configurations of devices:

Note: The following devices has been used for deployment and tests of OpenCCM demos:

• HP 6340 (with TI OMAP 1510 processor),
• Qtek 9090 (with Intel PXA 263 processor),
• Compaq iPAQ 38xx and 36xx series (with StrongARM processor).
• Dell Axim X50v (with Intel PXA 270 processor).

OpenCCM PDA Distribution Architecture

The OpenCCM distribution architecture for PDA is the following:

Compilation and Configuration Instructions

To configure and compile OpenCCM PDA module, you must have already installed OpenCCM :

To install and compile OpenCCM for PDA, you have to:

1. Go into the pda root directory corresponding to your OS device (Windows CE or Linux Familiar):

   $ cd pda/linux/ or $ cd pda/wince/

2. Edit the build.properties configuration file and set the following variables:

   
   

   Variable	Description	Example (WinCE/Linux)	Mandatory
   ORB.pda.name	Name of the used ORB.	JacORB-2.1	Yes
   openccm_build.dir	Path to the local OpenCCM installed directory on desktop.	/OpenCCM-0.9.0/openccm/build	Yes

3. Start the Ant tool to compile OpenCCM and generate scripts and configuration files for your device:

   $ ant

   This create the dist/OpenCCM directory that contain the whole OpenCCM distribution for your PDA.

4. Edit the dist/OpenCCM/envi_OpenCCM_PDA (.bat/.sh) environment script and set the following variables:

   
   

   Variable	Description	Example (WinCE/Linux)	Mandatory
   ORB_HOMEDIR	Path to the installed ORB on the device.	/Program Files/ORB/JacORB-2.1 (WinCE) /mnt/card/CORBA/JacORB-2.1 (Linux Familiar)	Yes
   OpenCCM_HOMEDIR	Path where OpenCCM will be installed on the device.	/Program Files/OpenCCM (WinCE) /mnt/card/OpenCCM (Linux Familiar)	Yes
   OpenCCM_CONFIG_DIR	Path to the OpenCCM configuration directory on the device.	/Temp/OpenCCM_CONFIG_DIR (WinCE) /home/OpenCCM_CONFIG_DIR (Linux Familiar)	Yes
   JVM	Java Virtual Machine configuration on device	Windows Mobile 2003 and IBM J9 PPRO10 (*): "\Program Files\J9\PPRO10\bin\j9.exe" -jcl:ppro10 -classpath "\Program Files\J9\PPRO10\lib\ppro-ui.jar;%OpenCCM_CLASSPATH%" Windows CE 2.x / 3.x and IBM J9: "\WSDD\bin\j9.exe" -bp:"\WSDD\lib\classes.zip" -cp:"\WSDD\lib\prsnlwin.jar;%OpenCCM_CLASSPATH%"" Linux and JRE Blackdown: "/j2re1.3.1/bin/java -classpath $OpenCCM_CLASSPATH"	Yes

   (*) Note:

   • The "-jcl:..." option is used to fix the device profile to use (MIDP, Personal Profile, Foundation Profile, etc., for instance are available for J9 JVM)
   • "ppro-ui.jar" or "prsnlwin.jar" are added to classpath here to add some GUI functionnalities to the IBM J9 JVM (as AWT). SWING is also available for Windows Mobile devices by adding to classpath the swingall.jar archive provided by SUN with its (EOL) Java Foundation Classes 1.1.

   Windows CE specific configuration parameters:

   Variable	Description	Example	Mandatory
   NS.IOR	The default CosNaming service host (Windows CE).	http://host.domain:8080/NameService.IOR mcast://multicast_address_group/NameService.IOR corbaloc::host.domain:2000/NameService	No
   DCI.IOR	The default DCI Manager host (Windows CE).	http://host.domain:8080/DCI.IOR mcast://multicast_address_group/DCI.IOR corbaname::host.domain:2000/NameService#ctx/DefaultDCI (ctx default value is OpenCCM/DCImanagers)	No
   DCI_NAME FACTORY_NAME CS_NAME NODE_NAME ASSEMBLY_NAME DEMO_NAME	Default CosNaming service registration parameters (Windows CE).	DCI_NAME=DefaultDCI FACTORY_NAME=DefaultFactory CS_NAME=ComponentServerMobile NODE_NAME=MainNode ASSEMBLY_NAME=MyAssembly DEMO_NAME=MyApp.aar	No
   ZIP_ARCHIVE	Path to CORBA Component Assembly archive to deploy (AAR).	/archives	No

5. Copy the content of this dist/OpenCCM directory to the OpenCCM_HOMEDIR of your device.

   Note:
   The pda/wince/build.bat script allows to compile, generate scripts and configuration files and automatically install OpenCCM on your WinCE device, using an external tool called Remote Command (RCMD) which copy via an ActiveSync link the content of the generated dist/OpenCCM directory from the desktop to the PDA (assuming your PDA is connected to your desktop via an active ActiveSync link). Moreover, if you download the (free) Windows Mobile Developer Toys from Microsoft, you'll be able to easily deploy OpenCCM to your device via ActiveSync (copy files from desktop to device, create or remove directories on device, etc.)

   To use the automatic installation on Window CE devices feature, just set the ORB.pda.name value and type:
   \pda\wince\> build.bat

   
   

6. Source the environment:
   

   On Windows CE devices, there are two possibilities:
   
   1- If you want to use OpenCCM command scripts directly from the Explorer on PDA (recommanded), launch the DOS interpreter program, then move in OpenCCM_HOMEDIR directory (where OpenCCM is installed), for example by entering cd "\Program Files\OpenCCM", then just type replace.bat. This generates the build directory. Note that the parameters defined in envi_OpenCCM_PDA.bat will be used as default arguments (e.g. NS.IOR, CS_NAME, etc.).
   
   2- To use OpenCCM command scripts in a command line style (using the DOS interpreter program), launch the DOS interpreter program, move in OpenCCM_HOMEDIR directory (for example by entering cd "\Program Files\OpenCCM"), then type replace.bat no_launch. This generates the build directory. After that, you have to source the OpenCCM environment by typing envi_OpenCCM_PDA.bat before using OpenCCM command scripts to set environment variables (e.g. OpenCCM_HOMEDIR, JVM, etc.).
   

   On Familiar Linux devices, just launch the envi_OpenCCM_PDA.sh script to use OpenCCM command scripts.

Dependencies for the PDA module

OpenCCM-0.9+ platform
Set the openccm_build.dir parameter in build.properties file to give the path to the installed OpenCCM platform.
e.g. openccm_build.dir=/ORB3/releases/OpenCCM-0.9.0/openccm/build.

Important note:
Since 0.9.1 release, to correctly compile the pda module, the openccm_build.dir value must point to an installed OpenCCM platform which version is higher or equal than 0.9.0. (in previously pda module contained in OpenCCM-0.9.0 -or lower- release, openccm_build.dir had to point to an installed OpenCCM platform which version is lower or equal than 0.8.2). In other words:

• Compilation of the pda module contained in 0.9.1 release of OpenCCM: openccm_build.dir value must point to an OpenCCM-0.9.0, OpenCCM-0.9.1 or higher distribution.
• Compilation of the pda module contained in 0.9.0 or 0.8.2 releases of OpenCCM: openccm_build.dir value must point to an OpenCCM-0.8.2 or lower distribution.
• Compilation of the pda module contained in 0.8.1 or lower releases of OpenCCM: no openccm_build.dir have do be specified (no dependency)

Results of Compilation

After compilation, the following directories and files are created in wince/dist/OpenCCM or linux/dist/OpenCCM directory:

Uninstall PDA Module

To uninstall OpenCCM for Linux PDA:

1. Move to the Linux directory with:

   $ cd pda/linux/

2. Execute the following command:

   $ ant clean

This will remove the linux/dist/OpenCCM directory from the desktop.

To uninstall OpenCCM for Windows CE PDA:

1. Move to the Windows CE directory with:

   $ cd pda/wince/

2. Execute the following command:

   $ ant clean

This will remove the wince/dist/OpenCCM directory from the desktop.

Warning: To remove the OpenCCM build directory from the WinCE device connected to the desktop via ActiveSync, launch:

$ build.bat clean

See the user's guide for usage instructions.