Process for optimizing accesses to a database

Details Process for optimizing accesses to a database Process for optimizing accesses to a database

1999-06-23

2002-11-19

Rones, Charles L. (Department: 2175)

Data processing: database and file management or data structures

Database design

Data structure types

C707S793000, C707S793000, C707S793000, C707S793000, C707S793000, C709S241000, C709S241000

Reexamination Certificate

active

06484160

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a process for optimizing accesses to a database.
2. Description of Related Art
Information Management Services for access to the information of an MIB (Management Information Base) are based on the CMIS standard (Common Management Information Service, ITU-T recommendation T X.
710
), which describes the operations that can be performed on specified objects in accordance with the model of the GDMO standard (Guidelines for the Definition of Managed Objects, ITU-T recommendation X.
722
).
The present invention uses the information management service in the CMIS standard. This service is attached to the CDSP (CMIS Dispatcher Process) (
FIG. 4
,
42
), which is a service for exchanging CMIS packets between entities of the OpenMaster™ platform. Which is an enterprise management software suite of BULL S.A., a French company, having offices at Louveciennes, France. OpenMaster™ is a total enterprise-wide solution involving security, asset management, application deployment and system and network operations, all linked by an underlying, integrated, open and flexible architecture. Further information regarding OpenMaster™ software suite can be obtained at http://www.openmaster.com. CDSP is a packet router for the management information service, i.e., a system for transferring data between two entities using the same protocol. The management applications call either agents (
43
a
,
43
b
,
43
c
) or local services of the platform that make it possible to locally manage a Management Information Base (MIB) organized hierarchically in the form of an object tree, without network access. In these management information bases (MIB), all the resources are represented in the form of objects in an object tree, as represented in FIG.
2
.
The objects themselves are grouped into classes. An object of a given class has a certain number of attributes, and each object instance has a distinguished name (DN). Addressing is done by means of a distinguished name (DN). For example, the DN of the object (
51
,
FIG. 2
) is “
a/a/b
”.
FIG. 4
represents the operation of an information management service. This service uses a two-level architecture. The first level is constituted by a manager entity (
4
) playing the role of a manager that must display and monitor resources, look up characteristics, etc. The second level is constituted by remote or local agent entities (
43
a
through
43
c
), which maintain the objects to which the operations sent by the manager level are to be applied. The purpose of an agent is to maintain a model of the resource it manages, a standardized model journaled in an MIB. At least one agent is installed in each machine of the network and can control a set of local or remote resources under the direction of one or more managers. A manager communicates with each agent using a standard management protocol. The OpenMaster™ management system marketed by the French company BULL, S.A. comprises one or more managers called ISM (Integrated System Management) and a plurality of agents (ISM Agent). Moreover, other agents marketed by other companies can be controlled by the OpenMaster™ manager via standard protocols.
The manager-agent mechanism is based on an object model in which the modeling of a resource constituted, for example, by elements of the system, software, states, users, etc., is based on an object-oriented approach and structuring of the management information. The “real” equipment of a networked system (a computer, a printer, a circuit, etc.) is represented by abstract objects organized into a management information base (MIB). The characteristics of these objects (the name of a computer, the characteristics of the peripheral equipment, the status of this equipment such as a printer, etc.) are called the attributes of the objects.
The objects are divided into what are most often called MOCs (Managed Object Classes), in which each MOC represents a type of resource. The MOCs define the information that the MIB will contain for each type of resource, i.e., what attributes the object will have. The MOCs can be interpreted as being part of the “schema” of the MIB. The manager records an object class MOC in the GDMO language, and it declares, among other things, the classes, and for each class, a list of attributes, name bindings, etc. This description is recorded in a GDMO object definition module attached to the manager ISM (
41
). Each MOC is instantiated in several MOIs (Managed Object Instances) representing the actual occurrences of this type of resource.
Take the example of three printers (Print
1
, Print
2
, Print
3
) represented by three object instances (P
1
, P
2
, P
3
) in a management information base (MIB). The attributes of the object representing the printer are “printer status” and “user”. It is therefore possible to define an object class MOC “printers” having “printer status” and “user” as its attributes. The object instances (MOIs) of the class “printers” can be the following:
MOI
MOC
ATTRIBUTES
(instance)
Class
printer status
user
Print 1
Printers
activated
none
Print 2
Printers
deactivated
none
Print 3
Printers
activated
Joe
The status of the resource Print activated without the current user in the instantiation of the above example. This example also includes the instances Print
2
and Print
3
. An application such as “ISM Monitor” supplied by the OpenMaster™ management system (
4
) makes it possible to display the MOIs and their statuses. Likewise, ISM Monitor (
46
) can display, in table form, the attributes of any MOI, for example the attributes “printer status” and “current user” for any MOI of the MOC “Printers”.
The entire set of managed objects forms a management information base (MIB).
A sub-tree directly attached to the root of the distinct tree of a management information base (MIB) is called an “MIBlet”. In spite of the division into MIBlets, the management information base (MIB) of the OpenMaster™ management system is recognized as a single composite entity, with all the MIBlets attached to the same MIB. An object MOI at the root of a MIBlet is called a “Rootlet”. The OpenMaster™ manager views the distributed system through the objects of the MIB and the system is controlled by manipulating objects of the MIB and their attributes. The objects are visible via the agents or the object manager attached to the OpenMaster™ manager, which map the equipment in an MIB in the form of an object tree. An agent can represent the status of a piece of equipment via a corresponding associated object represented in the MIB. This mapping can associate an object with several “real” pieces of equipment; likewise, a piece of equipment can be modeled in the form of several objects. The OpenMaster™ manager (
4
) sends commands to the agents (
43
a
through
43
c
) and the agents (
43
a
through
43
c
) send responses to its commands and notify the OpenMaster™ manager (
4
) of events through integrating agents (
45
a
), using a protocol such as SNMP (Simple Network Management Protocol,
45
a
), CMIP (Common Management Information Protocol,
45
b
), or others such as DSAC/AEP (Distributed Systems Administration and Control/Administrative Exchange Protocol) (
45
c
). Each management protocol provides a certain number of simple operations; for example, the protocol CMIP provides all the functions of the CMIS standard, i.e., the following:
the manager (
41
) can read the attributes of an MIB object (the operation M-GET). The agent (
43
) responds to a query M-GET by providing information on the equipment;
the manager (
41
) can modify the attributes of an MIB object (the operation (M-SET). The agent (
43
) modifies the “real” equipment as a function of the new attribute values provided by the manager;
the manager (
41
) can create and delete objects of the MIB (the operations M-CREATE and M-DELETE);
the manager (
41
) can perform an action on an MIB object (the operation M-ACTION). The agent (
43
) performs an action on the equipment as a function of the action requested by the manager

Affiliated with

Also associated with

Rating

Process for optimizing accesses to a database does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Process for optimizing accesses to a database, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Process for optimizing accesses to a database will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2984052