JP2015022688A - File search program, file search method and file search device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file search device for more efficiently performing file search required for operation and maintenance of a system.SOLUTION: In a computer readable file search program causing a computer to execute file search processing, the file search processing includes: a search condition acceptance process for accepting target component identification information of a target component and a search keyword; a file collection process for acquiring a work list of the target component identification information from a work list group having a work list of system construction corresponding to the component identification information, and collecting a work file associated with the work list; an extraction process for extracting partial element information described in the work file; and a search process for searching the work file including a description of the search keyword and the extracted partial element information with the work file of a plurality of components in a system as a target, and identifying information of the detected work file.

Description

  The present invention relates to a file search program, a file search method, and a file search device.

  In system operation / maintenance work, there are scenes in which materials created in each process during system development or construction are referred to. For example, when a system failure occurs in system operation / maintenance work or when a part of the system configuration is changed, data necessary for investigation or work is referred to. Specifically, when a part of the system configuration is changed, it is possible to determine the work that occurs along with the change and the effects caused by the change from the materials created at each process during system development and construction. Materials having information to be collected are collected (for example, Patent Document 1).

  By the way, at the time of system development or construction, the work process transitions from a work process with a high degree of abstraction that indicates requirement design or the like to a more detailed work process that indicates a process for generating a system configuration specification or the like. Then, materials (required specifications, various design documents, etc.) generated in units of operation systems and middleware generated in each process are classified for each process and stored in a folder. On the other hand, in system operation / maintenance work, a user collects data across each process in units of servers or functions that are the targets of investigation or work. Server unit and function unit materials are stored across multiple process folders.

  For this reason, the user opens each file in the folder of each process step by step to check whether or not the target information is included. Alternatively, the user performs a full text search for the upper directory of the folder in each process based on the keyword.

JP 2008-59028 A

  However, in system operation / maintenance work, there are scenes where new members with little knowledge who are not involved in system development or construction collect data. For this reason, when opening files in each process folder one by one and checking whether or not the target information is included, the files in almost all process folders are subject to confirmation, which is inefficient. . Also, when searching the full text, unnecessary minutes and other materials were detected, which was inefficient.

  In one aspect, an object of the present invention is to provide a file search program, a file search method, and a file search device that perform file search more efficiently.

  According to a first aspect of the present invention, there is provided a computer-readable file search program for causing a computer to execute a file search process related to a work target component in a system having at least a plurality of components indicating a server based on a search keyword. Is constituent element identification information indicating the name or type of the constituent element, and includes a search condition receiving step for receiving the target constituent element identification information of the target constituent element and the search keyword, and the constituent element identification information A file collection step for acquiring a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to and collecting a work file associated with the work list, and the work file Extract subelement information described in A search is performed for a work file including descriptions of the search keyword and the extracted partial element information, and a detected work file detected is specified for the output process and work files of the plurality of components in the system. And a search step.

  According to the first aspect, the file search is performed more efficiently.

It is a figure explaining the structure of the file search system in the example of this embodiment. It is a figure explaining the structure of the file search device in the present embodiment. It is a figure explaining the block diagram of the file search device in the present embodiment. It is a figure explaining the specific example of a system block diagram. It is a figure explaining the specific example of a system construction flow. It is a figure explaining the subject in a file search process. It is a figure which shows the specific example of the search screen in this Example, and a search result screen. It is a flowchart figure explaining the flow of a file search process. It is a figure explaining the specific example of a search screen. It is a figure explaining the example of a system construction flow and a product name list. It is a figure which illustrates the specific example of a search result screen.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the technical scope of the present invention is not limited to these embodiments, but extends to the matters described in the claims and equivalents thereof.

[File Search System Configuration]
FIG. 1 is a diagram for explaining the configuration of a file search system according to this embodiment. The file search system in FIG. 1 includes, for example, a file search device 10, a document management server 40, and a search terminal device 20, and is connected to be communicable with each other via a communication line 50 or the like. The document management server 40 is connected to the document management storage 41. The document management storage 41 stores files such as design documents to be searched. In addition, the search terminal device 20 displays a search screen that accepts input of search conditions. When receiving the search condition, the search terminal device 20 outputs the search condition to the file search device 10. Then, the file search apparatus 10 detects one or a plurality of files that match the search condition based on a file such as a design document stored in the document management storage 41.

[Configuration of file search device]
FIG. 2 is a diagram for explaining the configuration of the file search apparatus 10 in the present embodiment. 2 includes, for example, an input device 11, a display device 12, an external interface 13, a processor 14, a storage medium 15, and a memory 16. Each unit is connected to each other via a bus 17. The input device 11 indicates, for example, a keyboard and a mouse, and the display device 12 indicates a display screen such as a display. In addition, the processor 14 instructs the document management server 40 and the search terminal device 20 to be controlled via the external interface 13.

  The memory 16 stores a file search program PR in the present embodiment. The file search program PR cooperates with the processor 14 to realize a file search process. The storage medium 15 stores, for example, a system configuration diagram D1, a system construction flow D2, and a product name list, and is referred to by the file search program PR. The system configuration diagram D1, the system construction flow D2, and the product name list may be stored in an external storage medium accessible from the file search apparatus 10.

