Autonomic computing is the ability of an IT infrastructure to adapt to change in accordance with business policies and objectives. Quite simply, it is about freeing IT professionals to focus on higher-value tasks by making technology work smarter, with business rules guiding system to be self-configuring, self-healing, self-optimizing, and self-protecting.BACKGROUNDSelf-management means different things in different fields. The number of computing devices in use in forecast to grow at 38% per annum and the average complexity of each is increasing. Currently this volume and complexity is managed by highly skilled humans; but the demand for skilled IT personnel is already outstripping supply, with labor costs exceeding equipment costs by a ratio of up to 18:1. Computing systems have brought great benefits of speed and automation but there is now an overwhelming economic need to automate their maintenance.A general problem of modern distributed computing systems is that their complexity, and in particular the complexity of their management, is becoming a significant limiting factor in their further development. Large companies and institutions are employing large-scale computer networks for communication and computation. The distributed applications running on these computer networks for communication and computation. The distributed applications running on these computer networks are diverse and deal with many different tasks, ranging from internal control processes to presenting web content and to customer support. Additionally, Mobile computing is pervading these networks at an increasing speed; employees need  to communicate with their companies while they are not in their office. They do so by using laptops, PDAs,or mobile phones with diverse form of wireless technologies to access their companies’ data.This creates an enormous complexity in the overall computer network which is hard to control manually by one or more human operators. Manual control is time-consuming, expensive and error-prone. The manual effort needed to control a growing networked computer system tends to increase very quickly. 80% of such problems in infrastructure happen at the client specific application and database layer. Most ‘autonomic’ service providers guarantee only up to the basic plumbing layer(power, hardware, operating system, network and basic database parameters).A possible solution could be to enable modern, networked computing systems to manage themselves without direct human intervention. In a self-managing system Autonomic System, the human operator takes on a new role: He does not control system directly. Instead, he defines general policies and rules that serve as an input for self-management process.II. LITURATURE SURVEYAutonomic computing is a concept that brings together many fields of computing with the purpose of creating computing systems that self-manage. Autonomic Computing is an initiative started by IBM in 2001. Its ultimate aim is to create computer systems capable of self-management, and reduce the barrier that complexity poses to further growth. Since its beginning in 2001, the concept of Autonomic Computing has seen exponential growth in terms of research activities. Many Autonomic computing is the ability of an IT infrastructure to adapt to change in accordance with business policies and objectives. Quite simply, it is about freeing IT professionals to focus on higher-value tasks by making technology work smarter, with business rules guiding system to be self-configuring, self-healing, self-optimizing, and self-protecting.

BACKGROUND

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Self-management means different things in different fields. The number of computing devices in use in forecast to grow at 38% per annum and the average complexity of each is increasing. Currently this volume and complexity is managed by highly skilled humans; but the demand for skilled IT personnel is already outstripping supply, with labor costs exceeding equipment costs by a ratio of up to 18:1. Computing systems have brought great benefits of speed and automation but there is now an overwhelming economic need to automate their maintenance.

A general problem of modern distributed computing systems is that their complexity, and in particular the complexity of their management, is becoming a significant limiting factor in their further development. Large companies and institutions are employing large-scale computer networks for communication and computation. The distributed applications running on these computer networks for communication and computation. The distributed applications running on these computer networks are diverse and deal with many different tasks, ranging from internal control processes to presenting web content and to customer support. Additionally, Mobile computing is pervading these networks at an increasing speed; employees need  to communicate with their companies while they are not in their office. They do so by using laptops, PDAs,or mobile phones with diverse form of wireless technologies to access their companies’ data.

This creates an enormous complexity in the overall computer network which is hard to control manually by one or more human operators. Manual control is time-consuming, expensive and error-prone. The manual effort needed to control a growing networked computer system tends to increase very quickly. 80% of such problems in infrastructure happen at the client specific application and database layer. Most ‘autonomic’ service providers guarantee only up to the basic plumbing layer(power, hardware, operating system, network and basic database parameters).

A possible solution could be to enable modern, networked computing systems to manage themselves without direct human intervention. In a self-managing system Autonomic System, the human operator takes on a new role: He does not control system directly. Instead, he defines general policies and rules that serve as an input for self-management process.

                                                                                                                                                    I.     LITURATURE SURVEY

