US8311977B2 - Information processing apparatus - Google Patents

Information processing apparatus Download PDF

Info

Publication number
US8311977B2
US8311977B2 US12397927 US39792709A US8311977B2 US 8311977 B2 US8311977 B2 US 8311977B2 US 12397927 US12397927 US 12397927 US 39792709 A US39792709 A US 39792709A US 8311977 B2 US8311977 B2 US 8311977B2
Authority
US
Grant status
Grant
Patent type
Prior art keywords
attribute information
reliability
plurality
degree
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US12397927
Other versions
US20090228506A1 (en )
Inventor
Yuji Wada
Akira Katsuno
Yasuhide Matsumoto
Masazumi Matsubara
Kuniaki Shimada
Yukihiro Watanabe
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Grant date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0866Checking configuration
    • H04L41/0873Checking configuration by checking configuration conflicts with other network elements
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30286Information retrieval; Database structures therefor ; File system structures therefor in structured data stores
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/024Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0803Configuration setting of network or network elements
    • H04L41/0823Configuration optimization
    • H04L41/0836Configuration optimization to enhance reliability, e.g. reduce downtime
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/085Keeping track of network configuration
    • H04L41/0853Keeping track of network configuration by actively collecting or retrieving configuration information

Abstract

An information processing apparatus for managing attribute information as to resources constituting a system includes an acquisition unit which obtains a plurality of attribute information as to the same resources, a degree of reliability calculation unit which calculates, when a contradiction exists between the plurality of attribute information obtained by the acquisition unit, a degree of reliability as to each of the plurality of attribute information, and an attribute information determination unit which sets the attribute information, which has the highest degree of reliability calculated by the degree of reliability calculation unit, as attribute information as to the resources.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2008-059425, filed on Mar. 10, 2008, the entire contents of which are incorporated herein by reference.

FIELD

The embodiment discussed herein is related to an information processing apparatus, an information processing program, and an information processing method for managing attribute information as to resources constituting a system.

BACKGROUND

A database called an F-CMDB (Federated Configuration Management Database) is known. The F-CMDB manages all the information as to components of an information system by virtually integrating different types of databases which manage information.

As shown in FIG. 19, the F-CMDB enables a manipulation to be cross-sectionally executed to an arrangement information DB, an incident information DB, a trouble information DB, a release information DB, a change information DB, and an application information DB which are a plurality of virtually integrated databases. Each of the plurality of integrated databases manages CI (configuration item) which is attribute information about the resources that constitutes the system (equipment) and relationship between the information.

Further, as shown in FIG. 20, the F-CMDB has a reconciliation function. The reconciliation function adjusts information by managing the information of the same items, which are managed by a different name and a different local ID in each virtually integrated database, using a unique ID which can be commonly used for all the virtually integrated databases and integrating names.

However, when the information of the same CIs are integrated by the reconciliation function described above, there is a problem in that a plurality of information are registered as to the same CIs as well as a contradiction arises when the information, for example, the capacities of HDDs in the same CIs are different between the above information as shown in FIG. 21.

SUMMARY

According to an aspect of an embodiment of the invention, an information processing apparatus for managing attribute information as to resources constituting a system includes an acquisition unit which obtains a plurality of attribute information as to the same resources, a degree of reliability calculation unit which calculates, when a contradiction exists between the plurality of attribute information obtained by the acquisition unit, a degree of reliability as to each of the plurality of attribute information, and an attribute information determination unit which sets the attribute information, which has the highest degree of reliability calculated by the degree of reliability calculation unit, as attribute information as to the resources.

The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram showing an arrangement of an F-CMDB according to an embodiment;

FIG. 2 is a view showing state of use information;

FIG. 3 is a view showing property information;

FIG. 4 is a view showing information of a matching method;

FIG. 5 is a view showing information of a degree of a reliability selection standard;

FIG. 6 is a view showing information of an overall operation result;

FIG. 7 is a flowchart showing an operation of a manipulation execution unit;

FIG. 8 is a flowchart showing an operation of a relationship evaluation process;

FIG. 9 is a flowchart explaining an operation of a priority update process;

FIG. 10 is a view showing a difference of CI according to a priority update process and the attribute thereof;

FIG. 11 is a flowchart showing an operation of an operation result acquisition process;

FIG. 12 is a view showing CI having a standard arrangement and the relationship thereof;

FIG. 13 is a view showing CI having a non-standard arrangement and the relationship thereof;

FIG. 14 is a view showing an indirect relation in the F-CMDB;

FIG. 15 is a view showing the number of information related to CI;

FIG. 16 is a view showing CI that is altered based on the number of manipulations;

FIG. 17 is a flowchart showing an operation of a property evaluation process; and

FIG. 18 is a view showing a specific example of the property evaluation process.

FIG. 19 is a view showing a conventional F-CMDB;

FIG. 20 is a view showing a reconciliation function; and

FIG. 21 is a view showing a problem in a conventional reconciliation function.

DESCRIPTION OF EMBODIMENT

An embodiment of the present invention will be explained below referring to the drawings.

First, an arrangement of an F-CMDB according to the embodiment will be explained. FIG. 1 is a block diagram showing the arrangement of the F-CMDB according to the embodiment.

