Getting Started

In the Browser of the generated model, the + PredefinedTypes folder contains a bunch of atomic + datatype elements that will be referenced by other modeling parts + later. You don't have to worry about them for now. The models in + InterfaceDefinitions folder are the PICML + representations ofthe IDL files you just imported. Double-click + to open Broker, it will show you a white, document-like + entity which represents a <<FileRef>> instance and a + yellow box-shaped entity representing a <<Package>> + instance. Their equivalent representations in IDL files are + "#include" and "module" respectively. Figure 3 gives you a clear + view of GME representation of all the 3 idl files created. We + will cover the other folders in the next section.

Building Stock Quoter system in PICML
-

-Figure 4.
-
-

ComponentImplementation
-

-This folder contains models that describes the implementations of -component interfaces. In the Quoter example, we will have two -monolithic component implementations; respectively StockDistributorImplementation StockBrokerImplementation, and an -assembly -component implementation: StockQuoter, -which is an assembly of StockDistributorImplementation -and StockBrokerImplementaion. -idl_to_picml has created the -monolithic component implementations for us, as shown in figure 5 for -example, but we have to put them together by hand in order to construct -a Quoter system.
-
-
-

-Figure 5
-

-Assembly component is a recursive concept. It provides a boundary for -the composition of monolithic components.Assembly component does not -provide real implementation for any interface, i.e., it is a virtual -component. Modeling an assembly component is different from modeling a -monolithic component: you don't need to worry about the -artifacts.Instead, you need to create connections between monolithic -components so that they can talk via ports. Let's try to assemble the StockQuoter.
-

Right click folder ComponentImplementations, -choose Insert -Model->ComponentImplementationContainer, rename it -as "StockQuoterImplementation" in the Attribute Panel. Double click to -open it.
-
From the Part Browser, drag a <<ComponentAssembly>> -to the modeling window, -name it "StockQuoter". Double click to open it.
-
Now we will create two instances for interfaces StockBroker and StockDistributor. To do -that, expand the folder InterfaceDefinitions, -then expand the InterfaceDefinitions/Broker, then InterfaceDefinitions/Broker/Stock until the interface -definition of StockBroker shows. -While expanding the tree, always keep -the "StockQuoter" <<ComponentAssembly>> window open. -Then drag MyQuoter/InterfaceDefinitions/Broker/Stock/StockBroker -in the -browser to the "StockQuoter" <<ComponentAssembly>> window -while pressing ALT key. Repeat the -same steps for MyQuoter/InterfaceDefinitions/Distributor/Stock/StockDistributor, -and you will see two instances of component interfaces have been -created as shown in Figure 6 (the black line in the figure only -indicates .mapping)
-

-
-

-
-Figure 6 -
-

Create an <<PublishConnector>>.
-
Now assemble the components together according to Figure 1(make sure you change to connect -mode ) and -the resulting assembly model should look like Figure 7. Note that to -create connections between -StockDistributor.notify_out and StockBroker.notify_in, you will need -the intermediate connector <<PublishConnector>>.
-

-
-Figure 7
-

- -

ComponentPackage
-

-This folder contains deployable component packages. Every instance in -an assembly should have a corresponding monolithic implementation and -packaged in a ComponentPackagebe To create a package for StockBroker.instance
-

Right click folder ComponentPackages -, -insert a <<PackageContainer>>, name it "Broker"; Double -click to open it.
-
From the PartBrowser, add the following:
-
- a <<ComponentPackage>> named "Broker";
- a <<ComponentImplementationReference>> named -"Broker";
- a <<ComponentRef>> named "Broker";
-
Refer the <<ComponentImplementationReference>> Broker -to MyQuoter/ComponentImplementations/StockBrokerImplementation/StockBrokerMonolithicImpl. -Refer the -<<ComponentRef>> Broker to MyQuoter/InterfaceDefinitions/Broker/Stock/StockBroker. -To do a refering in GME, simply drage the tree node in the Browser -"into" the reference model. For example, you should drage the tree node -MyQuoter/ComponentImplementations/StockBrokerImplementation/StockBrokerMonolithicImpl -into <<ComponentImplementationReference>> Broker. Check -GME manual(tutorials) for more information.
Switch to Connect Mode and create two connections according to -the following relationship.
-
- <<ComponentImplementationReference>> Broker -implements <<ComponentPackage>> Broker;
- <<ComponentPackage>> Broker realizes -<<ComponentRef>> Broker.
-
-
- The model you built should resemble Figure 8.
-
-

-
-Figure 8
-
-
Now create a -ComponentPackage/StockDistributor following the same steps.
-
-

We will also need to create a package -for the assembly component -StockQuoter. Remember assembly component is a virtual component, it -does not "realize" a certain interface, so different from the Broker -and Distributor packages, the -StockQuoter does not need a <<ComponentRef>>. To create -this model:

1. Insert a <<ComponentPackage>> named "StockQuoter"
-

2. Add a -<<ComponentImplementationReference>> named "StockQuoter", -refer it to MyQuoter/ComponentImplementations/StockQuoter/StockQuoter

