Browse Prior Art Database

METHOD OF AUTONOMIC SERVICE STATE ENABLEMENT OF CUSTOM ALERT GENERATION TO IMPROVE SERVICEABILITY WITHIN AN AUTONOMIC DISTRIBUTED SYSTEM

IP.com Disclosure Number: IPCOM000199554D
Publication Date: 2010-Sep-09
Document File: 2 page(s) / 130K

Publishing Venue

The IP.com Prior Art Database

Abstract

The existing limitation of a fixed predetermined set of product alerts does not allow for customers to build an autonomic distributed environment based on the autonomic computing paradigm. It now becomes advantageous for the customer to utilize the method described to create and generate custom alerts to build and maintain autonomic distributed environments, and to improve serviceability within those environments. Currently, IBM products have serviceability management characteristics built into their products based on a predefined set of default alerts that contain a limited amount of information that is intended to be valuable to system administrators and/or engineers that are responsible for maintaining the distributed environment. Product alerts are standardized notifications to external consumers of system state changes and/or event conditions that may require the attention of the user. In addition, product alerts are statically linked into the software serviceability capabilities and are defined by the hardware and/or software development team(s) prior to the release of the product, and new alerts cannot be added or existing alert cannot be edited without a subsequent software release. Thus, product alerts cannot be customized to satisfy autonomic serviceability capabilities to manage large-scale distributed embedded system environment. If a customer’s IT policy required a new set of alerts to manage their distributed environment infrastructure, they would have to follow a formal (and sometimes long) process to request those specific alerts to be implemented into to a specialized software release from IBM. After the specialized software release has been delivered, the customer may then determine that it may not need every new alert that was initially requested or finds that they need to add additional alerts; therefore, they must start the entire process again of requesting new alerts. Thus a method is necessary to enable customers to create and generate customizable alerts, which allows them define the specific characteristics in which the system should monitor and react to in order to improve serviceability within an autonomic distributed embedded system environment. The core idea of the invention is to add a custom alert generation layer to the predefined product alert infrastructure to enable customers to genuinely create custom alerts that meet their changing IT policies and infrastructure to improve the way they service distributed embedded system environments. In addition to creating custom alerts to improve the autonomic serviceability capabilities within the normal embedded system, custom alerts will be used to inform the end-user of potential issues that are resident within the bounds of the distributed environment prior to initiating a code update, and to notify the end-user on the status of any code updates that are occurring outside of the system.

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

Page 1 of 2

METHOD OF AUTONOMIC SERVICE STATE ENABLEMENT OF CUSTOM ALERT GENERATION TO IMPROVE SERVICEABILITY WITHIN AN AUTONOMIC DISTRIBUTED SYSTEM

- Create custom alert(s) or modify existing alert(s)
o If the alert(s) does not exist, then assign attribute and values to custom alert(s).

Once the custom alert is created, save/update the alert in the alert template.ini file. The custom alert can be instantiated by the alert daemon.
• *

No rebooting of the system is required to discover the custom

alert(s).

Is the alert currently active on the system (in the current active alert list)?
• Yes: Do not modify current active alert and, update alerttemplate.ini, and exit.

No: Update alert template.ini file and exit.

o If the alert(s) exist

Modify current attributes of alert(s).

Save/update the alert(s) in the alert template.ini file.

Is the alert currently active on the system (in the current active alert list)?
• Yes: Do not modify current active alert and exit.

No: Update alert template.ini file and exit.

1

Page 2 of 2

2

[This page contains 1 picture or other non-text object]