The F-CMDB 10 has a manipulation execution unit 101 (acquisition unit), a matching execution unit 102, a reliability evaluation unit 103 (reliability calculation unit, statistic amount calculation unit, attribute information determination unit, selection unit), a data management unit 104, and an operation result acquisition unit 105. Further, the F-CMDB 10 is connected to a plurality of databases (not shown) for managing the information of items constituting a system through a network. The F-CMDB10 integrates the information of the same items managed by a different local ID in these databases. Further, a terminal 20 requests F-CMDB information, which is information as to a system that is matched and arranged by the F-CMDB 10.

The manipulation execution unit 101 requests the matching execution unit 102 to make matching and requests the reliability evaluation unit 103 to update the F-CMDB information.

The matching execution unit 102 requests the reliability evaluation unit 103 to execute a reliability evaluation process to be described later.

The reliability evaluation unit 103 executes the reliability evaluation process based on a degree of reliability selection standard 110 to be described later.

The data management unit 104 manages F-CMDB information 106, which manages CI and Relationship registered or updated by a resource, state of use information 107, property information 108, and matching method information 109.

Further, the operation result acquisition unit 105 obtains overall operation result information 111 to be described later based on an operation result acquisition request from the reliability evaluation unit 103.

Next, the state of use information will be explained. FIG. 2 is a view showing the state of use information.

The state of use information 107 is information to which the following information is caused to correspond:

CI/Relationship ID, which includes local ID showing CI or Relationship (CI: CI1, CI2, . . . . , Relationship: Rel1, Rel2, . . . );

the number of times of manipulation, which is the number of times at which CI or Relationship is referred to; and

a update date, which is a date on which CI or Relationship is changed.

Note that it is assumed that the number of times of use and the update date are managed in the respective databases managed by the F-CMDB 10, and that the data management unit 104 obtains these information items through the operation result acquisition unit 105.

Next, the property information will be explained. FIG. 3 is a view showing the property information.

The property information 108 is information to which the following information items are caused to correspond:

CI/Relationship ID;

an attribute name showing the attribute of CI or Relationship;

a property of the attribute (determination standard for determining a numerical value in the attribute); and

a specific matching method.

Next, the matching method information will be explained. FIG. 4 is a view showing the matching method information.

Further, the matching method information 109 is information to which the following information is caused to correspond:

matching method names which are the names added to respective matching methods; and

matching procedures which are the specific procedures of the matching methods.

Note that although the matching procedure is described by a natural language in FIG. 4 for the purpose of explanation, an actually described language is a language which can be interpreted by the F-CMDB 10. Further, although it is described in the matching procedure that “procedure 1 is called”, this shows a call for a predetermined procedure (program).

Further, in the matching method in the property information 108, when a logic function, which is previously assembled to the F-CMDB 10, is executed, it is shown by “-” and when the matching method information 109 is referred to, a matching method name in the matching method information 109 is described.

Next, the degree of reliability selection standard 110 will be explained. FIG. 5 is a view showing the degree of reliability selection standard.

The degree of reliability selection standard 110 is information in which a degree of reliability standard is caused to correspond to the priority of the standard. The degree of reliability standard is a rule to decide which “is right” among two information (CI or Relationship). The priority of the standard is the reliability of the rule (that is to say, priority). Although the degree of reliability standard includes matching to an operation result to be described later, presence or absence of an operation result, the number of related information (the number of Relationships), the number of times of manipulation, a update date, and the like, any degree of reliability standards other than the above standards may be provided. A priority is set to each of these standards of degree of reliability, and it is assumed in the embodiment that a standard having a larger value has a higher priority. Further, although this point is added by the reliability evaluation unit 103 when it satisfies a predetermined condition, this will be described later.

Next, the overall operation result information 111 will be explained. FIG. 6 is a view showing overall operation result information.

In the overall operation result information 111, resource names, which are the names of the resources constituting the system, are caused to correspond to the attributes of the resources. The overall operation result information 111 is used when “the matching to the operation result” and “the presence or absence of the operation result” are judged and may be previously prepared or created using any tool. Further, the resource names in the overall operation result information 111 are the names on the system, and the attributes corresponding to the respective resource names are the real device information of the devices themselves as the resources of the system managed by the F-CMDB 10. Specifically, the resource names are the names of the devices, IP addresses, vendors, and the like.

Next, an operation of the F-CMDB according to the present embodiment will be explained. FIG. 7 is a flowchart showing an operation of the manipulation execution unit.

First, when the manipulation execution unit 101 receives a request for registering or updating information D, for example CI of a resource A (S101), it determines whether or not information d, which is CI, exists in the same resource A as that of the information D in the F-CMDB information 106 (S102).

When the information d exists in the F-CMDB information 106 (S102, YES), the manipulation execution unit 101 determines whether or not the information D contradicts the information d (S103).

When the information D contradicts the information d (S103, YES), the manipulation execution unit 101 requests the matching execution unit 102 to solve the contradiction between the information D and the information d (S104).

In contrast, when the information D does not contradict the information d (S103, NO), the manipulation execution unit 101 requests the matching execution unit 102 to merge the information D with the information d (S105).

Further, when it is determined at step S102 that the information d does not exist in the F-CMDB information 106 (S102, NO), the manipulation execution unit 101 registers the information D to the F-CMDB information 106 as CI of the resource A through the data management unit 104 (S106).

As described above, when a contradiction exists between the already existing information d and the information D, which is new information as to the same resource as that of the information d, the manipulation execution unit 101 executes matching to solve the contradiction. Note that when the matching execution unit 102 receives a request for merging, it integrates the information D and the information d, and when the matching execution unit 102 receives a request for matching, it requests the reliability evaluation unit 103 to execute the reliability evaluation process.

