Table of Contents

• Availability
  • Requirements
  • Extra Requirements
  • Fully Supported Configurations
• Distribution
  • Extracting the contents of the OpenCCM archive
  • The contents of the OpenCCM archive
  • Using the CVS repository
• Configuration Instructions
• Compilation Instructions
  • Compiling OpenCCM
  • Compilation Results
• Installation Instructions
  • Installing OpenCCM
  • Installation Results
• Installation Instructions for Windows CE / Linux PDA

Availability

Requirements

To work correctly, OpenCCM has the following mandatory requirements:

• Any Windows or Unix-like system (including Linux, Mac OS X and CYGWIN).
• A Java Development Kit : versions 1.3, 1.4, or 5.0 are supported.
• The Apache Ant project (http://ant.apache.org/), version 1.6 and above.
• A full Java CORBA 2.4 compliant product, see currently supported CORBA products.
• Please note that Mac OS X users should use the provided Java Framework from MacOS X updates. Make sure to have the latest JavaVM update.

Extra Requirements

You may have to provide the following extra requirements:

• 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 (see the PSS module install guide` for detailed requirements).
  At this time, only the Kodo JDO (http://www.solarmetric.com) and Hibernate (http://www.hibernate.org/) products are supported.
  The ObjectWeb Speedo project (http://speedo.objectweb.org) will be supported as soon as possible.

Fully Supported Configurations

Currently, OpenCCM was successfully tested on the following configurations:

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

• On a Unix like system:

  Execute the following commands in a shell window to extract the contents of the OpenCCM archive:

  1. Uncompress the archive file:

     $ gunzip OpenCCM-0.9.0.tar.gz

  2. Untar the archive file:

     $ tar xvf OpenCCM-0.9.0.tar

• On a Microsoft Windows system, you can use a tool such as WinZip to extract the contents of the OpenCCM archive.
• On a Apple Mac OS X system, you can use your favorite tool to extract 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 modules :

Using the CVS repository

An up-to-date version of these instructions can be found on the forge website.

This project's CVS repository can be checked out through anonymous (pserver) CVS with the following instruction set.

The whole platform can be downloaded by checking out the CVS. When prompted for a password for anonymous, simply press the Enter key.

cvs -d:pserver:anonymous@cvs.forge.objectweb.org:/cvsroot/openccm login
        

cvs -z3 -d:pserver:anonymous@cvs.forge.objectweb.org:/cvsroot/openccm co -dP .
        

A full description of all modules provided on this CVS repository can be found on the Modules Guide page.

Configuration Instructions

To configure and compile OpenCCM, ensure you fill the requirements section.

Then configuring OpenCCM requires :

1. Check if the JAVA_HOME shell variable correctly points the JDK you will use.

2. Go into the OpenCCM core module directory, just do (on Unix or Windows systems):

   $ cd OpenCCM-0.9.0/openccm

3. Start a first Ant process to initialize setting files:

   $ ant

   As a result, the build.properties file is generated in the current OpenCCM core module directory.

4. Edit the generated build.properties file and set the following variables:

   Variable	Description	Default	Mandatory
   coach_tracing.needed	This is a switch to activate the COACH Tracing build.	false	No
   pss.needed	This is a switch to activate the Persistent State Service build.	false	No
   uml.needed	This is a switch to activate the UML module build.	false	No
   ORB.name	The name of the ORB product used to compile and execute OpenCCM. Select one ORB name in the proposed list by uncommenting it.		Yes
   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.	externals/ots	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
   pf.name	The name of the Persistent Framework used Only required for compiling and running PSS demonstrations.	jdo	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
   JDO.impl.name	The name of the JDO product used by the OpenCCM Persistent State Service. Only required for compiling and running PSS demonstrations.	kodo	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.	kodo-3.0.3	No
   jdo.home.dir	The directory where the used JDO implementation is installed. Only required for compiling and running PSS demonstrations.		No

   Warning: On Windows systems, directories must be separated by '/' instead of '\', e.g. write c:/dev/OpenCCM instead of c:\dev\OpenCCM.

   Warning: Directories containing space characters are not supported for the moment (see bug #100551). In the same way, clear any space characters at the end of path defining properties.

Compilation Instructions

Compiling OpenCCM

After configurating OpenCCM, just restart the ANT process:

$ ant

Compilation Results

After compilation, a build directory is created. It contains the following directories and files:

Installation Instructions

Installing OpenCCM

Execute the following command to install OpenCCM:

$ ant -Ddist.dir=<directory> distrib

Where <directory> is the path where you want to build the binary distribution.
Once the operation is finished, read the README file located in the distribution directory.

Installation Results

After installation, the following directories and files are created in the given dist.dir directory:

Installation Instructions for Windows CE / Linux PDA

Please find detailed instructions in the PDA Guide.