[Block diagram of file search device]
FIG. 3 is a diagram illustrating a block diagram of the file search apparatus 10 according to the present embodiment. 3 includes, for example, a search engine unit 31, a search screen generation unit 32, a system configuration diagram management unit 33, and a system construction flow management unit 34. Further, the document management server 40 has a design document holding unit 42. The system configuration diagram management unit 33 manages the system configuration diagram D1, and the system construction flow management unit 34 manages the system construction flow D2 corresponding to the system configuration diagram D1.

  The search screen generation unit 32 generates a search screen using the system configuration diagram D1 and causes the search terminal device 20 to display the search screen. The search screen of the search terminal device 20 accepts input of a search keyword and information on a component to be investigated or worked. The component is an element constituting the system, and indicates, for example, a server, a storage, a network device, or the like. The component information indicates, for example, identification names and types of servers, storages, network devices, and the like. For example, the name of the server is a name that makes the server identifiable, such as pc001. Further, for example, the server type is a type indicating the processing content, role, etc. of the server, such as a Web / AP server or a DB server.

  Further, the search engine unit 31 acquires a work item corresponding to information on the target component based on the system construction flow D2 read out via the system construction flow management unit 34. In addition, the search engine unit 31 collects a file such as a design document associated with each work item via the design document holding unit 42. Next, the search engine unit 31 extracts, for example, a product name as partial element information from the collected file, and detects a file including the extracted product name and the search keyword for the entire file. Then, the search engine unit 31 displays the detected file information on the search screen of the search terminal device 20.

[Specific example of system construction diagram]
FIG. 4 is a diagram for explaining a specific example of the system configuration diagram D1. The system configuration diagram D1 is a diagram having, for example, hardware and software, which are components of the system, and a network configuration. By referring to the system configuration diagram D1, the system operator can detect the configuration and scale of the system, and can also detect the names and types of the constituent elements to be investigated and worked.

  The system configuration diagram D1 of FIG. 4 is a configuration diagram of a system that provides a general cloud computing service, for example. The system configuration diagram D1 in FIG. 4 includes, for example, information on the names and types of hardware devices constituting the system and the network configuration between the devices. Specifically, the system shown in the system configuration diagram D1 of FIG. 4 includes servers s1 to s14, network devices w1 to w6, and storages r1 to r3. The names of the servers s1 to s14 are, for example, web001, web002, web011, web012, web021, web022, db001, db002, db011, db012, db021, db022, rep021, and rep022. The server type is, for example, a Web / AP server, a DB server, or a repository server. The names of the storages r1 to r3 are, for example, storage001 to storage003.

  The system configuration diagram D1 as shown in FIG. 4 is created by a system developer, for example. The system configuration diagram D1 may be a system configuration diagram created by the system developer, or the system configuration diagram D1 created by the system developer may be revised in accordance with the file search apparatus 10. , May be created.

[Specific example of system construction flow]
FIG. 5 is a diagram illustrating a specific example of the system construction flow. The system construction flow D2 has, for example, a list of work items performed on the components at the time of system construction corresponding to the respective components shown in the system configuration diagram D1 of FIG. That is, the system construction flow D2 has a work item list group (work list group) corresponding to the constituent elements. In this example, the system construction flow D2 has a list of work items for each type of component. For example, each component type includes a Web / AP server, a DB server, and an FCSW / storage.

  Specifically, the work item list AL1 in the system construction flow D2 in FIG. 5 is a work item performed at the time of construction of the Web / AP server, for example. In this example, the work items performed at the time of constructing the Web / AP server are “hardware setup”, “OS setup”, “hardware monitoring software setup”, “middleware setup”, “system monitoring middleware setup”, “performance”. “Monitoring middleware setup” and “Performance monitoring middleware tuning”. The system construction flow D2 may include work items scheduled to be executed in addition to work items performed at the time of construction. Similarly, the system construction flow D2 of FIG. 5 includes a DB server work item list AL2 and an FCSW / storage work item list AL3.

  Each work item is associated with one or more files. The file is, for example, design document data. For example, a hardware setup procedure manual is associated with the work item “hardware setup” in the work item list AL1 of the Web / AP server. Similarly, the OS-01 installation procedure manual is associated with the work item “OS setup” of the Web / AP server. Note that one or a plurality of files are also associated with work items scheduled to be executed. One file may be associated with a plurality of work items.

  Further, in the example of FIG. 5, the system construction flow D2 has a list of work items corresponding to the types of components. However, the present invention is not limited to this example, and the system construction flow D2 may have, for example, a list of work items corresponding to the names of the components. In this case, the system construction flow D2 has a list of work items performed at the time of construction corresponding to the server name web001 (FIG. 4), for example.

  As in the system configuration diagram D1, the system construction flow created by the system developer may be used for the system construction flow D2, or the system construction flow created by the system developer may be used as a file search device. It may be created by revising to match 10.