FIG. 8 is a flowchart showing an operation of the reliability evaluation process. It is assumed in FIG. 8 that the reliability evaluation unit has already requested execution of the reliability evaluation process. Further, although the number of CIs to be compared is set to two pieces D1 and D2 for the purpose of explanation, any number of CIs may be set as the objects to be compared.

First, the reliability evaluation unit 103, which receives the request for the reliability evaluation, selects a standard R having the highest priority value of the unprocessed standards of degree of reliability in the degree of reliability selection standard 110 (FIG. 5) (S201) and determines whether or not the standard R exists, that is, whether or not a selection standard to be selected does not exist (S202).

When the selection standard to be selected exists (S202, NO), the reliability evaluation unit 103 calculates the degree of reliability r1 of D1 and the degree of reliability r2 of D2 respectively, based on the standard R determined at step S201 (S203), and judges whether r1 is larger than r2 (S204).

When r1 is larger than r2 (S204, YES), the reliability evaluation unit 103 determines that D1 is correct (S205).

In contrast, when the r1 is equal to or smaller than the r2 (S204, NO), the reliability evaluation unit 103 determines whether the r1 is smaller than the r2 (S206).

When the r1 is smaller than the r2 (S206, YES), the reliability evaluation unit 103 determines that D2 is correct (S207).

In contrast, when the r1 is equal to or larger than the r2 (S206, NO), since r1≧r2 as well as r1≦r2, that is r1=r2, the reliability evaluation unit 103 selects a standard R which has the highest priority value of the unprocessed standards of degree of reliability in the degree of reliability selection standard 110 again (S201).

Further, when no selection standard to be selected exists in the determination at step S202 (S202: YES), that is, r1=r2 is established in all the standards in the degree of reliability selection standards, the reliability evaluation unit 103 determines that D1 is as correct as D2 (S208).

As described above, the reliability evaluation unit 103 compares the degrees of reliability of two CIs (D1, D2) between which a contradiction exists from a standard having a high degree of priority in the degree of reliability selection standard 110. When they have the same degree of reliability, the reliability evaluation unit 103 compares the CIs by a standard having a next highest priority. The comparison may be performed as to attributes which contradict each other in CIs (for example, the capacity and the amount of memory of the HDD). Further, when D1 is as correct as D2, a user is informed that D1 and D2 cannot be matched or they are matched by another matching method. The other matching method will be described later.

Note that the priority is not fixed at all times and is updated by the reliability evaluation unit 103 with a result that the priority of the standard of degree of reliability is changed.

FIG. 9 is a flowchart explaining an operation of a priority update process. Further, FIG. 10 is a view showing the difference of CIs subjected to the priority update process and the attribute thereof.

First, the reliability evaluation unit 103 determines the difference D of updated D1 and D2 (S301) and sequentially fetches the information A of the updated attributes from the determined difference D one by one (S302). Specifically, when the capacity of the HDD and OS are changed from the attribute of D1 to the attribute of D2 because D1 is matched with D2 as shown in FIG. 10, the HDD changed from 300 GB to 500 GB and the OS changed from OS 1 to OS 2 correspond to the information A, respectively.

Next, the reliability evaluation unit 103 determines whether or not the information A exists in the difference D (S303).

When the information A exists in the difference D (S303, NO), the reliability evaluation unit 103 examines a standard R relating to the change of the information A (S304) and determines whether or not the standard R exists (S305).

When the standard R exists (S305, YES), the reliability evaluation unit 103 increases the priority of the standard R relating to the change of the information A (S306), and sequentially fetches the information A of the updated attributes again from the difference D one by one (S302).

In contrast, when the standard R does not exist (S305, NO), the reliability evaluation unit 103 sequentially fetches the information A of the updated attributes again from the difference D one by one (S302).

Further, when it is determined at step S303 that the information A does not exist in the difference D (S303, YES), the reliability evaluation unit 103 finishes the priority update process.

As described above, the contradiction can be solved based on a standard having a higher degree of reliability of the matching standards for solving the contradiction by updating the priority of the degree of reliability selection standard 110.

Next, the standard of the degree of reliability selection standard 110 will be explained. As shown in FIG. 5, the standard of degree of reliability includes “the matching to the operation result”, “the presence or absence of operation result”, “the number of related information”, “the number of times of manipulation”, and “the alteration date”. First, “the matching to the operation result” and “the presence or absence of the operation result” in these standards of degree of reliability will be explained. FIG. 11 is a flowchart showing an operation of the operation result acquisition process.

When “the matching to the operation result” is selected from the degree of reliability selection standard 110 as the standard of degree of reliability at step S201 of the reliability evaluation process, the reliability evaluation unit 103 requests the operation result acquisition unit 105 to obtain an operation result. The operation result acquisition unit 105, which receives the request for obtaining the operation result, reads out the real device information held by the F-CMDB 10 first (S401) reads out operation result information as to the resource from the overall operation result information 111 (S402) collects the operation result information as to the resource from the network using, for example, a protocol such as SNMP (Simple Network Management Protocol) (S403) and then merges the real device information with the operation result information (S404).