3. Switch to connect mode and connect -<<ComponentImplementationReference>> StockQuoter with -<<ComponentPackage>> StockQuoter, as in Figure 9.
-

-
-

-
-Figure 9
-
-

PackageConfiguration
-

-This folder contains just one model capturing specific configuration of -Component packages.
-

In the folder PackageConfiguration, -and create a -<<PackageConfigurationContainer>>, name it "Default", click -to -open it.
-
Add a <<PackageConfiguration>> named "default" and a -<<ComponentPackageReference>>, name it "StockQuoter", -connect "Default" to "StockQuoter"
-
Refer <<ComponentPackageReference>> StockQuoter to -<<ComponentPackage>> MyQuoter/ComponentPackage/StockQuoter/StockQuoter - -(Not <<ComponentImplementationReference>>MyQuoter/ComponentPackage/StockQuoter/StockQuoter!) -

-
-

- -

ToplevelPackage
-

-This folder contains one model capturing information about the -top-level element that will be fed to -the application.
-

In the folder ToplevelPackage, -and create a -<<ToplevelPackageContainer>>, name it "Default", double -click to open it.
-
Add a <<ToplevelPackage>> named "ToplevelPackage" -and a <<PackageConfigurationReference>>, name it "Default", -connect "ToplevelPackage" to "Default"
-
Refer "Default" to MyQuoter/PackageConfiguration/Default/Default
-

-
-

- -

Targets
-

-This folder contains domain-specific models capturing information about -the target -environment in which component-based application will be deployed. In -this Quoter example, we can either deploy the two components into ONE -host, or into TWO different host. We will deploy the Quoter into two -different host.
-

In the folder Targets, -insert a new <<Domain>> named "Domain"; double click to -open it.
-
From the Part Browser, add two <<Node>> named -"Broker" and "Distributor" respectively.
-

-
-Now we are ready to deploy our Components to the actual physical -environment.
-

- -

DeploymentPlan
-

-This folder contains a plan model that captures information about the -assignment of component to nodes.
-

In the folder DeploymentPlan, -insert a model -<<DeploymentPlan>>; name it "Plan", click to open it
-
From the PartBrowser, add the following:
-
- Two <<CollocationGroup>>
- Two <<NodeReference>> named "Node_Broker" and -"Node_Distributor" respectively, refering to MyQuoter/Targets/Domain/Broker -and MyQuoter/Targets/Domain/Distributor respectively
- Two <<ComponentRef>> named "StockBroker" and -"StockDistributor" respectively, refering to MyQuoter/ComponentImplementations/StockQuoterImplementation/StockQuoter/StockBroker -and MyQuoter/ComponentImplementations/StockQuoterImplementation/StockQuoter/StockDistributor -respectively. Note that the <<ComponentRef>> in -DeploymentPlan is not refering to the interface, but rather, the actual -instance of the implementation.
-
Switch to Connect Mode, connect one -<<CollocationGroup>> to <<NodeReference>> Node_Broker, -connect another -<<CollocationGroup>> to <<NodeReference>> Node_Distributor. -Now the model looks like the following.
-
-

-
-Figure 10.
-
-
-
Now we need to associate <<ComponentRef>> -StockBroker to the -<<CollocationGroup>> running on the -<<NodeReference>> Broker, and <<ComponentRef>> -StockDistributor to the <<CollocationGroup>> running on the -<<NodeReference>> Distributor. To do that, switch the Edit -Mode Bar to Set Mode (), and move -the cursor to the <<CollocationGroup>> running on -<<NodeReference>> Distributor, right-click on it. You will -find the cursor is changed to set mode cursor, and only the -<<CollocationGroup>> you clicked in is highlighted, as -shown -in Figure 11.
-
-

-
-Figure 11
-
-

Now move your cursor to -<<ComponentRef>> StockDistributor, and left-click it, -so that it looks like Figure 12.
-

-
-

-
-Figure 12
-
-

This operation -associates StockDistributor component to the -<<CollocationGroup>> running on Distributor node. -To do the same with -Broker, just right-click on another <<CollocationGroup>>, -and left-click on StockBroker <<CollocationGroup>> which is -highlighted.
-
-

-
-Up to this point, we are basiclly done with the modeling part. Before -we generate anything from this model though, please DO remember to check the -constraints of the model as we mentioned earlier.
-
-After we are done with the modeling, the flattened_deploymentplan -interpreter that comes along with PICML will help us to generate a -flattened_deploymentplan.cdp file. Please make sure you generate this -file to MyQuoter/descriptors. -

-
-
-Ming Xiong
-

- -Last modified: -

Building Stock Quoter system in PICML

This section describes modeling the Quoter application using PICML. If you have trouble producing a functioning model from this tutorial, please see the, pre-built Quoter model which is provided for your reference. This model contains all elements created as part of this tutorial.