[File search example]
FIG. 6 is a diagram for explaining a problem in the file search process. FIG. 6 exemplifies a case of searching for a file that is related to the investigation or work of the type Web / AP server and includes the description of the search keyword “cluster”. The system construction flow D2 in FIG. 6 shows the same contents as the system construction flow D2 in FIG. However, in FIG. 6, a work item associated with a file including the description of the search keyword “cluster” is given a cluster mark indicated by white letters. That is, for example, the file associated with the work item “OS setup” of the Web / AP server has a description of “cluster”.

[File containing search keyword description]
First, a file including a description of the search keyword “cluster” will be described. According to FIG. 6, among the files associated with the work items of the Web / AP server, the file including the description of “cluster” is a file associated with the work items “OS setup” and “middleware setup”. Of the files associated with the work items of the DB server, the file including the description of “cluster” is assigned to the work items “OS setup”, “middleware setup”, “storage driver setup”, “storage software setup”, and “database setup”. The associated file. Of the files associated with the FCSW / storage work item, the file including the description of “cluster” is the file associated with the work item “Lun mapping setup”.

  According to the example of FIG. 6, the file including the description of “cluster” includes the work items “OS setup” and “middleware setup” of the Web / AP server, and the work items “OS setup”, “middleware setup”, and “storage driver setup” of the DB server. "Storage software setup", "Database setup", and FCSW / storage work item "Lun mapping setup".

  Note that Lun in the work item “Lun mapping setup” is a number for identifying a plurality of HDDs (units) connected to a SCSI (Small Computer System Interface), and is a logical unit number (Logical Unit Number). It is. For example, by performing Lun mapping, a plurality of HDDs can be recognized as one storage device or a plurality of storage devices. Lun mapping is a task related to the cluster.

[Product name included in the file]
Next, the product name included in the file associated with the work item will be described. In FIG. 6, symbols a to f corresponding to the product names described in the files associated with each work item are indicated by white characters for the work item performed when the Web / AP server is constructed. . That is, for example, a file associated with the work items “hardware setup” and “hardware monitoring software setup” of the Web / AP server includes descriptions of product name a and product name b.

  Similarly, in the example of FIG. 6, the file associated with the work item “OS setup” of the Web / AP server is the product name c, and the file associated with the work item “middleware setup” is the product name c. Contains a description of the name d. In addition, a file associated with the work item “system monitoring middleware setup” of the Web / AP server has a product name c and a product name e, and a file associated with the work item “performance monitoring middleware setup” has a product name c and a product. Contains a description of the name f. The file associated with the work item “performance monitoring middleware tuning” of the Web / AP server includes descriptions of product name a, product name b, and product name f.

  On the other hand, the descriptions of the product name a and the product name b are also included in the files associated with the work items “hardware setup” and “hardware monitoring software setup” of the DB server. The description of the product name e is a file associated with the DB server work item “system monitoring middleware setup”, and the description of the product name f is a file associated with the DB server work item “performance monitoring middleware setup”. Is also included.

[File detection omission]
As described above, the example of FIG. 6 illustrates a case of searching for a file that is related to the investigation or work of the type Web / AP server and includes the description of the search keyword “cluster”. When the server that is the target of the investigation or work is a Web / AP server, generally, a file including a description of the search keyword “cluster” is searched for files related to the Web / AP server. For example, a file including the description of the search keyword “cluster” is searched for the file associated with the work item of the Web / AP server in FIG. Therefore, according to the example of FIG. 6, as a result of the search, a file associated with the work items “OS setup” and “middleware setup” of the Web / AP server is detected.

  However, when the server that is the subject of the survey or work is a Web / AP server, not only the file associated with the work item of the Web / AP server but also the file containing the product description related to the work item of the Web / AP server It is desirable to be a search target. As a result, a more comprehensive search keyword search process is performed.

  That is, according to the example of FIG. 6, in addition to the files related to the work items of the Web / AP server, the work items “hardware setup” “hardware monitoring software setup” “system monitoring middleware setup” “performance monitoring middleware” of the DB server The files associated with the “setup” and FCSW / storage work item “Lun mapping setup” are also preferably search targets. Therefore, according to the example of FIG. 6, it is desirable to detect a file associated with the work item “Lun mapping setup” of the FCSW / storage in addition to the work items “OS setup” and “middleware setup” of the Web / AP server. .

  As described above, when a file including the description of the search keyword “cluster” is searched for only the file associated with the Web / AP server, the file associated with the FCSW / storage work item “Lun mapping setup” is detected. Leaks from the results. That is, a file detection failure occurs.