Note that the operation result information as the merged result may be stored in the overall operation result information 111 again. Further, the operation result information may be obtained by any method without executing steps S401 to S403 at all. Further, when the operation result information can not be obtained by a process having a high priority by adding a priority to the processes at steps S401 to S403, the operation result information may be obtained by a process having the next highest priority.

The reliability evaluation unit 103 judges “the matching to the operation result” and “the presence or absence of the operation result” based on the operation result information obtained as described above.

When the degree of reliability is determined based on “the matching to the operation result”, if “CI: a server 1” in FIG. 12 is CI whose degree of reliability has been determined, it is assumed that a higher degree of reliability can be obtained when the real device information of “CI: the server 1” is better matched to the attribute corresponding to the server 1 in the overall operation result information 111 (FIG. 6) (for example, a name agrees with an IP address). Further, when the CI whose degree of reliability has been determined is the “CI: the server 1” which has the non-standard arrangement as shown in FIG. 13, the degree of reliability is determined depending on how much the real device information of the related “CI: the server 1” is matched to the attribute corresponding to the server 1 in the overall operation result information 111. Further, it is assumed that when the real device information of “CI: software 1” related to “CI: server 1” is better matched with the real device information (not shown) of the software 1 in the overall operation result information 111, the degree of reliability is higher.

Note that when the degree of reliability is determined based on these standards of degree of reliability, the CI, which is related to the CI whose degree of reliability has been determined, need not to be directly related thereto and may be CI related to CI which is related as shown in, for example FIG. 14, that is, may be indirectly related CI.

Next, “the number of related information” as the standard of degree of reliability will be explained. FIG. 15 is a view showing the number of information related to CI.

Further, when the degree of reliability is determined based on “the number of related information”, the reliability evaluation unit 103 compares the amount of information (the number of Relationships) related to the D1, which is the CI already registered to the F-CMDB information 106, with the number of Relationships of the D2 (which is the newly registered CI), and employs the CI having a larger number of them as correct information, as shown in FIG. 15.

Next, “the number of times of manipulation” and “the updated date” as the standard of degree of reliability will be explained. FIG. 16 is a view showing CI altered based on the number of times of operation.

When the degree of reliability is determined based on “the number of times of manipulation”, the reliability evaluation unit 103 refers to the state of use information 107 managed by the data management unit 104, compares the number of times of manipulation of the D1, which is the CI already registered to the F-CMDB 106, with that of the D2, which is newly registered CI in the state of use information 107, and employs the CI having a larger number of manipulations as correct information, as shown in FIG. 16. This standard is effective in a system in which CI (which is manipulated, that is, referred to a larger number of times) has a higher probability that it is correct information.

Further, when the degree of reliability is determined based on “the updated date” and when the degree of reliability is determined based on “the number of times of manipulation”, the reliability evaluation unit 103 refers to the state of use information 107 managed by the data management unit 104, compares the updated date of the D1, which is the CI already registered to the F-CMDB information 106, with that of the D2, which is newly registered CI in the state of use information 107, and employs the CI having the new updated date as correct information. This standard is effective in a system in which newer information has a high probability that it is correct information. Further, a system, in which newer information has a low probability that it is correct information, may be arranged such that the CI, which is manipulated a larger number of times as well as is older, has a higher degree of reliability, in addition to the number of times of manipulation. This is because when information is not updated regardless of whether it has been referred to (manipulated), it has a higher probability that it is correct information.

Matching based on the degree of reliability of the CIs which contradict each other has been explained above. The reliability evaluation unit 103 also matches the CIs based on the property of attribute of the property information 108 (FIG. 3). Next, a property evaluation process executed by the reliability evaluation unit 103 will be explained. FIG. 17 is a flowchart showing an operation of the property evaluation process. It is assumed in FIG. 17 that the reliability evaluation unit 103 received a reliability evaluation request from the matching execution unit 102.

First, the reliability evaluation unit 103 determines a group A of attributes which contradict each other in different CIs (S501), fetches contradict attribute a from the group A (S502), and determines whether or not the attribute a exists (S503).

When the attribute a exists (S503, NO), the reliability evaluation unit 103 refers to the property information 108, determines a method of determining the correct values of the attribute a (S504), refers to a matching method information, determines the correct values of the attribute a by a matching procedure corresponding to a matching method corresponding to the method of determining the correct values (S505), and determines whether or not the attribute a exists again (S503).

In contrast, when the attribute a does not exist, (S503, YES), the reliability evaluation unit 103 finishes the property evaluation process.

Note that FIG. 18 specifically explains the process described above. FIG. 18 is a view showing a specific example of the property evaluation process.

When CIs which contradict each other exist, the reliability evaluation unit 103 selects HDDs and Memories as the group A of the attributes which contradict each other, refers to the property information 108, determines calculation of a minimum value as the matching method of the HDD, and executes a matching procedure corresponding to the calculation of the minimum value of the “HDD: 300 GB” and the “HDD: 500 GB,” by referring to the matching method information 109. Further, the reliability evaluation unit 103 refers to the property information 108 again and calculates the maximum values of Memory: 1 GB and Memory: 2 GB by a logic function previously assembled by the system because the matching method of Memories is “-”. It means matching procedure is not specified.

