Abstract: A configuration manager federated bean is provided for each host computer in the three-tiered management system. The configuration manager federated bean for a host computer is contacted by federated beans that manage each of the data services when a data service starts and stops using a data storage volume associated with the host computer. The configuration manager bean maintains persistent configuration information for each data service. In one embodiment, configuration manager beans can operate in a clustered environment where several beans store configuration information in a single storage area. Each of the beans implements an arbitration protocol so that only one bean writes to the storage area at any given time.

Abstract: A storage area network (SAN) system that includes a self-contained storage system is managed by a three-tier management system. Management of the self-contained storage system and data services for that system is provided by a three-tiered dedicated management system mirroring the management system that manages the SAN system. In both the SAN management system and the dedicated management system the lowest, or agent, tier comprises Common Information Model (CIM) provider objects that can configure and control the internal components, including the internal switch fabric and disks of both systems. The middle, or logic, tier of the dedicated management system is a set of management facades and federated Java beans. In order to integrate the dedicated management system with the SAN management system, the beans comprising the middle tier of the dedicated management system are also deployed in a shared Jiro™ station associated with the SAN management system.

Abstract: A configuration manager federated bean is provided for each host computer in the three-tiered management system. The configuration manager federated bean for a host computer is contacted by federated beans that manage each of the data services when a data service starts and stops using a data storage volume associated with the host computer. The configuration manager bean maintains persistent configuration information for each data service. In one embodiment, configuration manager beans can operate in a clustered environment where several beans store configuration information in a single storage area. Each of the beans implements an arbitration protocol so that only one bean writes to the storage area at any given time.

Abstract: A configuration manager federated bean is provided for each host computer in the three-tiered management system. The configuration manager federated bean for a host computer is contacted by federated beans that manage each of the data services when a data service starts and stops using a data storage volume associated with the host computer. The configuration manager bean maintains persistent configuration information for each data service. In one embodiment, configuration manager beans can operate in a clustered environment where several beans store configuration information in a single storage area. Each of the beans implements an arbitration protocol so that only one bean writes to the storage area at any given time.

Abstract: SVE management software uses management software running at a central service processor to control storage virtualization engines operating in a plurality application programming interface (API) that allows a consistent control of all SVE facilities by means of a set of API commands. The management software controls a dispatch module that translates the commands into appropriate instructions for the SVE nodes and communicates with the remote SVE nodes by a plurality of node client-node server pairs that transfer instructions from the dispatch module to the remote nodes and transfer requested information back from the remote nodes to the dispatch module. Various interfaces, such as a command line interpreter and a CIM provider can be built using the API commands.

Abstract: Management of data services in a distributed computer system is provided by a three-tiered system. The lowest, or agent, tier comprises Common Information Model (CIM) provider objects that can make method calls on the low-level kernel routines in the host providing the data service. The middle, or logic, tier is a set of management facades and federated Java beans. The federated Java beans include a general configuration bean for data services and configuration and health monitor service beans for each individual data service. The upper, or presentation, tier of the inventive system comprises web-based presentation programs that provide a first view go of the services provided by the federated beans for policy-based management and a second view of the data management facades for element-based management.

Abstract: Dedicated federated beans monitor an event service in a data services management system and sends human-readable messages to people involved in the administration of management services in order to inform the administrators that an event they are interested in has occurred. In one embodiment, the beans each contain a category list indicating which events are of interest to the administrators and the beans cooperate with each other to insure that the category lists in the beans are synchronized. In another embodiment, the federated bean composes and forwards e-mail messages to administrators. In still another embodiment, the federated bean also monitors and reports messages posted to a logging service.

Abstract: A three-tiered data imaging system is used on a distributed computer system comprising hosts connected by a network. The lowest tier comprises management facade software running on each machine that converts a platform-dependent interface written with low-level kernel routines that actually implement the data imaging system to platform-independent method calls. The middle tier is a set of federated Java beans that communicate with each other, with the management facades and with the upper tier of the system. The upper tier of the inventive system comprises presentation programs that can be directly manipulated by management personnel to view and control the system. In one embodiment, the federated Java beans can run on any machine in the system and communicate, via the network. A data imaging management facade runs on selected hosts and at least one data imaging bean also runs on those hosts.

Abstract: A data imaging system is managed by a three-tiered system. The lowest, or agent, tier comprises Common Information Model (CIM) provider objects that reside in the host providing the data imaging service and can make method calls on low-level kernel routines that implement the service. The middle, or logic, tier is a set of federated Java beans that communicate with each other, with the CIM providers and with the upper tier of the system and provide the business logic for the system. The upper, or presentation, tier of the inventive system comprises web-based presentation programs that can be directly manipulated by management personnel to view and control the system from virtually anywhere in the network.

Abstract: In accordance with the principles of the present invention, management of a data replication system is provided by a three-tiered arrangement. The lowest, or agent, tier comprises Common Information Model (CIM) provider objects that reside in the hosts providing the data replication service and that can make method calls on the low-level kernel routines. The middle, or logic, tier is a set of federated Java beans that communicate with each other, with the management facades and with the upper tier of the system. The upper, or presentation, tier of the inventive system comprises web-based presentation programs that can be directly manipulated by management personnel to view and control the data replication system.

Abstract: Data services are managed by a three-tiered system. The lowest tier comprises management facade software running on each machine that converts a platform-dependent interface written with the low-level kernel routines that actually implements the data services to platform-independent method calls. The middle tier is a set of federated Java beans that communicate with the management facades and with the upper tier of the system. The upper tier of the inventive system comprises presentation programs that can be directly manipulated by management personnel to view and control the system.

