blob: f35d6a77fe8f05160b48304f104a72e367991786 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<!-- $Id$ -->
<html> <head>
<title>CIAO - Component-Integrated ACE ORB</title>
</head>
<body>
<h1>CIAO - Component-Integrated ACE ORB</h1>
<h2>Introduction</h2>
CIAO is TAO's implementation of <a
href="http://cgi.omg.org/cgi-bin/doc?formal/02-06-65"> CORBA Component
Model (CCM)</a> specially optimized for distributed real-time embedded
(DRE) systems.
This page contains links to other documents and resources for building
and using CIAO.
<h2>The CIAO Project</h2>
<ul>
<li>The main
<a href="http://www.cs.wustl.edu/~schmidt/CIAO.html">
CIAO project page</a>.<p>
<li>CIAO <A HREF="../CIAO-INSTALL.html">Installation instructions</a>.<p>
<li>Project <a href="releasenotes/index.html">Status (aka. release
notes.)</a><p>
<li>This <a href="new_components.html">page on implementing new
component</a> explains all the user-defined and tool-generated
files when implementing a component.<p>
<li>A <a href="TODO.html">list of things</a> that we know need to be
done. :) <p>
<li>The <a href="ConfigValues.html">Configuration Name/Value
lists</a> lists all the configuration values that CIAO will pass
into vaious CCM mechanisms. The information shown in this page
is not visible to CIAO end-users, which include modeling tool
developers. The information that matters for most users is how
these configurations are represented in various XML
descriptors and CIDL specifications.<p>
<li>CIAO uses some <a href="EnvVars.html">environment variables</a>
to manage the internal behaviors.
</ul>
<h2>CCM-defined Interface Diagrams</h2>
Here is a set of UML diagrams that we use to figure out the
relationship among all the different interfaces in CCM. You can
browse the related part from the following list:
<UL>
<li><a href="imgs/component-basic.png"> Basic component interfaces
</a></li>
<li><a href="imgs/home-config.png"> Home and configuration interfaces
</a></li>
<li><a href="imgs/basic-container.png"> Basic container interfaces
</a></li>
<li><a href="imgs/extended-container.png"> Extended container
interfaces </a></li>
<li><a href="imgs/deployment.png"> Deployment and installation
interfaces </a></li>
</UL>
All these diagrams are generating from the <a href="imgs/CCM.vsd">CCM.vsd
Visio file</a> (The same file in Visio V.5 format is <a href="imgs/CCM-v5.vsd">here</a>.)
<h2>CIAO part-by-part</h2>
Here is a list of the major elements of CIAO that a user should be aware of.
<UL>
<li><a href="http://www.dre.vanderbilt.edu/Doxygen/Current/html/tao/ciao/tools/daemon/index.html"><strong>Daemon:</strong></a> A CIAO Daemon is the per-host Daemon process which is used to create/spawn the ComponentServer.</li><P>
<li><a href="http://www.dre.vanderbilt.edu/Doxygen/Current/html/tao/ciao/ciao/index.html"><strong>ComponentServer:</strong></a> A ComponentServer is the center part of CIAO. It's responsible for component/home creation.</li><P>
<li><a href="http://www.dre.vanderbilt.edu/Doxygen/Current/html/tao/ciao/tools/assembly_deployer/index.html"><strong>AssemblyDeployer:</strong></a> An AssemblyDeployer is responsible for starting the Assembly process.</li><P>
<li><a href="http://www.dre.vanderbilt.edu/Doxygen/Current/html/tao/ciao/tools/assembly_deployer/index.html"><strong>AssemblyManager:</strong></a> An AssemblyManager is the center part to do the Assembly work.</li><P>
<li><a href="static_ciao_index.html"><strong>Static Configurator:</strong> </a>The CIAO
Static Configurator acts as a pre-processor that parses the XML descriptor
files into intermediate representation that gets linked into the main application.
This reduces the initialization time for an application that is statically
built. It is mainly aimed at RTOS' like VxWorks that lacks facilities like
shared objects or DLL.</li>
</UL>
<h2>CIAO CCM tutorials</h2>
There are several tutorials to help you understand CIAO and CCM:
<UL>
<LI> <A
HREF="http://www.cs.wustl.edu/~schmidt/OMG-CCM-Tutorial.ppt">Tutorial
on the CORBA Component Model (CCM)</A>. This tutorial presents an overview of the CORBA Component Model (CCM),
describing its key features and illustrating how to write CCM
applications in C++. <P>
<li><a
href="./tutorial/Hello"><code>$(CIAO_ROOT)/docs/tutorial/Hello.</code></a>
This example shows the low level infomation about CIAO
Component/Component Home creation and deletion.</li><P>
<li><a
href="../examples/Hello"><code>$(CIAO_ROOT)/examples/Hello.</code></a>
This example illustrates how to build a CIAO based application <a
href="../examples/Hello/step-by-step.html">step-by-step</a>. There is
also a detailed documentation explaining this example avalable in both
<a href="http://www.dre.vanderbilt.edu/~lu/CCM/CCM_Hello_example.PDF">
PDF</a> and <a
href="http://www.dre.vanderbilt.edu/~lu/CCM/CCM_Hello_example.ppt">
PowerPoint</a> format.</li>
</UL>
<!--#include virtual="/~nanbor/signature.html" -->
<!-- <hr> -->
<!-- <\!-- hhmts start -\-> -->
<!-- Last modified: Mon Nov 04 07:55:22 Central Standard Time 2002 -->
<!-- <\!-- hhmts end -\-> -->
<!-- <address>Nanbor Wang <nanbor@cs.wustl.edu></address> -->
</body> </html>
<!-- LocalWords: CCM UML vsd Visio
-->
|
