PDA Module User's Guide

OpenCCM PDA available commands in generated build directory:

Command	Description
`ccm_install`	Install the OpenCCM Configuration Repository by creating the OpenCCM_CONFIG_DIR directory and other OpenCCM component servers directories.
`comanche_start`	Start the OpenCCM Comanche http and multicast server to give access to OpenCCM services (e.g. IOR of NameService)
`ns_start`	Starts the <ORB.name> 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`	Start an OpenCCM DCI Manager.
`factory_start`	Start an OpenCCM AssemblyFactory Manager.
`node_start`	Start an OpenCCM Node Manager in an OpenCCM Distributed Computing Infrastructure.
`jcs_start`	Start (manually) an OpenCCM Java ComponentServer.
`ccm_deploy`	Start the deployment process using the OpenCCM deploytool from the PDA.
`tear_down`	Tear down a running assembly.
`ccm_uninstall`	Uninstall 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 envi_OpenCCM_PDA.bat environment 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 envi_OpenCCM_PDA.bat environment 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 envi_OpenCCM_PDA.bat environment 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 envi_OpenCCM_PDA.bat environment 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 (path to the assembly) and DEMO_NAME (the assembly archive name) parameters provided in the envi_OpenCCM_PDA.bat environment 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 tear_down.bat command uses the NS.IOR and ASSEMBLY_NAME (the name of the running assembly) parameters provided in the envi_OpenCCM_PDA.bat environment file.