Abstract: Data volumes on local hosts are discovered and managed by federated Java beans that run on each host. The Java beans form part of a three-tiered data services management. The lowest tier comprises management facade software running on each machine that converts platform-dependent interface written with the low-level kernel routines to platform-independent method calls. The middle tier is a set of federated Java beans that communicate with the management facades and with the upper tier of the system. The upper tier of the inventive system comprises presentation programs that can be directly manipulated by management personnel to view and control the system. The federated beans can configure and control data volumes with either a SCSI terminal emulation interface or a storage volume interface and use a logical disk aggregator to present all volumes available on a local host as a single “logical volume” in which all information regarding the various volumes is presented in a uniform manner.

Abstract: A three-tiered data caching system is used on a distributed computer system comprising hosts connected by a network. The lowest tier comprises management facade software running on each machine that converts a platform-dependent interface written with low-level kernel routines that actually implement the data caching system to platform-independent method calls. The middle tier is a set of federated Java beans that communicate with each other, with the management facades and with the upper tier of the system. The upper tier of the inventive system comprises presentation programs that can be directly manipulated by management personnel to view and control the system. In one embodiment, the federated Java beans can run on any machine in the system and communicate, via the network. A data caching management facade runs on selected hosts and at least one data caching bean also runs on those hosts.

Abstract: A dedicated service finder runs on each host on which data management services run. This service finder caches handles that allow clients to manage the corresponding service and keeps track of other hosts that are also running the service finder. In one embodiment, the service finder registers itself with an existing lookup service so that a client can perform a single lookup for the service finder and then obtain other services from it. Accordingly, only a single lookup is required to obtain all the services running on a specific host. In accordance with another embodiment, the service finder monitors events generated by existing lookup services that occur when other service finders register with the lookup services. In this manner, the service finder can maintain a list of other hosts that have service finders running on them. This arrangement allows a client that has located one service finder to retrieve from that service finder information concerning other hosts and data services running on those hosts.

Abstract: A three-tiered data replication management system is used on a distributed computer system connected by a network. The lowest tier comprises management facade software running on each machine that converts a platform-dependent interface written in low-level kernel routines that actually perform the data replication to platform-independent method calls. The middle tier is a set of federated Java beans, which communicate with each other, with the management facades, and with the upper tier of the system. The upper tier of the inventive system comprises presentation programs that can be directly manipulated by management personnel to view and control the system. The federated Java beans can run on any machine in the system and communicate via the network. A data replication bean runs on each host and at least one such bean communicates directly with a management interface that is controlled by a user.

Abstract: SVE management software uses management software running at a central service processor to control storage virtualization engines operating in a plurality of remote SVE nodes via remote method calls. The management software provides an application programming interface (API) that allows a consistent control of all SVE facilities by means of a set of API commands. The management software controls a dispatch module that translates the commands into appropriate instructions for the SVE nodes and communicates with the remote SVE nodes by a plurality of node client-node server pairs that transfer instructions from the dispatch module to the remote nodes and transfer requested information back from the remote nodes to the dispatch module. Various interfaces, such as a command line interpreter and a CIM provider can be built using the API commands.

Abstract: Information concerning CIM classes and instances used to model a managed system is stored in two hash tables that are built at runtime when instances are added to the system. The first hash table, called a subclass table, identifies the subclasses of each CIM class. The second hash table, called an instance table, identifies the instances in the system for each class. The instance and subclass tables are used to retrieve information concerning the CIM instances. In particular, the instance table is used to retrieve all instances of a particular class and the subclass table is used to determine which classes to examine for instances. In one embodiment, the instance table is a hash table that contains a plurality of hash tables. The first hash table, called the primary instance table, contains key-value pair entries, in each entry the key is a CIM class and the value is a secondary hash table that contains the instances of that CIM class. The secondary hash table also contains key-value pair entries.

Abstract: A storage area network (SAN) system that includes a self-contained storage system is managed by a three-tier management system. Management of the self-contained storage system and data services for that system is provided by a three-tiered dedicated management system mirroring the management system that manages the SAN system. In both the SAN management system and the dedicated management system the lowest, or agent, tier comprises Common Information Model (CIM) provider objects that can configure and control the internal components, including the internal switch fabric and disks of both systems. The middle, or logic, tier of the dedicated management system is a set of management facades and federated Java beans. In order to integrate the dedicated management system with the SAN management system, the beans comprising the middle tier of the dedicated management system are also deployed in a shared Jiro™ station associated with the SAN management system.

Abstract: Management of data services in a distributed computer system is provided by a three-tiered system. The lowest, or agent, tier comprises Common Information Model (CIM) provider objects that can make method calls on the low-level kernel routines in the host providing the data service. The middle, or logic, tier is a set of management facades and federated Java beans. The federated Java beans include a general configuration bean for data services and configuration and health monitor service beans for each individual data service. The upper, or presentation, tier of the inventive system comprises web-based presentation programs that provide a first view go of the services provided by the federated beans for policy-based management and a second view of the data management facades for element-based management.

Abstract: In accordance with the principles of the present invention, management of a data replication system is provided by a three-tiered arrangement. The lowest, or agent, tier comprises Common Information Model (CIM) provider objects that reside in the hosts providing the data replication service and that can make method calls on the low-level kernel routines. The middle, or logic, tier is a set of federated Java beans that communicate with each other, with the management facades and with the upper tier of the system. The upper, or presentation, tier of the inventive system comprises web-based presentation programs that can be directly manipulated by management personnel to view and control the data replication system.