The complete PICML Quoter model consists of modeling elements distributed across various folders. If you used idl_to_picml to generate the initial model, you will see that it has created all these folders and some of the tedious boilerplate modeling for us. The rest of the section will explain the purpose of each folder as well as the modeling entities contained in these folders. We will also show how to model some of the folders that have to be done by hand.

ImplementationArtifacts

This folder contains implementation artifacts associated with components. idl_to_picml has created these artifacts for us, with their dependency relationships correctly captured. Figure 4 shows the Implementation Artifacts for Broker.

ComponentImplementation

This folder contains models that describe the implementations of component interfaces. In the Quoter example, we will have two monolithic component implementations - named StockDistributorImplementation and StockBrokerImplementation - and an assembly component implementation named StockQuoter, which is an assembly of StockDistributorImplementation and StockBrokerImplementaion. idl_to_picml has created the monolithic component implementations for us, as shown in figure 5 for example, but we have to specify the connections between them in order to construct a Quoter system.

Assembly components provide a boundary for the composition of monolithic components and even other assemblies. Assembly components do not provide actual implementations for their interface, it is a virtual component that delegates its ports and attributes to one or more of the entities it contains. There are slight differences between modeling an assembly and modeling a monolithic component. Since the assembly is a virtual component, it is not necessary to model a MonolithicImplementation. Instead, instances of other components are placed within the assembly and connected. Let's try to assemble the StockQuoter.

ComponentPackage

PackageConfiguration

ToplevelPackage

Targets

DeploymentPlan

Now move your cursor to <<ComponentRef>> StockDistributor, and left-click it, so that it looks like Figure 12.

This operation associates StockDistributor component to the <<CollocationGroup>> running on Distributor node. To do the same with Broker, just right-click on another <<CollocationGroup>>, and left-click on StockBroker <<CollocationGroup>> which is highlighted.
+

Up to this point, we are basically done with the modeling part. Before we generate anything from this model though, please DO remember to check the constraints of the model as we mentioned earlier.

After we are done with the modeling, the flattened_deploymentplan interpreter that comes along with PICML will help us to generate a flattened_deploymentplan.cdp file. Please make sure you generate this file to MyQuoter/descriptors.

Implementing Quoter Components with DAnCE
-

Implementing Quoter Components with DAnCE

Running the application

The Stock.dat 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.

Running the application

The Stock.dat 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.

Building a Stock Quoter with CoSMIC and DAnCE - A Tutorial
-

This tutorial provides a step-by-step lesson on developing -component-based distributed applications using CoSMIC modeling -toolkit and CIAO -DAnCE framework. The example application used in this tutorial is a -Stock Quoter that consists of two components; the StockDistributor -and the StockBroker. The StockDistributor -notifies one or more stock brokers whenever a stock price changes. Upon -receiving the notification, the StockBroker -fetches information about a particular stock from the StockDistributor. The figure bellow -shows the application diagram. -This Stock Quoter application -is based on a series of CORBA -component model columns written by Doug Schmidt and Steve Vinoski for C/C++ Users Journal and has consistently -been -used as an example for TAO.
-

This tutorial will show you how to use generic modeling techniques CoSMIC to assist the -development process of CIAO applications. All the necessary steps to -build a component-based application model via CoSMIC -toolkit are documented here. -

Getting Started
-

Getting Started

Building Stock Quoter system in PICML
-

Table of Contents

ImplementationArtifacts
-

ComponentImplementation
-

ComponentPackage
-

PackageConfiguration
-

ToplevelPackage
-

Targets
-

DeploymentPlan
-

Building Stock Quoter system in PICML

Table of Contents

ImplementationArtifacts

ComponentImplementation

ComponentPackage

PackageConfiguration

ToplevelPackage

Targets

DeploymentPlan

Implementing Quoter Components with DAnCE
-

Implementing Quoter Components with DAnCE

Running the application

Running the application

Building a Stock Quoter with CoSMIC and DAnCE - A Tutorial
-

Building a Stock Quoter with CoSMIC and DAnCE - A + Tutorial

Getting Started -

Getting Started

Building Stock Quoter system in PICML -

Table of Contents

ImplementationArtifacts -

ComponentImplementation -

ComponentPackage -

PackageConfiguration -

ToplevelPackage -

Targets -

DeploymentPlan -

Building Stock Quoter system in PICML

Table of Contents

ImplementationArtifacts

ComponentImplementation

ComponentPackage

PackageConfiguration

ToplevelPackage

Targets

DeploymentPlan

Implementing Quoter Components with DAnCE -

Implementing Quoter Components with DAnCE

Running the application

Running the application

Building a Stock Quoter with CoSMIC and DAnCE - A Tutorial -

Building a Stock Quoter with CoSMIC and DAnCE - A + Tutorial

Getting Started
-

Building Stock Quoter system in PICML
-

ImplementationArtifacts
-

ComponentImplementation
-

ComponentPackage
-

PackageConfiguration
-

ToplevelPackage
-

Targets
-

DeploymentPlan
-

Implementing Quoter Components with DAnCE
-

Building a Stock Quoter with CoSMIC and DAnCE - A Tutorial
-