Browse Prior Art Database

Generic Method for Specifying the Modification of Specific Sections of One or More Configuration Files Disclosure Number: IPCOM000169164D
Original Publication Date: 2008-Apr-08
Included in the Prior Art Database: 2008-Apr-08
Document File: 3 page(s) / 29K

Publishing Venue



Disclosed is a method for creating an easy-to-use interface for the modification of specific part or parts of configuration file(s) for complex software. Modern software often relies on multiple sources of stored data, either for installation, configuration, or maintenance purposes. These sources of data are frequently stored within files which can be spread throughout the infrastructure of the system. This infrastructure can involve different locations (e.g. multiple hard drives on a system), storage types (e.g. local hard disk device, tape backup drives), or even systems (e.g. a Windows server at one location, a Linux server at another) within a single implementation.

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 52% of the total text.

Page 1 of 3

Generic Method for Specifying the Modification of Specific Sections of One or More Configuration Files

The installation or maintenance of one or more programs can require numerous manual editing steps which entail locating specific files across a potentially complex infrastructure, opening the files, searching for a specific line, and precise editing of a specific piece of data in a particular way. The current standard method, if these files are not directly altered by an installation or configuration program, is to require a user to manually locate and edit the files.

This method is error-prone as a mistyped character, incorrect parameter, or invalid entry can be difficult to troubleshoot (for example, manually scanning a file and attempting to locate a problem where an 'l' was mistyped as '1' or 'I', or a '0' for an 'O'.) If such an error occurs after updating multiple files, the difficulty in correcting the situation increases dramatically.

With these problems, compounded with the fact that different editing methods may be required for different storage or operating systems within an infrastructure, the likelihood of error and difficulty of troubleshooting increases even more.

The best solution for such a problem is to eliminate the requirement to manually edit these files altogether. However, since many current infrastructures would not allow this without extensive redesign, an alternative intermediary solution is desirable. The goals of such a design are to simplify the location, editing, and updating of these files, all while reducing or eliminating the likelihood of an error. If such an implementation is used, the addition or inclusion of additional software components is simple, regardless of the origin, as long as direct file manipulation can accomplish the updates necessary.

To accomplish this, this disclosure describes an architecture of drawing multiple files into a single form to allow an end user to make any required changes. This is accomplished without altering the infrastructure of the existing programs eliminating any need for reworking existing code while allowing the addition of this capability at any time for any system.

This is accomplished through the creation of a three-tiered arrangement of 1) the file(s) to be edited or modified, 2) an interpreter file that describes which aspect of the file(s) should be visible, along with related options which are of interest, and 3) a reader/editor that uses the interpreter file to render and allow editing and saving of specific portions of the original file(s).

Tier 1 of the invention assumes the need or desire to alter or review an existing file or files (or the creation of a new file if particular parameters are required before creation.)

Example of a section from a configuration file, C:\Path to



Page 2 of 3