[Detect a large number of files]
Therefore, in order to avoid omission of file detection, when a file including the search keyword “cluster” is searched for all files, a large number of files are detected. According to the example of FIG. 6, in addition to the files associated with the work items “OS setup” and “middleware setup” of the Web / AP server, the work items “OS setup” “middleware setup” “storage software setup” “database” of the DB server. A file associated with the “setup” and a file associated with the FCSW / storage work item “Lun mapping setup” are detected.

  In this case, a file associated with the work items “OS setup”, “middleware setup”, “storage software setup”, and “database setup” of the DB server, which does not need to be detected but does not need to be detected, is also detected. That is, a large number of files including unnecessary files are detected.

  In this way, when keyword search is performed only on files associated with the server that is the target of investigation or work, file detection omission occurs, and when keyword search is performed on all files, files that do not need to be detected Will also be detected.

  Therefore, the file search process in the present embodiment is component element identification information indicating the name or type of the component element, and accepts the search condition for receiving the target component element identification information of the target component element and the search keyword. The file search process includes a work list of the target component identification information from a work list group (system construction flow) having a system construction work list corresponding to the component identification information. A file collection step for collecting work files associated with the list; The file search processing includes an extraction process for extracting partial element information (product name in the example of FIG. 6) described in the work file, a search keyword for the work file of a plurality of components in the system, A search process for searching for a work file including a description of the extracted partial element information and specifying information of the detected work file detected.

  As a result, in addition to the file associated with the target server of the survey or work, the search keyword description can be specified for the file that contains the description of the product name (partial element information) related to the work item of the target server. A search for the containing file is performed. As a result, omission of detection of a file is avoided and a large number of files including unnecessary files are avoided. That is, in the example of FIG. 6, only the file associated with the work item “OS setup” and “middleware setup” of the Web / AP server and the file associated with the work item “Lun mapping setup” of the FCSW / storage can be detected. Become.

  Here, a specific example of the search screen and the search result screen in the present embodiment will be described.

[Search screen, search result screen]
FIG. 7 is a diagram illustrating a specific example of the search screen 21-1 and the search result screen RS-1 in the present embodiment. The search screen 21-1 in FIG. 7 includes search keyword input items and a system configuration diagram D1-1. For example, the user designates “environment variable” as the input item of the search keyword, selects the target component db001 (server name) in the system configuration diagram D1-1, and presses the search button. As a result, a file that is related to the investigation or work of the server db001 and includes the description of the search keyword “environment variable” is searched. In the present embodiment, the user indicates, for example, an operator.

  In addition, the search result screen RS-1 in FIG. 7 shows a list of file information detected by the file search process in the present embodiment. In the search result screen RS-1, for example, a file name and a link to the storage location of the file are displayed as file information. In this example, the file information list is sorted and displayed in descending order of the degree of matching with the search condition. Details will be described later.

  Next, the flow of the file search process in this embodiment will be described.

[File search process flow]
FIG. 8 is a flowchart for explaining the flow of the file search process. The user inputs a search keyword and information indicating the target component on the search screen displayed on the search terminal device 20, and presses the search button (S11). In this example, for example, a server name is input as information indicating the target component. Subsequently, the file search apparatus 10 receives input of a search keyword and a server name from the search terminal apparatus 20, and acquires a work item corresponding to the server name based on the system construction flow D2 (S12). Subsequently, the file search apparatus 10 collects storage locations of files associated with the acquired work items (S13).

  Then, the file search apparatus 10 extracts the partial element information described in the file for the collected file (S14). The partial element information indicates, for example, product identification information or product type. The product may be either hardware or software. Further, since the product name may be information that can identify the product, it may be an abbreviated product name or a part of the product name. In this embodiment, the case where the partial element information indicates a product name is illustrated. The case where the partial element information indicates the type of product will be described in another embodiment.

  For example, the file search device 10 extracts all the product names included in the used product name list item in the collected file or files. Alternatively, the file search device 10 refers to the product name list and extracts the product names described in the collected one or more files from the product names included in the product name list. As a result, a list of product names whose descriptions are included in the file associated with the work item of the target component is extracted.

  Subsequently, the file search device 10 detects a file including descriptions of the extracted product name and the search keyword input on the search screen for all files (S15). That is, in addition to the file associated with the work item with the server name input on the search screen, the file associated with the work item with the other server name is also a search target. When there are a plurality of extracted product names, the file search apparatus 10 detects a file including a description of any product name and search keyword for all files. Then, the file search device 10 displays the name and storage location of the detected file on the search result screen of the search terminal (S16).

  Next, a specific example of the file search process in this embodiment will be described.

