Hari Haranath Madduri

Composition of before/after metaclasses in SOM

In SOM, the IBM System Object Model, a class is a run-time object that defines the behavior of its instances by creating an instance method table. Because classes are objects, their behavior is defined by other classes (called metaclasses). For example, a “Before/After Metaclass” can be used to define the implementation of classes that, by suitable construction of their instance method tables, arrange for each invocation of a method to be preceded by execution of a “before method” and followed by execution of an “after method”. This paper introduces and solves the problem of composing different Before/After Metaclasses in the context of SOM. An enabling element in the solution is SOMs concept of derived metaclasses , i.e., at run-time a SOM system derives the appropriate metaclass of a class based on the classes of its parents and an optional metaclass constraint.

IBM service management architecture

In this paper we describe the IBM Service Management (ISM) architecture, a service-oriented architecture designed to automate and simplify the management of business services. We describe the four major components of ISM: portal-based user interfaces, a process layer that includes the process runtime and service management solutions, an information layer that includes a configuration management database, and operational management products and their integration with service management processes. We describe the way in which the service management solutions are based on industry best practices, and in particular ITIL® (Information Technology Infrastructure Library®). We discuss our experiences implementing ISM and conclude with ideas for future work, including how ISM lays out the groundwork for the future implementation of autonomic functions.

A configuration management database architecture in support of IBM service management

In this paper, we present the architecture of the IBM Tivoli® Change and Configuration Management Database. Its main features include a rich data model, automatic discovery of data for configuration items, visualization of application dependencies on configuration items, and multicustomer support. We discuss implementation topics, such as relationship management, composite configuration items, data federation, reconciliation of data from different sources, a security model for multicustomer support, and integration of change-management and configuration-management processes.

Design of an enablement process for on demand applications

In todays business and economic conditions, enterprise customers are demanding information technology (IT) solutions that are cheaper, less complex, and easier to install. At the same time, independent software vendors (ISVs) are seeing revenue from their core licensed offerings erode because of competition and market saturation. Many believe that the answer to these problems is to offer IT solutions by means of utility computing. Like an electric utility, software applications can be offered as on demand services, and customers pay only for what they use. Creating and implementing such utilities is by no means trivial. It requires some expert help and adherence to established standards and guidelines. In this paper we describe the design of such a process that we call the Application Enablement Program. The process helps ISVs transform their applications into on demand services. This process is structured, repeatable, and globally deployable.

Development of distributed and client/server object-oriented applications (panel): industrial solutions

The panel will discuss emerging “industrial” solutions that help programmers to develop distributed and client/server applications based on objects supporting so-called openness and heterogeneity. The goal of the panel is to help answer the question whether there can be one single solution or whether various (integrated) approaches are needed. The panel will also compare industrial solutions such as COM, DSOM, CORBA and OODCE with results that came out of academia. Finally, a set of questions will be answered by each panelist according to the approach he will propose.

Designing a Cognitive Concierge Service for Hospitals

This paper and associated talk is based on our experience at Jefferson Health implementing a cognitive patient concierge system. In this paper and presentation we describe: how the environmental constraints in a typical hospital (e.g., network security and privacy considerations) affect the design, how to use current speech recognition technologies to deliver acceptable levels of cognitive accuracy, how to connect various sensors and get their data correlated with speech input, how to interface with the hospitals’ information systems and building automation systems (e.g., to control HVAC systems), and how to design for solution enhancement and maintenance. We also illustrate other human factors for placement of microphones, speakers and controls in patient rooms for both ergonomic and hygienic reasons.

A Smart Road Maintenance System for Cities - An Evolutionary Approach

One of the biggest challenges faced by cities today is maintaining their roads. Smart Road Maintenance can lead to more operational efficiency, timely response to citizens, and cost-effectiveness. Efficient and effective management and maintenance of a city’s road infrastructure not only improves the quality of life for its citizens, but also makes the city more attractive for business investment. The IBM Krakow SWG Laboratory, in the cooperation with AGH University of Science & Technology, Krakow and the city of Krakow, created an innovative solution for road maintenance problems. In this paper we describe the challenges currently faced by many cities in road maintenance and how one could bring low-cost, ubiquitous technology to help cope with those challenges. This project also exemplifies the Smarter Planet/Smarter Cities initiatives being promoted by IBM worldwide.

The future of distributed object computing (Panel Session)

In order for users to deploy mission-critical applications using distributed object technology, the fragility of ORB implementations is a concern. Also, practical considerations dictate that customers have to deploy objects on existing heterogeneous collections of machines. Therefore, out of necessity, more robust, scalable, and interoperable ORBS will be developed. BIO: Hari Madduri received his M.S. and Ph.D.(‘85) degrees in Computer Science from the University of Wisconsin-Madison. He has worked on distributed systems, object oriented systems, and fault tolerance for over a decade. He was at Honeywell Research (Minneapolis) for five years working on various distributed systems projects. After joining IBM in April 1990 he worked on an advanced technology project aimed at building an object-oriented compound document toolkit (SOM grew out of this project) as an architect/designer. After that, he worked as the lead architect/designer of the Replication Framework component of the SOM Objects Toolkit. He is currently the lead designer and architect for the next release of DSOM.