The reliability evaluation unit 103 calculates more correct values by the property previously set to the attributes as described above. The process may be executed before or after the reliability evaluation process. Further, the reliability evaluation unit 103 may use any of the reliability evaluation process and the property evaluation process, depending on an attribute when the contradiction in a plurality of CIs is solved. For example, since a correct value must be determined as to the type of OS by the reliability evaluation process and a peak load, a maximum power consumption, and the like must be derived from the values of a plurality of CIs, correct values are calculated by the property evaluation process so that the reliability evaluation unit 103 can employ information having a high probability as correct information in all the attributes included in the CIs.

A program implementing the embodiments may be recorded on computer-readable media comprising computer-readable recording media. Examples of the computer-readable recording media include a magnetic recording apparatus, an optical disk, a magneto-optical disk, and/or a semiconductor memory (for example, RAM, ROM, etc.). Examples of the magnetic recording apparatus include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape (MT). Examples of the optical disk include a DVD (Digital Versatile Disc), a DVD-RAM, a CD-ROM (Compact Disc-Read Only Memory), and a CD-R (Recordable)/RW.

All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiment(s) of the present inventions have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.

Claims (17)

1. An information processing apparatus of an Federated Configuration Management database for managing attribute information of hardware or software application resources constituting a computer system, the information processing apparatus comprising a processor to execute a process including:
obtaining a plurality of attribute information of the same hardware and software application resources;
calculating, when a contradiction exists among the plurality of attribute information obtained by the acquisition unit, a degree of reliability for each of the plurality of attribute information; and
setting the attribute information, which has a highest degree of reliability calculated by the calculating procedure, to be the attribute information of the hardware and software application resources,
wherein the processor sets a plurality of processes for calculating a degree of reliability, adds a priority to each of the plurality of processes, and calculates the degree of reliability by a process to which the highest priority is added in the plurality of processes and where as long as the processor, using the highest priority process of the plurality of processes, calculates a plurality of contradictory attribute information as being equally reliable, that highest priority process is removed from the plurality of processes and the reliability is recalculated, whereas when the plurality of contradictory attribute information do not have the same level of reliability, the processor changes the priority of the process that calculated the degree of reliability.
2. The information processing apparatus according to claim 1, wherein the processor calculates, when a contradiction exists among the plurality of attribute information, a statistic amount of the plurality of attribute information based on the attribute of the attribute information, wherein the processor determines the statistic amount of the attribute information of the hardware and software application resources.
3. The information processing apparatus according to claim 1, wherein the plurality of processes include a process for calculating a matching property of fixed attribute information as the degree of reliability of the attribute information whose degree of reliability is being calculated.
4. The information processing apparatus according to claim 1, wherein the attribute information is related to other attribute information, and
the plurality of processes include a process for calculating a number of the attribute information related to the attribute information whose degree of reliability is being calculated as the degree of reliability.
5. The information processing apparatus of claim 1, wherein the degree of reliability is calculated based on at least one of an updated date of the attribute information, a number indicating how many times the attribute information is referred to, a number indicating how many relationships the attribute information has, or a degree of matching with operation result information of the hardware or software application.
6. The information processing apparatus according to claim 2, wherein the processor selects either calculation of the degree of reliability executed by the processor or calculation of the statistic amount executed by the processor based on the attribute of the attribute information.
7. A non-transitory computer readable recording medium recording an information processing program causing a computer to execute a process comprising:
obtaining a plurality of attribute information regarding resources of the computer;
calculating, when a contradiction exists among the plurality of attribute information, a degree of reliability for each of the plurality of attribute information; and
determining the attribute information, which has a highest degree of reliability, as the attribute information of the resources,
wherein the calculating sets a plurality of processes for calculating the degree of reliability, adds a priority to each of the plurality of processes, and calculates the degree of reliability by a process to which the highest priority process is added in the plurality of processes, and where as long as the reliability calculation unit, using the highest priority process of the plurality of processes, calculates a plurality of contradictory attribute information as being equally reliable, that highest priority process is removed from the plurality of processes and the reliability is recalculated, whereas when the plurality of contradictory attribute information do not have the same level of reliability, the degree of reliability calculation unit changes the priority of the process that calculated the degree of reliability.
8. The computer readable recording medium recording an information processing program according to claim 7, the process further comprising
calculating, when a contradiction exists between the plurality of attribute information, a statistic amount of the plurality of attribute information based on the attribute of the attribute information,
wherein the determining determines the statistic amount as the attribute information of the resources.
9. The computer readable recording medium recording an information processing program according to claim 7, wherein the plurality of processes include a process for calculating a matching property of fixed attribute information as the degree of reliability of the attribute information whose degree of reliability is being calculated.
10. The computer readable recording medium recording an information processing program according to claim 7, wherein the attribute information is related to other attribute information, and
the plurality of processes include a process for calculating a number of the attribute information related to the attribute information whose degree of reliability is being calculated as the degree of reliability.
11. The computer readable recording medium recording an information processing program according to claim 7, wherein the degree of reliability is calculated based on at least one of an updated date of the attribute information, a number indicating how many times the attribute information is referred to, a number indicating how many relationships the attribute information has, or a degree of matching with operation result information of the hardware or software application.
12. The computer readable recording medium recording an information processing program according to claim 8, further comprising selecting either calculating the degree of reliability or calculating the statistic amount based on the attribute of the attribute information.
13. An information processing method of managing attribute information of hardware and software application resources of a computer system, comprising:
obtaining, by a computer processor, a plurality of attribute information of the same resources;
calculating, by the computer processor, when a contradiction exists among the plurality of attribute information, a degree of reliability for each of the plurality of attribute information; and
determining the attribute information which has a highest degree of reliability to be the attribute information of the resources,
wherein the calculating sets a plurality of processes for calculating the degree of reliability, adds a priority to each of the plurality of processes, and calculates the degree of reliability by a process to which the highest priority process is added in the plurality of processes, and where as long as the reliability calculation unit, using the highest priority process of the plurality of processes, calculates a plurality of contradictory attribute information as being equally reliable, that highest priority process is removed from the plurality of processes and the reliability is recalculated, whereas when the plurality of contradictory attribute information do not have the same level of reliability, the degree of reliability calculation unit changes the priority of the process that calculated the degree of reliability.
14. The information processing method according to claim 13, further comprising
calculating, when a contradiction exists among the plurality of attribute information, a statistic amount of the plurality of attribute information based on an attribute of the attribute information,
wherein the determining determines the statistic amount of the attribute information of the hardware and software application resources.
15. The information processing method according to claim 13, wherein the plurality of processes include a process for calculating a matching property of fixed attribute information as the degree of reliability of the attribute information whose degree of reliability is being calculated.
16. The information processing method according to claim 13, wherein the attribute information is related to other attribute information, and
the plurality of processes include a process for calculating a number of the attribute information related to the attribute information whose degree of reliability is being calculated as the degree of reliability.
17. The information processing method according to claim 13, wherein the degree of reliability is calculated based on at least one of an updated date of the attribute information, a number indicating how many times the attribute information is referred to, a number indicating how many relationships the attribute information has, or a degree of matching with operation result information of the hardware or software application.
US12397927 2008-03-10 2009-03-04 Information processing apparatus Expired - Fee Related US8311977B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2008059425A JP2009217455A (en) 2008-03-10 2008-03-10 Information processor, information processing program, and method
JP2008-059425 2008-03-10