Autonomic computing is a concept that brings together many fields of computing with the purpose of creating computing systems that self-manage. Autonomic Computing is an initiative started by IBM in 2001. Its ultimate aim is to create computer systems capable of self-management, and reduce the barrier that complexity poses to further growth. Since its beginning in 2001, the concept of Autonomic Computing has seen exponential growth in terms of research activities. Many research organization are pouring in millions to design and create systems which is ‘autonomic’. Lots of results have been produced and many more are yet to arrive on the scene.Symptom Catalog is a repository of the rules which are used for monitoring the application. It maintains the rules and associated steps to be taken when that rule is breached. The present complex system needs a huge knowledge database to operate tools which keeps system administrator away from implementing Autonomic solutions. Also there is a need for easier way of maintaining symptom rules for an administrator is evident. Autonomic System Manager (ASM) is focused on creating an environment for the system administrator where he can monitor and maintain applications by creating policies for the working of the application. Any breach of policy is undesired, the ASM takes care and alerts the administrator to take appropriate action associated with the rule. The ASM  provides the administrator with a user friendly “SYMPTOM CATALOG” (SC) which allows him to create policies for the application. Administrator is endowed with the ability to create simple rules by having rule expressions as combinations of various events and operations between them. The simpler rules can be reused for the creation of complex rules. This is a new feature of SC to provide complex rule creation is what makes the ASM unique.The traditional structure of symptom catalog suffers from long delays in action taken due to complex XML structures of symptom database. So an attempt has been made to employ a symptom structure that is not only simple but also faster in identifying the action to be initiated. III. PROPOSED SYSTEMWith the need of the hour being a user friendly way of storing rules the policies, an attempt was made to do same by implementing a system based on autonomic concepts which can allow administrator to create and maintain rules and policies as per their wishes.PROBLEM DOMAINIT infrastructure is becoming exceedingly complex. Service Oriented Architecture(SOA) enables companies to execute software modules that lie outside their own infrastructure and control, for example at a business partner’s site. Corporate websites require multiple, interconnected resources, including application, web and database servers as well as network equipment and software, to operate. New requirements for deployment and problem determination across geographically distributed technology introduce the need for functionality that is beyond the capability of yesterday’s enterprise management tools.The domain of this paper orient around current applications which maintain log files for maintenance purposes. The log files ensure easier analysis and maintenance of the application by creating a record for every event occurring during the working of the application. The applications, although maintains logs, can neither take any steps to curb the errors occurring nor can they prevent similar errors from occurring in future runs. The consequences of such type of errors may lead to a system crash or loss of data and information. Such crashes or data losses cannot be tolerated in today’s scenario where every millisecond lost by crashed system can lead to enormous losses to business. Our focus is around such systems in which applications create log files of their execution but do not have capability to protect themselves from crashes. We try to create a system which can sustain itself by taking appropriate actions before that can occur.SYSTEM OVERVIEWThe proposed system to achieve above mentioned requirements consists of software known as ASM as illustrated in the figure 3.1. The ASM software is an implementation of the concepts of the autonomic computing and is focused on providing a user(in this case the system administrator) friendly environment to create and maintain rules. The main part of the ASM software is the symptom editor Figure 3.1 System ArchitectureWhich will allow the user to create and maintain his rules. The software presents the self monitoring and self healing property of an autonomous system by monitoring a log file for breach of policies(set by administrator) and altering the administrator in the case of any breaches(an act healing).The system can generate these alerts as an email or as an SMS. The system can also accept back replies from the administrators is a similar way and perform the specific actions as notified by the administrators. If the administrator does not wish to reply, or wants this action to be taken automatically, he can do so using the symptom creating and editing feature. These symptoms are stored on the hard disk and accessed by the system every time to match against the record. Thus, the property of automatically taken actions in case of case of errors demonstrates the self healing property. The proposed architecture of the ASM software consists of 4 main sub components they are:1.Monotoring: Monitors the application and fetches its log-records. After fetching, the log records are matched against policies. If the match is successful, action-subcomponent is invoked.2.Actions:Once a breach of policy is detected, this action sub-component sends an alert to the administrators. The administrator can reply back with the specific action-command. The action-sub-component extracts this command and executes it as remedial step. If no reply is received, a default action set for that policy is executed.3.Symptom Catalog:The monitoring sub-component fetches the policies for matching the symptoms from the symptom catalog. The Symptom Catalog is a file organized as a hash table containing the symptoms/policies in variable record fiels length format, stored by the administrator. The following figure 3.2 shows the symptom catalog: Figure 3.2 Format of symptom catalogEvery rule created by the user is validated and returned into symptom catalog. Each symptom in the symptom catalog is variable length record with three fields namely Rule_ID, Rule description and action. 4.Symptom editor:The creation and manipulation of symptoms in the symptom catalog would be carried out with the help of a tool called a symptom editor for any application being monitored.IV. GENERAL CONSTRAINTSThe primary constraint of the Autonomic System Manager is that it can monitor only a few applications which maintain their logs.The actions of the Autonomic System Manager are limited to alerts and execution of APIs of the target applications. The monitoring is limited to the symptoms listed in the symptom catalog.DEPENDENCIES:• The working depends on the administrator to specify a set of actions when exceptions occur.• The Autonomic System Manager depends on the format of log files to be known for monitoring purposes.IV CONCLUSIONThe proposed work is simpler method of implementing IBM’s MAPE-K framework of Autonomic system that supports self-healing capability of software product. The structure of symptom catalog improves symptom access time. The software product would be monitored for healthy working by presenting novel approach for building a symptom catalog that contains possible symptoms and associated actions. It also empowers the administrators the administrators with the ability to create and maintain primitive policies for any application in convenient wayV REFERENCES1 Jeffrey O. Kephart, David M. Chess., ” The vision of           Autonomic Computing “, IEEE Computer Society, January 2003, IBM Thomas J. Watson Research Centre.2 Paul Horn (senior vice president), ” Autonomic Computing IBM?s perspective on the state of Information Technology”, IBM Research. 3 Hassan, S.; Al-Jumeily, D.; Hussain, A.J. “Autonomic Computing Paradigm to Support System’s development,” Developments in eSystems Engineering (DESE), 2009 IEEE Second International Conference, vol., no., pp.273- 278, 14-16 Dec. 2009 4 Henxing Zhao; Congying Gao; Fu Duan; , “A survey on Autonomic computing research,” Computational Intelligence 2009 and Industrial Applications, 2009. IEEE PACIIA 2009. Asia-Pacific Conference on, vol.2, no. pp.288-291, 28-29 Nov. 5 IBM ” An Architectural Blueprint for autonomic Computing “, whitepaper, June 2005. 6 A. G. Ganek, T. A. Corbi, ” The dawning of the Autonomic Computing Era “, IBM System Journal Vol. 42, No. 1, 2003. 7 M.G.Hinchey and R. Sterritt, “Self Managing Software in Computer”, IEEE Computer Society, Vol.39, Pages 107- 109, Feb. 2006.

x

Hi!
I'm Joan!

Would you like to get a custom essay? How about receiving a customized one?

Check it out