JP2013012225A - Name specification program, configuration management server and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To specify an application name more accurately, for arbitrary application which operates on a business server.SOLUTION: A configuration management server communicably connected with a business server which manages a process generated by an application program which realizes a service for a business client comprises: a storage device for storing a collected process list in which process identification information for identifying a process and waiting port information showing a port the process is waiting for are associated with each other; and a control part for acquiring an HTML document from the business server on the basis of designated port information, acquiring a TITLE element showing a title of the HTML document from the acquired HTML document, and specifying the acquired TITLE element as an application name of the process identification information which is associated with the waiting port information matching the designated port information in the collected process list.

Description

  The present invention mainly relates to a technique for identifying names of applications constituting the business system as a business system management method executed in an information processing system including a plurality of computers using a network.

  There are a business server group and a business client group connected to a network, and there is a computer system that provides a service to a business client by operating an application on the business server. In this computer system, it is important to know information about what name of an application is running on which business server in order to stably operate the business system.

  One way to know the application name is to keep the relationship between the application name and the TCP (Transmission Control Protocol) / UDP (User Datagram Protocol) standby port as information, or to communicate using an application-specific management protocol. By doing so, a method of identifying the name of an application that operates on the business server is considered (Non-patent Document 1).

  Further, a method is conceivable in which the directory name itself of the executable file installed on the business server is obtained as the name of the installed application (Non-patent Document 2).

"IBM Tivoli Application Dependency Discovery Manager", [online], October 2008, http://www-01.ibm.com/software/tivoli/products/taddm/ InstList 2002, http://www.forest.impress.co.jp/lib/sys/instmng/softmng/instlist.html

The above conventional technique has the following problems.
In the method of holding the relationship between the application name and the TCP / UDP standby port as information, or communicating with the application specific management protocol, the standby port and management protocol are different for each application and each application version. There is a problem that the names of new types of applications and upgraded applications cannot be specified because they may be different.

  To solve this, there is a method of using the directory name of the executable file as described above. By using the directory name of the executable file, the name of the application can be obtained for any version of any application. Unfortunately, there are many cases where the application name obtained is not accurate in the method using the directory name of the executable file. For example, when there is an application that installs an executable file divided into a plurality of directories, the application is specified as a plurality of independent applications. In recent years, some commercial applications are Java (registered trademark) and the rest are implemented as normal execution files. In this case, a directory for storing a Java processing system and a normal execution file are stored. Since the directories are different, the above problems occur.

  In addition, execution files of a plurality of applications are placed (stored) in directories (shared directories) such as / usr / bin / and / usr / local / bin /. Although processes consisting of executable files placed in these directories are originally different applications, they are all identified as the same application name, and the name is completely different from the application name.

  Therefore, an object of the present invention is to more accurately specify the name of an application for an arbitrary application operating on a business server.

The present invention includes a communication interface capable of communicating with a business server that stores and manages a process generated by operating an application program that implements a service provided to a business client, process identification information for identifying a process, Configuration management comprising: a storage unit storing process information in which standby port information indicating a port on which the process is listening is associated; and a control unit that identifies an application name of a process executed by the business server The control unit of the server indicates a first step of acquiring an HTML document from the business server via the communication interface based on the designated port information, and the title of the HTML document from the HTML document acquired by the first step. A second step of obtaining a TITLE element; A third step of identifying the TITLE element acquired by the step as the application name of the process identification information associated with the standby port information of the process information stored in the storage unit that matches the specified port information; Is executed.

  ADVANTAGE OF THE INVENTION According to this invention, the name of an application can be pinpointed more correctly with respect to the arbitrary applications which operate on a business server.

It is an example of the figure showing the whole structure of the information processing system of the 1st Embodiment of this invention. 2 is an example of a diagram illustrating a configuration of a configuration management server 101. FIG. It is a figure which shows the structure of the collected process list | wrist 210, the content, and a specific example. 5 is a diagram illustrating a structure, contents, and a specific example of a business server list 220. 3 is a diagram illustrating a structure, contents, and a specific example of an OS standard process list 230. FIG. It is a figure which shows the structure of the interpreter name list 240, the content, and a specific example. It is a figure which shows the structure of the shared directory absolute path name list 250, the content, and a specific example. It is a figure which shows the structure of the execution directory relative path name list 260, the content, and a specific example. It is a figure which shows the structure of the application name acquisition method list | wrist 270, the content, and a specific example. It is a figure which shows the structure of the specified application name list 280, the content, and a specific example. It is a figure which shows the flow of the data between each process part and the various information in the 1st Embodiment of this invention. It is a flowchart which shows the identification method of the application name in the 1st Embodiment of this invention. The flow chart continues to FIG. 13 and FIG. FIG. 13 is a flowchart illustrating a method for identifying an application name, continuing from FIG. 12. FIG. 13 is a flowchart illustrating a method for identifying an application name, continuing from FIG. 12. FIG. 13 is a flowchart illustrating a method for identifying an application name, continuing from FIG. 12.

<First Embodiment>
〔Constitution〕
Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is an example of a diagram illustrating the overall configuration of the information processing system according to the first embodiment of this invention. The information processing system includes a configuration management server 101, a business server 102, and a business client 103. The business server 102 provides a service to the business client 103 by operating an application program (hereinafter, simply referred to as “application”) on the server.

  The configuration management server 101 and the business server 102 are connected to the management network 104 via a link 109. The business server 102 and the business client 103 are connected to the business network 105 via a link 109. The link 109 is a wired or wireless connection method, and may include a subnetwork. The configuration management server 101, the business server 102, and the business client 103 may be connected to the management network 104 or the business network 105 by different methods. The management network 104 and the business network 105 may be the same network.

  The business server 102 and the business client 103 are each exemplified as two units, but may be one or more units. Further, any two or more of the configuration management server 101, the business server 102, and the business client 103 may be the same casing or the same virtual machine (VM).

  The business server 102 stores the contents of the execution file held by the business server 102 as a program in the main memory of the business server 102, and generates a process by executing the program on the processor of the business server 102. The business server 102 provides a service to the business client 103 by executing an application program and generating one or more processes.

