blob: 036f43ebf27affd6455efc3a80eb71a682da435b (
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
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
Store Tutorial
==============
This tutorial that shows how to use SCA and Tuscany to build multiple
variations of an online Store application. The variations demostrate the
evolution of the Store as it goes through the following stages:
1 - Initial online fruit store
2 - Fruit store merges with vegetable store to form the fruit and vegetable store
3 - The fruit and vegetable store move to using a database for storing the cart
4 - The fruit and vegetable store acts as a supplier to other online stores
5 - The fruit and vegetable store ships their software solution to another geography
For diagrams of the scenarios covered here, please refer to Tutorial.pdf
Running The Tutorial Application
--------------------------------
Start the SCA Domain Manager on linux:
cd domain
java -jar ../../../modules/tuscany-node-launcher-1.5.jar domain
Start the SCA Domain Manager on windows:
cd domain
java -jar ..\..\..\modules\tuscany-node-launcher-1.5.jar domain
Access the SCA Domain Manager application by pointing your Web browser at:
http://localhost:9990/ui/cloud/
This shows you all of the Tuscany nodes that are configured to run
in the store tutorial domain. If you are interested, the configuration
is stored on disc in the store/domain directory but for now let's just
start some nodes and see what happens.
The different nodes you see are used to start different scenarios in
the tutorial. Select the node you want to start (e.g StoreNode), then click the
Start button. You may need to give the nodes a little time to start up. Check the
console where you lauched the domain manager application and you will see the
following message when nodes have started.
INFO: INFO: Press 'q' to quit, 'r' to restart.
Remember to shut down the nodes before you exit the domain manager application.
The following describes the nodes you have to start for each scenario and some
usful links to explore once the node has started.
1 - Initial online fruit store
----------------------------
Start
StoreNode
The store itself can be found at
http://localhost:8100/ui/
If you want to look at how Tuscany provides remote bindings you can take
a look at the service description that Tuscany created automatically
for the store catalog service which is exposed over a JSONRPC binding
Point your browser at:
http://l3localhost:8100/StoreCatalog?smd
The service is configured in the SCA composite file in the following way:
<component name="StoreCatalog">
<implementation.java class="services.FruitsCatalogImpl"/>
<property name="currencyCode">USD</property>
<service name="Catalog">
<t:binding.jsonrpc/>
</service>
<reference name="currencyConverter" target="StoreCurrencyConverter"/>
</component>
Note the inclusion of <t:binding.jsonrpc/>. This is all that is required to
make this service available over JSONRPC. If you want to expose the service
over web services simply add <binding.ws/> instead of (or as well as) <t:binding.jsonrpc/>.
2 - Fruit store merges with vegetable store to form the fruit and vegetable store
---------------------------------------------------------------------------------
Start
CatalogsNode
StoreMergerNode
The store itself can be found at
http://localhost:8101/ui/
Now you see that there are more items in the catalog as the fruit and
vegetable catalogs are both providing content. The vegetable catalog
that was introduced during the merger is contacted using web services.
If you want to see the WSDL for the vegetable catalog point your browser
at
http://l3aw203:8200/VegetablesCatalogWebService?wsdl
The vegetable catalog service is configured in an SCA composite file
in the following way:
<component name="VegetablesCatalogWebService">
<implementation.java class="services.VegetablesCatalogImpl"/>
<service name="Catalog">
<binding.ws/>
</service>
</component>
3 - The fruit and vegetable store move to using a database to storing the cart
------------------------------------------------------------------------------
Start
StoreDBNode
The store itself can be found at
http://l3aw203:8102/ui/
This looks the same as the scenario 2 store but this time a database is used
for storing items put into the shopping cart. When you add items you
will see messages on the console indicating that items are added to the
database. For example.
INFO: insert into Cart values ('cart-8c8bcc43-5036-4e9a-b282-0dd3d00d350c', 'Apple', '$2.99')
This scenario shows how you change the implementation of a service without
changing any of the configuration of the rest of the application
4 - The fruit and vegetable store acts as a supplier to other online stores
---------------------------------------------------------------------------
Start
StoreSupplierNode
The store itself can be found at
http://localhost:8103/ui/
Again this is the same basic store as in scenario 3. However this time the
shopping cart and catalog serivces have been given additional remote bindings so that
the services can be accessed by others. For example, take a look at the WSDL
description of the shopping cart service that is now available at:
http://l3aw203:8333/ShoppinCartTotalWebService?wsdl
This WSDL is available as the shopping cart total service is now configured with a web services
binding in the following way:
<component name="StoreSupplierShoppingCart">
<implementation.java class="services.db.ShoppingCartTableImpl"/>
<property name="database">../store-supplier/target/cart-db</property>
<service name="Cart">
<t:binding.atom uri="/ShoppingCart/Cart"/>
</service>
<service name="Total">
<t:binding.jsonrpc/>
<binding.ws uri="/ShoppinCartTotalWebService"/>
</service>
</component>
If you want to actually exercise these services from a standalone application
you can run up the StoreClientNode using the provided launcher
store/store-client/launch/LaunchStoreClientNode
5 - The fruit and vegetable store ships their software solution to another geography
------------------------------------------------------------------------------------
Start
CurrencyNode
StoreEUNode
The store itself can be found at
http://localhost:8104/ui/
Notice now that the prices are quoted in Euros and the language is French. This was
achieved by editing the store.html file to change the language and presentation to
be appropriate for Europe. The curreny was changed by reconfiguring the catalog
component to use EUR instead of USD.
<component name="StoreEUCatalog">
<implementation.java class="services.merger.MergedCatalogImpl"/>
<property name="currencyCode">EUR</property>
...
</component>
For more detailed information about how to get started with Apache Tuscany
see our online guides at:
http://tuscany.apache.org/sca-java-getting-started-guides-1x.html
|