[Specific example of search screen]
FIG. 9 is a diagram for explaining a specific example of the search screen 21. The search screen 21 is displayed on the screen of the search terminal device 20, for example. However, the search screen 21 may be displayed on the display device 12 of the file search device 10. In this example, two search screen forms 21-1 and 21-2 are illustrated.

  The search screen 21-1 in FIG. 9 includes search keyword input items, a system configuration diagram D <b> 1-2, and target component input items to be investigated and worked. The system configuration diagram D1-2 of the search screen 21-1 illustrates a plurality of servers, and each server displays a type in addition to a name. Therefore, the user can select and specify the name or type of the target server based on the system configuration diagram D1-2. In the example of FIG. 9, for example, “cluster” is specified as the search keyword input item, and the Web / AP server is specified as the type of the target server. As described above, the type of the target server may be input to the information of the target component instead of the name of the target server. As a result, it is possible to search for a file related to the work of the target server of the specific type and including the description of the search keyword “cluster”.

  Further, the search screen 21-2 in FIG. 9 includes search keyword input items and target server name and type selection items. In this example, the system configuration diagram D1 is not shown. In this example, for example, “cluster” is specified as an input item of a search keyword, and a Web / AP server is specified from a list of names or types of a plurality of target servers. Thus, the system configuration diagram D1 is not necessarily shown on the search screen 21-2. In addition, the name or type of the target server is listed on the search screen 21-2 and can be selected by the user, so that the user can easily perform the operation even when the system configuration diagram D1-2 is not shown. The name or type of the target server can be selected.

  Next, specific examples of the system construction flow D2-1 and the product name list will be described.

[Specific example of system construction flow]
FIG. 10 is a diagram illustrating specific examples of the system construction flow D2-1 and the product name list PL. The system construction flow D2-1 in FIG. 10 has types of components constituting the system, work items of Web / AP server, DB server, and FCSW / storage, and file names associated with the work items.

  Specifically, according to the system construction flow D2-1 in FIG. 10, the file associated with the work item OS setup performed for the Web / AP server is the “OS-01 installation procedure”. Similarly, the file associated with the work item “hardware monitoring software setup” performed on the Web / AP server is the “log collection application setting procedure”. The file associated with the work item “middleware setup” performed on the Web / AP server is “integrated operation application X installation procedure”.

  In the specific example of the present embodiment, as shown in the search screens 21-1 and 21-2 in FIG. 9, the search keyword “cluster” and the Web / AP server are specified as the server type. Therefore, the file search apparatus 10 collects file storage locations associated with each work item of the Web / AP server based on the system construction flow D2-1 of FIG. 10 (S12, S13). In the example of FIG. 10, for example, “http: //.../.../OS-01 installation procedure” “http: //.../.../log collection application setting” "Procedure manual", "http: //...////integrated operation application X installation procedure manual", and the like are collected. Subsequently, the file search device 10 is described in one or more collected files among the product names included in the product name list PL with reference to, for example, the product name list PL illustrated in FIG. A product name is extracted (S14).

  Specifically, in this example, the file “OS-01 installation procedure” associated with the work item “OS setup” of the Web / AP server and the file “integrated operation application” associated with the work item “middleware setup”. The “X installation procedure manual” includes a description of the product name “operation system 01”. Further, the file “integrated operation application X installation procedure” associated with the work item “middleware setup” of the Web / AP server includes a description of the product name “integrated operation application X”.

  Thus, based on the collected files “OS-01 installation procedure manual”, “log collection application setting procedure manual”, “integrated operation application X installation procedure manual”, etc., the product name “operation system 01” “integrated operation application X” Is extracted. The product names “operation system 01” and “integrated operation application X” are part of the extracted product names, and other product names are also extracted in practice.

  Subsequently, the file search device 10 includes a file including descriptions of the extracted product names “operation system 01”, “integrated operation application X”, etc. from all the files, and the search keyword “cluster” input on the search screen. Is detected (S15).

  According to the example of FIG. 10, for example, a file including the description of the extracted product name “operation system 01” and the search keyword “cluster” is a file associated with the work item “OS setup” of the Web / AP server. “OS-01 installation procedure” and a file “integrated operation application X installation procedure” associated with the work item “middleware setup”. The file including the description of the extracted product name “integrated operation application X” and the search keyword “cluster” is a file “integrated operation application X installation procedure” associated with the work item “middleware setup” of the Web / AP server. And the file “Lun mapping procedure” associated with the FCSW / storage work item “Lun mapping setup”.

  Therefore, in the specific example of the present embodiment, for example, the files “OS-01 installation procedure manual”, “integrated operation application X installation procedure manual”, and “Lun mapping procedure manual” are detected. When the server name is input on the search screen of FIG. 9, the storage location of the file associated with the work item of the type corresponding to the name of the target server based on the system construction flow D2-1 of FIG. Are collected (S12, S13). Or system construction flow D2-1 may have a work item corresponding to a server name.

