Browse Prior Art Database

Method for Simulating Hardware in a Server Management Application

IP.com Disclosure Number: IPCOM000015317D
Original Publication Date: 2001-Dec-07
Included in the Prior Art Database: 2003-Jun-20
Document File: 3 page(s) / 81K

Publishing Venue

IBM

Abstract

Disclosed is a software architecture for simulating hardware in a computer management application. The design allows virtual and actual hardware components to appear simultaneously in an application.

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

Page 1 of 3

Method for Simulating Hardware in a Server Management Application

Disclosed is a software architecture for simulating hardware in a computer management application. The design allows virtual and actual hardware components to appear simultaneously in an application.

Designing a hardware management application is often difficult due to not only the number of hardware variants supported, but also the number of boundary conditions imposed by each variant. In developing such an application, it is generally impractical to assemble each hardware combination for testing. Furthermore, some would-be users of the software tool, such as documentation editors, help center personnel, recruiters, sales people, etc, may have no access to the managed hardware. It is therefore highly beneficial to be able to simulate hardware in the management tool. This capability is implemented in ServeRAID Manager, an object-oriented, Java-based application used to configure and monitor ServeRAID adapters.

ServeRAID Manager is a tool for configuring and monitoring RAID adapters in an IBM server. The program uses a client-server architecture, so the management console may be separated from the agent portion that is always co-located with the RAID adapters. The agent is pure Java, but it must use DLLs to communicate with the RAID drivers. The simulation engine is located at the lowest layer of the Java agent, just above the DLLs (Figure 1). This layer uses a parallel set of objects, each of which...