OpenCCM Demonstrations

The following demonstrations are available:

Demonstration	Description
`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 component.
`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 consumer sinks.
`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 2002 Yokohama (Japan) and Orlando (USA) OMG Meetings to show interoperability between CCM implementations.
`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:
```
$ build.sh
```
or on Windows systems:
```
$ build.bat
```

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:

Script	Description
`bin/start_java`	The demonstration deployment is done by a Java program. By default, this deploys the CIDL based component implementations.
`bin/start_java --ots`	The demonstration deployment is done by a Java program and uses a transactional service.
`bin/start_java --trace`	The demonstration deployment is done by a Java program and uses a trace service.
`bin/start_java --trader`	Starts the CosTrading service and deploys the demonstration.
`bin/start_java --xml`	The demonstration deployment is done by the `ccm_deploy` tool and uses the CCM XML files from the META-INF/ directory.
`bin/start_java --xml --trader`	The demonstration deployment is done by the `ccm_deploy` tool and uses the CCM XML files from the META-INF/ directory. Moreover, the CosTrading service will be started and used to register components and homes.
`bin/start_java --monolithic`	The demonstration deployment is done by a Java program and uses the monolithic based component implementations (deprecated).
`bin/start_jish`	The demonstration deployment is done by a Java IDLscript engine.
`bin/start_cssh`	The demonstration deployment is done by a CorbaScript engine.

Warning: bin/start_java --monolithic is deprecated but the Component Implementation Framework allows you to implement components both with the monolithic and segmented strategies.

Let's 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).

Let's note also that for the hello demonstration, you have also to do:

bin/install_java or

bin/install_java --ots (required bin/start_java --ots) or

bin/install_cssh or

bin/install_jish
bin/run_java or

bin/run_cssh or

bin/run_jish

Then, have fun with the demonstrations...

Let's 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.

Stopping a Demonstration

To stop the demonstration, execute respectively:

bin/stop_java,
bin/stop_jish, or
bin/stop_cssh.

Table of Contents

OpenCCM Demonstrations

Compiling a Demonstration

Starting a Demonstration

Stopping a Demonstration