The business server 102 includes a process management unit 106, a network management unit 107, and a command execution unit 108.
The process management unit 106 holds information on processes generated on the business server 102.
The network management unit 107 holds information on a TCP or UDP standby port used by the process.
The command execution unit 108 executes a command input from an external computer such as the business client 103, for example.
The process management unit 106, the network management unit 107, and the command execution unit 108 may store a program in the main memory of the business server 102, and the program may be executed by the processor of the business server 102. Further, the process management unit 106, the network management unit 107, and the command execution unit 108 may be integrated and realized by hardware.

  The configuration management server 101 includes a process information collection unit 120, a standard process determination unit 121, an interpreter determination unit 122, a shared directory determination unit 123, a subdirectory determination unit 124, an application name specification unit 125, and a special application name specification unit 126. Note that at least one of the standard process determination unit 121, the interpreter determination unit 122, the shared directory determination unit 123, the subdirectory determination unit 124, the application name specification unit 125, and the special application name specification unit 126 does not exist. good. The configuration management server 101 will be described in detail with reference to FIG.

  FIG. 2 is an example of a diagram illustrating the configuration of the configuration management server 101. The configuration management server 101 includes a processor 200 (control unit), a main storage 201 (storage unit), an input device 203, an output device 204, an external storage device interface 205, a communication interface 206, and a storage device 110 (storage unit). They are connected so that they can communicate with each other.

  Process information collection program 2020, standard process determination program 2021, interpreter determination program 2022, shared directory determination program 2023, subdirectory determination program 2024, application name specification program 2025, special application name specification program 2026, etc. stored in the main memory 201 Are executed by the processor 200, the process information collection unit 120, the standard process determination unit 121, the interpreter determination unit 122, the shared directory determination unit 123, the subdirectory determination unit 124, the application name identification unit 125, and the special application Processing in each unit such as the name specifying unit 126 is performed.

  Of the various programs 202 such as a process information collection program 2020, a standard process determination program 2021, an interpreter determination program 2022, a shared directory determination program 2023, a subdirectory determination program 2024, an application name specification program 2025, and a special application name specification program 2026. At least one or more may not exist.

  Instead of executing the various programs 202 by the processor 200, the process information collecting unit 120, the standard process determining unit 121, the interpreter determining unit 122, the shared directory determining unit 123, the subdirectory determining unit 124, the application name specifying unit 125, the special application name The identification unit 126 may be realized by hardware by integrating it as a processing unit that performs each process. Hereinafter, in order to simplify the description, each processing unit realized by the processor 200 executing the various programs 202 on the main memory 201 will be described as the subject of each processing.

  The external storage device interface 205 is connected to the storage device 110. The storage device 110 may be provided outside the configuration management server 101 or may be provided inside the configuration management server 101. The storage device 110 includes a collected process list 210 (process information), a business server list 220 (business server information), an OS standard process list 230 (operating system standard process information), an interpreter name list 240 (interpreter name information), and a shared directory. Absolute path name list 250 (shared directory absolute path name information), execution directory relative path name list 260 (execution directory relative path name information), application name acquisition method list 270, specified application name list 280 (specified application program name information) ) Etc. are stored.

  Collected process list 210, business server list 220, OS standard process list 230, interpreter name list 240, shared directory absolute path name list 250, execution directory name relative path list 260, application name acquisition method list 270, specified application name list At least one or more of 280 may not exist. Also, one or more pieces of information 207 held in the storage device 110 may be stored in the main memory 201. Various types of information 207 will be described in detail with reference to FIGS.

  The communication interface 206 is connected to the management network 104. The communication interface 206 and the external storage device interface 205 may be the same interface.