[Specific example of search result screen RS-2]
FIG. 11 is a diagram illustrating a specific example of the search result screen RS-2. The search result screen RS-2 is displayed on the screen of the search terminal device 20, for example. However, the search result screen RS-2 may be displayed on the display device 12 of the file search device 10.

  In the search result screen RS-2 of FIG. 11, the detected files “OS-01 installation procedure manual”, “integrated operation application X installation procedure manual”, and “Lun mapping procedure manual” are displayed. For example, the detected files are displayed in ascending order from the detection file having many description parts of the search keyword and the extracted product name. Thereby, the user can preferentially refer to the detection file having the highest degree of description portion of the search keyword and the extracted product name.

  In addition, in the search result screen RS-2 of FIG. 11, in addition to the detected file name and storage location information, the extracted file name (hereinafter, “extracted product name”) has a description in the file. Has the product name included. Thereby, in addition to the information of a detection file, the user can detect the extracted product name whose description is included in the detection file.

  In general, the detection file with the most description portions of the search keyword and the extracted product name is a highly useful file that is requested by the user. However, the second and third most frequently detected files are not necessarily the second and third most useful files. However, it can be considered that the detection files having the description of the same product name have high relevance. Therefore, the file search apparatus 10 according to the present embodiment displays the product name included in the detection file among the extracted product names in addition to the name of the detection file and the storage destination information. Accordingly, the user can identify a detection file having a high relevance to the detection file having the largest number of description portions of the search keyword and the extracted product name among the detection files based on the product name.

  Further, when the search keyword is a general term, the detection file with the most description portions of the search keyword and the extracted product name is not necessarily the most useful file. For example, “threshold” is a term used in various product fields. When the search keyword “threshold” is specified, the detection file having the most description portions of the search keyword and the extracted product name does not necessarily include a description related to the product threshold required by the user. Therefore, the user can identify a desired detection file by referring to the product name whose description is included in the detection file.

  In this embodiment, the case where one word is input as a search keyword has been illustrated. However, a plurality of words may be input as the search keyword. In this case, for example, for all files, the file search apparatus 10 detects a file including a description of the extracted product name and a description of all of the plurality of search keywords as a detection file (S15 in FIG. 8). That is, an AND condition of a plurality of search keywords is applied. Alternatively, for example, the file search apparatus 10 detects a file including a description of the extracted product name and one of a plurality of search keywords as a detection file for all files (S15 in FIG. 8). That is, the OR condition of a plurality of search keywords is applied. The AND condition and the OR condition may be arbitrarily selected by the user. Thereby, a more flexible file search becomes possible.

