System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

1 2 192.168.1.1323 52224 biron@lucy5 hallowelt6 Listing 6.1: Example of the XMPP configuration in the XML configurationfile on the probe - ServerIP and ServerPortdetermine the address of the communication server.ServerAccount and Password are used to define theaccount used <strong>for</strong> the probe.to other entities. A special XMPPException object is thrown whenever an erroroccurs on using XMPP functionalities.Details <strong>for</strong> the communication with the communication server are defined inthe XML configuration file (see Listing 6.1). A server can be addressed by aIP address and a port. For the login on the communication server, the methodlogin() needs the name of the account and the corresponding password. Ifthe given parameters match the data on the XMPP server, the connection issuccessfully established. Otherwise an XMPPException will be thrown.The probe and the client are using a predefined standard configuration. Theconfiguration of the client can be changed by setting the parameters on the startview. The configuration of the probe can be set directly in the configurationfile.The data exchanged between the probe and the client is filled into Stringpairscontaining a key and a value. To append several pairs to a message eachpair is first added to a map. This map and the recipient are <strong>for</strong>warded tothe sendMessage() method. XMPP is capable of sending String-pairs byadding properties to the message stanza. When sending a new message theproperty map is parsed and all value pairs are added to the message. Thecommunication interface also offers the possibility to attach a body to eachmessage. This body can be used to add some additional textual in<strong>for</strong>mationto a message (e.g. logging in<strong>for</strong>mation on how the data was collected). Onceall data is appended the message gets <strong>for</strong>warded to the recipient.Additionally the implementation of the probe can <strong>for</strong>ward exception objectscaught by the elements of the probe by using the sendError() method. Theimplementation of the XMPPCommunicator reads the errorhandler-object andadds the stacktrace of the error handler to a new message. Error messages are<strong>for</strong>warded to all clients connected to the element catching the error.35
6.2 The Probe - Implementation of the Server SideDue to the use of the BonSAI interface (see chapter 4.2) the implementationof the probe is called ReSAI (Remote Sensor Actuator Interface). Figure 6.3shows the main classes implemented <strong>for</strong> the probe. For a better overview alllists controlled by the different elements are left out. Also helper classes (e.g.TimerConverter) are not shown.Figure 6.3: Main classes of the probe - The ReSAIServer classcreates and initializes all needed dispatchers. Each dispatchercontrols several sub components.ReSAIServer - Initializing the ProbeThe ReSAIServer class initializes at startup all needed classes <strong>for</strong> the probe.The Clients class extends the Observable class and holds a hash map of allclients connected and their current beacon count. This list is used to monitorall connected clients which connect during the runtime of the probe. For theconfiguration of the probe the XML configuration file is parsed and stored inthe ServerConfig. The ServerConfig holds all details <strong>for</strong> the communicationserver, the list of available component threads to be initialized and the36
Page 1: Bringing System <s
Page 5 and 6: AbstractSystem <st
Page 7 and 8: output, so each component is offeri
Page 9 and 10: of the system and the decisions mad
Page 11 and 12: created a telelaboratory where two
Page 13 and 14: Like the telelaboratory there is a
Page 15 and 16: with a very high frequency which ma
Page 17 and 18: Due to improving technology the use
Page 19 and 20: Figure 4.1: ToBI platfor</s
Page 21 and 22: Figure 4.3: The architecture behind
Page 23 and 24: Figure 4.5: Typical instant messagi
Page 25 and 26: 5 System DesignThe
Page 27 and 28: Figure 5.2: Message exchange betwee
Page 29 and 30: Figure 5.4: Beacon running between
Page 31 and 32: Figure 5.5: Reading and processing
Page 33 and 34: data and only forw
Page 35 and 36: For example a developer can select
Page 37 and 38: Figure 5.13: Principle of tabbed na
Page 39: 6.1 The Communication InterfaceThe
Page 43 and 44: stop all active processes of the co
Page 45 and 46: is received containing the TAG of t
Page 47 and 48: The selected sensors give a good im
Page 49 and 50: 1 2 4 6 8 Listing 6.2: Example of t
Page 51 and 52: TabConfig - The Status ViewThe TabC
Page 53 and 54: Each view adds a listener to the co
Page 55 and 56: LoginController which also observes
Page 57 and 58: tends the JPanel class. The templat
Page 59 and 60: 7 EvaluationIn the previous chapter
Page 61 and 62: Name Description CharactersSingleli
Page 63 and 64: Figure 7.1: Latency of receiving da
Page 65 and 66: For this thesis only a rough estima
Page 67 and 68: Laptop CPU load without Probe CPU l
Page 69 and 70: 8 ConclusionsIn the context of this
Page 71 and 72: 9 OutlookGiven this new tool its no
Page 74: BibliographyBurrell, A. and A. Soda
Page 77 and 78: 6.10 Main classes of the Java clien
Page 79 and 80: AppendixUse CasesUse Case 1: Connec
Page 81 and 82: Use Case 4: Disconnect from compone
Page 83 and 84: Use Case 9: Sending beacon to keep
Page 85 and 86: Figure 9.4: Latency of receiving da

System Introspection for System Analysis on Mobile Devices

Create successful ePaper yourself

Delete template?

Save as template?