Table of content
Installation Instructions for Windows CE /
Linux PDA
The OpenCCM for PDA distribution is now available as a separated module
on the CVS. The OpenCCM runtime archive provided with this PDA
distribution support now the Distributed Computing Infrastructure (DCI)
features. To get the pda module, execute the following command:
$ cvs checkout pda
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 CORBA product, 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.
Fully supported configurations:
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).
OpenCCM distribution architecture for PDA
The OpenCCM distribution architecture for PDA is the following:
Directory |
|
File |
Description |
common/ |
|
|
All OpenCCM for Windows CE and Linux
common files. |
|
externals/ |
|
All external Java archives (Apollon,
JIDLscript, Xerces, Browser framework, etc.). |
|
jar/ |
OpenCCM_Launcher.jar |
The OpenCCM Launcher Java archive. |
|
|
OpenCCM_Plugins.jar |
OpenCCM plugins (Browser plugin, etc.). |
|
src/ |
dtd/ccm/*.dtd |
The OpenCCM DTDs. |
|
|
xml/launcher/*.xml |
All XML files for the OpenCCM
launcher. |
linux/ |
|
|
OpenCCM for Linux device files. |
|
|
build.xml |
Linux PDA Ant build file. |
|
|
build.properties |
Linux PDA configuration file. |
|
src/ |
bin/*.sh |
OpenCCM Linux command scripts. |
|
|
xml/launcher/Runtime.xml |
OpenCCM Linux specific runtime XML Launcher configuration file. |
|
lib/ |
OpenCCM_*.jar |
OpenCCM Linux PDA specific runtime libraries. |
wince/ |
|
|
OpenCCM for Windows CE device files. |
|
|
build.xml |
Windows CE PDA Ant build file. |
|
|
build.properties |
Windows CE PDA configuration file. |
|
archives/ |
|
CORBA Component Assembly archive of
OpenCCM demonstrations for Windows CE. |
|
externals/ |
|
External tools for Windows CE distribution
(Remote Command tool to automatically install OpenCCM on the device
via ActiveSync). |
|
src/ |
bin/*.bat |
OpenCCM Windows CE command scripts. |
|
|
xml/launcher/Runtime.xml |
OpenCCM Windows CE specific runtime XML Launcher configuration file. |
|
lib/ |
OpenCCM.jar |
OpenCCM Windows CE specific runtime library. |
doc/ |
|
readme.htm |
This HTML guide. |
Installation, Compilation and Configuration
Instructions
To install and compile OpenCCM for PDA, you have to:
-
Go into the pda root directory corresponding to your OS device
(Windows CE or Linux):
$ cd pda/linux/
or $ cd pda/wince/
-
Edit the build.properties
configuration file and set the
following variables:
Variable |
Description |
Example (WinCE/Linux) |
Mandatory |
orb.install.dir |
Path to the installed ORB on the device. |
/ORB/JOB-4.1.0 |
Yes |
openccm.install.dir |
Path where OpenCCM build dir will be
installed (on the device). |
/OpenCCM/build |
Yes |
openccm.config.dir |
Path to the OpenCCM configuration
directory (Linux only). |
/OpenCCM_CONFIG_DIR (Linux) |
Yes |
java.install.dir
|
Path to the installed JVM on the device. |
\\WSDD (Windows CE / IBM J9 JVM)
/j2re1.3.1 (Linux / Blackdown JVM) |
Yes |
CLASSPATH
|
Classpath for Java and OpenCCM. |
Windows CE:
-cp:${java.install.dir}\\prsnlwin.jar;
${openccm.install.dir}\\externals\\xerces\\xerces.jar;
${openccm.install.dir}\\jar\\OpenCCM_Launcher.jar
Linux:
-classpath ${openccm.install.dir}/externals/xerces/xerces.jar:
${openccm.install.dir}/jar/OpenCCM_Launcher.jar
|
Yes |
zip_archive.dir |
Path to CORBA Component Assembly archive
to deploy (ZIP). |
${openccm.install.dir}/archives |
No |
Windows CE specific configuration parameters:
Variable |
Description |
Example (WinCE/Linux) |
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=ComponentServer2
NODE_NAME=MainNode
ASSEMBLY_NAME=MyAssembly
DEMO_NAME=MyApp.aar
|
No
|
-
Start the Ant tool to compile OpenCCM and generate scripts and
configuration files for your device:
$ ant build
This create the [linux-or-wince]/build
directory that
contain the whole OpenCCM distribution for your PDA.
-
Copy the content of this build/
directory to the
openccm.install.dir
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 build
directory from the desktop to the PDA
(assuming your PDA is connected to your desktop via an active ActiveSync
link). The first time you use this script, you have to
unfortunately create the entire structure of the OpenCCM architecture
directories on your device as the RCMD tool is not able to remotely
create directory on device (or simply by copying the content of the
build/
to the openccm.install.dir
directory).
Nevertheless, 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 this, just type:
\pda\wince\> build.bat
Deinstalling OpenCCM for PDA
To deinstall OpenCCM for Linux PDA:
- Move to the Linux directory with:
$ cd pda/linux/
- Execute the following command:
$ ant clean
This will remove the linux/build
directory from the
desktop.
To deinstall OpenCCM for Windows CE PDA:
- Move to the Windows CE directory with:
$ cd pda/wince/
- Execute the following command:
$ ant clean
This will remove the wince/build
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
OpenCCM for PDA User Guide
OpenCCM PDA available commands:
Command |
Description |
ccm_install |
Installs the OpenCCM Configuration Repository by creating the OpenCCM_CONFIG_DIR directory and other OpenCCM component servers directories. |
ns_start |
Starts the ORBacus-4.x CosNaming Service on the PDA. By default, the CosNaming Service is started on the port 2000. |
ns_set |
Set the IOR of the started CosNaming Service. |
dci_set |
Set the IOR of the started DCI Manager. |
dci_start |
Starts an OpenCCM DCI Manager. |
factory_start |
Starts an OpenCCM AssemblyFactory Manager. |
node_start |
Starts an OpenCCM Node Manager in an OpenCCM Distributed Computing Infrastructure. |
jcs_start |
Starts (manually) an OpenCCM Java ComponentServer. |
ccm_deploy |
Starts the deployment process using the OpenCCM deploytool from the PDA. |
tear_down |
Tear down a running assembly. |
ccm_deinstall |
Deinstalls the OpenCCM environment. |
Set the IOR of the started CosNaming Service
Usage: ns_set <IOR|URL>
- Linux PDA:
Execute one of the following commands from a console on the device:
$ ns_set.sh http://host.domain:8080/NameService.IOR
$ ns_set.sh mcast://multicast_address_group/NameService.IOR
$ ns_set.sh corbaloc::host.domain:2000/NameService
Set the IOR of the started DCI Manager
Usage: dci_set <IOR|URL>
- Linux PDA:
Execute one of the following commands from a console on the device:
$ dci_set.sh http://host.domain:8080/DCI.IOR
$ dci_set.sh mcast://multicast_address_group/DCI.IOR
$ dci_set.sh corbaname::host.domain:2000/NameService#OpenCCM/DCIManagers/DCI_NAME
Starting an OpenCCM Java ComponentServer on your
device
The jcs_start
command manually starts an OpenCCM Java
ComponentServer on the device. Starting a ComponentServer on the device
requires that first a CosNaming Service is running somewhere in a node of the
network.
Usage: jcs_start <ComponentServerName>
- Linux PDA:
Execute the following command from a console on the device:
$ jcs_start.sh <ComponentServerName>
- WinCE PDA:
Execute the following command from a DOS console on the device:
> jcs_start.bat <NS.IOR>
<ComponentServerName>
Warning:
If no argument is provided (if the script is
directly launched from an explorer), the jcs_start.bat
command uses the NS.IOR
parameter
provided in the wince/build.properties
configuration file
to locate the CosNaming service for its registration, and uses the
CS_NAME
parameter as the
<ComponentServerName>
value.
Starting an OpenCCM DCI Manager on your
device
The dci_start
command starts an OpenCCM DCI Manager on the
device. Starting a DCI Manager on the device requires that first a
CosNaming Service is running somewhere in a node of the network.
Usage: dci_start <DCIName>
- Linux PDA:
Execute the following command from a console on the device:
$ dci_start.sh <DCIName>
- WinCE PDA:
Execute the following command from a DOS console on the device:
> dci_start.bat <NS.IOR> <DCIName>
Warning:
If no argument is provided (if the script is
directly launched from an explorer), the dci_start.bat
command uses the NS.IOR
parameter
provided in the wince/build.properties
configuration file
to locate the CosNaming service for its registration, and uses the
DCI_NAME
parameter as the <DCIName>
value.
Starting an OpenCCM Assembly Factory on your
device
The factory_start
command starts an OpenCCM Factory
Manager on the device. Starting a Factory Manager on the device requires
that first a CosNaming Service is running and that a DCI manager is
started somewhere in a node of the network.
Usage: factory_start <FactoryName>
- Linux PDA:
Execute the following command from a console on the device:
$ factory_start.sh <FactoryName>
- WinCE PDA:
Execute the following command from a DOS console on the device:
> factory_start.bat <NS.IOR> <DCI.IOR>
<FactoryName>
Warning:
If no argument is provided (if the script is
directly launched from an explorer), the factory_start.bat
command uses the NS.IOR
parameter
provided in the wince/build.properties
configuration file
and uses the DCI_NAME
and FACTORY_NAME
values.
Starting an OpenCCM Node Manager on your
device
Since OpenCCM-0.8 release, it is possible to start an OpenCCM Node
Manager in an OpenCCM Distributed Computing Infrastructure
(DCI). No need to start an OpenCCM ServerActivator
and
ComponentInstallation
on the device (by launching deprecated
ci_start
and activator_start
command scripts of
the previous release), as it is now provided as interfaces by the Node
Manager. It provides functionalities to start and stop OpenCCM Component
Servers, to install and manage CORBA component archives or to access meta
information about the node.
The node_start
command starts an OpenCCM Node Manager on
the device. Starting a Node Manager on the device requires that first a
CosNaming Service is running and that a DCI manager is started somewhere
in a node of the network.
Usage: node_start <NodeName>
- Linux PDA:
Execute the following command from a console on the device:
$ node_start.sh <NodeName>
- WinCE PDA:
Execute the following command from a DOS console on the device:
> node_start.bat <NS.IOR> <DCI.IOR>
<NodeName>
Warning:
If no argument is provided (if the script is
directly launched from an explorer), the node_start.bat
command uses the NS.IOR
parameter
provided in the wince/build.properties
configuration file
and uses the DCI_NAME
and NODE_NAME
values.
Starting a deployment process from your
device
The ccm_deploy
command starts the deployment process of an
OpenCCM application from the device.
Usage: ccm_deploy -F <FactoryName> <AssemblyArchive>
where <AssemblyArchive>
is the path to the CORBA
Component Assembly ZIP archive to deploy.
- Linux PDA:
Execute the following command from a console on the device:
$ ccm_deploy.sh -F <FactoryName> <AssemblyArchive>
- WinCE PDA:
Execute the following command from a DOS console on the device:
> ccm_deploy.bat <NS.IOR> <DCI.IOR>
<FactoryName> <AssemblyArchive>
Warning:
If no argument is provided (if the script is
directly launched from an explorer), the ccm_deploy.bat
command uses the NS.IOR
, DCI.IOR
,
DCI_NAME
, FACTORY_NAME
,
zip_archive.dir
(path to the assembly) and
DEMO_NAME
(the assembly archive name) parameters provided
in the wince/build.properties
configuration file.
Tear down the Assembly
The tear_down
command tear down a running assembly.
Usage: tear_down <AssemblyName>
-
Linux PDA:
Execute the following command from a console on the device:
$ tear_down.sh <AssemblyName>
-
WinCE PDA:
Execute the following command from a DOS console on the device:
> tear_down.bat <NS.IOR> <AssemblyName>
Warning:
If no argument is provided (if the script is directly launched from an explorer), the ccm_deploy.bat
command uses the NS.IOR
and ASSEMBLY_NAME
(the name of the running assembly) parameters provided in the wince/build.properties
configuration file.