|
OpenCCM
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
|
Table of Contents
-
Availability
-
Requirements
-
Extra Requirements
-
Supported CORBA Products
-
Fully Supported Configurations
-
Distribution
-
Extracting the contents of the OpenCCM archive
-
The contents of the OpenCCM archive
-
Configuration Instructions
-
Compilation Instructions
-
Compiling OpenCCM
-
Generating OpenCCM Documentation
-
Compilation Results
-
Installation Instructions
-
Installing OpenCCM
-
Installation Results
-
Installation Instructions for Windows CE / Linux PDA
-
Requirements
-
Fully Supported Configurations
-
OpenCCM distribution architecture for PDA
-
Installation, Compilation and Configuration Instructions
-
Deinstalling OpenCCM for PDA
-
Installation Instructions for the Packaging/Assembling Tool
-
Requirements
-
Build Instructions
-
Setting The Environment
Availability
Requirements
To work correctly, OpenCCM has the following mandatory requirements:
Extra Requirements
You may have to provide the following extra requirements:
-
If you want to generate the detailed OpenCCM APIs,
you need to have the doxygen tool
(http://www.doxygen.org).
-
If you are using the OpenORB
product and if you want to use the OpenCCM transactions facilities,
you need to have OpenORB OTS libraries according to your OpenORB version number.
-
If you want to use IDLscript deployment scripts for OpenCCM
demonstrations, you need to have an IDLscript interpreter
You can have a look to
CorbaScript
(http://corbaweb.lifl.fr/CorbaScript)
or Java IDLscript
(http://www.lifl.fr/~roos/jidlscript).
-
If you want to use the OpenCCM Persistent State Service (for PSS
demonstrations), you need to have a Java Data Objects (JDO) implementation.
At this time, only the Kodo JDO product
(http://www.solarmetric.com)
is supported.
The ObjectWeb Speedo project
(http://speedo.objectweb.org)
will be supported as soon as possible.
-
If you are an Apple MacOS X user and did not install a Java Development Kit,
the provided Java Framework from MacOS X updates should be sufficient.
Make sure to have the latest JavaVM update.
Supported CORBA Products
Currently, OpenCCM is supported on the following CORBA products:
If you want to use the CosTrading Service (mainly for
deployment purpose), you need to have a CosTrading Service
implementation. The table below shows currently fully
supported configuration of CosTrading Services.
ORB name | CosTrading Service Product |
Borland Enterprise Server 5.0.2 and 5.2 for Java | None |
JacORB 2.0 and 2.1 | JacORB CosTrading Service 2.0 and 2.1 |
ORBacus 4.1.x for Java | ORBacus Trader 2.0 |
The Community OpenORB 1.2.1, 1.3.0, 1.3.1 and 1.4.0-BETA1 | The Community OpenORB CosTrading Service 1.3.0, 1.3.1 and 1.4.0-BETA1 |
Warning: For The Community OpenORB 1.4.0-BETA1, it is required
to download at least all the following packages and uncompress them
in a same directory.
OpenORB module name | Comments |
OpenORB | Required |
tools | Required |
NamingService | Required |
TransactionService | Only required if the CosTransactions Service will be used |
TradingService | Only required if the CosTrading Service will be used |
PersistentStateService | Only required if the CosTrading Service will be used |
EvaluatorUtility | Only required if the CosTrading Service will be used |
Fully Supported Configurations
Currently, OpenCCM was successfully tested on the following configurations:
ORB name and release | Operating system | Java compiler |
Borland Enterprise Server 5.0.2 for Java | Linux |
SUN JDK 1.3.1
|
Borland Enterprise Server 5.0.2 for Java | Windows |
SUN JDK 1.3.1
|
Borland Enterprise Server 5.2 for Java | Windows XP |
SUN J2SDK 1.4.1-r_02
|
JacORB 2.0 | Linux |
SUN JDK 1.3.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.2
|
JacORB 2.0 | Windows XP |
SUN J2SDK 1.4.1-r_02
SUN J2SDK 1.4.2
|
JacORB 2.1 | Linux |
SUN J2SDK 1.4.2
SUN J2SDK 1.4.2_03
|
JacORB 2.1 | Windows XP |
SUN J2SDK 1.3.1_03
|
OpenORB 1.2.1 | Linux |
SUN JDK 1.3.1
SUN J2SDK 1.4.0
|
OpenORB 1.2.1 | Solaris | SUN JDK 1.3.1 |
OpenORB 1.2.1 | Windows XP |
SUN JDK 1.3.1
SUN J2SDK 1.4.0
SUN J2SDK 1.4.1-r_02
|
OpenORB 1.3.0 | Linux |
SUN JDK 1.3.1
SUN JDK 1.3.1_03
SUN JDK 1.3.1_04
SUN J2SDK 1.4.0
SUN J2SDK 1.4.0_01
SUN J2SDK 1.4.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.2
SUN J2SDK 1.4.2_03
|
OpenORB 1.3.0 | MacOS X | Apple Java Framework 1.4.1 |
OpenORB 1.3.0 | Solaris | SUN JDK 1.3.1 |
OpenORB 1.3.0 | Windows 2000 |
SUN JDK 1.3.1_03
SUN J2SDK 1.4.0
SUN J2SDK 1.4.2
|
OpenORB 1.3.0 | Windows XP |
SUN JDK 1.3.1
SUN JDK 1.3.1_03
SUN JDK 1.3.1_04
SUN J2SDK 1.4.0
SUN J2SDK 1.4.0_01
SUN J2SDK-1.4.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.1-r_02
SUN J2SDK 1.4.2
|
OpenORB 1.3.1 | Linux |
SUN J2SDK 1.4.2
SUN J2SDK 1.4.2_03
|
OpenORB 1.4.0-BETA1 | Linux |
SUN J2SDK 1.4.0
Blackdown J2SDK 1.4.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.2
|
OpenORB 1.4.0-BETA1 | Windows XP |
SUN J2SDK 1.4.0
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.1-r_02
SUN J2SDK 1.4.2
|
ORBacus 4.1.0 for Java | Linux |
SUN JDK 1.3.1
SUN JDK 1.3.1_03
SUN JDK 1.3.1_04
SUN J2SDK 1.4.0
SUN J2SDK 1.4.0_01
Blackdown J2SDK 1.4.1
SUN J2SDK 1.4.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.1_03
SUN J2SDK 1.4.2
|
ORBacus 4.1.0 for Java | Linux Familiar |
Blackdown 1.3.1
|
ORBacus 4.1.0 for Java | Solaris | SUN JDK 1.3.1 |
ORBacus 4.1.0 for Java | Windows 2000 |
SUN JDK 1.3.1
SUN JDK 1.3.1_03
SUN J2SDK 1.4.0
SUN J2SDK 1.4.2
|
ORBacus 4.1.0 for Java | Windows XP |
SUN JDK 1.3.1
SUN JDK 1.3.1_03
SUN JDK 1.3.1_04
SUN J2SDK 1.4.0
SUN J2SDK 1.4.0_01
SUN J2SDK 1.4.1
SUN J2SDK 1.4.1_01
SUN J2SDK 1.4.1-r_02
SUN J2SDK 1.4.2
|
ORBacus 4.1.0 for Java | WinCE 2.x and 3.0 |
JVM J9 IBM
|
Thank you to report to the OpenCCM community mailing list
any other configurations where you have successfully tested OpenCCM.
Distribution
Extracting the contents of the OpenCCM archive
WinZip is a registered trademark of WinZip Computing, Inc.
The contents of the OpenCCM archive
The OpenCCM archive contains the following directories and files:
Directory | File | Description |
| build.bat | Windows script for Ant compilation process. |
| build.sh | Unix script for Ant compilation process. |
config/ | | The configuration directory. |
| BES-5.0.2/ | BES-5.0.2 configuration dependencies. |
| BES-5.2/ | BES-5.2 configuration dependencies. |
| JacORB-2.0/ | JacORB-2.0 configuration dependencies. |
| JacORB-2.1/ | JacORB-2.1 configuration dependencies. |
| OpenORB-1.2.1/ | OpenORB-1.2.1 configuration dependencies. |
| OpenORB-1.3.0/ | OpenORB-1.3.0 configuration dependencies. |
| OpenORB-1.3.1/ | OpenORB-1.3.1 configuration dependencies. |
| OpenORB-1.4.0/ | OpenORB-1.4.0 configuration dependencies. |
| ORBacus-4.1/ | ORBacus-4.1 configuration dependencies. |
| Monolog/ | ObjectWeb Monolog configuration dependencies. |
| jdo/ | Java Data Objects (JDO) configuration dependencies. |
| jdo/Kodo/ | Kodo JDO configuration dependencies. |
demo/ | | The OpenCCM demonstrations directory. |
| chat/ | This illustrates a chat application. |
| common/ | Common build files and execution scripts for all demonstrations. |
| demo1/ | This illustrates a simple clients / server application. |
| demo2/ | This illustrates a simple producer / consumers application. |
| demo3/ | This illustrates a simple clients / server-producer / consumers application. |
| dinner/ | This illustrates the philosopher dinner. |
| filetransfer/ | This illustrates a file transfer application. |
| hello/ | This illustrates the classical Hello World application. |
| pss/ | All OMG Persistent State Service (PSS) demonstrations. |
doc/ | | The OpenCCM documentation directory. |
| CHANGES | Old change log. |
| COPYRIGHT | Copyright notice. |
| html/ | The whole OpenCCM documentation. |
| LICENSE | GNU Lesser General Public License. |
externals/ | | OpenCCM external dependencies. |
| ant/ |
The Apache/Jakarta Ant
compilation tool.
|
| apollon/ |
The ObjectWeb Apollon
XML DTD to GUI generation tool.
|
| cpp/ |
The MinGW Windows C/C++ preprocessor (1.0.1-20010726).
|
| fcgi/ | The FastCGI library. |
| jacl/ | The Java/Tcl library. |
| javacc/ | The JavaCC 3.2 tool. |
| jdo/ | The Sun Microsystem Java Database Objects (JDO) library. |
| jidlscript/ | The LIFL Java IDLscript library. |
| monolog/ | The ObjectWeb Monolog project. |
| ots/ | A CosTransactions Service implementation. |
| velocity/ |
The Apache/Jakarta Velocity tool.
|
| winprocess/ | Common applications to manage processes under Windows:
exec , kill , ps .
|
| xerces/ | The
Apache Xerces
XML parser.
|
| xml_dtd/ | The Enhydra Zeus tool. |
src/ | | The OpenCCM source code directory. |
| ant/ | All OpenCCM Ant files. |
| cpp/ | All OpenCCM C++ source code files. |
| doxygen/ | All OpenCCM doxygen configuration files. |
| dtd/ | All OpenCCM XML DTD files. |
| idl/ | All OpenCCM OMG IDL files. |
| java/ | All OpenCCM Java source code files. |
| PDA/ | The OpenCCM distribution for PDA. |
| resources/ | All OpenCCM resource files (e.g. icons). |
| unix/ | All OpenCCM Unix scripts. |
| windows/ | All OpenCCM Windows scripts. |
| winprocess/ | Utilities source code to manage processes under Windows (Visual Studio project). |
| xml/ | All OpenCCM XML files. |
test/ | | All OpenCCM test files. |
| idl/ | All OpenCCM OMG IDL test files. |
| ir3/ | All OpenCCM Interface Repository test files. |
| psdl/ | All OpenCCM OMG PSDL test files. |
| runtime/ | All OpenCCM runtime test files. |
| trading/ | All OpenCCM CosTrading Service related test files. |
| various/ | Various OpenCCM test files. |
| sample.cidl | The OMG CIDL sample file used in the OpenCCM User's Guide. |
| sample.idl3 | The OMG IDL 3.0 sample file used in the OpenCCM User's Guide. |
| sample.psdl | The OMG PSDL sample file used in the OpenCCM User's Guide. |
| sample.xmi | The XMI UML sample file used in the OpenCCM User's Guide. |
Configuration Instructions
To configure and compile OpenCCM, you must have already installed
a CORBA
product supported by OpenCCM.
Then configuring OpenCCM requires:
-
To check if the JAVA_HOME shell variable is correctly set
to the JDK you will use.
-
To go into the OpenCCM root directory, just do (on Unix or Windows systems):
$ cd OpenCCM-0.8.1/openccm
-
To start the Ant tool
a first time, just do on Unix systems:
$ build.sh
or on Windows systems:
$ build.bat
As result, the build.properties file is generated
in the OpenCCM root directory.
-
To edit the generated build.properties file
and set the following variables:
Variable | Description | Mandatory |
ORB.name |
The name of the ORB product used to compile and execute OpenCCM.
Select one ORB name in the proposed list.
|
Yes
|
install.dir |
The directory where the OpenCCM platform will be installed.
Default value is the local build directory.
|
No
|
ORB.home.dir |
The directory where the used ORB product is installed.
|
Yes
|
NS.home.dir |
The directory where the used CosNaming Service is installed.
Default value is ORB.home.dir .
Must be set when the used CosNaming Service is installed
in a directory different that the ORB one.
|
No
|
trader.home.dir |
The directory where the used CosTrading Service is installed.
Default value is ORB.home.dir .
Must be set when the used CosTrading Service is installed
in a directory different that the ORB one.
|
No
|
OTS.home.dir |
The directory where the used CosTransaction Service is installed.
If not set then OpenCCM will not be able to use the CosTransaction Service.
|
No
|
cpp.compiler |
The path to an installed C/C++ preprocessor.
By default, if not set then OpenCCM compilers will use their own Java-based preprocessor.
|
No
|
JDO.impl.name |
The name of the JDO product used by the OpenCCM Persistent State Service.
Only required for compiling and running PSS demonstrations.
|
No
|
JDO.impl.version |
The version of the JDO product used by the OpenCCM Persistent State Service.
Only required for compiling and running PSS demonstrations.
|
No
|
JDO.impl.prop.dir |
The directory where your JDO property file is stored
(e.g. kodo.properties ).
Only required for compiling and running PSS demonstrations.
|
No
|
JDO.impl.home.dir |
The directory where the used JDO implementation is installed.
Only required for compiling and running PSS demonstrations.
|
No
|
JDBC.driver.jar |
The full path to the JDBC driver Jar file used to access
your database.
Only required for compiling and running PSS demonstrations.
|
No
|
jre.jars.dir |
This is the location for your Java Runtime Environment JAR files, typically
the lib/ directory of your JDK.
This is the default, but MacOS X users must change this value to the commented
one in case they're using built-in Java Framework.
|
No
|
Warning: On Windows systems, directories must be
separated by '/' instead of '\', e.g. write
c:/dev/OpenCCM instead of
c:\dev\OpenCCM .
Else a lot of errors will appear at compilation and
execution times.
Warning: Don't put some space characters at the end of lines
of the previously configurated properties,
else some Ant build errors would raise.
Compilation Instructions
Compiling OpenCCM
After configurating OpenCCM, just do on Unix systems:
$ build.sh
or on Windows systems:
$ build.bat
Generating OpenCCM Documentation
To generate OpenCCM APIs documentation, you must have already installed the
Doxygen tool. Then, just do:
$ build.sh doc
or
$ build.bat doc
Compilation Results
After compilation, a directory is created according to the name of the used
ORB product. It contains the following directories and files:
Directory | File | Description |
bin/ | | All generated binaries. |
classes/ | | All compiled Java classes. |
doc/ | | All generated documentation. |
dtd/ | | All XML DTD files. |
externals/ | | All external used Java archives. |
generated/ | | All generated Java source files. |
idl/ | | All OpenCCM OMG IDL files. |
jar/ | | All OpenCCM merged Java archives. |
lib/ | | All OpenCCM generated Java archives. |
resources/ | | All OpenCCM resource files (e.g. icons). |
templates/ | | All generator template files. |
xml/ | | All XML files for the launcher or the GUIs. |
Installation Instructions
Installing OpenCCM
Execute the following command to install OpenCCM:
$ build.sh install
or
$ build.bat install
Installation Results
After installation, the following directories and files are created in
the install.dir directory configurated in the
build.properties file:
Directory | File | Description |
bin/ | | All OpenCCM binaries and scripts.
See OpenCCM User's Guide for more
information. |
| envi_OpenCCM.bat | The environment file for using OpenCCM from Windows shells. |
| envi.OpenCCM.sh | The environment file for using OpenCCM from Unix shells (sh, bash, etc). |
| envi.OpenCCM.csh | The environment file for using OpenCCM from Unix C-shells (csh, tcsh, etc). |
doc/ | | All OpenCCM documentation. |
dtd/ | | All OpenCCM XML DTD files. |
externals/ | | All external Java archives. |
idl/ | | All OpenCCM OMG IDL files. |
jar/ | | All OpenCCM merged Java archives. |
resources/ | | All resource files (e.g. icons). |
templates/ | | All generator template files. |
xml/ | | All XML files for the launcher or the GUIs. |
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.
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:
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 | OpenCCM for PDA Installation and User 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:xerces.jar;OpenCCM_Launcher.jar
Linux:
-classpath xerces.jar:OpenCCM_Launcher.jar
|
Yes
|
zip_archive.dir |
Path to CORBA Component Assembly archive to deploy (AAR).
|
${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
Installation Instructions for the Packaging/Assembling Tool
The OpenCCM's Packaging/Assembling Tool is now available as a
separate module in the CVS. Still available in its former version
within the OpenCCM's main module, we recommend to use this version,
since of course it's more up to date, and can be used without
building a complete version of OpenCCM. Being dependant on the
utils module, everything can be downloaded using :
$ cvs checkout openccm-pat
This will download in your current working director both utils
module and packaging_assembling_tool , in two
separate folders that interact together during the build process.
ATTENTION, you must not separate them until the tool
build process isn't complete.
Requirements
The Apache/Jakarta Ant
compilation tool is NOTshipped with these modules.
You have to have your own installation of this software in order
to build the OpenCCM's Packaging/Assembling Tool.
There are no other specific requirements, except for a Java
Development Kit. No ORB implementation is required to build or
run the tool
Build Instructions
The build process must be intiated from the
packaging_assembling_tool directory. Everything builds in
a build subdirectory, and all final JARs are
copied to the build/lib dir, calling the following
ANT target (assuming the ANT_HOME environment variable is set, and
the binary is in the path) :
$ ant ccm_tool
Setting The Environment
You don't need to setup your environment to use the tool. Of
course, you can still add the appropriated build/bin
directory to your path, for convenient access from anywhere in your
system to the script, named ccm_assembling.
Usage instructions for the OpenCCM's Packaging/Assembling Tool
can be found
here.
| |