〔data structure〕
FIG. 3 is a diagram illustrating the structure, contents, and specific example of the collected process list 210. The collected process list 210 is in a tabular format and includes one or more lines. Every row contains 5 columns. Here, the five columns are a business server name 211, a process ID (Identification) 212, an executable file absolute path name 213, a command line 214, and a standby port list 215. Although not shown, each row of the collected process list 210 may include other columns.

  The collected process list 210 stores one line of information for processes operating on each business server 102 existing in the information processing system. That is, the host name of the business server 102 is the business server name 211, the process ID for identifying the process is the process ID 212, the absolute path name of the process execution file is the execution file absolute path name 213, and the process command line (process (Including the name) in the command line 214 and the TCP or UDP port on which the process is waiting is stored in the waiting port list 215.

  The information stored in the business server name 211 can be obtained by the same method as obtaining the host name of the business server 102 described in FIG. That is, it can be acquired from the execution result when the hostname command is executed on the business server 102 and the information of the instance of the W32 Win32_ComputerSystem class.

  The process ID 212, the process execution file absolute path name 213, and the process command line 214 can be acquired from the process management unit 106 in the business server 102. For example, the execution result when the ps command or the lsof command is executed on the business server 102, the contents of a file under the / proc / file system, or an instance of the Win32_Process class of WMI (Windows (registered trademark) Management Infrastructure) These information can be acquired from the process management unit 106 by referring to the properties. Other methods may be used to obtain the process ID 212, the process execution file absolute path name 213, and the process command line 214 information.

  Information stored in the standby port list 215 is acquired from the network management unit 107 in the business server 102. For example, by referring to the execution result when the netstat command or the lsof command is executed on the business server 102, these pieces of information can be acquired from the network management unit 107. Information on the standby port list 215 may be acquired using a method other than these.

  Information stored in the collected process list 210 is used in all of the various programs 202. The information of the collected process list 210 may be created manually by a system administrator of the information processing system, or may be created by using some tool or utility.

  If the special application name specifying unit 126 does not perform processing for obtaining an application name using the application name acquisition method list 270 as described later, the collected port list 215 may not include the standby port list 215. good. If the interpreter determination unit 122 does not perform processing for obtaining a directory name or script name from the command line 214 using the interpreter name list 240, the collected process list 210 may not include the command line 214.

  FIG. 4 is a diagram illustrating the structure, contents, and specific example of the business server list 220. The business server list 220 has a tabular format and includes one or more rows. Every row contains three columns. Here, the three columns are the business server name 221, the OS name 222, and the OS version 223. Although not shown, each row of the business server list 220 may include other columns.

  The business server list 220 stores one line of information for each business server 102 existing in the information processing system. That is, the host name of the business server 102 is stored in the business server name 221, and the name and version of the OS (for example, Windows) operating on the business server 102 are stored in the OS name 222 and the OS version 223, respectively.

Among these, the business server name 221 can be acquired from the execution result when the hostname command is executed on the business server 102 and the instance information of the Win32_ComputerSystem class of WMI.
The OS name 222 and the OS version 223 can be acquired from, for example, an execution result when the uname command is executed on the business server 102 or information on an instance of the WMI Win32_OperationSystem class.

  Information stored in the business server list 220 is used in the standard process determination unit 121. The information stored in the business server list 220 may be created manually by a system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 5 is a diagram showing the structure, contents, and specific example of the OS standard process list 230. The OS standard process list 230 is in a table format and includes one or more lines. Every row contains three columns. Here, the three columns are OS name 231, OS version 232, and executable file absolute path name 233. Although not shown, each row of the OS standard process list 230 may include other columns.

  The OS standard process list 230 includes information on the absolute path name of an execution file of a process that is operating immediately after OS installation and the absolute path name of an execution file of a process that does not need to specify an application name. Along with the version, the executable file absolute path name 233, the OS name 231 and the OS version 232 are stored. The absolute path name of the execution file of the process that is running immediately after OS installation is, for example, executed when the OS is installed on an arbitrary computer and the ps command or lsof command is executed on the computer immediately after the installation is completed. It can be acquired from the result and information of an instance of the Win32_Process class of WMI. The OS name and OS version can be acquired from the execution result when the uname command is executed on the computer and the instance information of the WMI Win32_OperatingSystem class.

  Information stored in the OS standard process list 230 is used in the standard process determination unit 121. Information stored in the OS standard process list 230 may be created manually by a system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 6 is a diagram showing the structure, contents, and specific example of the interpreter name list 240. The interpreter name list 240 is in a tabular format and consists of one or more lines. Every row contains one column. Here, one column is an interpreter name 241. Although not shown, each row of the interpreter name list 240 may include other columns.

  In the interpreter name list 240, process names of interpreter processing systems that process script languages such as perl, Python, and sh, and process names of interpreter (language) processing systems that process intermediate languages such as Java are stored in the interpreter name 241. ing.

  Information stored in the interpreter name list 240 is used in the interpreter determination unit 122. The information stored in the interpreter name list 240 may be created manually by a system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 7 is a diagram showing the structure, contents, and a specific example of the shared directory absolute path name list 250. The shared directory absolute path name list 250 is in a tabular format and includes one or more lines. Every row contains one column. Here, one column is the shared directory absolute path name 251. Although not shown, each row of the shared directory absolute path name list 250 may include other columns.

  The shared directory absolute path name list 250 includes a plurality of applications under the directory such as / usr / bin /, / usr / local / bin /, / opt /, c: \, c: \ Program Files \, and the like. The directory name (absolute path name) of the directory that stores the execution file is stored in the shared directory absolute path name 251.

  Information stored in the shared directory absolute path name list 250 is used in the shared directory determination unit 123. The information stored in the shared directory absolute path name list 250 may be created manually by the system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 8 is a diagram showing the structure, contents, and specific example of the execution directory relative path name list 260. The execution directory relative path name list 260 is in a tabular format and includes one or more lines. Every row contains one column. Here, one column is an execution directory relative path name 261. Although not shown, each row of the execution directory relative path name list 260 may include other columns.

  In the execution directory relative path name list 260, sub directory names where there is a high possibility that an execution file is placed immediately below or lower than, such as / bin /, / tools /, are stored in the execution directory relative path name 261.

  Information stored in the execution directory name list 260 is used in the subdirectory determination unit 124 and the application name identification unit 125. The information stored in the execution directory relative path name list 260 may be created manually by the system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 9 is a diagram showing the structure, contents, and specific example of the application name acquisition method list 270. The application name acquisition method list 270 has a tabular format and includes one or more lines. Every row contains three columns. Here, the three columns are a standby port number 271, a use protocol 272, and an acquisition method 273. Although not shown, each row of the application name acquisition method list 270 may include other columns.

  The application name acquisition method list 270 stores, as a method other than obtaining the application name from the directory name, what protocol is used and what information is acquired from the application to identify the application name. . Specifically, the standby port number for the application is the standby port number 271, the protocol to be used is the usage protocol 272, and the data acquisition method according to the protocol to be used (for example, if the protocol to be used is http, Data to be acquired is an HTTP document (details will be described later)).

  Information stored in the application name acquisition method list 270 is used in the special application name specifying unit 126. The information stored in the execution directory name list 260 may be created manually by a system administrator of the information processing system, or may be created using some tool or utility.

  FIG. 10 is a diagram showing the structure, contents, and specific example of the identified application name list 280. The identified application name list 280 has a tabular format and includes one or more lines. Every row contains three columns. Here, the three columns are an absolute path name 281, a process ID list 282, and an application name 283. Although not shown, each row of the identified application name list 280 may include other columns.

  The identified application name list 280 stores the names of applications identified in the present embodiment and information related thereto. Specifically, the absolute path name of the directory to which the specified application is installed is stored in the absolute path name 281, the process ID of the process is stored in the process ID list 282, and the specified application name is stored in the application name 283. .

  Information stored in the identified application name list 280 is used in the interpreter determination unit 122, the shared directory determination unit 123, the subdirectory determination unit 124, and the application name identification unit 125. The information stored in the identified application name list 280 can be created manually by the system administrator of the information processing system or by automating part or all of the work using some tool or utility. May be.

[Outline of processing]
FIG. 11 shows a standard process determination unit 121, an interpreter determination unit 122, a shared directory determination unit 123, a subdirectory determination unit 124, and an application name specification unit 125 in the configuration management server 101 according to the first embodiment of this invention. The processing flow in each processing unit such as the special application name specifying unit 126, the business server list 210 stored in the storage device 110, the collected process list 220, the OS standard process list 230, the interpreter name list 240, shared It is a figure which shows the data flow between various information 207, such as the directory absolute path name list 250, the execution directory name relative path list 260, the application name acquisition method list 270, and the specified application name list 280, and each processing unit. Details of processing in each processing unit will be described with reference to FIGS. In FIG. 11, a solid line arrow indicates a rough process flow, and a broken line arrow indicates a data flow.

  First, the business server name 130 is input to the process information collection unit 120. The business server name 130 input here is, for example, input from the input device 203 of the configuration management server 101 by a user who wants to specify the name of an application running on the business server 102. The process information collection unit 120 acquires a list of processes operating on the business server 102 corresponding to the business server name 130 from the collected process list 210. Information on the collected process list 210 is acquired from the process management unit 106 and the network management unit 107 in the business server 102. Information may be acquired using a method other than this and stored in the collected process list 220. Further, the process information collection unit 120 may directly acquire from the process management unit 106 and the network management unit 107.

  Next, using each of the acquired processes as an input, the standard process determination unit 121, the interpreter determination unit 122, the shared directory determination unit 123, and the subdirectory determination unit 124 perform processing, and an application name specifying unit 125, a special application name specifying unit In 126, the application name is specified.

  It should be noted that at least one processing unit among the standard process determination unit 121, interpreter determination unit 122, shared directory determination unit 123, subdirectory determination unit 124, and special application name identification unit 126 may not exist.

  The standard process determination unit 121 determines whether it is necessary to specify an application name for the process obtained by the process information collection unit 120. This obtains the OS name and OS version of the business server 102 from the business server list 220, and indicates whether or not the input process is an OS standard process for the OS name and the OS version. Do it by examining. Note that the OS name and OS version of the business server may be acquired directly from the business server 102 by the standard process determination unit 121.

  By eliminating the application as an OS that does not need to specify a name or the version of the OS by the process in the standard process determination unit 121, it is not necessary to obtain a large number of application names. Application names can be obtained by focusing on applications that are directly related to the system.

  The interpreter determination unit 122 determines whether the process obtained by the process information collection unit 120 is an interpreter processing system process (interpreter process) such as Java, Perl, or sh by referring to the interpreter name list 240. These interpreters may be used from different applications. In this case, when the application name is obtained from the directory name for the interpreter process, different applications have the same application name. Therefore, when it is determined that the process is an interpreter process, the application name is specified from the command line, not the directory name of the process execution file.

  By the processing in the interpreter determination unit 122, the application name can be specified more accurately for the interpreter process.

  The shared directory determination unit 123 determines whether the process execution file obtained by the process information collection unit 120 exists directly under the shared directory by referring to the shared directory absolute path name list 250. A shared directory is a number of applications directly below / usr / bin /, / usr / local / bin /, etc. (more specifically, executable files that implement these applications or implement the processes). The directory to be placed. When an application name is obtained from the directory name of the process execution file for a process including an execution file placed directly under this directory, different applications have the same application name. Therefore, when it is determined that the process consists of an executable file directly under the shared directory, the application name is obtained from the executable file name.

  By the processing in the shared directory determination unit 123, the application name can be specified more accurately for the process including the executable file placed immediately under the shared directory.

  The subdirectory determination unit 124 determines whether or not the processes can be regarded as the same application by referring to the execution directory relative path name list 260, although the directory names of the execution files of the processes are different. For example, if there is an application installed in “c: \ myapp \”, the directory of process A is “c: \ myapp \ bin \” and the directory of process B is “c: \ myapp \ tools \” To do. For these processes, when the application name is obtained from the directory name of the executable file, the application name is supposed to be the same application, but the application name is different. Therefore, the relative path name of the directory in which the execution file is often placed is included in the execution directory relative path name list 260, and if the end of the directory name of the process execution file matches that, it is excluded. Then, the directory names excluded for a plurality of processes are compared with each other, and processes in which the directory names match or one of the processes becomes the other subdirectory are regarded as the same application.

  By the processing in the subdirectory determination unit 124, the application name can be specified more accurately for an application that installs an execution file in a plurality of directories deeper than the installation destination directory.

  The application name specifying unit 125 obtains the application name from only the process information. When the interpreter determination unit 122 determines that the process is an interpreter, the application name is obtained from the command line. When the shared directory determination unit 123 determines that the process execution file is directly under the shared directory, the application name is obtained from the execution file name. Otherwise, the application name is obtained from the directory name of the process execution file.

  When obtaining the application name from the directory name, it is checked whether the end of the directory name matches the execution directory relative path name list 260, and if it matches, the application name is obtained from the directory name after excluding it. That is, when the subdirectory determination unit 124 determines that a directory has a parent-child relationship in the same application with a different directory name of the process execution file, the application name is obtained from the parent directory name.

  By the processing in the application name specifying unit 125, the application name can be specified for an arbitrary application operating on the business server 102.

  The special application name identifying unit 126 obtains the application name using a protocol that can be used in common by a plurality of types of applications, such as HTML and JSR77, instead of process information. When the standby port of the process matches the standby port indicated by a certain line in the application name acquisition method list 270, that is, the value registered in the standby port number 271, the protocol indicated by that line, That is, the application name is obtained using the value registered in the usage protocol 272.

  By the processing in the special application name specifying unit 126, the application name can be specified more accurately than the application name obtained by the application name specifying unit 125 for some applications.

  When the above processing is performed, a list of application names operating on the business server 102 corresponding to the input business server name 130 is stored in the identified application name list 280. The contents can be output via an output device 204 such as a display or a printer.

[Details of processing]
Details of processing of the application name specifying method in the first embodiment of the present invention will be described with reference to FIGS. 12, 13 (generic name of FIGS. 13A and 13B) and FIG.
FIG. 12 shows the processing in the process information collection unit 120 (step 401, step 402), the processing in the standard process determination unit 121 (step 403, step 404), and the application name in the first embodiment of the present invention. It is a flowchart which shows the process (Step 408 to Step 413) in the specific | specification part 125. FIG. The processing in FIG. 12 starts with receiving the business server name as an argument.

  First, the process information collection unit 120 acquires each row in the collected process list 210 using the received business server name as a key (step 401). If there is a line to be acquired (“repeat” in step 401), it is stored in the variable P and the process proceeds to step 402. If there are no more rows to be acquired and the processing for each row is completed (“After Repeat” in step 401), the process proceeds to step 441 in FIG. The process information collection unit 120 may directly acquire process information from the process management unit 106 and the network management unit 107 in the actual business server 101 and store them in the variable P. Further, instead of proceeding to step 441 in FIG. 14, the processing may be terminated here.

  Next, from the executable file absolute path name (210; see FIG. 3) in the variable P, the executable file name of the variable P that does not include the directory name part and the directory name is extracted, and the former is the directory absolute path name of the variable P. Are stored in the variable D and the latter in the variable E (step 402). After storing in variables D and E, the process proceeds to step 403.

  Next, the standard process determination unit 121 searches for a row in the business server list 220 that matches the received business server name. Then, the OS name (222; see FIG. 4) and OS version (223; see FIG. 4) are acquired from the line (step 403). Note that the OS name and OS version of the business server may be acquired directly from the business server 102 by the standard process determination unit 121. After the acquisition, go to step 404.

Next, it is checked whether the OS standard process list 230 includes a line that matches the OS name and OS version acquired in step 403 and the absolute path name of the executable file stored in the variable P. That is, it is determined whether or not the line matches the values of the OS name 231, OS version 232, and executable file absolute path name 233 (step 404). If it exists (Yes in Step 404), the process returns to Step 401. If it does not exist (No in Step 404), the process proceeds to Step 420 in FIG.
Note that the processing (steps 403 and 404) in the standard process determination unit 121 may be omitted, and step 420 in FIG.

  Next, after any one of the interpreter determination unit 122, shared directory determination unit 123, and subdirectory determination unit 124 (details will be described later), the application name identification unit 125 performs the character string of the variable A (see step 426 later). It is checked whether the first part of the value matches any of the shared directory absolute path names 251 in the shared directory absolute path name list 250 (step 408). If they match (Yes in step 408), the matched shared directory absolute path name 251 is removed from the beginning of the character string value of the variable A (step 409). Thereafter, the directory delimiter (/ or \) is replaced with a blank character from the character string value of the variable A (step 410). On the other hand, if there is no match (No in step 408), step 409 is skipped and the process proceeds to step 410.

  Subsequently, it is checked whether a line having the same absolute path name 281 as the value of the variable D (referred to as “line X”) exists in the identified application name list 280 (step 411). If it does not exist (No in step 411), the value of the variable D is the absolute path name 281; the process ID in the variable P is the process ID list 282; the value of the variable A is the application name 283; A row is added to (step 412). If it exists (Yes in step 411), the process ID in the variable P is added to the process ID list 282 for the row X in the identified application name list 280, and the value of the variable A is stored in the application name 283. The row X is updated (step 413). In both step 412 and step 413, the process returns to step 401 next.

  FIG. 13 shows processing in the interpreter determination unit 122 (steps 420 to 426), processing in the shared directory determination unit 123 (steps 427 to 430), and subdirectory determination unit in the first exemplary embodiment of the present invention. It is a flowchart which shows the process (step 431-step 437) in 124.

  First, the interpreter determination unit 122 substitutes false for the variable I (step 420), and then checks whether an interpreter name 241 that matches the value of the variable E exists in the interpreter name list 240 (step 421). If it does not exist (No in step 421), the process proceeds to step 426. If it exists (Yes in Step 421), the process proceeds to Step 422.

  Next, it is checked whether the execution file name indicated by the variable E is Java (step 422). When it is determined as Java (Yes in step 422), the absolute path name of the intermediate language file is obtained from the command line in the variable P, and the obtained absolute path name of the intermediate language file is stored in the variable S (step 423). After the storage, go to step 425. On the other hand, when it is determined that it is not Java (No in step 422), the absolute path name of the script file is obtained from the command line in the variable P, and the obtained absolute path name of the script file is stored in the variable S (step 424). ). After the storage, go to step 425.

  Next, from the absolute path name of the variable S, the execution file name of the variable S that does not include the directory name portion and the directory name is extracted, the former is set as the variable D as the directory absolute path name of the variable S, and the latter is set as the variable E. Then, store true and substitute true for variable I (step 425). After these storage and assignment, the value of variable D is assigned to variable A (step 426). After the substitution, go to step 427. Note that a part of the processing (from step 421 to step 425) in the interpreter determination unit 122 may be omitted, and the process may proceed from step 420 to step 426. Further, for a processing system using an intermediate language other than Java, processing corresponding to step 422 to step 423 may be added between step 422 and step 424.

  An example of a method for obtaining the absolute path name of the Java intermediate language file in step 423 is as follows. In the case of Java, there is a command line option passed to the processor itself at the beginning of the command line, followed by a class name or a jar file name to be executed.

  When the class name is next to the command line option, the class path specified by the command line option -cp or -classpath or the environment variable CLASSPATH is obtained. If there is a “.” In the class path, get the current working directory of the process and replace it with “.”. Then, on the file system of the business server 102 corresponding to the business server name received at the start of the processing in FIG. 12, the class name is stored in the directory indicated by the class path or the jar file indicated by the class path. Check whether a corresponding class file exists. If the class file to be found exists in the directory, the absolute path name of the class file is obtained and used as the absolute path name of the intermediate language file. If the class file to be found exists in the jar file, the absolute path name of the jar file is obtained and set as the absolute path name of the intermediate language file.

  If there is a jar file name next to the command line option, the absolute path name of the jar file is obtained and used as the absolute path name of the script. When the jar file name is a relative path, the current working directory set in the process is obtained, and the absolute path is obtained by considering the current working directory as a relative path from the current working directory. The current working directory and environment variables set for the process can be acquired by inquiring the process management unit 106 in the business server 102.

  An example of a method for obtaining the absolute path name of the script file in step 424 is as follows. The method for obtaining the absolute path name of the script file from the command line differs depending on the interpreter processing system. For interpreter processing systems that process script languages, such as perl, Python, and sh, there are usually zero or more command line options passed to the processing system itself starting with "-" at the beginning of the command line, followed by execution Get the name of the script file that should be used. When the file name of the script is a relative path, the current working directory of the process is obtained, and the absolute path of the script file is obtained by regarding the relative path from the current working directory. The current working directory set for a process can be acquired by inquiring the process management unit 106 in the business server 102.

  Next, the shared directory determination unit 123 checks whether the shared directory absolute path name 251 that matches the value of the variable D exists in the shared directory absolute path name list 250 (step 427). If it does not exist (No in step 427), the process proceeds to step 431. If it exists (Yes in step 427), it is checked whether the variable I is false and the execution file name in the variable P is equal to the process name in the variable P (step 428). The execution file name is obtained by excluding the directory name from the absolute path name of the execution file in P, and the process name is the first character string obtained by separating the command line character string in P with a space. When the condition of step 428 is met (Yes in step 428), the process name in the variable P is substituted into the variable A (step 429), and then the process proceeds to step 408 in FIG. If the above condition is not met (No in step 428), the variable A is stored with the concatenation of the character string of the value of the variable D and the character string of the value of the variable E (D + E) (step 430). Proceed to step 408 of FIG. Note that the processing (from step 427 to step 430) in the shared directory determination unit 123 may be omitted, and the process may proceed from step 426 to step 431.

  Next, the subdirectory determination unit 124 determines whether the subdirectory name at the end of the directory absolute path name indicated by the variable D matches any of the execution directory relative path names 261 in the execution directory relative path name list 260. That is, it is checked whether or not there is an execution directory relative path name 261 that matches the subdirectory name (step 431). For example, when the execution directory relative path name 261 is only “bin”, if the value of the variable D is “/ opt / someapp / bin /”, it is determined to match, and “/ opt / someapp / sbin / "Is determined not to match. If there is a match (Yes in step 431), the matching execution directory relative path name is removed from the end of the variable D (step 432). After removal, go to step 433. On the other hand, if there is no match (No in step 431), the process proceeds to step 433 as it is.

  Next, from each line of the identified application name list 280, a line having the absolute path name 281 as the directory name is acquired (step 433). If there is a line to be acquired (“repeat” in step 433), it is stored in the variable C and the process proceeds to step 434. If there are no more rows to be acquired and the processing for each row is completed (“after repetition” in step 433), the process proceeds to step 408 in FIG.

  Next, it is checked whether the absolute path name indicated by the variable C is a subdirectory name of the directory name indicated by the variable D (step 434). If so (Yes in Step 434), the absolute path name 281 is replaced with the value of the variable D for the line corresponding to the variable C in the identified application list 280, and the process proceeds to Step 408 in FIG. Step 435). Otherwise (No in step 434), the process proceeds to step 436.

  Next, it is checked whether the directory name indicated by the variable D is the same as the absolute path name indicated by the variable C or a subdirectory name of the directory name indicated by the variable C (step 436). If so (Yes in step 436), the value of variable C is stored in variable D, and the application name 283 in variable C is stored in variable A (step 437). After storing, the process proceeds to step 408 in FIG. On the other hand, if not (No in step 436), the process returns to step 433.

  Note that the processing (from step 431 to step 437) in the subdirectory determination unit 124 may be omitted, and the process may proceed from step 427 to step 408 in FIG. Further, a part of the processing (from step 433 to step 437) in the subdirectory determination unit 124 may be omitted, and the process may proceed from step 431 and step 432 to step 408 in FIG.

  FIG. 14 is a flowchart showing processing (steps 441 to 449) of the special application name specifying unit 126 in the first embodiment of this invention.

  First, the special application name specifying unit 126 acquires each row of the specified application name list 280 (step 441). If there is a line to be acquired (“repeated” in step 441), the contents of the line are stored in the variable P and the process proceeds to step 442. If there are no more rows to be acquired and the processing for each row is completed (“After Repeat” in step 441), the processing is terminated.

  Next, each line of the application name acquisition method list 270 is acquired (step 442). If there is a line to be acquired (“repeat” in step 442), the contents of that line are stored in the variable G and the process proceeds to step 443. If there are no more rows to be acquired and the processing for each row is completed (“after repetition” in step 442), the process returns to step 441.

  Next, it is checked whether the standby port number of the variable G (271; see FIG. 9) exists in the list of standby ports of the variable P (215; see FIG. 3) (step 443). That is, it is determined whether or not the value stored in the standby port number 271 matches the value stored in the standby port list 215. If it exists (Yes in Step 443), the process proceeds to Step 444. If it does not exist (No in Step 443), the process returns to Step 442.

  Next, it is checked whether or not the acquisition method (273; see FIG. 9) indicated by the variable G is HTML (step 444). If it is HTML (Yes in step 444), an HTML document is used for the business server 102 by using the port (value of the standby port number 271) and the protocol (value of the used protocol 272) indicated by the variable G. To get. In the first embodiment of the present invention, an HTML document at / is acquired by sending a “GET / HTTP / 1.0” request, and the contents of the TITLE element therein are stored in a variable A. Proceed to 449 (step 445). In addition, an HTML document may be acquired from /index.php, /index.jsp, /index.do, /index.cgi, or the like. On the other hand, when it is not HTML (No in Step 444), the process proceeds to Step 446.

  Next, it is checked whether or not the acquisition method indicated by the variable G is JSR77 (step 446). If it is JSR77 (Yes in step 446), the port (value of the standby port number 271) and the protocol (value of the used protocol 272) indicated by the variable G are used for the business server 102. According to the method shown, a J2EE application name (Application Object: OBJECT_NAME) is acquired, stored in variable A, and the process proceeds to step 449 (step 447). On the other hand, if it is not JSR77 (No in step 446), the process proceeds to step 448.

  Next, in the case of an acquisition method other than HTML or JSR77, an application name is acquired using a protocol according to each acquisition method, and stored in variable A (step 448). Then, the contents of the variable A are stored in the application name 283 for the line of the identified application name list 280 corresponding to the variable P (step 449), and the process returns to step 441.