[Modification]
In the modification, a case will be described in which the partial element information indicates a product type. The file search apparatus 10 may extract the product type described in the file for the collected file (S14 in FIG. 8). The product type indicates, for example, a category or classification used for the product. Specifically, the product type is, for example, a Web / AP server, a DB server, an HTTP server, a storage, or the like. However, it is not limited to this example. In the modification, for example, the file search apparatus 10 refers to the product type list and extracts the product types described in the collected one or more files from the product types included in the product type list (FIG. 8). S14). Thereby, according to the modification, a list of product types whose description is included in the file associated with the work item of the target component is extracted.

  Here, a description will be given based on a specific example. In a specific example, for example, pc001 (server name) and the search keyword “cluster” are input as information indicating the target component on the search screen (S11). Subsequently, the file search apparatus 10 acquires a work item corresponding to the server pc001 based on the system construction flow D2 (S12), and collects storage locations of files associated with the work item (S13). Then, the file search apparatus 10 extracts the product type described in the file for the collected file (S14).

  In a specific example, for example, the product type list includes a Web / AP server, an HTTP server, a DB server, a storage, and the like. For example, a Web / AP server and an HTTP server are extracted as product types described in a file associated with the work item of the server pc001. Therefore, the file search apparatus 10 detects files including descriptions of the Web / AP server and the search keyword “cluster” and the HTTP server and the search keyword “cluster” for all files (S15). Then, the file search device 10 displays the name and storage location of the detected file on the search result screen of the search terminal (S16).

  As a result, the search for files including the description of the search keyword is performed on all files including descriptions of the Web / AP server and the HTTP server. That is, in addition to the file associated with the work item of the server pc001, the file associated with the work item of the component (for example, server) sharing the usage category or classification of the product used with the server pc001. It becomes the search target of the search keyword. Therefore, in addition to the file related to the work item of the target component, the file related to the work item of the component having the same use and function as the target component is also a search target. Thereby, highly useful files can be comprehensively detected.

  In addition, according to the modification, there may be a case where more comprehensive detection is possible compared to the case where the product name is used as the partial element information. For example, although the products are different, the case where the first and second products having the same application and category are used in different servers is illustrated. Specifically, for example, the server pc001 uses the first product, and the server pc002 uses the second product. If the partial element information is a product name, the first product name is extracted in step S14 of FIG. Then, in step S15 of FIG. 8, a file including the description of the first product name and the search keyword is detected for all files. That is, a file related to a work item of a server that uses the first product is a search target.

  On the other hand, in the modified example, the product type indicating the usage of the first product and the second product is extracted in step S14 of FIG. In step S15 in FIG. 8, a file including descriptions of product types and search keywords is detected for all files. In other words, in the modified example, the files related to the work items of the server that uses the first product and the server that uses the second product are searched. As a result, more comprehensive detection is possible when the product name is used as the partial element information.

  As described above, the file search process according to the present embodiment receives the component identification information indicating the name or type of the component, and the target component identification information of the target component and the search keyword. A search condition receiving step; Also, the file search process acquires a work list of the target component identification information from a work list group having a work list for system construction corresponding to the component identification information, and collects work files associated with the work list. It has a file collection process. The file search processing includes an extraction process for extracting the partial element information described in the work file, and a description of the search keyword and the extracted partial element information for the work files of a plurality of components in the system. And a search process for specifying information of the detected detected work file.

  As described above, according to the file search processing in the present embodiment, in addition to the file associated with the work item of the target component of the investigation or work, the partial element information related to the work item of the target component is displayed. A file including a search keyword description is searched for a file including the description. As a result, detection of a large number of files including unnecessary files is avoided, and omission of detection of files is avoided. Therefore, even a new member with little know-how can comprehensively detect and refer to highly useful files. In addition, since the detection of unnecessary files is suppressed, the detection process of the detected files by the user is made more efficient. As described above, the file search process according to the present embodiment makes it possible to search for a desired file efficiently and comprehensively. Further, according to the file search process in the present embodiment, a system configuration diagram and a work list group (system construction flow) may be prepared in advance. For this reason, in the file search process, man-hours required for shifting from the system construction to the operation phase can be reduced.

  Further, in the file search process in the present embodiment, in the search condition receiving step, a system configuration diagram illustrating the component identification information in the system is further displayed, and target component identification specified based on the system configuration diagram Accept information. For this reason, the user can specify the component which becomes the object of work or investigation based on the system configuration diagram on the search display screen. That is, the user can omit the operation of searching the system configuration diagram itself from the storage medium and detecting the information of the target component. As a result, the file search process can be performed quickly, and an intuitively understandable interface for the user can be provided.

  Further, in the file search process in the present embodiment, in the search process, information of the detected detection work file is further displayed, and from the detection work file having many description locations of the search keyword and the extracted partial element information. Display in ascending order. Thereby, the user can identify a highly useful detection work file.

  Further, in the file search process in the present embodiment, in the search step, the detected work file information is further displayed, and in addition to the detected work file information, the detected work file includes a description. Display subelement information. Thereby, in addition to the information of the detection work file, the user can detect the partial element information whose description is included in the detection work file. Therefore, the user can identify a desired file from the plurality of detection work files based on the partial element information. Further, the user can identify the degree of relevance between the plurality of detection work files based on the partial element information. As a result, the user can identify a detection work file having a high relevance to the detection work file having the largest number of description parts of the search keyword and the partial element information.

  In the file search process according to the present embodiment, the partial element information indicates product identification information or type. As a result, not only the file related to the work list of the target component, but also the file related to the work list of the component sharing the product identification information and type, which is the partial element information, becomes the search target. For this reason, the user can detect a highly useful file more comprehensively.

  In the file search process according to the present embodiment, the information on the detected work file includes the name of the detected work file and the storage location of the detected work file. Thereby, the user can refer to the detection work file more easily.

  In the file search process according to the present embodiment, the search condition receiving step accepts a plurality of search keywords, and the search step includes a work file including descriptions of all the plurality of search keywords and the extracted partial element information. Alternatively, a work file including a description of one of a plurality of search keywords and the extracted partial element information is searched. As a result, according to the file search processing in the present embodiment, it is possible to search for a desired file at high speed and with high completeness even when a plurality of search keywords are input. In addition, more flexible file search is possible.

  The above embodiment is summarized as follows.

(Appendix 1)
In a computer-readable file search program for causing a computer to execute a file search process on a component to be worked on in a system having at least a plurality of components indicating a server based on a search keyword,
The file search process
A search condition receiving step for receiving the component identification information indicating the name or type of the component, the target component identification information of the target component, and the search keyword,
A file collection step of acquiring a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collecting work files associated with the work list When,
An extraction step of extracting partial element information described in the work file;
A search step of searching for a work file including descriptions of the search keyword and the extracted partial element information for a plurality of work files of the component in the system, and specifying the detected work file; ,
A file search program.

(Appendix 2)
In Appendix 1,
In the search condition receiving step, a file search program for further displaying a system configuration diagram illustrating the component identification information in the system and receiving the target component identification information specified based on the system configuration diagram.

(Appendix 3)
In Appendix 1 or 2,
In the search step, the file search program further displays information of the detected detection work file, and displays the information in the ascending order from the detection work file having many description locations of the search keyword and the extracted partial element information.

(Appendix 4)
In any one of supplementary notes 1 to 3,
In the search step, a file search for further displaying information of the detected detection work file and displaying the extracted partial element information including a description in the detection work file in addition to the information of the detection work file. program.

(Appendix 5)
In any one of supplementary notes 1 to 4,
The partial element information is a file search program indicating product identification information or type.