Publications (2)

Publication Number Publication Date
US20090228506A1 true US20090228506A1 (en) 2009-09-10
US8311977B2 true US8311977B2 (en) 2012-11-13

Family

ID=40600621

Family Applications (1)

Application Number Title Priority Date Filing Date
US12397927 Expired - Fee Related US8311977B2 (en) 2008-03-10 2009-03-04 Information processing apparatus

Country Status (3)

Country Link
US (1) US8311977B2 (en)
JP (1) JP2009217455A (en)
GB (1) GB0903894D0 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110161353A1 (en) * 2009-12-28 2011-06-30 Fujitsu Limited Management device and management method

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5146020B2 (en) * 2008-03-10 2013-02-20 富士通株式会社 The information processing apparatus, resource identification program, resource identification method
US8799436B2 (en) * 2009-07-14 2014-08-05 International Business Machines Corporation System and method for automated configuration control, audit verification and process analytics
JP2011248661A (en) * 2010-05-27 2011-12-08 Sharp Corp Database control device, database control method, program and recording medium
US8645543B2 (en) 2010-10-13 2014-02-04 International Business Machines Corporation Managing and reconciling information technology assets in a configuration database
WO2013111330A1 (en) * 2012-01-27 2013-08-01 富士通株式会社 Information processing method, device and program
US9338057B2 (en) * 2013-10-30 2016-05-10 Netapp, Inc. Techniques for searching data associated with devices in a heterogeneous data center

Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5440738A (en) 1991-05-16 1995-08-08 Tally Systems Corporation Method and apparatus for digital data processor file configuration detection
US6205478B1 (en) * 1998-07-08 2001-03-20 Fujitsu Limited System for exchanging user information among users
US20030140087A1 (en) * 2002-07-30 2003-07-24 Patrick Lincoln Systems and methods for negotiated resource utilization
US6675149B1 (en) * 1998-11-02 2004-01-06 International Business Machines Corporation Information technology project assessment method, system and program product
US6766318B1 (en) * 1999-03-11 2004-07-20 Oracle International Corporation Approach for collecting statistical information in information systems
US20040153435A1 (en) * 2003-01-30 2004-08-05 Decode Genetics Ehf. Method and system for defining sets by querying relational data using a set definition language
US20040179528A1 (en) * 2003-03-11 2004-09-16 Powers Jason Dean Evaluating and allocating system resources to improve resource utilization
US20050172162A1 (en) * 2002-12-26 2005-08-04 Fujitsu Limited Operation management method and operation management server
US20060174132A1 (en) * 2003-02-20 2006-08-03 Bea Systems, Inc. Federated management of content repositories
JP2006318371A (en) 2005-05-16 2006-11-24 Nippon Telegr & Teleph Corp <Ntt> Device and method for detecting data inconsistency
US20060288413A1 (en) * 2005-06-17 2006-12-21 Fujitsu Limited Intrusion detection and prevention system
US20070038587A1 (en) * 2005-07-27 2007-02-15 Fujitsu Limited Predicting apparatus, predicting method, and computer product
US7181471B1 (en) * 1999-11-01 2007-02-20 Fujitsu Limited Fact data unifying method and apparatus
US20070112769A1 (en) * 2005-11-14 2007-05-17 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20070174346A1 (en) * 2006-01-18 2007-07-26 Brown Douglas P Closed-loop validator
US20070200908A1 (en) * 2006-02-24 2007-08-30 Seiko Epson Corporation Image Forming Apparatus and a Method of Controlling the Image Forming Apparatus
US20070203952A1 (en) * 2006-02-28 2007-08-30 Microsoft Corporation Configuration management database state model
WO2007115940A1 (en) 2006-04-11 2007-10-18 International Business Machines Corporation Weighted determination in configuration management systems
US20070283206A1 (en) * 2006-05-15 2007-12-06 Fujitsu Limited Reliability evaluation device, Reliability evaluation method, and computer program product
US20070282856A1 (en) * 2006-04-28 2007-12-06 Bmc Software, Inc. Database Application Federation
US7360219B2 (en) * 2002-12-13 2008-04-15 Hewlett-Packard Development Company, L.P. Systems and methods for facilitating fair and efficient scheduling of processes among multiple resources in a computer system
US20080114870A1 (en) * 2006-11-10 2008-05-15 Xiaoyan Pu Apparatus, system, and method for generating a resource utilization description for a parallel data processing system
US20080114770A1 (en) * 2006-11-14 2008-05-15 Jinfang Chen Attribute level federation from multiple data sources
US20080177688A1 (en) * 2006-09-07 2008-07-24 Friedlander Robert R System and method for managing a chaotic event by providing optimal and adaptive sequencing of decision sets with supporting data
US20080183690A1 (en) * 2007-01-26 2008-07-31 Ramachandran Puthukode G Method for providing assistance in making change decisions in a configurable managed environment
US7409586B1 (en) * 2004-12-09 2008-08-05 Symantec Operating Corporation System and method for handling a storage resource error condition based on priority information
US20080201381A1 (en) 2007-02-16 2008-08-21 Aditya Abhay Desai Method and system for increasing data reliability using source characteristics
US20080208904A1 (en) * 2007-02-26 2008-08-28 Friedlander Robert R System and method for deriving a hierarchical event based database optimized for analysis of complex accidents
US20080320219A1 (en) * 2007-06-21 2008-12-25 Wataru Okada Computer and method for configuring data backup environment used by plurality of associatively operated applications
US20090112531A1 (en) * 2007-10-31 2009-04-30 Naoto Sato Determining composite service reliability
US20090144393A1 (en) * 2007-11-29 2009-06-04 Yutaka Kudo Method and apparatus for locating candidate data centers for application migration
US7570587B1 (en) * 2000-12-14 2009-08-04 Nortel Networks Limited Resource allocation for multi-service gateways
US7730342B2 (en) * 2006-03-16 2010-06-01 Fujitsu Limited Server system
US8082222B2 (en) * 2009-01-14 2011-12-20 Bmc Software, Inc. CMDB federation method and management system
US8112758B2 (en) * 2008-01-08 2012-02-07 International Business Machines Corporation Methods and apparatus for resource allocation in partial fault tolerant applications

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001118179A (en) * 1999-10-15 2001-04-27 Nissan Motor Co Ltd Delivery plan support system
JP2004021880A (en) * 2002-06-20 2004-01-22 Fuji Xerox Co Ltd Device retrieval system and its method
JP4271665B2 (en) * 2005-03-04 2009-06-03 日本電信電話株式会社 Overlay network corresponding routing method and overlay nodes