JSR77 is detailed at http://www.jcp.org/en/jsr/detail?id=77. When the protocol used is ioop (Internet Inter-ORB Protocol), it communicates with the MEEJB (Management EJB) component running on the business server using the ioop protocol, obtains J2EE (Java 2 Enterprise Edition) ApplicationObject, and The value of the OBJECT_NAME attribute is the application name.
When the protocol used is “snmp” (Simple Network Management Protocol), it communicates with the SNMP agent operating on the business server by the SNMP protocol, and iso.org.dod.internet.private.enterpirises.sun.jcp. Information indicated by MIB (Management Information Base) in j2ee.j2eeMIB.j2eeObjects.j2eeMoGroup.j2eeAppTable is acquired, and the value of J2EEAppMoName therein becomes the J2EE application name.
Also, when the protocol used is http (HyperText Transfer Protocol) or https (HyperText Transfer Protocol Security), XML using HTTP or https is used for the Common Information Model Object Manager (CIMOM) operating on the business server. -Communicate with the CIM protocol, obtain a J2EE_DeployedObject object, and the Name property value in it becomes the application name. The XML-CIM protocol is detailed in http://www.dmtf.org/standards/wbem/CIM-XML.

  According to the first exemplary embodiment of the present invention, the system administrator of the information processing system can know the names of applications running on the business server 102 by looking at the identified application name list 280. In particular, the processing in the interpreter determination unit 122 makes it possible to more accurately identify the application name for an application that uses the interpreter processing system. In addition, the processing in the shared directory determination unit 123 makes it possible to more correctly identify the application name for the application corresponding to the executable file placed directly under the shared directory. Then, the processing of the sub-directory determining unit 124 can identify an application name that installs an executable file in a plurality of different directories as one application name instead of identifying an independent application name for each directory. Become. Furthermore, the processing in the special application name specifying unit 126 makes it possible to specify a more accurate application name than specifying the application name from the directory name.

  Conventionally, each vendor specifies the name of the application by using know-how specific to the application provided by the vendor to the customer. However, there is a problem in that the name specified in such a manner is not versatile, and the maintenance work of the know-how becomes complicated when the version of the application is upgraded. Therefore, in the technology that uses the directory name of the executable file as the name of the application as in the present invention, only general-purpose information such as information that can be standardly acquired from the OS, know-how for each OS, information on a well-known interpreter, etc. By using it, the maintenance work is simplified.

