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
131
132
133
134
135
136
137
138
139
140
|
This directory contains various XML descriptors and configuration
files required to compose the HUDisplay application in a variety of
different ways. Let's go over a few important files first:
test.dat:
---------
This file describes the deployment daemons CIAO's Assembly_Manager
will contact to instantiate ComponentServer's, home's, and component
instances. Each line specify the name of a installation
"destination" (I used this to specify <processcollocation>
destination in various *.cad files) and the corresponding IOR for
the CIAO_Daemon. The first entry is the "default" destination the
deployment framework will use.
For example, test.dat now contains:
Default corbaloc:iiop:localhost:10000/ServerActivator
Remote corbaloc:iiop:localhost:12000/ServerActivator
You can copy and modify the copy to deploy the components in various
different locations to let the application truely "distributed".
For example, changing the remote ServerActivator to:
corbaloc:iiop:deuce.doc.wustl.edu:13000/ServerActivator
Remember to start up the Assembly_Manager in Step 2 using the
revised "test.dat" you created, and start up the CIAO_Daemon's in
Step 1 according to the specification.
*.cad:
------
These files specify how an application should be composed. The
specification includes, where to install a component, what
implementation to use, and how to connect components together.
Currently, we have:
BasicSP.cad: Plain vanilla assembly descriptor. This file install
all components using the "Default" (the first daemon)
in 'test.dat. You can see the application output
from the default daemon shell.
Unfortunately, there's no run_test.pl for starting and running these
example configurations/assemblies as these daemons/managers programs
are still under development. You will need several shell windows for
them. All the following step should be run from this subdirectory
($CIAO_ROOT/examples/OEP/Display/descriptors/). Here are the
steps to demonstrate the examples:
Step 1:
=======
You need to start up the CIAO daemon as specified in the
deployment configuration file 'test.dat' (Notice the endpoint
specification.) If you run more than one daemon (each with its
own host port), I recommend running each CIAO_Daemon in its own
shell window so you can tell where a component in the example
application is running. Here are some hints on how to start the
daemon:
${CIAO_ROOT}/tools/Daemon/CIAO_Daemon -ORBEndpoint iiop://localhost:10000 -n ../../../../tools/ComponentServer/ComponentServer
and on Windows
%CIAO_ROOT%/tools/Daemon/CIAO_Daemon -ORBEndpoint iiop://localhost:10000 -n ../../../../tools/ComponentServer/ComponentServer
Note that the environment variable CIAO_ROOT must be set
(to TAO_ROOT/CIAO).
Step 2:
=======
Next, you will need to start up the Assembly_Manager which actually
does the assembly work. This should also be started in a separate
shell window.
${CIAO_ROOT}/tools/Assembly_Deployer/Assembly_Manager -o ior -c test.dat
or
%CIAO_ROOT%/tools/Assembly_Deployer/Assembly_Manager -o ior -c test.dat
Step 3:
=======
You then need to instruct the Assembly_Manager to deploy a specific
component assembly descriptor. For example:
${CIAO_ROOT}/tools/Assembly_Deployer/Assembly_Deployer -k file://ior -a BasicSP.cad -o IDfile
or
%CIAO_ROOT%/tools/Assembly_Deployer/Assembly_Deployer -k file://ior -a BasicSP.cad -o IDfile
Step 4:
=======
All the .cad files instruct the Assembly_Manager to write the IOR of
the RateGen component to a file called "rategen.ior" in this
directory. You will then need to use a controller program in a
separate shell window to switch on/off the Rate Generator. Cont
Execute the controller with:
..\EC\controller -o # To switch on the EC component
See its source to check what options are available to start up the
controller. (Hints: you can control the rate (hertz) of the Rate
Generator component.)
Once the controller is running, check out the Daemon window for
text-based BMClosedED and BMDisplay components. Once you are
happy with it, you can stop the EC component by executing the
controller as:
../EC/controller -f # To switch off the EC component
Repeat this step again to instruct the EC component to start
generating events.
Step 5:
=======
Once you are done with the test. Use the following command to
tear_down the application, kill all ComponentServer's, and terminate
both the Assembly_Deployer and Assembly_Manager process.
${CIAO_ROOT}/tools/Assembly_Deployer/Assembly_Deployer -k file://ior -d IDfile
or
%CIAO_ROOT%/tools/Assembly_Deployer/Assembly_Deployer -k file://ior -d IDfile
Repeat Step 2-5 using different configurations and assembly
descriptors.
Step 6:
=======
Terminate CIAO_Daemon (either using ^C or DaemonController.)
|
