summaryrefslogtreecommitdiff
path: root/TAO/CIAO/docs/tutorials/CoSMIC/04.html
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/CIAO/docs/tutorials/CoSMIC/04.html')
-rw-r--r--TAO/CIAO/docs/tutorials/CoSMIC/04.html57
1 files changed, 0 insertions, 57 deletions
diff --git a/TAO/CIAO/docs/tutorials/CoSMIC/04.html b/TAO/CIAO/docs/tutorials/CoSMIC/04.html
deleted file mode 100644
index 27a5344af23..00000000000
--- a/TAO/CIAO/docs/tutorials/CoSMIC/04.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
-<html>
-<head>
- <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;
-</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 &quot;destination&quot; and the corresponding
-IOR for the CIAO_Daemon.</p>
-<ul type="square">
- <li><em>NOTE</em>: As one can see, we use the &quot;Stock.dat&quot; 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>