Browse Prior Art Database

Configuration Based Serviceability Instrumentation for Integrated Development Enviroments

IP.com Disclosure Number: IPCOM000028941D
Original Publication Date: 2004-Jun-08
Included in the Prior Art Database: 2004-Jun-08
Document File: 1 page(s) / 38K

Publishing Venue

IBM

Abstract

Adding serviceability instrumentation to source code is time consuming, error prone, and it often produces inconsistent results. All of these problems can lead to software products that are more difficult to diagnose and service when they are deployed in a production environment.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 57% of the total text.

Page 1 of 1

Configuration Based Serviceability Instrumentation for Integrated Development Enviroments

This article describes an approach for adding serviceability instrumentation to source code which does not suffer from the problems listed above. The idea is to take advantage of the plug-in mechanism provided by many IDEs, such as Websphere Studio. A plug-in is provided which can parse one or more source code files that are loaded in the IDE. It uses a configuration file (or configuration panel provided by the IDE which allows the developer to set the following properties:

Pattern based recognition for determining placement -- this tells the plugin what patterns to look for in the source code when deciding where to insert serviceability code. The pattern can be a complex regular expression or as simple as a string match.

Template for content -- this tells the plugin what the inserted serviceability code should look like. Variables are used in the template to allow for contextual strings to be generated such as the name of the enclosing method or the current line number.

Verbosity Level -- the level of verbosity that should be used by default in the serviceability code. This setting influences how much diagnostic information will be produced at runtime by default, without the end user manually adjusting the verbosity level.

The advantages of this approach are:

Ease of use -- The plugin can easily be invoked on one or more files from a simple context menu. The files don't nee...