Abstract:
Pursuant to the increase in the number of objects to be managed and the complication of relations of the objects to be managed, the current condition is that the visibility of the GUI of management software is deteriorating. As one such current condition, there is a problem in that the display name of equipment to be managed on the GUI cannot be entirely displayed depending on the screen. Thus, the present invention improves the readability on the GUI by changing the display name according to the objective of the administrator by using a label in which the display name is divided into morphemes and the priority assigned thereto, as well as using topology information, and fitting the display name within the display area prepared on the screen.

Description:
TECHNICAL FIELD 
       [0001]    The present invention relates to a technology of generating or changing a screen display name of an object to be managed in a management computer system. 
       BACKGROUND ART 
       [0002]    The number of objects to be managed is increasing considerably and the relation of objects to be managed is becoming complicated pursuant to the widespread use of the virtualization technology, and it is becoming difficult for an infrastructure administrator or a tenant administrator to promptly perform individual identification of objects to be managed on a screen of management software. 
         [0003]    For example, when the display names of volumes are automatically numbered only using numerical values by the storage management software, it is not possible to instantaneously determine the information regarding where and for what the volume is being used. Moreover, since a substantial number of objects to be managed are displayed on a single screen, the area of the display name of individual objects to be managed will become small and only a part of the display name of the object to be managed can be displayed and, therefore, individual identification is difficult. 
       CITATION LIST 
     Patent Literature 
       [0004]    PTL 1: Japanese Patent Application Publication No. 2003-122469 
       SUMMARY OF THE INVENTION 
     Problems to be Solved by the Invention 
       [0005]    PTL 1 describes a technology of providing an information processing apparatus capable of improving the user&#39;s operability by constantly displaying devices in an identifiable state upon displaying information related to the devices on a network. 
         [0006]    With this technology, when there are any coinciding parts in the display names of objects to be managed, the information of such coinciding parts is omitted to shorten the display names of objects to be managed, and the identification of the objects to be managed can thereby be facilitated even in cases where the display area is small. 
         [0007]    In order for an administrator to identify an object, it is important for the administrator to be able to determine what the object is from its display name. Nevertheless, since a scheme of omitting character strings that coincide in the display names of a plurality of objects to be managed merely eliminates the redundancy of the character strings and does not go as far as comprehending the meaning or contents of the display name, the foregoing scheme does not contribute to the generation of a display name possessing readability where the administrator can promptly identify the object to be managed; that is, the foregoing scheme does not contribute to the generation of a so-called Human-Readable display name. 
       Means to Solve the Problems 
       [0008]    Thus, the present invention acquires, from topology information of the system of the objects to be managed, client information (tenant information or the like) that is related to the management objects to be displayed and a display name of IT equipment/parts or application which may be used together with the information of the objects to be managed, assigns a priority to the display name, and manages the result as relevant information. The management software adjusts the length of the display name by adding or deleting information to or from the display name according to the priority to match the size of the display area where the display name of the object to be managed is to be displayed. 
       Advantageous Effects of the Invention 
       [0009]    According to the present invention, an infrastructure administrator or a tenant administrator can promptly identify the objects to be managed, and it is thereby possible to shorten the operation time. 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0010]      FIG. 1  is a block diagram showing an example of the computer system. 
           [0011]      FIG. 2  is a block diagram explaining a hardware configuration and a software configuration of the management server. 
           [0012]      FIG. 3  is a block diagram explaining the hardware configuration and the software configuration of the server. 
           [0013]      FIG. 4  is a block diagram explaining the hardware configuration and the software configuration of the storage. 
           [0014]      FIG. 5  is a block diagram explaining the hardware configuration and the software configuration of the virtual server. 
           [0015]      FIG. 6  is a diagram showing the overview of the processing performed in the computer system. 
           [0016]      FIG. 7A  is an explanatory diagram showing an example of the management object table. 
           [0017]      FIG. 7B  is an explanatory diagram showing an example of the management object table. 
           [0018]      FIG. 8A  is an explanatory diagram showing an example of the association table. 
           [0019]      FIG. 8B  is an explanatory diagram showing an example of the association table. 
           [0020]      FIG. 9  is an explanatory diagram showing an example of the topology table. 
           [0021]      FIG. 10  is an explanatory diagram showing an example of the account table. 
           [0022]      FIG. 11  is an explanatory diagram showing an example of the label rule table. 
           [0023]      FIG. 12  is an explanatory diagram showing an example of the label table. 
           [0024]      FIG. 13  is an explanatory diagram showing an example of the pattern table. 
           [0025]      FIG. 14A  is an explanatory diagram showing an example of the screen information table. 
           [0026]      FIG. 14B  is an explanatory diagram showing an example of the screen information table. 
           [0027]      FIG. 15  is a flowchart explaining an example of the processing to be executed by the information acquisition module of the management server. 
           [0028]      FIG. 16  is a flowchart explaining an example of the processing to be executed by the topology generation module of the management server. 
           [0029]      FIG. 17  is a flowchart explaining an example of the processing to be executed by the label registration module of the management server. 
           [0030]      FIG. 18A  is a flowchart explaining an example of the processing to be executed by the display name generation module of the management server. 
           [0031]      FIG. 18B  is a flowchart explaining an example of the processing to be executed by the display name generation module of the management server. 
           [0032]      FIG. 18C  is a flowchart explaining an example of the processing to be executed by the display name generation module of the management server. 
           [0033]      FIG. 19  is a diagram explaining an example of the display screen of the management server. 
           [0034]      FIG. 20  is a diagram explaining an example of the display screen of the management server. 
           [0035]      FIG. 21  is an explanatory diagram showing an example of the label rule table. 
       
    
    
     DESCRIPTION OF EMBODIMENTS 
       [0036]    An embodiment of the present invention is now explained with reference to the appended drawings. 
         [0037]    In the ensuing embodiments, since components that have the same structure and are given the same reference numeral generally perform the same operation, the redundant explanation thereof is omitted. Moreover, the processing explained below is performed by the respective pieces of hardware through association. Moreover, each type of processing may also be realized with hardware such as an integrated circuit as the processing unit to perform such processing. Furthermore, the programs (including modules) as the basis of executing the processing may be stored in advance in a storage device within the computer or in an external storage device, or may be loaded into an external storage device as needed through a removable storage medium or a communication medium (wired, wireless or optical network, or carrier waves or digital signals on such network). 
         [0038]    Moreover, if the ID in the tables used in the ensuing embodiments can be identified based on other independent columns or the combination of other columns in the table, the column of that ID may be omitted. Moreover, as the ID, an identification number in ascending order may also be automatically assigned as the identifier. 
       Embodiment 1 
       [0039]      FIG. 1  is a block diagram showing an example of the computer system of the first embodiment of the present invention. A management server  101  is connected, via a management LAN  100 - 1  and a NW-SW (management network switch)  104 , to a management interface (management I/F)  106  of a NW-SW  104 , a management interface  106  of a NW-SW (business network switch)  111 , a management interface  106  of a FC (Fibre Channel)-SW  109 , a management interface  106  of servers  105 - 1  to  105 - 3 , a management interface  106  of virtual servers  108 - 1  to  108 - 2 , and a management interface  106  of a storage apparatus  110 . Note that each management interface  106  is an interface for sending information of each piece of equipment according to an inquiry from the management server  101  and, for instance, a network interface described later may be adopted. 
         [0040]    The management LAN  100 - 1  and the NW-SW  104  configure a network for the management server  101  to manage a plurality of servers  105 - 1  to  105 - 3 . Note that, in the ensuing explanation, the servers  105 - 1  to  105 - 3  are collectively referred to as the server  105 , and the virtual servers  108 - 1  to  108 - 2  are collectively referred to as the virtual server  108 . 
         [0041]    The management server  101  operates and manages the distribution of the OS and application that run on the server  105  and the power supply control of the server  105 . The NW-SW  111  configures a business network, and is a network that is used by the business application that is executed in the server  105  and the virtual server  108 . Note that the NW-SW  111  communicates, via the business LAN  100 - 2 , with an external client computer of the computer system connected via a WAN or the like. 
         [0042]    A control module  102  as a program is executed in the management server  101 , and refers to and updates a management table group  103 . The management table group  103  is updated or set as described later by the control module  102 . 
         [0043]    A tenant  107  is an area that is demarcated and managed by the management server  101 , and shows a range of the computer resource that has been assigned to a tenant administrator. The tenant administrator may freely use the computer resource that has been assigned to oneself within the category determined by an infrastructure administrator. 
         [0044]      FIG. 2  is a block diagram showing the configuration of the management server  101 . The management server  101  is configured from a CPU (Central Processing Unit)  201  which performs arithmetic operations, a memory  202  which stores programs to be executed by the CPU  201  and data used in executing the programs, a BMC (Basement Management Controller)  203  which controls the power supply control and the respective interfaces, a disk interface  204  which is used for accessing the storage apparatus  110  or the like storing programs and data, and a network interface  205  which is used for communication via an IP network. 
         [0045]    With the management server  101  of  FIG. 2 , while only one network interface  205  and one disk interface  204  are representatively shown, they may also each be provided in a plurality. For example, different network interfaces  205  may be used for connecting to the management network  100 - 1  and to the business network  100 - 2 . 
         [0046]    The memory  202  stores a control module  102  and a management table group  103 . 
         [0047]    The control module  102  includes various modules as programs, and specifically includes an information collection module  206  (refer to  FIG. 15 ), a topology generation module  208  (refer to  FIG. 16 ), a label registration module  207  (refer to  FIG. 17 ), and a display name generation module  209  ( FIG. 18 ). 
         [0048]    The information collection module  206 , the label registration module  207 , the topology generation module  208 , and the display name generation module  209  are each loaded as a program into the memory  202 . 
         [0049]    The CPU  201  operates as a function part which realizes a predetermined function by operating according to the respective programs. For example, the CPU  201  functions as the information collection module  206  by operating according to the information collection program. The same applies to the other programs. Furthermore, the CPU  201  also operates as a function part which realizes each of the plurality of types of processing that is executed by the respective programs. The management table group  103  includes a management object table  212  (refer to  FIG. 7 ), an association table  211  (refer to  FIG. 8 ), a topology table  215  (refer to  FIG. 9 ), an account table  213  (refer to  FIG. 10 ), a label rule table  210  (refer to  FIG. 11 ), a label table  216  (refer to  FIG. 12 ), a pattern table  217  (refer to  FIG. 13 ), and a screen information table  218  (refer to  FIG. 14 ). 
         [0050]    The information of each table may be automatically generated by the program (function part) in the management server  101 , or may be input manually by the user (or management terminal), or may be input by an application that coordinates with the management server  101 . An application that coordinates with the management server  101 , for example, is configured from a high-order configuration management application. 
         [0051]    The types of the management server  101  and the server  105  may be a physical server, a blade server, a virtualized server, or a logically/physically partitioned or a physically partitioned server, and the advantageous effects of this invention can be yielded regardless of which of the foregoing servers is used. 
         [0052]    Information of programs and tables that realize the respective functions of the control module  102  may be stored in a storage device such as the storage apparatus  110  or a non-volatile semiconductor memory, a hard disk drive, or an SSD (Solid State Drive), or in a computer-readable non-temporary data storage medium such as an IC card, an SD card, or a DVD. 
         [0053]      FIG. 3  is a block diagram showing the configuration of the server  105 . The server  105  includes a CPU  301  which performs arithmetic operations, a memory  302  which stores programs to be executed by the CPU  301  and data used in executing the programs, a disk interface  304  which is used for accessing the storage apparatus (or storage sub system)  110  storing programs and data, a network interface  305  which is used for communication via an IP network, and a BMC (Basement Management Controller)  303  which controls the power supply control and the respective interfaces. The OS  308  in the memory  302  is executed by the CPU  301 , and the device management is thereby performed by the server  105 . The business application  306  and the monitoring program  307  are executed under the control of the OS  308 . 
         [0054]    In  FIG. 3 , while only one network interface  304  and one disk interface  305  are respectively shown, they may also each be provided in a plurality. For example, different network interfaces  305  may be used for connecting to the management network  100 - 1  and the business network  100 - 2 . In this embodiment, the server  105  includes a network interface  305  for connecting to the management network (NW-SW  104 ) and the business network (NW-SW  111 ). Moreover, the management I/F  106  (refer to  FIG. 1 ) shows a network interface  305  for management network (NW-SW  104 ). 
         [0055]      FIG. 4  is a block diagram showing the configuration of the storage apparatus  110 . The storage apparatus  110  includes a disk controller  406 , and the disk controller  406  comprises an MPB (Micro Processor Blade)  401  which performs arithmetic operations, a cache memory  402  which stores programs to be executed by the MPB  401  and data used in executing the programs, a disk interface  404  as an interface for accessing the volume  407  in the storage apparatus  110  or other storage devices, a port  405  which is used for connecting to equipment such as the server  105 , and a management I/F  106  which is used by the management server  101  for managing the storage apparatus  110 . In  FIG. 4 , while one disk interface  404 , one port  405  and one disk controller  406  are representatively shown, they may also each be provided in a plurality. Note that a network interface may be used as the management I/F  106 . Moreover, the storage apparatus  110  includes a volume  407  which stores the programs and data sent from the storage apparatus  110  and equipment connected to the storage apparatus  110 . 
         [0056]      FIG. 5  is a block diagram showing the hardware configuration and the software configuration of a plurality of virtual servers  108  that are provided by executing the virtualization module  520 . The server  105  virtualizes the computer resources of the server  105  with the virtualization module  520 , and thereby provides one or more virtual servers  108 . Note that the virtualization module  520  is configured, for example, from a hypervisor or a VMM (Virtual Machine Monitor). 
         [0057]    The memory  302  stores the foregoing virtualization module  520  which virtualizes the computer resources, and the server  105  provides one or more virtual servers  108 . Moreover, the virtualization module  520  comprises a virtualization unit management interface  522  as a control interface. The virtualization module  520  configures the virtual server  108  by virtualizing the computer resources of the server  105 . 
         [0058]    The virtual server  108  is configured from a virtual CPU  501 , a virtual memory  502 , a virtual network interface  504 , a virtual disk interface  505 , and a virtual VMC  503 . The virtual memory  502  stores an OS  510 , and a virtual device group in the virtual server  108  is thereby managed. Moreover, a business application  511  is being run on the OS  510 . Failure detection, power supply control of the OS, and inventory management are provided by the management program  512  running on the OS  510 . 
         [0059]    The virtualization module  520  manages the association of the physical computer resources of the server  105  and the virtual computer resources. The virtualization module  520  includes a virtual switch  521  for performing communication among a plurality of virtual servers  108 . The virtual switch  521  can connect the physical interface of the server  105  to a plurality of virtual servers  108 . The virtual server  108  is able to thereby connect with the external equipment of the server  105  via the interface of the server  105 . 
         [0060]    The virtualization unit management interface  522  is an interface for the virtualization module  520  to communicate with the management server  101 , and is used for notifying information from the virtualization module  520  to the management server  101 , or sending instructions from the management server  101  to the virtualization module  520 . Moreover, the virtualization unit management interface  522  can also be used directly from a user terminal (not shown) or the like. 
         [0061]      FIG. 6  shows an overview of an example of the processing to be performed in the present invention. 
         [0062]    The management server  101  is managing a management object group  612 . The management server screen  602  is an example representing a management screen before applying the present invention, and includes a server management screen  603  and a storage management screen  605 . Moreover, the server management screen  603  includes a screen display area  604 - 1  and a screen display area  604 - 2  which respectively represent a server  105 - 1  and a server  105 - 2  of the management object group. The storage management screen  605  includes screen display areas  606 - 1  to  606 - 4  which respectively represent volumes  407 - 1  to volume  407 - 4  in the storage  110  of the management object group  612 . The management server screen  611  is an example of a management screen after applying the present invention, and includes a server management screen  607  and a storage management screen  609 . Moreover, the server management screen  607  includes a screen display area  608 - 1  and a screen display area  608 - 2  which respectively represent a server  105 - 1  and a server  105 - 2  of the management object group  612 . The storage management screen  609  includes screen display areas  610 - 1  to  610 - 4  which respectively represent volumes  407 - 1  to  407 - 4  in the storage  110  of the management object group  612 . 
         [0063]    The management object group  612  includes, as an example of objects to be managed, a tenant  107 - 1  and a tenant  107 - 2 , and the storage  110 . Moreover, the tenant  107 - 1  includes a server  105 - 1  including business applications  306 - 1  and  306 - 2 . Similarly, the tenant  107 - 2  includes a server  105 - 2  including a business application  306 - 3 . 
         [0064]    The administrator  601  comprehends the objects to be managed of the management object group  612  from the management screen  602  that was output from the management server  101 . With the pre-invention management screen  602 , while there are text boxes representing the server  604 - 1  and the server  604 - 2  of the management object group  612  displayed on the server management screen  603 , because the display names are long, the display names are cut off midway and, because the cut-off display names are the same, the server  604 - 1  and the server  604 - 2  cannot be differentiated. Meanwhile, while there are text boxes  606 - 1  to  606 - 4  representing the Volume  407 - 1  to the Volume  407 - 4  of the management object group  602  on the storage management screen  605  of the pre-invention management screen  602 , the display names are configured only from numbers and there is no information as to which Volume is being used by which server, and the administrator is unable to tell to which server the information has been assigned. 
         [0065]    The post-invention management screen  611  shows the management screen after applying the present invention to the pre-invention management screen  602 . With the server management screen  607  of the management screen  602 , while the information of the server displayed in the text box  604 - 1  and the text box  604 - 2  of the server management screen  603  is the same, the display names have been changed. The display names have been changed so that the text box  608 - 1  and the text box  608 - 2  can be respectively differentiated and, because information related to the server is also displayed, the administrator is able to differentiate the servers. Moreover, while the text boxes  610 - 1  to  610 - 4  of the storage screen  609  are of the same information of the Volumes as the text boxes  606 - 1  to  606 - 4  displayed on the storage management screen  605 , the display names have been changed as with the foregoing server management screen. The administrator  601  is thereby able to obtain information regarding for what the Volume is being used. 
         [0066]      FIG. 7A  and  FIG. 7B  are explanatory diagrams shown an example of the management object table in Embodiment 1 of the present invention. 
         [0067]    The management object table  212  stores configuration information and other information of the equipment to be managed. Specifically, the management object table  212  includes a management object ID  701 , a display name  702 , a management IP  703 , OS information  704 , a model  705 , a management object type  706  and the like. Otherwise, while not shown in the diagrams, the management object table  212  may also include authentication information such as the user name and password for accessing the objects to be managed, and configuration information and performance information of the CPU and memory of the objects to be managed. 
         [0068]    The management object ID  701  stores identifiers for uniquely identifying the objects to be managed such as a server, storage, network switch or FC switch in the computer system managed by the management server  101 . The display name  702  stores the names to be displayed when the objects to be managed are output to the screen or the like of the management server  101 . The first display name to be stored here may be named by the administrator, or automatically assigned by the management server  101  or the OS running on the object to be managed. The display names are displayed on the GUI as shown in  FIG. 19  and  FIG. 20  described later by the display program stored in the memory of the management server (not shown). 
         [0069]    The management IP address  703  stores the management IP address assigned to the object to be managed. The management server  101  connects to the equipment to be managed based on the management IP address. 
         [0070]    The OS  704  stores the OS information of the object to be managed. 
         [0071]    The model  705  stores information related to the model of the object to be managed. The information stored in the model  705  is information related to the infrastructure, and the manufacturer, performance, limit of configurable system and other matters of the equipment to be managed can be comprehended based on this information. 
         [0072]    The management object type  706  stores information related to the type of the object to be managed. For example, information on whether the object to be managed is a physical server or a virtual server is stored in the management object type  706 . 
         [0073]      FIG. 8A  and  FIG. 8B  are explanatory diagrams showing an example of the association table in Embodiment 1 of the present invention. 
         [0074]    The association table  211  includes a management object ID  801 , an associated node ID  802 , tenant information  803 , application information  804 , and a display necessity flag  805 , and stores information of related equipment which is related to the equipment to be managed as the associated node, information of the tenant belonging to the object to be managed, information of the business application that runs on the object to be managed, and information regarding whether the display of equipment to be managed needs to be displayed in the first place. 
         [0075]    The management object ID  801  shows the same ID as the foregoing management object table  212 . The associated node ID  802  stores the ID related to the object to be managed shown in the management object ID  801 ; that is, the ID of the physically or logically connected object to be managed. Specifically, this includes cases where the tenant ID and the application ID, or the application ID and the associated node ID, or the associated nodes ID have a relation of the virtualization infrastructure and the virtual server, cases where they have a relation of the server and the business application running on the memory thereof, cases where they have a physical connection relation between the NW-SW and the server, and cases where they have a relation of the tenant and the business application running in the tenant. 
         [0076]    The tenant information  803  stores information of the tenant to which the object to be managed identified with the management object ID  801  belongs. 
         [0077]    The application information  804  stores information of the business application included in the object to be managed identified with the management object ID  801 . The display necessity flag  805  stores information to be used by the tenant administrator or the tenant user to determine whether it is necessary to display the object to be managed identified with the management object ID  801 . The display necessity flag may be registered from the beginning, or may be manually set by the administrator. 
         [0078]      FIG. 9  is an explanatory diagram showing an example of the topology table in Embodiment 1 of the present invention. 
         [0079]    The topology table  215  includes a topology ID  901 , a tenant ID  902 , an application ID, an application ID  903 , and associated node IDs  904  to  910 . 
         [0080]    The topology ID  901  stores an identifier for uniquely identifying information of the topology representing the relation between the objects to be managed in the computer system managed by the management server  101 . 
         [0081]    The management object ID  902  stores the tenant information to be used as the base point of the topology. For example, in  FIG. 9 , a topology is generated with tenant 1 as the base point. 
         [0082]    The management object ID  903  stores information of the business application to be used as the base point of the topology. 
         [0083]    The associated node IDs  904  to  910  stores information of the associated objects to be managed and starts from the network ID. 
         [0084]    Note that, in order to assign a priority to labels described later, the associated node IDs  905  to  910  may also be sorted based on the application ID or the tenant ID after creating the topology information. 
         [0085]    Moreover, in addition to storing the simple physical or logical connection between the objects to be managed as the topology, the management server may also store the relation of the objects to be managed that are frequently used together for failure analysis based on RCA (Root Cause Analysis), the relation of the objects to be managed that configure the converged infrastructure in which the server and the storage are integrated, the relation of the objects to be managed which are often simultaneously referred to by the administrator, or the relation of the objects to be managed in which information is often simultaneously referred to based on the management operation history or the like. 
         [0086]      FIG. 10  is an explanatory diagram showing an example of the account table in Embodiment 1 of the present invention. 
         [0087]    The account table  213  includes an account ID  1001 , an account name  1002 , role information  1003 , and a management object ID  1004 . 
         [0088]    The account ID  1001  stores an identifier for uniquely identifying the account of the administrator using the management server  101 . 
         [0089]    The account name  1002  stores the account name of the administrator using the management server  101 . 
         [0090]    The role information  1003  stores the role information of the administrator using the management server  101 . Here, the term “role” is information related to the type of administrator, and shows the administrator&#39;s role with regard to the system. Specifically, considered may be a tenant administrator who manages tenants, and an infrastructure administrator who manages the infrastructure. 
         [0091]    The management object ID  1004  stores the management object ID of the objects to be managed which are being managed by the administrator of the account ID stored in the account ID  1001 . 
         [0092]      FIG. 11  is an explanatory diagram showing an example of the label rule table in Embodiment of the present invention. 
         [0093]    The term “label” is a character string or a numerical string as a morpheme of the display name of the object to be managed, and is basically an abbreviated version of the ID or display name of the object to be managed which is abbreviated according to the abbreviation method described later. When displaying a certain object to be managed on the management screen, a Human-Readable display name that will fit into the limited display area of the screen can be generated by adding a label of a related object to be managed to the management object to be displayed, or deleting an unneeded label from the management object to be displayed. 
         [0094]    The label rule table  210  includes a rule ID  1101 , account information  1102 , a management object type  1103 , an abbreviation method  1104 , and a linking method  1105 . 
         [0095]    The rule ID  1101  stores an identifier for uniquely identifying the generation rule upon generating a label. 
         [0096]    The account information  1102  stores the account information of the administrator to which the generation rule of the rule ID  1101  is applied. Depending on the generation rule, a plurality of accounts may refer to the same generation rule. Moreover, in  FIG. 11 , while the generation rule is determined based on the account information, the generation rule may also be determined for each type of administrator such as the infrastructure administrator or the tenant administrator. 
         [0097]    The management object type  1103  stores information regarding the type of object to be managed to be used as the condition for determining whether to apply the generation rule of the rule ID  1101 . Depending on the generation rule, there may be cases where the generation rule is applied only in cases of tenant information, or cases where the generation rule is applied only in cases of a virtual server. Moreover, the account may also include a plurality of rules. However, in the foregoing case, the management object type of the rule must not overlap. 
         [0098]    The abbreviation method  1104  stores the method of abbreviating the display name of the object to be managed in order to create a label. 
         [0099]    This is because a comprehensible abbreviation method may vary depending on the administrator or the management object type. Considered may be the following methods; for instance, leaving the first or last several characters when the display name is a character string, or leasing the first several characters of the character string and leaving the numerical string when a character string and a numerical string are used in combination. For example, when the infrastructure administrator wishes to abbreviate the tenant&#39;s display name of “Tenant1” to “Ten1” and use the abbreviated version, the infrastructure administrator registers, as the abbreviation method, information of leaving the first three characters (Ten) and leaving the final character (1). The abbreviation method may be manually registered by the administrator, or be included in the management system as a default setting. 
         [0100]    The linking method  1105  stores the linking method in cases of linking labels. 
         [0101]    As with the abbreviation method, a comprehensible linking method of labels may vary depending on the administrator or the management object type. For example, when the infrastructure administrator wishes to abbreviate the tenant&#39;s display name “Tenant1” to “Ten1” as the label and link it with the application of “hogeDB” to display “Ten1HogeDB”, information of Camel Case is registered as the linking method. The linking method may be manually registered by the administrator, or be included in the management system as a default setting. 
         [0102]      FIG. 12  is an explanatory diagram showing an example of the label table in Embodiment 1 of the present invention. 
         [0103]    The label table  216  includes a label ID  1201 , an account ID  1202 , a management object ID  1203 , a management object label  1204 , and a priority  1205 . 
         [0104]    The label ID  1201  stores an identifier for uniquely identifying the label that may be added to the display name when each administrator views the display name of the object to be managed of the management object ID  1203 . 
         [0105]    The account ID  1202  is information for identifying the administrator to view the label of the label ID  1201 . For example, since the administrator identified with the account ID of Ac.1 and the administrator identified with the account ID of Ac.2 have different label IDs, even if they view the same information of the same object of management, the display name of the object to be managed will be different. 
         [0106]    The management object ID  1203  shows the object to be managed by the administrator. 
         [0107]    The label  1204  stores the label of the object to be managed. When the administrator (account) or the management object ID is different, there may be cases where the stored information will also be different. This is because the display name or label of the object to be managed that can be easily managed by the administrator is different. 
         [0108]    The priority  1205  stores information related to the priority of the label. The priority may be changed based on an input from the user (administrator) or as needed by the management server  101 . Note that, in Embodiment 1, the priority is higher as the value is smaller. 
         [0109]    Moreover, the label  1204  may include the location, time or user name as items that can also be applied to any object to be managed. Specifically, with regard to the respective objects to be managed, considered may be the ID of the rack where the object to be managed is being stored, location (geographical name) where the object to be managed is installed, name of the data center where the object to be managed is installed, time that the object to be managed was created or added, and user name of the user to use the object to be managed. 
         [0110]      FIG. 13  is an explanatory diagram showing an example of the pattern table  217  in Embodiment 1 of the present invention. 
         [0111]    The term “pattern” refers to a format to which the display name of the object to be managed is applied in order to confirm whether it is a Human-Readable display name, and is represented using an evaluation formula or the like. For example, when determining whether the character strings of two display names (display name A, display name B) coincide, a pattern of an evaluation formula of display name A=display name B is used. Moreover, when determining whether the display name is configured only from numbers, a pattern of an evaluation formula of display name A=[0-9]+ is used. This pattern determines whether the display name is a numerical string in which only numbers of 0 to 9 are lined up in an arbitrary quantity. 
         [0112]    The pattern table  217  includes a pattern ID  1301 , role information  1302 , a pattern  1303 , an evaluation formula  1304 , and measures to be taken  1305 . 
         [0113]    The pattern ID  1301  stores an identifier for uniquely identifying the pattern information for determining whether the display name of the object to be managed can be easily read by the administrator, and whether it is a Human-Readable display name. 
         [0114]    The role information  1302  stores information regarding the type of administrator to which the pattern stored in the pattern ID is applied. In  FIG. 13 , the role information  1302  is classified for each type of administrator such as the tenant administrator or the infrastructure administrator, but the pattern may also be set for each administrator by using the account ID (refer to  FIG. 10 ). 
         [0115]    The pattern  1303  stores the explanation of the pattern to be applied to the display name of the object to be managed. For example, the pattern of “only numbers” shows whether the display name is configured only from numbers, and whether it is a Human-Readable display name. For example, when the pattern coincides with the administrator&#39;s role, it is determined that the display name is not a Human-Readable display name. 
         [0116]    The evaluation formula  1304  stores the evaluation formula to be used upon actually applying the pattern explained in the pattern  1303  to the display name of the object to be managed. 
         [0117]    The measures to be taken  1305  show the measures to be taken to the display name of the object to be managed when the evaluated display name of the object to be managed coincides with the pattern. 
         [0118]    The patterns registered in the pattern table  217  may be manually set by the administrator, or be included in the management system as default values. Moreover, an unneeded pattern may be deleted or the role of the pattern may be changed. 
         [0119]      FIG. 14A  and  FIG. 14B  are explanatory diagrams showing an example of the screen information table in Embodiment 1 of the present invention. 
         [0120]    The screen information table  218  includes a display area ID  1401 , role information  1402 , a management screen  1403 , a display-target management equipment ID  1404 , a displayable area  1405 , and an unneeded label  1406 . 
         [0121]    The display area ID  1401  stores an identifier for uniquely identifying the area of displaying the display name of the object to be managed on the screen of the management system. 
         [0122]    The display area ID  1402  represents the type of administrator to view the display name of the object to be managed in the display area indicated in the display area ID. Note that, in  FIG. 14 , while the role is represented as an infrastructure administrator or a tenant administrator, the role may also be classified for each administrator by using the account ID (refer to  FIG. 10 ). 
         [0123]    The management screen  1403  stores information regarding the type of screen to display the object of management. 
         [0124]    The display-target management equipment ID  1404  stores information of the object to be managed to be displayed in the display area. This is the same as the management object ID shown in  FIG. 7 . 
         [0125]    The displayable area  1405  shows the size of the displayable area (for instance, the word count) upon displaying the display name of the object to be managed. 
         [0126]    The unneeded label  1406  stores the type of unneeded label upon displaying the display name of the object to be managed. For example, when the infrastructure administrator is to view the object to be managed from the tenant management screen, the tenant is obvious at the point in time that the infrastructure administrator views the tenant management screen and, therefore, a label related to the tenant is not required in the display name. In the foregoing case, “tenant” is designated in the unneeded label  1406 . 
         [0127]    As a result of using the foregoing tables, the display name of the object to be managed can be displayed, upon adding a label of high priority or deleting a label of low priority, in accordance with the displayable area which will differ depending on the size of the display area of the object to be managed and the management screen. 
         [0128]      FIG. 15  is a flowchart explaining an example of the processing to be executed by the information collection module  206  of the management server  101  in Embodiment 1 of the present invention. 
         [0129]    The information collection module  206  detects a start instruction of the information collection processing input from the administrator (step S 1501 ). 
         [0130]    Note that the trigger for starting the information collection processing is not limited to the detection of the start instruction input from the administrator. For example, the processing may be started after the lapse of a predetermined time based on the schedule function equipped in the management server  101 , or the processing may be started periodically, or the processing may be started when the management server  101  detects a change in the configuration of the object to be managed. 
         [0131]    Moreover, the start instruction of the information collection processing also includes information for identifying the object of information collection designated by the administrator. Information for identifying the object of information collection processing will suffice so as long as it is information capable of identifying the processing target such as the management object ID. 
         [0132]    The information collection module  206  starts the repetitive processing for the number of objects to be managed (step S 1502 ). The information collection module  206  thereafter identifies the object of management from which information is to be acquired (step S 1503 ), and acquires configuration information from the object to be managed (step S 1504 ). The information collection module  206  subsequently writes the acquired configuration information of the object to be managed into the management object table, and thereby updates the information of the management object table and the association table (step S 1505 ). The information collection module  206  thereafter ends the repetitive processing from step S 1501  (step S 1506 ). Finally, the information collection module  206  notifies the topology generation module  208  that the information collection processing is complete (step S 1507 ), and then ends the processing of the information collection module. 
         [0133]    Based on the foregoing processing, it is possible to acquire the configuration information of the objects to be managed and a management object list related to the objects to be managed stored in the association table. 
         [0134]      FIG. 16  is a flowchart explaining an example of the processing to be executed by the topology generation module  208  of the management server  101  in Embodiment 1 of the present invention. 
         [0135]    The topology generation module  208  detects a start instruction from the administrator (step S 1601 ). Note that the trigger for starting the topology generation processing is not limited to the detection of the start instruction input from the administrator. For example, the processing may be started after the lapse of a predetermined time based on the schedule function equipped in the management server  101 , or the processing may be started periodically, or the processing may be started when the management server  101  detects a change in the configuration of the object to be managed. 
         [0136]    Subsequently, the topology generation module  208  acquires, from the association table  211 , the relevant information (specifically, the management object ID and the associated node ID) of the objects to be managed required for generating the topology (step S 1602 ). The topology generation module  208  thereafter starts the repetitive processing for the number of physical servers and virtual servers registered in the association table  211  (step S 1603 ). Subsequently, the topology generation module  208  extracts the tenant ID and the application ID of the server and registers the extracted tenant ID and application ID in the topology table (step S 1604 ). The topology generation module  208  thereafter starts the repetitive processing for the number of associated node IDs regarding the objects to be managed selected in S 1604  (step S 1605 ). Subsequently, the topology generation module  208  registers the selected associated node IDs in the topology table  215  (step S 1606 ). In step S 1607 , the topology generation module  208  refers to the association table  211  regarding the objects to be managed that correspond to the associated node ID registered in step S 1606 , and proceeds to step S 1606  when there is an associated node ID other than the associated node IDs registered in step S 1606 , and proceeds to step S 1608  in other cases. When all associated node IDs have been processed in step S 1608 , the topology generation module  208  ends the repetitive processing started from step S 1605 , and then proceeds to step S 1609 . When all physical servers and virtual servers have been processed in step S 1609 , the topology generation module  208  ends the processing started from S 1603 , and then proceeds to step S 1610 . In step S 1610 , the topology generation module  208  sends a processing completion notice to the label registration module. 
         [0137]    Based on the foregoing processing, the connection relation of the management object group can be registered as a topology in the topology table  215 . 
         [0138]      FIG. 17  is a flowchart explaining an example of the processing to be executed by the label registration module  207  of the management server  101  in Embodiment 1 of the present invention. 
         [0139]    The label registration module  207  detects the completion notice from the topology generation module  208  (step S 1701 ), and thereafter acquires information of the management object table  212 , information of the label rule table  210 , information of the account table  213 , and information of the topology table  215  (step S 1702 ). 
         [0140]    Subsequently, the label registration module  207  starts the repetitive processing for the number of accounts in the account table  213  (step S 1703 ), and then proceeds to step S 1704 . 
         [0141]    The label registration module  207  thereafter acquires information of the object to be managed, which is being managed by the account, from the information of the column of the object to be managed of the account table  213  (step S 1704 ), and starts the repetitive processing for that quantity (step S 1705 ). In step S 1706 , the label registration module  207  uses the role information of the account table  213  and the information of the management object type acquired from the management object table  212  based on the information of the object to be managed that is linked to the role of the account table  213 , and acquires, from the label rule table  210 , the generation rule of the label related to both of the foregoing pieces of information. The label registration module  207  thereafter applies the rule acquired in step S 1706  to the display name of the object to be managed (step S 1707 ). In step S 1708 , the label registration module  207  registers the label generated in step S 1707  in the label table  216 , and then proceeds to step S 1709 . In step S 1709 , when the repetitive processing has been performed for the number of objects to be managed, which are managed by the account, the label registration module  207  ends the repetitive processing of step S 1705 . In step S 1710 , the label registration module  207  sets the priority in the priority  1205  of the label table  216 . 
         [0142]    The targets to which the priority is set can be generally classified into two types, and the priority is set by combining the two types of targets. One type is a label in which the tenant and the application are added to a label in which an object to be managed does not exist in the management object group, such as tenant information, application information, location information, or time information. All of these labels are likely to be Human-Readable labels for the administrator. The other type is the label having an object to be managed in the management object group, excluding the tenant and the application. In the ensuing explanation, the former is referred to as “environment information” and the latter is referred to as “relevant information”. For example, since “server 1” exists in the management object group, it corresponds relevant information, and “tenant 1” exists in the management object group but because it is Human-Readable, it corresponds to environment information. Furthermore, “tokyo” is a term that is used in the display name and indicates the location where the object to be managed exists, and corresponds to environment information since it does not exist in the management object group. 
         [0143]    Foremost, since environment information is basic management information, it is generally set to have a priority that is higher than relevant information. Nevertheless, the priority may be kept low for each administrator or for each role, or the setting may be changed by deeming it to be an unneeded label. Specifically, the setting may be changed based on the service used by the administrator (for instance, tenant management or infrastructure management), the priority of information which is frequently referred to by the administrator may be set high, the priority of information which is not frequently referred to by the administrator may be set low, or it may be deemed to be an unneeded label. 
         [0144]    The priority of relevant information is determined by using the relevant information of the equipment of the topology table  215 . In the topology table  215 , the tenant ID and the application ID are environment information. Foremost, the label registration module  207  determines whether the tenant ID as the environment information is an object to be managed. When the tenant ID is an object to be managed, the highest priority is assigned. Subsequently, the label registration module  207  refers to the application ID, which is the right field of the tenant ID, and determines whether the application ID is an object to be managed. When the application ID is an object to be managed, the next highest priority is assigned. Furthermore, the same processing is also performed regarding the right field, and this is repeated up to the right end of the topology entry. Subsequently, the label registration module  207  repeats the same processing for the subsequent topology entry, and continues this until a priority is assigned to all objects to be managed by the administrator to reflect the priority of the association table. Note that, with regard to the environment information excluding the tenant and the business application, a priority is set by performing processing that is separate from the foregoing processing, and reflected in the label of the association table. 
         [0145]    For example, in cases where the account name is “Alice”, the object to be managed can be derived from the account table. The topology table is consequently referred to from the high-ranking entry. Foremost, the leftmost field in the uppermost entry of the topology table is the tenant, and “tenant 1” is stored therein. Since this is an object to be managed by Alice, the highest priority is assigned to “tenant 1”. Next, the right field is the application ID, and “business application 1” is stored therein. Since this is also an object to be managed by Alice, the next highest priority is assigned to “business application 1” after “tenant 1”. This processing is repeated until a priority is assigned to all objects to be managed by Alice. Consequently, in cases of being used by Alice, it is possible to create a state where a priority is assigned to all labels. Note that the setting of priority is not limited to the order of topology, and the user (administrator) may apply a weight to the tenant ID, the application ID, the network node ID and the node ID of the topology table  215 , and the priority may be changed based on such weight. If repetitive processing has been performed for the number of accounts in step S 1711 , the label registration module  207  ends the repetitive processing of step S 1703 . 
         [0146]    Finally, the label registration module  207  sends a processing completion notice to the display name generation module (step S 1712 ). 
         [0147]    Based on the foregoing processing, it is possible to generate a label to be used in displaying the object to be managed, and register the generated label in a table. Moreover, based on the foregoing processing, since it is possible to add information, in ascending order of importance, to information which is required by the administrator and to be displayed on the screen, the operability of management software can be improved. 
         [0148]      FIG. 18  is a flowchart explaining an example of the processing to be executed by the display name generation module  209  of the management server  101  in Embodiment 1 of the present invention. 
         [0149]    The display name generation module  209  acquires, in step S 1801 , information of the label table  216 , the screen information table  218 , the account table  213 , the pattern table  217 , the management object table  212 , the association table  211  and the topology table  215 . 
         [0150]    Subsequently, in step S 1802 , the display name generation module  209  starts the repetitive processing for the number of accounts registered in the account table  213 . 
         [0151]    In step S 1803 , the display name generation module  209  acquires, from the screen information table  218 , information of the management screen to be used by the account. 
         [0152]    In step S 1804 , the display name generation module  209  starts the repetitive processing for the number of types of management screens to be used by the account from the information of the management screen to be used by the accounted acquired in step S 1803 . 
         [0153]    Subsequently, in step S 1805 , the display name generation module  209  acquires, from the account table  213 , information of the object to be managed by the account. 
         [0154]    In step S 1806 , the display name generation module  209  starts the repetitive processing for the number of objects to be managed by the account acquired in step S 1805 . 
         [0155]    In step S 1807 , the display name generation module  209  evaluates whether the display necessity flag  805  of the association table  211  is “necessary” or “not necessary” regarding the object to be managed. When the display necessity flag  805  is “necessary”, the display name generation module  209  proceeds to step S 1808 , and when the display necessity flag  805  is “not necessary”, the display name generation module  209  proceeds to step S 1829 . 
         [0156]    In step  1808 , the display name generation module  209  acquires the display name of the object to be managed from the display name column  702  of the management object table  212 , and compares the acquired display name with the displayable area of the displayable area column  1405  of the screen information table  218 . As a result of the comparison, when the word count of the display name of the object to be managed is greater than the displayable area, the display name generation module  209  proceeds to sub process P 1827 , and when the word count of the display name of the object to be managed is smaller than the displayable area, the display name generation module  209  proceeds to sub process P 1828 . 
         [0157]    In the flowchart ( FIG. 18B ) of sub process P 1827 , label information with the lowest priority, excluding the unneeded label indicated in the column  1406  of the screen information table  218  of  FIG. 14 , in the display name of the object to be managed is acquired in step S 1809 . 
         [0158]    In step S 1810 , the display name generation module  209  deletes the label acquired in S 1809  from the display name of the object to be managed. 
         [0159]    In step S 1811 , the display name generation module  209  acquires pattern information of the role corresponding to the pattern table  217 . In the diagram, processing is described on the assumption that information of pattern P.1 and pattern P.2 has been acquired. 
         [0160]    In step S 1812 , pattern P.1 is checked. The display name generation module  209  determines whether pattern P.1, which is the display name of the object to be managed, is configured entirely of numbers. When the display name of the object to be managed is configured only with numbers, the display name generation module  209  proceeds to step S 1813 . When the display name of the object to be managed is not configured only with numbers, the display name generation module  209  proceeds to step S 1814 . 
         [0161]    In step S 1813 , measures are taken against the display name of the object to be managed corresponding to the pattern check performed in step S 1812 . In the case of this Embodiment, the display name of the object to be managed is configured only from numbers and is determined as not being a Human-Readable display name. Thus, as the measures to be taken, label information having the highest priority other than the display name of the object to be managed and configured from a character string other than the label deleted in step S 1810  and other than numbers is acquired from the list of labels related to the display name of the object to be managed, and added to the display name. After the foregoing measures are taken, the display name generation module  209  proceeds to step S 1814 . 
         [0162]    In step S 1814 , pattern P.2 is checked. The display name generation module  209  determines whether a display name, which is entirely the same as the display name of the object to be managed, exists on the management screen. When the same display name as the display name of the object to be managed exists on the management screen, the display name generation module  209  proceeds to step S 1815 . When the same display name as the display name of the object to be managed does not exist on the management screen, the display name generation module  209  proceeds to step S 1816 . 
         [0163]    In step S 1815 , measures are taken against the display name of the object to be managed corresponding to the pattern check performed in step S 1814 . In the case of this Embodiment, the same display name as the display name of the object to be managed exists on the management screen and is determined as not being a Human-Readable display name. Thus, as the measures to be taken, different numbers are respectively added to the end of the display name of the object to be managed and to the end of the same display name. After the foregoing measures are taken, the display name generation module  209  proceeds to step S 1816 . 
         [0164]    In step S 1816 , the display name generation module  209  determines whether the character string of the display name of the object to be managed is less than or the same as the displayable area. When character string of the display name of the object to be managed is less than or the same as the displayable area, the display name generation module  209  proceeds to step S 1829  of the flowchart of  FIG. 18A . When character string of the display name of the object to be managed is not less than or not the same as the displayable area, the display name generation module  209  proceeds to step S 1817 . 
         [0165]    In step S 1817 , since the character string of the display name of the object to be managed does not fit in the displayable area, the display name generation module  209  acquires information of the label of the next lowest priority to additionally delete a label. After the foregoing information is acquired, the display name generation module  209  returns to step S 1810  and once again repeats the processing. 
         [0166]    In the flowchart ( FIG. 18C ) of sub process P 1828 , label information of high priority other than the display name of the object to be managed and excluding the unneeded label indicated in the column  1406  of the screen information table  218  of  FIG. 14  is acquired in step S 1818 . 
         [0167]    In step S 1819 , the display name generation module  209  adds the label acquired in S 1818  to the display name of the object to be managed. 
         [0168]    In step S 1820 , the display name generation module  209  acquires pattern information of the role corresponding to the pattern table  217 . In the diagram, processing is described on the assumption that information of pattern P.1 and pattern P.2 has been acquired. 
         [0169]    In step S 1821 , pattern P.1 is checked. The display name generation module  209  determines whether pattern P.1, which is the display name of the object to be managed, is configured entirely of numbers. When the display name of the object to be managed is configured only with numbers, the display name generation module  209  proceeds to step S 1822 . When the display name of the object to be managed is not configured only with numbers, the display name generation module  209  proceeds to step S 1823 . 
         [0170]    In step S 1822 , measures are taken against the display name of the object to be managed corresponding to the pattern check performed in step S 1821 . In the case of this Embodiment, the display name of the object to be managed is configured only from numbers and is determined as not being a Human-Readable display name. Thus, as the measures to be taken, label information having the highest priority other than the display name of the object to be managed and configured from a character string other than numbers is acquired from the list of labels related to the display name of the object to be managed, and added to the display name. After the foregoing measures are taken, the display name generation module  209  proceeds to step S 1823 . 
         [0171]    In step S 1823 , pattern P.2 is checked. The display name generation module  209  determines whether a display name, which is entirely the same as the display name of the object to be managed, exists on the management screen. When the same display name as the display name of the object to be managed exists on the management screen, the display name generation module  209  proceeds to step S 1824 . When the same display name as the display name of the object to be managed does not exist on the management screen, the display name generation module  209  proceeds to step S 1825 . 
         [0172]    In step S 1824 , measures are taken against the display name of the object to be managed corresponding to the pattern check performed in step S 1823 . In the case of this Embodiment, the same display name as the display name of the object to be managed exists on the management screen and is determined as not being a Human-Readable display name. Thus, as the measures to be taken, different numbers are respectively added to the end of the display name of the object to be managed and to the end of the same display name. After the foregoing measures are taken, the display name generation module  209  proceeds to step S 1825 . 
         [0173]    In step S 1825 , label information of the next highest priority regarding the object to be managed is acquired. 
         [0174]    In step S 1826 , the display name generation module  209  determines whether the total word count of the work count of the display name of the object to be managed and the word count of the label acquired in step S 1825  is less than or the same as the displayable area. When the total word count of the work count of the display name of the object to be managed and the word count of the label acquired in step S 1825  is less than or the same as the displayable area, the display name generation module  209  proceeds to step S 1819 . When the total word count of the work count of the display name of the object to be managed and the word count of the label acquired in step S 1825  is not less than or not the same as the displayable area, the display name generation module  209  proceeds to step S 1829  of the flowchart of  FIG. 18A . 
         [0175]    In step S 1829 , when the processing has been repeated and completed for the number of objects to be managed in step S 1806 , the loop processing is ended. 
         [0176]    In step S 1830 , when the processing has been repeated and completed for the number of types of management screens in step S 1804 , the loop processing is ended. 
         [0177]    In step S 1831 , when the processing has been repeated and completed for the number of accounts in step S 1802 , the loop processing is ended. 
         [0178]    Note that the trigger for starting the information collection processing may be when a start instruction input from the administrator is detected, the processing may be started after the lapse of a predetermined time based on the schedule function equipped in the management server  101 , or the processing may be started periodically, or the processing may be started when the management server  101  detects a change in the configuration of the object to be managed. 
         [0179]    Based on the foregoing processing, it is possible to display, as much as possible, information which is Human-Readable and required by the administrator in a limited display area, and thereby improve the operability of management software. 
         [0180]      FIG. 19  shows an example of the graphical user interface (GUI) that is displayed by the management server  101  to the administrator in Embodiment 1 of the present invention. 
         [0181]    The GUI is used by the user for referring to information of objects to be managed in order to manage such objects to be managed. 
         [0182]    Moreover, while omitted in the GUI, the GUI may also include an input interface to be operated for performing the power supply operation of objects to be managed and for changing the configuration of objects to be managed. 
         [0183]    The GUI may be displayed on an input terminal (not shown) connected to the management server  101 , or a similar GUI may be displayed with an application that is coordinating with the management server  101 . 
         [0184]    A GUI screen  1901  shows a screen for referring to information of objects to be managed. This screen may display different information for each account of the administrator. For example, when the administrator is a tenant administrator, the screen may display only information of the equipment to be managed by oneself, and hide other information. 
         [0185]    A button  1902  is used for determining whether to perform the operation of adding the label of an object to be managed related to the display name of the present invention to the display name of the object to be managed, and when the abbreviated display is OFF, the abbreviated display function of the present invention is not used. When the abbreviated display is ON, the abbreviated display function of the present invention is used. 
         [0186]    A box  1903  shows the address information of the GUI screen  1901 . In the case of  FIG. 19 , the screen has changed from the overall resource screen to the tenant A management screen, and is currently displaying the virtual server screen. 
         [0187]    A box  1904  shows the address information of the object to be managed in the same manner as the box  1903 . In the case of  FIG. 19 , the screen has changed from the resource screen to the tenant screen, and is currently displaying the virtual server screen. 
         [0188]    A box  1905  shows a list of the objects to be managed. In the case of  FIG. 19 , a list of the virtual servers is displayed. 
         [0189]    A column  1906  to a column  1909  show information such as the name (display name), the operating state, the IP address, and the OS related to the objects to be managed. Note that, while omitted in the diagrams, equipment information of the objects to be managed may also be displayed. 
         [0190]    The name of the object to be managed of the column  1906  is the target of the present invention. The display area of the name changes depending on the size of the GUI screen  1901  or the size of the columns of boxes  1905 ,  1906 . In accordance with the foregoing change, the present invention enables the display of a Human-Readable name based on the method explained above. 
         [0191]      FIG. 20  shows an example of the graphical user interface (GUI) that the management server  101  displays to the administrator of the tenant 1 in Embodiment 1 of the present invention. 
         [0192]    The GUI is used by the user for referring to information of objects to be managed in order to manage such objects to be managed. Unlike the GUI illustrated in  FIG. 19 , the GUI of  FIG. 20  expresses the physical or logical relation of the respective equipment using connections or nesting of boxes so that the user can understand such relation on the GUI. 
         [0193]    Moreover, while omitted in the GUI, the GUI may also include an input interface to be operated for performing the power supply operation of objects to be managed and for changing the configuration of objects to be managed. 
         [0194]    The GUI may be displayed on an input terminal (not shown) connected to the management server  101 , or a similar GUI may be displayed with an application that is coordinating with the management server  101 . 
         [0195]    A GUI screen  2001  shows a screen for referring to information of objects to be managed. This screen may display different information for each account of the administrator. For example, when the administrator is a tenant administrator, the screen may display only information of the equipment to be managed by oneself, and hide other information. 
         [0196]    A box  2003  shows the screen for displaying the management information of the tenant. This screen displays a box representing the object to be managed. 
         [0197]    A box  2005  represents the NW-SW  111 . The box  2005  displays the display name. While not drawn in the diagram, a component such as a port configuring the NW-SW  105  may also be expressed by creating an additional box within the box. Moreover, while the management network switch NW-SW 1 has a connection relation with all objects to be managed, it is omitted in the diagram. 
         [0198]    A box  2006  and a box  2009  respectively express the server  105 - 1  and the server  105 - 3  described above. The box  2006  and the box  2009  respectively display the display name. Moreover, the box  2006  includes a box  2007  and a box  2008 , which respectively express the application running on the physical server  105 - 1 . The box  2009  includes a box  2010  in the box. The box  2010  expresses the virtual server  108 - 1 . Moreover, the box  2010  expresses the application running on the virtual server  108 - 1  as a box  2011  in the same manner as the physical server of the box  2006 . 
         [0199]    A box  2012  shows the FC-SW 1. While only the box  2012  is shown in the diagram, a component such as an internal port may also be expressed by creating an additional box within the box  2012 . 
         [0200]    A box  2013  shows the storage 1. The box  2013  includes a box  2014  and a box  2015 , which express the Volume, within the box. The box  2014  and the box  2015  are respectively connected, via the box  2012  showing the FC-SW 1, to the box  2006  expressing the physical server and the box  2010  expressing the virtual server. 
         [0201]    With the GUI of  FIG. 20 , the name of the object to be managed indicated in the box  2005  to the box  2013  is the target of the present invention. The display area of the name changes depending on the size of the GUI screen  2001  or the size of the respective boxes. In accordance with the foregoing change, the present invention enables the display of a Human-Readable name based on the method explained above. 
         [0202]    As described above, a Human-Readable display name can be generated and displayed by using the topology information, the administrator information, and the screen information of the object to be managed. Note that the topology table  215  of this Embodiment was explained in a mode where the entire objects to be managed are generated as a topology table triggered by an instruction from the administrator, but the generation of the topology table is not limited to the foregoing mode. As other modes, considered may be temporarily generating a topology table configured from objects to be managed related to the objective of the administrator&#39;s operations and the objects to be managed that are related thereto triggered by the administrator&#39;s operation on the GUI (for example, when the screen on the GUI changes from a screen that is not displaying the display name of the object to be managed to a screen that displays the display name of the object to be managed, or when the GUI is activated with a screen displaying the foregoing display name as the initial screen). Specifically, considered may be a case of generating a topology table of objects to be managed subject to a failure alert and objects to be managed which are physically or logically connected thereto for the objective of analyzing or identifying the root cause of failure during the occurrence of a failure. 
         [0203]    In Embodiment 1, the display name of the object to be managed containing information which is Human-Readable and required by the administrator was generated by abbreviating the management object group of the administrator in the form labels, and combining the labels to match the administrator and the management screen. 
       Embodiment 2 
       [0204]    In Embodiment 1, a label was generated by abbreviating the display name of the object to be managed based on the label rule table  210 , and the label was added to or deleted from the display name of the object to be managed according to the priority. 
         [0205]    In Embodiment 2, the display name of the object to be managed is analyzed based on a given pattern, and the display name is divided. The character string of the divided display name is used as a label, and the display name of the object to be managed is reconfigured according to the priority. 
         [0206]      FIG. 21  is an explanatory diagram showing an example of the label rule table in Embodiment 2 of the present invention. 
         [0207]    The label rule table  210  includes a rule ID  2101 , account information  2102 , a management object type  2103 , a linking method  2104 , a label type  2105 , and a priority  2106 . 
         [0208]    The rule ID  2101  stores an identifier for uniquely identifying the generation rule upon generating a label. 
         [0209]    The account information  2102  stores the account information to be used as the condition for determining whether to apply the generation rule of the rule ID  2101 . Depending on the generation rule, a plurality of accounts may refer to the same generation rule. Moreover, in  FIG. 21 , while the generation rule is determined based on the account information, the generation rule may also be determined for each type of administrator such as the infrastructure administrator or the tenant administrator. 
         [0210]    The management object type  2103  stores information regarding the type of object to be managed to be used as the condition for determining whether to apply the generation rule of the rule ID  2101 . Depending on the generation rule, there may be cases where the generation rule is applied only in cases of tenant information, or cases where the generation rule is applied only in cases of a virtual server. 
         [0211]    The linking method  2104  stores the linking method in cases of linking labels. 
         [0212]    The linking method stores the method of linking the character strings as labels. For example, when the naming rule of the server is “location_(underscore) tenant_(underscore) application-(hyphen) number”, since there is no character string to be linked before the location, the column of the linking method is blank, and because there is an _(underscore) before the character string of the tenant (between “location” and “tenant”), _(underscore) is indicated as the linking method. The same applies to subsequent applications and numbers. 
         [0213]    The label type  2105  expresses the type of label that is generated upon analyzing and dividing the display name of the object to be managed. 
         [0214]    The priority  2106  expresses the priority in cases of using the information of the label type  2105  as the display name of the object to be managed. In the diagram, the priority is indicated in ascending order, and the priority is higher as the value is smaller. 
         [0215]    As a result of using the foregoing label rule table  210 , for instance, when the display name of the object to be managed is “Tokyo_ABC_Web-1”, the display name can be analyzed with “Tokyo” as the label of “location” of the third highest priority, “ABC” as the label of “tenant” of the highest priority, “Web” as the label of “application” of the second highest priority, and “1” as the label of “number” of the fourth highest priority. 
         [0216]    Subsequently, these labels can be registered in the label table  216  in the same manner as Embodiment 1.