Debugging and Logging Services for Defence Service Oriented Architectures.
Scientific Publication
- Report Number:
- DSTO-TR-2664
- Authors:
- Pilling, M.
- Issue Date:
- 2012-02
- AR Number:
- AR-015-224
- Classification:
- Unclassified
- Report Type:
- Technical Report
- Division:
- Command, Control, Communication and Intelligence Division (C3ID)
- Release Authority:
- Chief, Command, Control, Communication and Intelligence Division
- Task Sponsor:
- DG Integrated Capability Development
- Task Number:
- CDG 07/355
- File Number:
- 2011/1195600/1
- Pages:
- 17
- References:
- 20
- Terms:
- Debugging; Distributed computing; Software maintenance; Service oriented architecture; Software tools; Software architecture
- URI:
- http://hdl.handle.net/1947/10184
Abstract
While often thought of as a “Dark Art", debugging is nevertheless a necessary part of fielding quality computing systems which can and should be done systematically. Service Oriented Architectures (SOAs) show great promise but also represent one of the most challenging environments in which to debug system services. In addition to all the issues of distributed and paralled de- bugging, SOAs introduce the complexity of significant parts of one's programs being provided by others. This paper examines the features of SOAs that complicate debugging and shows how integrated logging is an essential part of finding the cause of service failures. We draw on Agan's work in developing systematic strategies for debugging to generate system features that are necessary or helpful for debugging in an SOA environment. These are in turn used to specify requirements for a debugging system integrated into the fabric of the SOA. We argue that deep integration is necessary to produce significant debugging efficiency improvement in an SOA environment and provide some recommendations for Defence in this area.
Executive Summary
This document proposes an integrated distributed debugging and logging service for Defence's Service Oriented Architecture. It argues for them on the basis that:; • Debugging SOA specific issues requires integrated debugging hooks within SOA components.; • Message and event logging with vector timestamps will allow programmers fixing bugs to avoid many spurious symptoms and get a clearer picture of the problem at hand.; • Logging of application and component success or failure is essential to build up a statistical picture on which to quantify the reliability of SOA-based subsystems as a basis for fielding such subsystems for deployment.; The report also provides a software specification for such an SOA debugger. The requirements for this debugger and associated logging system are derived specifically from debugging strategies that are known to work and the information requirements that support them.; It makes several recommendations chief among them being that whatever SOA infrastructure Defence chooses, it must be flexible enough to allow Defence to modify key components in order to add functions supporting debugging and adequate logging.