Table of Contents
Warning: The OpenCCM User's Guide is now split
into the following documents:
Environment for using OpenCCM
The OpenCCM's Compilation Chain
Generation and implementation rules
The OpenCCM's Execution Chain
Writing an application with OpenCCM
Writing CCM XML meta files
Using deployment functionnalities
Browsing and managing your application
The Persistent State Service
The following demonstrations are available:
|demo/hello||This illustrates the classical Hello World application showing how
component-unaware clients could create a server component and use
a facet provided by this one.
|demo/demo1||This illustrates a simple clients / server application showing how client
components could be connected by a receptacle to a facet provided by a server
|demo/demo2||This illustrates a simple producer / consumers application showing how a
producer component could push events by an event source to a set of event
|demo/demo3||This illustrates a simple clients / server-producer / consumers application
showing how a component can simultaneously be a server providing a facet and
a producer with an event source.
|demo/dinner||This illustrates the philosopher's dinner with Philosopher, Fork and Observer
components. Philosophers try to acquire both forks to eat and publish events
with their state to observer components. This demo was used at
(Japan) and Orlando (USA) OMG Meetings to show interoperability between CCM
|demo/chat||This illustrates a chat demonstration showing how client components use a facet
provided by a server component to display text and how the server component could
push events (all entered texts) to all clients.
|demo/filetransfer||This illustrates a file transfer application based on three component types.
Program components manage and send images to Channel components. Channel components
receive images from Programs and send these images to TV components. The TV components
are deployed on user's device and images are displayed and/or stored.
Each demonstration (except for the filetransfer demonstration) contains both monolithic based
(deprecated) and CIDL based component implementations.
Compiling a demonstration
To compile a demonstration, do the next steps:
- Go to the associated directory.
Execute the following command on Unix systems:
or on Windows systems:
This compiles both the monolithic based (deprecated) and CIDL based
component implementations of each demonstration.
Starting a demonstration
To start the demonstration, execute one of the following scripts:
| The demonstration deployment is done by a Java program.
By default, this deploys the CIDL based component implementations.
| The demonstration deployment is done
by a Java program and uses a transactional service.
| The demonstration deployment is done
by a Java program and uses a trace service.
|The demonstration deployment is done by the
and uses the CCM XML files from the META-INF/ directory.
|The demonstration deployment is done by a Java program
and uses the monolithic based component implementations (deprecated).
|The demonstration deployment is done by a Java IDLScript engine.
|The demonstration deployment is done by a CorbaScript engine.
bin/start_java --monolithic is deprecated but the
Component Implementation Framework allows you to implement components both
with the monolithic and segmented strategies.
Note that for the filetransfer demonstration, the demonstration deployment is always done by the
ccm_deploy tool. Just type
bin/start_java to start it (
--xml is implicit and not required here).
Note also that for the hello demonstration, you have also to do:
bin/install_java --ots (required
bin/start_java --ots) or
Then, have fun with the demonstrations...
Stopping a demonstration
To stop the demonstration, execute respectively:
Note that to execute the demonstrations from Java IDLscript or CorbaScript,
it is required that these scripting engines are accessible through the
PATH environment variable.