Patent Citations (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5440738A (en) 1991-05-16 1995-08-08 Tally Systems Corporation Method and apparatus for digital data processor file configuration detection
US6205478B1 (en) * 1998-07-08 2001-03-20 Fujitsu Limited System for exchanging user information among users
US6675149B1 (en) * 1998-11-02 2004-01-06 International Business Machines Corporation Information technology project assessment method, system and program product
US6766318B1 (en) * 1999-03-11 2004-07-20 Oracle International Corporation Approach for collecting statistical information in information systems
US7181471B1 (en) * 1999-11-01 2007-02-20 Fujitsu Limited Fact data unifying method and apparatus
US7570587B1 (en) * 2000-12-14 2009-08-04 Nortel Networks Limited Resource allocation for multi-service gateways
US20030140087A1 (en) * 2002-07-30 2003-07-24 Patrick Lincoln Systems and methods for negotiated resource utilization
US7360219B2 (en) * 2002-12-13 2008-04-15 Hewlett-Packard Development Company, L.P. Systems and methods for facilitating fair and efficient scheduling of processes among multiple resources in a computer system
US20050172162A1 (en) * 2002-12-26 2005-08-04 Fujitsu Limited Operation management method and operation management server
US20040153435A1 (en) * 2003-01-30 2004-08-05 Decode Genetics Ehf. Method and system for defining sets by querying relational data using a set definition language
US20060174132A1 (en) * 2003-02-20 2006-08-03 Bea Systems, Inc. Federated management of content repositories
US20040179528A1 (en) * 2003-03-11 2004-09-16 Powers Jason Dean Evaluating and allocating system resources to improve resource utilization
US7409586B1 (en) * 2004-12-09 2008-08-05 Symantec Operating Corporation System and method for handling a storage resource error condition based on priority information
JP2006318371A (en) 2005-05-16 2006-11-24 Nippon Telegr & Teleph Corp <Ntt> Device and method for detecting data inconsistency
US20060288413A1 (en) * 2005-06-17 2006-12-21 Fujitsu Limited Intrusion detection and prevention system
US20070038587A1 (en) * 2005-07-27 2007-02-15 Fujitsu Limited Predicting apparatus, predicting method, and computer product
US20070112769A1 (en) * 2005-11-14 2007-05-17 Canon Kabushiki Kaisha Information processing apparatus, information processing method, and storage medium
US20070174346A1 (en) * 2006-01-18 2007-07-26 Brown Douglas P Closed-loop validator
US20070200908A1 (en) * 2006-02-24 2007-08-30 Seiko Epson Corporation Image Forming Apparatus and a Method of Controlling the Image Forming Apparatus
US20070203952A1 (en) * 2006-02-28 2007-08-30 Microsoft Corporation Configuration management database state model
US7730342B2 (en) * 2006-03-16 2010-06-01 Fujitsu Limited Server system
WO2007115940A1 (en) 2006-04-11 2007-10-18 International Business Machines Corporation Weighted determination in configuration management systems
US20070282856A1 (en) * 2006-04-28 2007-12-06 Bmc Software, Inc. Database Application Federation
US20070283206A1 (en) * 2006-05-15 2007-12-06 Fujitsu Limited Reliability evaluation device, Reliability evaluation method, and computer program product
US20080177688A1 (en) * 2006-09-07 2008-07-24 Friedlander Robert R System and method for managing a chaotic event by providing optimal and adaptive sequencing of decision sets with supporting data
US20080114870A1 (en) * 2006-11-10 2008-05-15 Xiaoyan Pu Apparatus, system, and method for generating a resource utilization description for a parallel data processing system
US20080114770A1 (en) * 2006-11-14 2008-05-15 Jinfang Chen Attribute level federation from multiple data sources
US20080183690A1 (en) * 2007-01-26 2008-07-31 Ramachandran Puthukode G Method for providing assistance in making change decisions in a configurable managed environment
US20080201381A1 (en) 2007-02-16 2008-08-21 Aditya Abhay Desai Method and system for increasing data reliability using source characteristics
US20080208904A1 (en) * 2007-02-26 2008-08-28 Friedlander Robert R System and method for deriving a hierarchical event based database optimized for analysis of complex accidents
US20080320219A1 (en) * 2007-06-21 2008-12-25 Wataru Okada Computer and method for configuring data backup environment used by plurality of associatively operated applications
US20090112531A1 (en) * 2007-10-31 2009-04-30 Naoto Sato Determining composite service reliability
US20090144393A1 (en) * 2007-11-29 2009-06-04 Yutaka Kudo Method and apparatus for locating candidate data centers for application migration
US8112758B2 (en) * 2008-01-08 2012-02-07 International Business Machines Corporation Methods and apparatus for resource allocation in partial fault tolerant applications
US8082222B2 (en) * 2009-01-14 2011-12-20 Bmc Software, Inc. CMDB federation method and management system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110161353A1 (en) * 2009-12-28 2011-06-30 Fujitsu Limited Management device and management method
US8838639B2 (en) 2009-12-28 2014-09-16 Fujitsu Limited Management device and management method for managing constituent elements of an information technology system

Also Published As

Publication number Publication date Type
JP2009217455A (en) 2009-09-24 application
US20090228506A1 (en) 2009-09-10 application
GB0903894D0 (en) 2009-04-22 grant
GB2458204A (en) 2009-09-16 application

Similar Documents

Publication Publication Date Title
US7912853B2 (en) Query processing client-server database system
US20060048155A1 (en) Organizing transmission of repository data
US20080021917A1 (en) Resource Name Reconciliation in a Configuration Database
US20120166469A1 (en) CEP engine and method for processing CEP queries
US20090037430A1 (en) Unwired enterprise platform
US6560591B1 (en) System, method, and apparatus for managing multiple data providers
US20070266029A1 (en) Recovery segment identification in a computing infrastructure
US20100257149A1 (en) Data synchronization and consistency across distributed repositories
US7801932B2 (en) Undo hints to speed up segment extension and tuning of undo retention
US6850958B2 (en) Backup system, backup method, database apparatus, and backup apparatus
US20100082671A1 (en) Joining Tables in Multiple Heterogeneous Distributed Databases
US20060218127A1 (en) Selecting a resource manager to satisfy a service request
US20120072903A1 (en) Multi-image migration system and method
US20090271529A1 (en) Stream data processing method and computer systems
US20060136585A1 (en) Resource reconciliation
US20120079083A1 (en) Sharing Performance Data Between Different Information Technology Product/Solution Deployments
US7904460B2 (en) Determining computer information from processor properties
US8180922B2 (en) Load balancing mechanism using resource availability profiles
CN104106241A (en) System and Method to Generate Secure Name Records
US8805971B1 (en) Client-specified schema extensions in cloud computing environments
US20100332637A1 (en) Virtual-machine management program and method for managing virtual machines
US9075788B1 (en) Account state simulation service for cloud computing environments
US7693816B2 (en) Computer system, computer, data access method and database system
US20050027724A1 (en) Data processing apparatus and method
US20140122706A1 (en) Method for determining system topology graph changes in a distributed computing system

Legal Events

Date Code Title Description
AS Assignment

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WADA, YUJI;KATSUNO, AKIRA;MATSUMOTO, YASUHIDE;AND OTHERS;REEL/FRAME:022345/0664;SIGNING DATES FROM 20081126 TO 20081127

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WADA, YUJI;KATSUNO, AKIRA;MATSUMOTO, YASUHIDE;AND OTHERS;SIGNING DATES FROM 20081126 TO 20081127;REEL/FRAME:022345/0664

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
FP Expired due to failure to pay maintenance fee

Effective date: 20161113