データ流通プラットフォームの使い方...④WireCloud/home の画面が表示されればログイン 完了です ③初回のログイン時のみ、WireCloudへのアクセスを
WireCloud, WStore and WMarket
-
Upload
aitor-magan-garcia -
Category
Presentations & Public Speaking
-
view
262 -
download
0
Transcript of WireCloud, WStore and WMarket
WireCloud, WStore & WMarket Aitor Magán (UPM)[email protected] @aitormagan
Agenda
1. WireCloud1. What is WireCloud?2. What can I do with WireCloud?3. Using WireCloud4. Working with Mashups5. Developing with WireCloud
2. WStore1. What is WStore?2. Data Market3. Using WStore
3. WMarket1. What is WMarket?2. Using WMarket
2
WHAT IS WIRECLOUD?Data/Applications Visualization and Mashup
What is WireCloud?
Widget
Mashupdat
a
Backendservice Backend
service
Backendserviceope
rator
wiring
Object StorageAPI
NGSI API
ContextBroker
piping
5
WHAT CAN I DO WITH WIRECLOUD?
Data/Applications Visualization and Mashup
Perspectives
• From the developer perspective:– Use web technologies for easily developing mashable web
components (widgets)– Integrate web mashups with backend services (e.g. support
for pub/sub, “connectors” to a number of FIWARE GEs, etc.)• From the user perspective:
– Develop application mashups: integrate heterogeneous data, application logic, and UI web components to create value added instant applications.• Without the need of programing skills (e.g. end users,
infomediaries, etc.)• Fostering the reuse and shareability of widgets, mashups,
etc.
7
8
9
Configurable dashboards... and much more
• Wiring– Wiring and support for channel creation
• HTTP proxy– Cross-site HTTP requests
• APIs to some GEs– Context Broker, Object Storage
• Public App Mashups– Access without login to a mashup
• Embedded mashups– Integrate public mashups in any website
• Integration with the WStore and IdM
13
14
Behavior Oriented Wiring
• Wiring can be a mess when we have too many widgets/operators
• Split wiring into parts: behavior– Behavior: One identified action that users can
perform with the mashups– A behavior involves a subset of all the mashable
components of the MashUp– While editing the behavior, these mashable
components are highlighted while the rest are blurred
15
16
Recent success stories
• Málaga CitySense
Watch it on Youtube18
USING WIRECLOUDApps/Data Delivery Chapter
Using Wirecloud
• Create a FIWARE Lab account (if not done yet)• Choose mashup tab• Play https://mashup.lab.fiware.org
add widgets to workspace
wiring tool my resources
store
21
WORKING WITH MASHUPSApps/Data Delivery Chapter
Managing your MashUps
• Create as many workspaces as you want• Rename them, remove them…• Upload a MashUp to “My Resources”
– With/without widgets/operators embedded• Create a workspace from a MashUp
23
Create/modify your own MashUp
• Add widgets with the button• Choose widgets on the left panel and click on “+”
sign to add them• Go to the wiring tool
– Add your widgets and deploy any operator– Connect input and output endpoints as you want
• There are not restrictions
24
Public/Embedded MashUps
25
Publish a MashUp in the WStore
26
Consume MashUps
• Consume the offer with a different user
• Phases1. Acquire in the WStore2. Install from your
resources3. Create a workspace
from the MashUp
27
DEVELOPING WITH WIRECLOUD
Apps/Data Delivery Chapter
Developing a widget
• Typical web app structure
• config.xml is the description– It references the HTML– HTML links with the rest
30
Widget description – config.xml
31
Using preferences
32
Making HTTP requests
33
Working with wiring
34
Developing an operator
• config.xml is similar– References a JavaScript file
35
Using Context Broker GE
• Declaring the feature
• Opening the connection
36
Using Context Broker GE
• Creating an entity
37
Using Context Broker GE
• Creating a subscription
http://conwet.fi.upm.es/wirecloud
https://mashup.lab.fiware.org
http://edu.fiware.org/course/view.php?id=53
http://catalogue.fiware.org/enablers/application-mashup-wirecloud/documentation
https://github.com/Wirecloud/wirecloud https://github.com/wirecloud-fiware
https://store.lab.fiware.org/search/tag/starterKit
39
https://hub.docker.com/r/fiware/wmarket
Store
WHAT IS WSTORE?Apps/Data Delivery Chapter
WStore
• Generic Online Store intended for Digital Assets– Publish Offering with products/services– Acquire these offerings
• Key features– Support for rich price models– Support for charging– Support for billing– Support accounting callbacks– Integration with PayPal– Support for FIWARE MarketPlace, Repository and RSSS
42
WStore: Main Components (1)
• Resources– The product or the service to be sold– Default resource types: Files or APIs– Extensions to support specific resource types
• Mashable components• Datasets• …
43
WStore: Main Components (2)
• Offerings:– Commercial Properties definition
• Basic description• Image• Snapshots• Legal Terms • Price Plans• Involved Resources• …
– Life Cycle1. Created2. Published3. Deleted
– Open Offerings: Not need to be acquired. Its resources can be accesses immediately
44
Wstore: Main Components (3)
45
OFFERING Resource 1 Resource n…
Resources
… Price Plan 1
Price Component 1.1
Price Component 1.n…
Price Plan n
Price Component n.1
Price Component n.n…
Price Plans
WStore: Main Components (4)
• One resource can be included in one or more offerings
• Offerings with more than one Price Plan– The purchaser selects the one to be applied
• Price Components– Single payment– Recurring Payment
• Subscription• Pay per use
– Combined in one Price Plan as desired
46
DATA MARKET + + Extensions
FIWARE Data Market: + + Extns.
• Integrated with FIWARE Lab IdM (OAuth2)– Users do not need to have different accounts– Same user than in the rest of FIWARE Portals (Store, WireCloud,…)– Users can access the portal without log in to read open data
• Ability to create private datasets– Accessible only by certain users
• Integration with WStore allows to:– Manage the users that can access private datasets– Charge users for accessing your data– Ensure that users only access your data under some legal terms– …
• https://data.lab.fiware.org
48
USING WSTOREApps/Data Delivery Chapter
Creating a Resource
50
1
2
3 4
Creating an Offering (1)
51
1
2
3 4
52
Creating an Offering (2)
5
Creating an Offering (3)
53
6
Creating an Offering (and 4)
54
7
8
9
Acquiring Offering
1. Select the Offering to be acquired2. Choose the Price Plan to be used3. Accept the legal terms
55
https://store.lab.fiware.org
http://edu.fiware.org/course/view.php?id=104
http://catalogue.fiware.org/enablers/store-wstore/documentation
https://github.com/conwetlab/wstore
56
http://wstore.readthedocs.org/en/latest/
https://hub.docker.com/r/fiware/wstore
WMarket
WHAT IS WMARKET?Apps/Data Delivery Chapter
WMarket
• Business Component focused on aggregate the offerings coming from different Stores
• It is just an showcase: the final transaction (buying) is handled by the corresponding Store
• Allow final purchasers to view the offerings published by different providers and select those with higher benefits– Trivago– Rastreator– …
• Key features:– Offerings comparison– Store & Offerings Review– Recommendations– Full integration with WStore– Semantic Search based on the market segment (Feb. 2016)
59
WMarket: Main Components
• Stores– The basic units to aggregate offerings
• Descriptions– Pointers to a Linked-USDL file that contains the descriptions of
one ore more offerings• Offerings
– The units to be sold. Includes:• Services (similar to WStore resources)• Price Plans (as the ones defined in WStore)
• Categories– “Tags” to categorize the published offerings– Automatically created based on the type of the services
included in the offerings
60
USING WMARKETApps/Data Delivery Chapter
Creating a Store
62
1
2
Creating a Description
63
1
2
64
Comparing Offerings
1
2
65
Reviewing Store/Offerings
1. Access the entity (store or offering) to be reviewed
1
2
https://marketplace.lab.fiware.org
http://catalogue.fiware.org/enablers/marketplace-wmarket/documentation
https://github.com/conwetlab/wmarket
66
http://wmarket.readthedocs.org/en/latest/
WMarket
https://hub.docker.com/r/fiware/wmarket
Thanks!Thanks!