<Second Embodiment>
Hereinafter, a second embodiment, which is an improvement of the first embodiment of the present invention, will be described.
In the second embodiment, the application name obtained in the first embodiment is handled as the display name of the business server passed as an argument to the processing of FIG. If a plurality of application names are specified, the display names of the business servers are obtained by combining them with a blank or the like.

  Similarly, when the business server passed as an argument to the processing of FIG. 12 is operating in a virtual environment, it can be treated as the virtual machine name (VM name) of the server instead of the display name of the server. good.

  According to the second exemplary embodiment of the present invention, the system administrator of the information processing system only looks at the display name of the business server, or just looks at the virtual machine name corresponding to the business server operating in the virtual environment. Now, you can see at a glance what kind of application is running on the business server.

<Third Embodiment>
The third embodiment, which is an improvement of the first embodiment of the present invention, will be described below.
In the third embodiment, the application name obtained in the first implementation is set as the host name of the business server passed as an argument to the processing of FIG. If a plurality of application names are specified, the server host name is obtained by simply combining them or by combining them with “-” or “.” Between them. Since only the specified characters can be used in the host name, it is recommended to delete the characters that cannot be used or replace them with "-". In addition, since there is a maximum value for the length of the host name, it is recommended to delete character strings that exceed the maximum value. The characters that can be used for the host name and the maximum length of the host name are detailed in RFC952 or RFC1123.

  Similarly, when the business server passed as an argument to the processing of FIG. 12 is operating in the virtual environment, the file name of the disk image corresponding to the virtual environment can be renamed to the obtained application name. good. As with host names, file names have characters that cannot be used and the maximum number of characters.

  According to the third embodiment of the present invention, the system administrator of the information processing system simply looks at the host name of the business server or the file name of the disk image corresponding to the business server operating in the virtual environment. You can see at a glance what kind of application is running on the business server.

