summaryrefslogtreecommitdiff
path: root/modules/CIAO/docs/tutorials/CoSMIC/04.html
diff options
context:
space:
mode:
Diffstat (limited to 'modules/CIAO/docs/tutorials/CoSMIC/04.html')
-rw-r--r--modules/CIAO/docs/tutorials/CoSMIC/04.html77
1 files changed, 77 insertions, 0 deletions
diff --git a/modules/CIAO/docs/tutorials/CoSMIC/04.html b/modules/CIAO/docs/tutorials/CoSMIC/04.html
new file mode 100644
index 00000000000..dce2fb1364c
--- /dev/null
+++ b/modules/CIAO/docs/tutorials/CoSMIC/04.html
@@ -0,0 +1,77 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for Mac OS X (vers 1st December 2004), see www.w3.org" />
+
+ <title>Building a Stock Quoter with TAO - A Tutorial</title>
+ <!-- $Id$ -->
+</head>
+
+<body style=
+"color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" link=
+"#000FFF" vlink="#FF0F0F">
+ <h3>Running the application<br /></h3>Now that we have all the
+ components and driver programs successfully built, along with the
+ flattened_deploymentplan generated by PICML, we will be able to
+ run our application<br />
+ <br />
+ From different command prompts in
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/descriptors/</code>
+ directory:
+
+ <ul>
+ <li>Start NodeManagers (NodeDameon) by running
+ <code>runNodeDaemon.pl</code></li>
+
+ <li>Start the execution manager
+ <code>%CIAO_ROOT%/DAnCE/ExecutionManager/Execution_Manager -o
+ ior -i Stock.dat</code>&nbsp;</li>
+ </ul>
+
+ <p>The <code>Stock.dat</code> file describes the deployment
+ daemons CIAO's Execution_Manager will contact to instantiate
+ ComponentServer's, home's, and component instances. Each line
+ specify the name of a installation "destination" and the
+ corresponding IOR for the CIAO_Daemon.</p>
+
+ <ul type="square">
+ <li><em>NOTE</em>: As one can see, we use the "Stock.dat" file
+ to instruct the Execution_Manager how to find the endpoint of
+ each individual NodeManager (i.e., Node Daemon) where
+ component(s) will be deployed, so this is non-standard. We plan
+ to use Naming Service to do this in the future.</li>
+ </ul>
+
+ <ul>
+ <li>Start the plan_launcher by running
+ <code>%CIAO_ROOT%/DAnCE/Plan_Launcher/Plan_Launcher -p
+ flattened_deploymentplan.cdp -k file://ior</code></li>
+
+ <li>By now the components should be successfully deployed. You
+ may run the driver program to start the application. e.g. you
+ can try the following<br /></li>
+ </ul>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/Distributor/Distributor.exe
+ -o</code><br />
+ <br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/Broker/Broker.exe
+ -s MSFT</code><br />
+ <br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/Broker/Broker.exe
+ -s IBM</code><br />
+ <br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/Broker/Broker.exe
+ -u MSFT</code><br />
+ <br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <code>%CIAO_ROOT%/docs/tutorials/Quoter/Simple/Distributor/Distributor.exe
+ -f</code><br />
+ <br />
+</body>
+</html>