Atlas Atlas Reactivity Engine Handson Session Mobile Computing

Atlas & Atlas Reactivity Engine Hands-on Session Mobile Computing - CNT 5517 -5564 Dr. Sumi Helal Professor Computer & Information Science & Engineering Department University of Florida, Gainesville, FL 32611 helal@cise. ufl. edu

Agenda • Demo – – – Knopflerfish Atlas Middleware Atlas Emulators Kit. Sample. App Atlas Reactivity Engine • Atlas Service API – Atlas. Service & Atlas. Client Interface – Kit. Sample. App Code Study • ARE Code Review • Q&A

DEMO

Project Set Up • Install Knophlerfish OSGi (Version 1. 3. 5) – http: //www. knopflerfish. org/download. html#1. 3. 5 • Install Atlas middleware – http: //www. icta. ufl. edu/atlas/ • Install Atlas Device Emulators – http: //www. icta. ufl. edu/atlas/emulator/ • Atlas demo application • Install Atlas Reactivity Engine – http: //www. icta. ufl. edu/atlas/are/ (You may find all the links in http: //www. icta. ufl. edu/atlas/)

Install Knophlerfish • Download and install. • After installation, launch the Knopflerfish OSGi framework by double clicking the executable JAR file “framework. jar” or typing “java –jar framework. jar” in the command line. • The OSGi window (right) will pop up.

Install Atlas Middleware • Install the middleware bundles. Click File Open Bundles in the OSGi menu • Launch all middleware bundles • Bundles reside in the directory: …Atla. Soft-1. 5 cleanAtla. Soft-1. 5 copyatlas

Install Atlas Device Emulators • Device emulators include: - Digital. Contact. Sensor. Emulator HS 322 Servo. Emulator Humidity. Sensor. Emulator Interlink. Pressure. Sensor. Emulator Temperature. Sensor. Emulator • Install and launch • The GUI for the emulators is shown (right)

Atlas Demo Application Kit. Sample. App. jar is an Atlas demo application (bundle) that will use the device services provided by the emulator bundles. - Install the Atlas Kit Sample Application bundle. Click File Open Bundles in the OSGi menu, launch Kit. Sample. App. jar. - The GUI for the kit sample application (right). Note that devices are shown as offline if their corresponding service bundles have not yet been activated

Atlas Demo Application • Customize sensor measurements. Readings and the sampling rate of the Pressure sensor can now be customized using the GUI interface. User can change their values by either sliding the slider or typing in a value in the text box. Once changes are applied by pressing the update button, they will be reflected in the application window. • Maneuvering servos. Controlling the servo is the other way around since it is an actuator. Users issue “move servo” command from the application window and specify a turning angle by sliding the slider. The servo emulator will virtually turn the angle and shows the current position. • Uninstall emulators. Uninstalling emulators is easy. Just click on the close button on the emulator window. The bundle will be ejected from the OSGi automatically. And the device icons on the application will return to offline.

Install Reactivity Engine • Find the engine in: …Atlas. REATLAS RE REFERENCE IMPLEMENTATIONsrcAtlas. Reactivi ty. Engine 10jarsReactive. Engine. jar • Install and launch Atlas Reactivity Engine. The GUI for it will pop up immediately. (Right)

Reactivity Engine Code Review • An OSGi bundle is basically like a normal Java application instantiated by an Activator class. • Each bundle have its own Activator which links the application into OSGi. • Reactivity Engine is implemented as an OSGi bundle as well. • Our job mainly focuses on the. java file “Kit. Sample. App. java”

ATLAS Service API* * http: //www. icta. ufl. edu/atlas/emulator/Atlas. Dev_Javadocs/doc/

Atlas Service • Atlas Service – Providing basic Atlas Service Functions such as sensor data subscription & delivery – A base class (interface) for developers to extend and build their own Atlas device services, e. g. temperature sensor, sensor emulators. – Two versions (package: com. pervasa. atlas. dev. service) • Interface Atlas. Service • Class Atlas. Servie. Class – Key methods: • • Data. Handler(String, String) subscribe. To. Sensor. Data(Atlas. Client) unsubscribe. To. Sensor. Data(Atlas. Client) get. Data(Atlas. Service) -> get. Sensor. Reading(Atlas. Client) *

Atlas Client • Atlas Client – An interface implemented by applications require sensor data from the Atlas network – For example, Kit. Sample. App and ARE are Atlas Clients. – package: com. pervasa. atlas. dev. service – Key methods: • Received. Data(String, Properties)

Push & Pull APIs • Push Method name void subscribe. To. Sensor. Reading(Atlas. Client ac) void unsubscribe. To. Sensor. Reading (Atlas. Client ac) void Received. Data (Atlas. Client ac) • Pull Emulator Method name Contact. Sensor void get. Contact. Reading(Atlas. Client ac) Interlink. Pressure void get. Pressure. Reading(Atlas. Client ac) Humidity void get. Sensor. Reading(Atlas. Client ac) Temperature void get. Sensor. Reading(Atlas. Client ac)

CODE REVIEW

Command Interpreter • LIST: list all the basic events, basic actions, userdefined events, user-defined actions and rules. • BASIC: list all the basic events, basic actions. • DEFINE: used to define event, condition – Define atomic event: DEFINE event e 1=ref_ID (range) - Define composite event: DEFINE event e 2=e 1+e 2*e 3 - Define action: DEFINE action a 1=ref_ID(range)

Command Interpreter • DEFINE: used to define event, condition – Define condition: DEFINE condition c 1=true (or false) – Define rule: DEFINE rule r 1=e 1, c 1, a 1 • RUN • STOP

Q&A