<Others>
An example of the embodiment of the present invention has been described above, but the present invention is not limited to this and can be appropriately changed without departing from the spirit of the present invention.

For example, in this embodiment, basically,

(A): Processing in the standard process determination unit 121 (steps 403 and 404)
→ (B): Processing in interpreter determination unit 122 (step 420 to step 426)
→ (C): Processing in shared directory determination unit 123 (steps 427 to 430)
→ (D): Processing in subdirectory determination unit 124 (steps 431 to 437)

The name of the application is specified through the above procedure (processing in the application name specifying unit 125 (steps 408 to 413)). However, this procedure is changed to (A) → (C) → (B) → (D), (A) → (D) → (B) → (C),. It is also possible to specify the name. At this time, although there may be a difference in the name specifying performance, an optimal procedure can be selected according to the property of the application for which the name is to be specified.

  It is also possible to specify the name of the application using at least one of (A) to (D) (more preferably using at least one of (B) to (D)).

  In addition, specific configurations of hardware, software, flowcharts, and the like can be changed as appropriate without departing from the spirit of the present invention.

101 configuration management server 102 business server 104 management network 105 business network 106 process management unit 107 network management unit 108 command execution unit 122 interpreter determination unit 123 shared directory determination unit 124 subdirectory determination unit 210 collected process list 220 business server list 230 OS Standard Process List 240 Interpreter Name List 250 Shared Directory Absolute Path Name List 260 Execution Directory Relative Path Name List 270 Application Name Acquisition Method List 280 Specified Application Name List

