Main.Documentation.Merge ProvidedByUjfBranch en 0 Main.Documentation.Merge xwiki:XWiki.nkef xwiki:XWiki.nkef xwiki:XWiki.nkef 1241426535000 1241426849000 1241426849000 1.4 1 Provided By UJF Branch ---- #toc("" "" "true") ---- * Plug and Play Sensors (using iPOJO+WireAdmin+WireAdminBinder) : data collected for sensors must be add in the extension element of the ECReport. * EPCIS extension to store sensors data (position, measurement, answers to survey, …) : the data must be extracted from the ECReport by the EPCIS. * GWT-based User Console relying on the RFIDSuite” EPCIS (developed with EJB3.0)+ extensions (sensors data) : should we keep/discard the “Warning ” features (lost objects, pairing, …): they will be replaced by the BEG, isn’t it ? * Edge Premice Server Architecture ??? Question: does the AIT branch can model the 3 layer architecture ? * Communication (JMS, HTTP/SOAP, SMTP, XMPP) between Edge and Premice and between Premice and EPCIS to transport ECReports * « ONS » based on Web Services and EJB3.0 + WS-Metadata (JSR 181). * Porting the existing readers (Tagsys, TIRIS, ACS122, Mir:ror) to the HAL wrapper * Bluetooth bridge as a reader * HTTP bridge as a reader * NFC MIDLets ** with BT to the Bluetooth Bridge ** with HTTP to the HTTP Bridge * Management and deployment : ** LDAP for X509 certificates publication and for architecture description ** JMX for configuration and monitoring ** use Felix MOSGi project for the JMX agent ** may be UPnP and DNSSD for Edge and premice mutual dynamic discovery in the warehouse/store network) * JVisualVM and JConsole plugins for OSGi management (may be contributed to the Apache Felix community). * Generic build for demopacks (ANT, JMX (and IzPack in the future)) <h2 class="heading-1"><span id="HProvidedByUJFBranch">Provided By UJF Branch</span></h2><p class="paragraph"/> <hr class="line"/> <hr class="line"/> <ul class="star"> <li>Plug and Play Sensors (using iPOJO+WireAdmin+WireAdminBinder) : data collected for sensors must be add in the extension element of the ECReport.</li> <li>EPCIS extension to store sensors data (position, measurement, answers to survey, …) : the data must be extracted from the ECReport by the EPCIS.</li> <li>GWT-based User Console relying on the RFIDSuite” EPCIS (developed with EJB3.0)+ extensions (sensors data) : should we keep/discard the “Warning ” features (lost objects, pairing, …): they will be replaced by the BEG, isn’t it ?</li> <li>Edge Premice Server Architecture ??? Question: does the AIT branch can model the 3 layer architecture ?</li> <li>Communication (JMS, HTTP/SOAP, SMTP, XMPP) between Edge and Premice and between Premice and EPCIS to transport ECReports</li> <li>« ONS » based on Web Services and EJB3.0 + WS-Metadata (JSR 181).</li> <li>Porting the existing readers (Tagsys, TIRIS, ACS122, Mir:ror) to the HAL wrapper</li> <li>Bluetooth bridge as a reader</li> <li>HTTP bridge as a reader</li> <li>NFC MIDLets<ul class="star"> <li>with BT to the Bluetooth Bridge</li> <li>with HTTP to the HTTP Bridge</li> </ul> </li> <li>Management and deployment :<ul class="star"> <li>LDAP for X509 certificates publication and for architecture description</li> <li>JMX for configuration and monitoring</li> <li>use Felix MOSGi project for the JMX agent</li> <li>may be UPnP and DNSSD for Edge and premice mutual dynamic discovery in the warehouse/store network)</li> </ul> </li> <li>JVisualVM and JConsole plugins for OSGi management (may be contributed to the Apache Felix community).</li> <li>Generic build for demopacks (ANT, JMX (and IzPack in the future))</li> </ul>