(Appendix 6)
In Appendix 3 or 4,
The detection work file information includes a file search program including a name of the detection work file and a storage location of the detection work file.

(Appendix 7)
In any one of supplementary notes 1 to 6,
In the search condition receiving step, a plurality of the search keywords are received,
In the search step, a work file including descriptions of all the plurality of search keywords and the extracted partial element information, or a work including descriptions of any of the plurality of search keywords and the extracted partial element information. A file search program that searches for files.

(Appendix 8)
In any one of appendices 1 to 7,
The component is a file search program including one or both of a storage and a network device in addition to the server.

(Appendix 9)
In Appendix 5,
The product is a file search program indicating either or both of hardware and software.

(Appendix 10)
Based on a search keyword, a file search method for a component to be worked on in a system having at least a plurality of components indicating a server,
A search condition accepting step in which the processor is constituent element identification information indicating the name or type of the constituent element, and receives the target constituent element identification information of the target constituent element and the search keyword;
The processor acquires a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collects work files associated with the work list File collection process,
An extraction step in which the processor extracts partial element information described in the work file;
The processor searches a work file including descriptions of the search keyword and the extracted partial element information for work files of a plurality of the component elements in the system, and specifies a detected work file detected A search process to
A file search method comprising:

(Appendix 11)
Based on a search keyword, a file search device for a component to be worked on in a system having at least a plurality of components indicating a server,
Search condition receiving means for receiving the component identification information indicating the name or type of the component, the target component identification information of the target component, and the search keyword;
File collection means for acquiring a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collecting work files associated with the work list When,
Extraction means for extracting partial element information described in the work file;
Search means for searching a work file including descriptions of the search keyword and the extracted partial element information for a plurality of work files of the component in the system, and specifying the detected work file detected; ,
A file search device having:

10: file search device, 20: search terminal device, 40: document management server, 41: document management storage, 11: input device, 12: display device, 13: external interface, 14: processor, 15: storage medium, 16: memory

Claims (11)

In a computer-readable file search program for causing a computer to execute a file search process on a component to be worked on in a system having at least a plurality of components indicating a server based on a search keyword,
The file search process
A search condition receiving step for receiving the component identification information indicating the name or type of the component, the target component identification information of the target component, and the search keyword,
A file collection step of acquiring a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collecting work files associated with the work list When,
An extraction step of extracting partial element information described in the work file;
A search step of searching for a work file including descriptions of the search keyword and the extracted partial element information for a plurality of work files of the component in the system, and specifying the detected work file; ,
A file search program. In claim 1,
In the search condition receiving step, a file search program for further displaying a system configuration diagram illustrating the component identification information in the system and receiving the target component identification information specified based on the system configuration diagram. In claim 1 or 2,
In the search step, the file search program further displays information of the detected detection work file, and displays the information in the ascending order from the detection work file having many description locations of the search keyword and the extracted partial element information. In any one of Claims 1 thru | or 3,
In the search step, a file search for further displaying information of the detected detection work file and displaying the extracted partial element information including a description in the detection work file in addition to the information of the detection work file. program. In any one of Claims 1 thru | or 4,
The partial element information is a file search program indicating product identification information or type. In claim 3 or 4,
The detection work file information includes a file search program including a name of the detection work file and a storage location of the detection work file. In any one of Claims 1 thru | or 6.
In the search condition receiving step, a plurality of the search keywords are received,
In the search step, a work file including descriptions of all the plurality of search keywords and the extracted partial element information, or a work including descriptions of any of the plurality of search keywords and the extracted partial element information. A file search program that searches for files. In any one of Claims 1 thru | or 7,
The component is a file search program including one or both of a storage and a network device in addition to the server. In claim 5,
The product is a file search program indicating either or both of hardware and software. Based on a search keyword, a file search method for a component to be worked on in a system having at least a plurality of components indicating a server,
A search condition accepting step in which the processor is constituent element identification information indicating the name or type of the constituent element, and receives the target constituent element identification information of the target constituent element and the search keyword;
The processor acquires a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collects work files associated with the work list File collection process,
An extraction step in which the processor extracts partial element information described in the work file;
The processor searches a work file including descriptions of the search keyword and the extracted partial element information for work files of a plurality of the component elements in the system, and specifies a detected work file detected A search process to
A file search method comprising: Based on a search keyword, a file search device for a component to be worked on in a system having at least a plurality of components indicating a server,
Search condition receiving means for receiving the component identification information indicating the name or type of the component, the target component identification information of the target component, and the search keyword;
File collection means for acquiring a work list of the target component element identification information from a work list group having a work list for constructing the system corresponding to the component element identification information, and collecting work files associated with the work list When,
Extraction means for extracting partial element information described in the work file;
Search means for searching a work file including descriptions of the search keyword and the extracted partial element information for a plurality of work files of the component in the system, and specifying the detected work file detected; ,
A file search device having:

Images