An Autonomic Architecture for Legacy Systems

Incorporating autonomic functionality into applications without user involvement is useful not only for application programmers who are building distributed systems from scratch, but also for users of legacy systems. This paper proposes a technique of injecting user code with autonomic primitives by statically analyzing the legacy code and partitioning it to manageable autonomic components. To harvest the benefit of this approach, a transparent underlying autonomic architecture is proposed which requires minimal user interaction to operate. Our goal is to provide users and programmers of such systems with an easy to use environment to work within, fulfilling the vision of autonomic computing

[1]  M. Salehie,et al.  Autonomic computing , 2005, ACM SIGSOFT Softw. Eng. Notes.

[2]  Muga Nishizawa,et al.  An Easy-to-Use Toolkit for Efficient Java Bytecode Translators , 2003, GPCE.

[3]  Yannis Smaragdakis,et al.  J-Orchestra: Automatic Java Application Partitioning , 2002, ECOOP.

[4]  Alessandro Orso,et al.  A technique for dynamic updating of Java software , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[5]  Walter F. Tichy,et al.  Adding autonomic functionality to object-oriented applications , 2003, 14th International Workshop on Database and Expert Systems Applications, 2003. Proceedings..

[6]  Jonathan E. Cook,et al.  Infrastructure for Making Legacy Systems Self-Managed Naoman , 2004 .

[7]  Debzani Deb,et al.  Towards an Automatic Distribution System - Issues and Challenges , 2005, Parallel and Distributed Computing and Networks.

[8]  Gail E. Kaiser,et al.  Kinesthetics eXtreme: an external infrastructure for monitoring distributed legacy systems , 2003, 2003 Autonomic Computing Workshop.

[9]  André Spiegel,et al.  Automatic distribution of object oriented programs , 2002 .

[10]  Petr Jan Horn,et al.  Autonomic Computing: IBM's Perspective on the State of Information Technology , 2001 .

[11]  Shigeru Chiba,et al.  A Bytecode Translator for Distributed Execution of "Legacy" Java Software , 2001, ECOOP.

[12]  Ming Zhang,et al.  Autonomia: an autonomic computing environment , 2003, Conference Proceedings of the 2003 IEEE International Performance, Computing, and Communications Conference, 2003..

[13]  Gail E. Kaiser,et al.  Adding Self-healing capabilities to the Common Language Runtime , 2005 .

[14]  Michael Philippsen,et al.  JavaParty – transparent remote objects in Java , 1997 .

[15]  Jeffrey O. Kephart,et al.  The Vision of Autonomic Computing , 2003, Computer.

[16]  Michael J. Oudshoorn.  Scheduling and Latency-Addressing the Bottleneck , 2003 .

[17]  M. Muztaba Fuad,et al.  AdJava - Automatic Distribution of Java Applications , 2002, ACSC.

[18]  Jorge Lobo,et al.  Policy-based management of networked computing systems , 2005, IEEE Communications Magazine.

[19]  Steve R. White,et al.  Unity: experiences with a prototype autonomic computing system , 2004 .

[20]  Jeffrey O. Kephart,et al.  An architectural approach to autonomic computing , 2004 .

[21]  Joseph L. Hellerstein,et al.  Benchmarking autonomic capabilities: promises and pitfalls , 2004 .

[22]  Zhen Li,et al.  AutoMate: Enabling Autonomic Applications on the Grid , 2006, Cluster Computing.