Claims (6)

A communication interface capable of communicating with a business server that stores and manages processes generated by operating application programs that implement services provided to business clients;
A storage unit for storing process information in which process identification information for identifying the process is associated with standby port information indicating a port on which the process is waiting;
A control unit that identifies an application name of a process executed by the business server;
In the control unit of the configuration management server having
A first step of acquiring an HTML document from the business server via the communication interface based on designated port information;
A second step of acquiring a TITLE element indicating the title of the HTML document from the HTML document acquired by the first step;
A TITLE element acquired in the second step is specified as an application name of process identification information associated with standby port information of process information stored in the storage unit that matches the specified port information. 3 steps,
Name identification program to execute. In the storage unit,
Application name acquisition information in which standby port information indicating a port waiting for the application program and data acquisition method information according to a process generated from the application program are associated with each other is further stored.
The first step includes
An acquisition method information acquisition step of acquiring acquisition method information associated with the standby port information of the application name acquisition information stored in the storage unit that matches the specified port information;
An HTML document acquisition step of acquiring an HTML document from the business server via the communication interface based on the acquisition method information acquired by the acquisition method information acquisition step;
The name identification program according to claim 1, comprising: A communication interface capable of communicating with a business server that stores and manages processes generated by operating application programs that implement services provided to business clients;
A storage unit for storing process information in which process identification information for identifying the process is associated with standby port information indicating a port on which the process is waiting;
A control unit that identifies an application name of a process executed by the business server;
Have
The controller is
An HTML document is acquired from the business server via the communication interface based on specified port information, a TITLE element indicating the title of the HTML document is acquired from the acquired HTML document, and the acquired TITLE element is Identifying the application name of the process identification information associated with the standby port information of the process information stored in the storage unit that matches the specified port information;
A configuration management server. In the storage unit,
Application name acquisition information in which standby port information indicating a port waiting for the application program and data acquisition method information according to a process generated from the application program are associated with each other is further stored.
The controller is
Acquiring acquisition method information associated with standby port information of application name acquisition information stored in the storage unit that matches the specified port information, and based on the acquired acquisition method information, the business server Obtaining an HTML document from the communication interface via the communication interface;
The configuration management server according to claim 3. A business server that stores and manages processes generated by operating application programs that implement services provided to business clients;
A communication interface capable of communicating with the business server;
A storage unit for storing process information in which process identification information for identifying the process is associated with standby port information indicating a port on which the process is waiting;
A control unit that identifies an application name of a process executed by the business server;
A configuration management server having
With
The control unit of the configuration management server includes:
An HTML document is acquired from the business server via the communication interface based on specified port information, a TITLE element indicating the title of the HTML document is acquired from the acquired HTML document, and the acquired TITLE element is Identifying the application name of the process identification information associated with the standby port information of the process information stored in the storage unit that matches the specified port information;
An information processing system characterized by In the storage unit of the configuration management server,
Application name acquisition information in which standby port information indicating a port waiting for the application program and data acquisition method information according to a process generated from the application program are associated with each other is further stored.
The control unit of the management server
Acquiring acquisition method information associated with standby port information of application name acquisition information stored in the storage unit that matches the specified port information, and based on the acquired acquisition method information, the business server Obtaining an HTML document from the communication interface via the communication interface;
The information processing system according to claim 5.

Images