Changes between Version 26 and Version 27 of TestbedOverview

Timestamp:

Oct 28, 2010, 12:18:36 PM (14 years ago)

Author:

arne.munch-ellingsen

Comment:

--

TestbedOverview

@@ -61 +61 @@
 == How does it work? ==
 
-So how does the SENSEI system work in practice? The easiest way to find out is try it for yourself. First a System Provider is needed. There are two options: either the [wiki:SpUsingTestbed Pan-European testbed] can be used or you can host your own system. By default Resource Provider components like the Java REP and Gateways are configured to use the Pan-European testbed. Deploying your own system is also not too difficult, all the needed components including the Management GUI and included in a [wiki:SpVirtualMachine virtual machine image].
+So how does the SENSEI system work in practice? The easiest way to find out is try it for yourself. First a System Provider is needed. There are two options: either the [wiki:SpUsingTestbed Pan-European testbed] can be used or you can host your own system. By default Resource Provider components like the Java REP and Gateways are configured to use the Pan-European testbed. Deploying your own system is also not too difficult, all the needed components including the Management GUI are included in a [wiki:SpVirtualMachine virtual machine image].
 
 Next some resources need to be connected to the system. The Resource User guide includes several different implementaions of resource end points. The easiest way to get started is to use the [wiki:RpRepDeployment Java REP], which creates dummy resources on a standard PC. The Java REP can then be extended with your own resources. If suitable sensor node hardware is available, then the [wiki:NativeGateway Native Gateway] can be used on a PC to interconnect sensor nodes running either [wiki:node-tinyos TinyOS] or [wiki:node-contiki Contiki]. In addition a [wiki:ZigbeeGateway ZigBee Gateway] and [wiki:AndroidREP Android Java REP] implementations are provided.