1. RESTifying WS-* Services A Case Study in RFID (Radio Frequency IDentification) Dominique Guinard SAP Research & ETH Zurich Mathias Mueller University of Fribourg 167
16. Dominique Guinard guinard.org SAP Research / ETH Zurich dominique.guinard at sap.com Mathias Mueller diuf.unifr.ch/softeng University of Fribourg, CH mathias.mueller at unifr.ch Delicious: delicious.com/misterdom/RESTfulEPCIS Blog: webofthings.com
Where we started, a quick overview of our first trials to integrate sensor networks to business applications. A few guidelines on how to make sensor nodes first class citizens of the Web. Our implementation of these guidelines on the Sun SPOT plateform, including the video of a business use case we implemented using the RESTful Sun SPOTs.
The ``what'': what tagged products (EPCs) were read. The ``when'': at what time were the products read. The ``where'': where were the products read, in terms of Business Location (e.g. ``Floor B''). The ``who'': what readers (Read Point) recorded this trace. The ``which'': what was the business context (Business Step) recording the trace (e.g. ``Shipping''). Set of standards: Creating an « Internet of Things » The EPCIS is the information service: Sharing of RFID data. Exposes as standard WS-* interface Serveral EPCIS vendors: SAP AII (Auto-Id Infrastructure) IBM InfoSphere Fosstrak EPCIS (open source) Oracle Oracle Sensor Data Manager
According to expert of the domain (benchmarking made at SAP): Apache CFX According to me: Jersey
EPCIS: Fosstrak, SAP AII REST Fwork: jersey Atom: Abdera Container: Apache tomcat / Grizzly / Glassfish v3.
Yes, cool! But actually: Warning!!!! -> We could really optimize WS-* services to perform way better (caching the WSDL, compressing the data). Still, these results are nicely surprising! Hem actually we could also optimize REST services as well (compressing and …. caching!!!!)
Test it on epcmashup.webofthings.com
Find all the links and resources mentionned in this talk on: http://delicious.com/misterdom/RESTfulEPCIS