JP2012181794A - File retrieval device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To detect a similar policy under conditions where there are multiple policies in which predetermined information related to a retrieval is defined and reuse the policy, and to reduce a ratio of leaving unnecessary policies by detecting and deleting policies satisfying predetermined deletion conditions.SOLUTION: Policies in which the predetermined retrieval information is defined are registered in policy management data 108. When creating the policy management data 108 according to a request from a client 11 if there are policies similar to a newly created policy in the policies that are registered in the policy management data 108, a policy management section 104 in response to the request from the client 11, compiles retrieval information of the similar policies, or newly creates a policy and registers it in the policy management data 108. Further, the policy management section 104 deletes a policy that satisfies the predetermined deletion conditions and of which deletion is requested from the client 11, from the policy management data 108.

Description

  The present invention relates to a file search apparatus for searching for a file stored in a file system.

  In recent years, digitization of information has been progressing rapidly. In the past, data stored in files and DBs (Data Base) is stored in files and DBs (data bases) that are used by computer systems such as corporations, government offices, etc. to execute mission-critical operations such as bank accounts and municipal resident cards. It was the center of

On the other hand, various documents created in daily operations in organizations such as companies are now stored as document files, table files, databases, etc. on each employee's client PC (Personal Computer), and attached as e-mail attachments. It has been sent to another client PC. In addition, the introduction of the file server makes it possible to centrally manage these data, and the document files stored in the file server are referred to and updated by various employees.
In this way, a large number of document files, table files, e-mails, databases, records stored in the databases, programs, etc. (hereinafter collectively referred to as “files”) are stored in the file server.

  On the other hand, in an organization, information may be accumulated in a DB and used for various purposes. For example, in order to manage the file server, if file search is periodically performed and the result is accumulated in the DB, statistical information such as the size of each file type and the increasing tendency of the number of cases can be easily calculated. More specifically, a search condition, a search schedule, and a search result are defined as a policy according to a search purpose and the policy DB is obtained by accumulating policy information.

  Here, a technology for defining a policy for restricting use of a document as a policy, storing characteristic information for the policy in a policy DB, and detecting an appropriate policy candidate as a policy to be applied to the document using the policy DB Is known (see, for example, Patent Document 1).

JP 2010-134586 A

  However, although the technique disclosed in Patent Document 1 has a difference in information defined as policies, it only shows candidate policies, and edits and reuses candidate policies or uses frequency. No consideration is given to organizing the policy DB such as deleting if there is a low policy.

  An object of the present invention is to detect and reuse similar policies and detect and delete policies satisfying a predetermined deletion condition under conditions where there are many policies in which predetermined information related to search is defined. Accordingly, it is an object of the present invention to provide a file search apparatus capable of reducing the ratio of remaining unnecessary policies.

In order to achieve the above object, the file search apparatus of the present invention provides:
Policy management data storage means for storing policy management data in which a plurality of policies defined with predetermined search information are registered;
Policy creation request accepting means for accepting a policy creation request including predetermined search setting conditions from a client;
When a policy creation request is accepted by the policy creation request accepting means, a search condition for each policy registered in the policy management data stored by the policy management data storage means, and a search setting condition included in the policy creation request; Based on the policy management data, it is determined whether or not there is a similar policy similar to the newly created policy, and if it is determined that there is no similar policy, A new policy is created based on the search setting condition included in the policy creation request and is registered in the policy management data. When it is determined that a similar policy exists, the policy of the similar policy is determined according to the request from the client. Edit the search information, or use the search setting conditions included in the policy creation request. And policy creation means to be registered in the policy management data to create a new policy Zui,
Policy organization request accepting means for accepting a policy organization request from the client;
When a policy rearrangement request is accepted by the policy rearrangement request acceptance unit, a deletion candidate policy that satisfies a predetermined deletion condition is detected from the policies registered in the policy management data stored by the policy management data storage unit. A deletion candidate policy list presentation means for presenting a list of deletion candidate policies to the client;
Policy deletion request accepting means for accepting a policy deletion request for deleting a policy included in the list of deletion candidate policies from a client;
When a policy deletion request is received by the policy deletion request receiving unit, a policy deletion unit that deletes the policy requested to be deleted by the policy deletion request from the policy management data stored by the policy management data storage unit;
Is provided.

Preferably, the file search device of the present invention is
Schedule receiving means for receiving schedule information indicating a schedule for executing a search based on each policy registered in the policy management data stored in the policy management data storage means;
Schedule management means for managing the schedule information received by the schedule reception means, and performing a search based on each policy according to the schedule indicated by the schedule information;
A reset request accepting unit that accepts a reset request from a client to reset the schedule information of the similar policy managed by the schedule managing unit when it is determined by the policy creating unit that a similar policy exists;
A schedule resetting unit for resetting schedule information of the similar policy managed by the schedule management unit in response to the reset request received by the resetting request receiving unit;
Is provided.

  According to the present invention, it is possible to detect and reuse a similar policy and to detect and delete a policy that satisfies a predetermined deletion condition under a condition where there are many policies in which predetermined information related to search is defined. Thus, the ratio of remaining unnecessary policies can be reduced.

It is a figure which shows an example of a structure of the file search device which concerns on embodiment of this invention. It is a figure which shows an example of a data structure of user management data. It is a conceptual diagram of an example of a list of file systems. It is a figure which shows an example of a data structure of policy management data. It is the figure which illustrated file search conditions. It is a figure which shows an example of the data structure of a search result. It is a flowchart which shows an example of operation | movement of the WEB page display part concerning a file search. It is the figure which illustrated the login screen. It is a flowchart which shows an example of operation | movement of the search map part at the time of a login process request | requirement. It is the figure which illustrated the starting screen selection screen. It is the figure which illustrated the designation | designated screen of the policy name. It is the figure which illustrated the selection screen of the file system. It is the figure which illustrated the designation | designated screen of search conditions. It is the figure which illustrated the schedule setting screen. It is the figure which illustrated the policy list screen. It is the figure which illustrated the schedule reset screen. It is the figure which illustrated the search condition reset screen. It is the figure which illustrated the policy detailed display screen. It is the figure which illustrated the search result data screen. It is a flowchart which shows an example of operation | movement of the search map part at the time of a similar policy list creation request. It is the figure which illustrated the similar policy list screen. It is a flowchart which shows an example of operation | movement of the search map part at the time of a deletion candidate policy list creation request. It is the figure which illustrated the deletion candidate policy list screen.

  Hereinafter, a file search system according to an embodiment of the present invention will be described in detail with reference to the drawings.

<Configuration and function of the entire file search system>
FIG. 1 shows an example of the configuration of a file search system according to an embodiment of the present invention.
The file search system connects a file search server 10, a client 11, and a file server 12 to a LAN (Local
(Area Network) 13 or the like is a system in which communication is possible with a wired or wireless communication line.

In FIG. 1, the file search server 10, the client 11, and the file server 12 are communicably connected to each other via a LAN 13. However, the connection method is not limited to the LAN. For example, a WAN (Wide Area Network) is used. ) Or the Internet. In FIG. 1, the file search server 10, the client 11, and the file server 12 are connected on the same LAN segment. However, this configuration is only an example, and any configuration is possible. Good.
Further, in FIG. 1, one client 11 and one file server 12 exist, but two or more each may exist. The file search server 10, the client 11, and the file server 12 do not have to be different devices. For example, the functions of the file search server 10, the client 11, and the file server 12 may be realized by a single device. Is possible.

With the configuration described above, the client 11 transmits a search request to the file server 12 via the file search server 10, and the file server 12 passes through the file search server 10 to obtain file search result data, that is, search conditions. A file name, a file path, etc. (hereinafter abbreviated as “search result data”) matching the above can be transmitted.
As described above, in the present specification and claims, all digital information stored in the information processing apparatus such as document files, table files, e-mails, databases, records stored in the database, programs, etc. Are collectively referred to as “files”.

<Configuration / Function of Client 11>
The client 11 is a computer and is communicably connected to the input device 112, the display device 113, and the storage device 114.
The input device 112 is a device such as a keyboard and a mouse, and the operator of the client 11 can instruct a process to be executed by the client 11 by operating the input device 112. That is, the input device 112 functions as an input unit of the client 11.
The display device 113 is a device such as a liquid crystal display or a printer, and displays or prints out the result of processing executed by the client 11. That is, the display device 113 functions as a display unit and an output unit of the client 11.
The storage device 114 is a device such as a magnetic disk, and is built in the client 11 or connected externally. The storage device 114 and the main storage device of the client 11 (not shown) function as storage means of the client 11.

Although not shown, the client 11 includes a CPU (Central Processing Unit), a main storage device, and the like. Although not shown, the CPU loads a program such as a WEB browser stored in the storage device 114 onto the main storage device, and executes various kinds of processing by executing the instruction code.
Since the technique related to the program execution as described above is well known, in the following description and drawings, in order to avoid complicated description related to the program execution, a WEB browser is referred to as a WEB page display unit 111. The program is described as if the hardware is present, and is described as if each unit executes a process. It should be noted that each unit (for example, the WEB page display unit 111) can be configured by an electronic device or a combination of an electronic device and firmware.

As described above, the WEB page display unit 111 is a WEB browser, and transmits a URL (Uniform Resource Locator) or the like input by the operator of the client 11 using the input device 112 to the file search server 10 or from the file search server 10. WEB page composed of HTML (Hypertext Markup Language) or the like is displayed on the display device 113.
Here, the file search server 10, the client 11, and the file server 12 have an IP address for uniquely specifying a location on the communication line, and an identification name corresponding to the IP address (hereinafter simply “identification name”). For example, the client 11 sends the IP address of the client 11 in addition to the URL to the IP address of the file search server 10 so that the file search server 10 can access the WEB page. Specify where to send.

<Configuration / Function of File Search Server 10>
The file search server 10 is a computer, and includes a search unit 101, a search map unit 102, a WEB page transmission unit 103, and a policy management unit 104, and is communicably connected to the storage device 105.
Although not shown, the file search server 10 includes a CPU, a main storage device, and the like.
The storage device 105 is a device such as a magnetic disk, and is built in the file search server 10 or connected externally. The storage device 105 functions as a storage unit of the file search server 10.
Although not shown, the storage device 105 stores a search program, a search map program, a WEB server program, and a policy management program. Although not shown in the figure, the CPU loads these programs from the storage device 105 onto the main storage device and executes the instruction codes to thereby search the search unit 101, the search map unit 102, the WEB page transmission unit 103, and the policy. Each function of the management unit 104 is realized.

In addition to the above-described programs, the storage device 105 stores user management data 106, file system management data 107, policy management data 108, and search result data 109.
As described later, the user management data 106 stores zero or more user information for logging in to the search map unit 102.
The file system management data 107 stores one or more pieces of information on the file server 12 to be searched (hereinafter referred to as “file system list”). As will be described later, the file search server 10 transmits a file system list to the WEB page display unit 111, and the WEB page display unit 111 displays the received file system list on the display device 113. Then, the operator of the client 11 selects a file system that matches the search target from the list of file systems displayed using the input device 112.

Registered in the policy management data 108 is a policy in which search information including a policy name designated by an operator of the client 11, a search condition, a file system name, and the like is defined. As will be described later, it can be defined according to the purpose, such as a policy for searching for a file that has not been accessed for a specific period at a specific time, and information of a plurality of policies can be accumulated.
The search result data 109 stores search result data searched based on policy search information, as will be described later. Hereinafter, searching based on policy search information is referred to as “execution of policy”.
Although one policy may be repeatedly executed, search result data 109 stores search result data at the time of final execution.

The WEB page transmission unit 103 is a WEB server such as Apache (registered trademark), for example, refers to the URL received from the WEB page display unit 111, creates a WEB page composed of HTML or the like, and the WEB page display unit 111. Send to.
In addition, when the URL received from the WEB page display unit 111 has a predetermined value, the WEB page transmission unit 103 causes the CPU to execute a search map program and activate the search map unit 102.

The search map unit 102 creates a WEB page such as a login screen, a policy name designation screen, a file system selection screen, a search condition designation screen, a schedule setting screen, etc., and delivers it to the WEB page transmission unit 103. The WEB page transmission unit 103 transmits the delivered WEB page to the WEB page display unit 111. Information input by the operator of the client 11 is transmitted to the policy management unit 104.
The policy management unit 104 creates policy management data 108 based on the received information. The policy management unit 104 has a policy schedule management function and a policy control function, and executes the policy according to the set schedule. How the policy management unit 104 performs policy schedule management can be realized by a well-known schedule management function using a function such as an OS or an open source library, and the explanation is complicated. To avoid this, it will not be described in detail here.

Further, the policy management unit 104 transmits a policy search condition and the like to the search map unit 102 when executing the policy. The search map unit 102 creates a search command based on search conditions and the like, causes the CPU to execute a search program, and starts the search unit 101. The search unit 101 executes a search according to the search command, and transmits search result data indicating the search result to the search unit 101 and / or the policy management unit 104. The policy management unit 104 receives the search result data directly from the search unit 101 or via the search map unit 102.
The policy management unit 104 deletes all past search result data corresponding to the executed policy, and registers the search result data at the time of the final execution in the search result data 109. Furthermore, the policy management unit 104 updates the policy management data 108 to the latest information.

The search unit 101 searches for a file stored in the file server 12 using the search keyword received from the search map unit 102, and transmits the search result data to the search map unit 102 and / or the policy management unit 104. To do.
Since it is a well-known technique to search for a file by the search unit 101 as described above, how the search unit 101 searches for a file is not described in detail here, but for example, the search unit 101 Receives a file search command (for example, “File Extension is 'doc'”: file extension is 'doc', “Size Greater than '1MB'”: search for a file with a file size of 1 MB or more) from the search map unit 102 And then search. In other words, the search map unit 102 may create a command understandable by the search unit 101 and transmit it to the search unit 101. The file server 12 includes a search agent (program), the search unit 101 transmits a search command or the like to the search agent, and the search agent transmits search result data to the search unit 101.
It is also possible to search for a file on the file server 12 from the file search server 10 using a file sharing service such as NFS (Network File System) or CIFS (Common Internet File System).

<Configuration / Function of File Server 12>
The file server 12 is a computer and is communicably connected to the storage device 121. Although not shown, the file server 12 includes a CPU, a main storage device, and the like. The storage device 121 is a device such as a magnetic disk, and is built in the file server 12 or connected externally. The storage device 121 and the main storage device of the file server 12 function as storage means of the file server 12.
Although only one storage device 121 is illustrated in FIG. 1, a plurality of storage devices 121 of various types such as a magnetic tape, a magnetic disk, and an optical disk can be connected. As is well known, for example, when the search unit 101 searches for a file stored in the file server 12, the search unit 101 uses various logical volume names, file paths, etc. A plurality of types of devices can be configured, and a file can be specified by a logical volume name, a file path, and the like.

A search target file 122 is stored in the storage device 121. Here, the search target file 122 does not indicate a specific file stored in the storage device 121 but indicates all files that can be the target file. Therefore, the search target file 122 may be all the files stored in the storage device 121, or may be all files excluding highly confidential files such as system logs.
The file server 12 receives a search command or the like from the search unit 101, searches for a file that matches the search condition, for example, includes a search keyword from the files stored in the search target file 122, and searches the search result data for the search unit 101.

<Configuration of each file>
FIG. 2 shows an example of the data configuration of the user management data 106. The user management data 106 is composed of zero or more user-specific login authority records 20.
The login authority record 20 for each user stores user information and the like for logging in to the search map unit 102. Specifically, the login authority record 20 for each user includes items of a user ID 211 and a password 212. User IDs 211 and passwords 212 are collectively referred to as login authority 21 for each user, and are set in the search map unit 102 for the number of users having login authority.

FIG. 3 is a conceptual diagram of an example of a list of file systems.
In the configuration of the file server 12 shown in this conceptual diagram, the identification name of one file server 12 is “Server1”, and the identification name of another file server 12 is “Server2”. “Server1” is composed of two logical volumes, and each logical volume can be uniquely identified by the names “vol1” and “vol2”, respectively. “Server2” is composed of logical volumes that can be uniquely identified by the name of “vol1”.
“Vol1”, “vol2” of “Sever1”, and “vol1” of “Server2” have file paths including folders and files as illustrated. For example, “vol1” of “Server1” has two folders “etc” and “doc”, and one file “file3.doc” exists in the “doc” folder. Similarly, one folder “pjt” exists in “vol2” of “Server1”, and three folders “pjt1,” “pjt2,” “pjt3” exist in the “pjt” folder. In the “pjt1” folder, there are two files “file4.txt” and “file5.doc”. Further, “vol1” of “Server2” has one folder “usr”, and the “usr” folder has three folders “usr1”, “usr2”, and “usr3”, and “usr2” There is one “file5.doc” file in the folder.

Of the above file server 12, logical volume, and file path, for example, the file paths indicated by dotted lines of “file system 301”, “file system 302”, and “file system 303” in FIG. It is stored as a system list 30.
Although not shown, the file search server 10 includes a file system list creation / update program. Although not shown, the operator of the file search server 10 operates an input device such as a keyboard and a mouse connected to the file search server 10 to cause the CPU to execute a file system list creation / update program. The file system list 30 is created, changed, or deleted.

FIG. 4 shows an exemplary data structure of the policy management data 108.
The policy management data 108 is created by the policy management unit 104, registered, updated, and deleted. As for the schedule management function of the policy management unit 104, data management is generally performed using a dedicated DB. However, as described above, in order to avoid complicated explanation, it is not shown here.
The policy management data 108 stores a record indicating the status of zero or more policies. Specifically, the policy management data 108 includes items of a policy identification ID 401, a policy name 402, a state 403, a final execution date / time 404, a total execution count 405, a search condition 406, and a file system 407.

In the policy identification ID 401, an ID (Identifier) for the search map unit 102 to identify a policy is set. The policy identification ID 401 is automatically assigned by the policy management unit 104.
In the policy name 402, a value input by the operator of the client 11, for example, “Policy01” is set.
The state 403 is updated by the policy management unit 104. In state 403, “scheduled” if the policy is waiting to start a schedule, “running” if the policy is being executed, no schedule is set in the policy, or all scheduled schedules have been completed. “No schedule” is set if it is in the state.

The last execution date and time 404 is updated by the policy management unit 104. In the last execution date and time 404, an execution date and time executed at the end of the policy, for example, “2011-01-06 10:00:00” is set. Before the first policy is activated and during execution, since the last execution date and time 404 has not been determined, a character such as a blank indicating that it has not been determined is set.
In the total execution count 405, the number of times the policy has been executed is set. For example, when the execution of the first policy is completed, the total number of executions 405 is updated from “0” to “1” by the policy management unit 104.
The search condition 406 is updated by the policy management unit 104. As described later, the search condition 406 includes values input by the operator of the client 11, such as “File Extension is doc”, “Size Greater than
In the case of “1MB” and “Logic is Match All”, it is set by connecting with a comma “,” like “File Extension is doc, Size Greater than 1MB, Logic is Match All”.
The file system 407 is updated by the policy management unit 104. In the file system 407, a value input by the operator of the client 11, for example, “filesystem01” is set.

FIG. 5 shows a typical example of file search conditions. For example, when the field 501 is “File Extension”, the operator 502 is “Is”, and the value 503 is the file extension “doc”, the search condition is “File Extension is
Also, when the “field 501 is“ Size ”, the operator 502 is“ Greater than ”, and the value 503 is the file size“ 1 MB ”, the search condition is“ Size Greater than 1 MB ”.
Thus, the search condition 406 is set in the format of “field operator value”. When there are multiple search conditions, each search condition is set by connecting with a comma “,”.

In addition, “Logic is Match All” is set for the specification that satisfies all the conditions as described above, but “Logic is Match Any” is set for the specification that satisfies any one of the conditions. Is done. “Logic is Match
“All” or “Logic is Match Any” is connected by a comma “,” following the search condition, and one of them is always set. Here, a simple setting example is given, but the search condition 406 is a search condition. As long as the map unit 102 can create a command that can be understood by the search unit 101, the format may be other than those described above.

FIG. 6 shows an example of the data structure of the search result.
The search result data 109 is composed of zero or more file search result data. Specifically, it includes items of a policy identification ID 601, a sequence number 602, and a search result 603.
The policy identification ID 601 stores an ID corresponding to the policy management data 108. That is, if the policy identification ID 601 is the same as the policy identification ID 401, it indicates search result data for that policy. Since a plurality of search results 603 may be stored, the sequence number 602 is for management by number. Search result data is stored in the search result 603.
In the example of FIGS. 4 and 6, the search result data of the policy having the policy identification ID “123456” are “/vol1/etc/file1.doc”, “/vol1/etc/file2.doc”, and “/ vol1”. You can see that it is “/doc/file3.doc”.
Here, the policy management data 108 and the search result data 109 are divided into two in order to reduce the redundancy of the data. However, they may be the same table or may not have the above-described data configuration.

<Operation of each part>
FIG. 7 is a flowchart showing an example of the operation of the WEB page display unit 111 related to file search.
<Process up to Step S701 in FIG. 7>
When the operator of the client 11 operates the input device 112 to cause the CPU to execute a WEB page display program and activates the WEB page display unit 111, the WEB page display unit 111 displays a WEB browsing screen on the display device 113. Then, the operator of the client 11 operates the input device 112 to input a predetermined URL (for example, “http://fserver.somecompany.com/fsearch/login.html”) in the URL input / display field of the web browsing screen. When entered, the WEB page display unit 111 transmits the input URL to the file search server 10.
The WEB page transmission unit 103 of the file search server 10 receives the input URL and transmits a WEB page for a login screen to the WEB page display unit 111. The WEB page display unit 111 displays the received WEB page on the display device 113 as a login screen.
A display example of the login screen is shown in FIG. In the following screen display examples including FIG. 8, the fields provided in the display screen of a normal WEB browser, such as the URL input / display field and the “return” button, are not displayed. Are naturally displayed on the screen.

<Login process (process related to S701 in FIG. 7)>
When the operator of the client 11 operates the input device 112 to input the user ID and password of the login screen in the user ID input field G81 and password input field G82, respectively, and clicks the login button at the bottom of the login screen, the WEB page The display unit 111 transmits the input user ID and password to the WEB page transmission unit 103 together with a login process request.
As a method for transmitting a login processing request, a predetermined URL (for example, “http://fserver.somecompany.com/fsearch/cgi/login.cgi”) that specifies a CGI (Common Gateway Interface) or the like to execute the login processing is used. ) Is transmitted to the WEB page transmission unit 103, and various methods are known, and these methods may be selected and used. (S701 above)

Note that the same method can be used for a startup screen selection processing request or the like to be described later. In this case, for example, for a startup screen selection process request, a predetermined URL (for example, “http://fserver.somecompany.com/fsearch/cgi/select.cgi”) designating a CGI different from the login process request is sent to the WEB page transmission unit. By transmitting to 103, it is possible to cause the search map unit 102 to execute a startup screen selection process instead of a login process. That is, in this case, the search map program (search map unit 102) is composed of a plurality of CGIs.
Furthermore, a parameter (“page = policy” in this example) can be added to the CGI specification, such as “http://fserver.somecompany.com/fsearch/cgi/wizard.cgi&page=policy”. By doing in this way, it becomes possible to perform different processes depending on the parameters for one CGI.

Also, in the screen transition process described later, the value specified / selected on the screen transitions to the next screen, such as “http://fserver.somecompany.com/fsearch/cgi/wizard.cgi&page=filesystem&policy=Policy01” It can also be passed by adding parameters to the designation of the CGI to be performed (in this example, the designation of the next screen is “page = filesystem” and the value designated on the screen is “policy = Policy01”). That is, the search map unit 102 can store the delivered parameters.
Note that encoding processing and decoding processing may be necessary during parameter delivery or analysis. However, in the following description, it is a well-known technique and avoids complicated description of parameter analysis processing. These are simply expressed as “passing parameters” and “decomposing parameters”.

FIG. 9 is a flowchart illustrating an example of the operation of the search map unit 102 during login processing, that is, when the WEB page transmission unit 103 receives a login processing request from the WEB page display unit 111.
When receiving a login processing request from the WEB page display unit 111, the WEB page transmission unit 103 causes the CPU to execute a search map program and activates the search map unit 102.
The search map unit 102 searches the user management data 106 to determine whether or not the combination of the user ID and password transmitted by the WEB page transmission unit 103 is correct (S901).

If the combination of user ID and password does not match any user management data 106 (NO in S901), the search map unit 102 creates an error screen (S902) and ends the process.
In the following description including this error screen, “search map unit 102 creates X screen” means that search map unit 102 is displayed on display device 113 by WEB page display unit 111 from HTML or the like. To create a WEB page.
When the combination of the user ID and password matches one of the records of the user management data 106 (YES in S901), the search map unit 102 creates an activation screen selection screen (S903).
The search map unit 102 ends the process when the startup screen selection screen is created. Then, the error screen and start-up screen selection screen created by the search map unit 102, that is, the WEB page of each screen is transmitted to the WEB page display unit 111 by the WEB page transmission unit 103.

<Startup screen selection processing (processing related to S702 in FIG. 7)>
Here, the operation of the WEB page display unit 111 will be described using FIG. 7 again. The WEB page display unit 111 displays the WEB page received from the search map unit 102 on the display device 113.
Therefore, when the WEB page display unit 111 receives the WEB page of the error screen from the search map unit 102, the error screen is displayed on the display device 113, so the operator of the client 11 solves the cause of the error. Then, the login operation may be performed again. In this case, the WEB page display unit 111 performs the process of S701 again.
On the other hand, when the WEB page display unit 111 receives the WEB page of the startup screen selection screen from the search map unit 102, the startup screen selection screen is displayed on the display device 113, and the operator of the client 11 performs the startup screen selection operation. It can be carried out.

A display example of the startup screen selection screen is shown in FIG. As shown in FIG. 10, a radio button and a start screen name (“policy creation wizard” or “policy list screen”) are displayed in the start screen selection unit G1001 of the start screen selection screen, and the operator of the client 11 You can select the screen you want to start.
Note that the operator of the client 11 normally selects the “policy creation wizard” when creating a new policy, and selects the “policy list screen” when confirming the created policy information. In FIG. 10, the “policy creation wizard”
The state in which is selected is illustrated.
When the operator of the client 11 clicks the radio button on the screen to be activated using the input device 112, activates the radio button and clicks the activation button at the bottom of the activation screen selection screen, the WEB page display unit 111 becomes active. A screen activation process request corresponding to the radio button is transmitted to the WEB page transmission unit 103. When receiving the screen activation processing request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102.

When the content of the screen activation processing request is “policy creation wizard”, the search map unit 102 displays a policy name designation screen that is the first screen of the policy creation wizard as a new screen, that is, as a separate screen from the startup screen selection screen. Create
The “Policy Creation Wizard” is divided into several steps such as “Policy Name Specification Screen”, “File System Selection Screen”, “Search Condition Specification Screen”, and “Schedule Setting Screen”. The policy is created while inputting or selecting necessary information on each screen.

On the other hand, when the content of the screen activation process request is “policy list screen”, the search map unit 102 transmits a policy information acquisition request to the policy management unit 104. The policy management unit 104 acquires policy information and transmits the policy information to the search map unit 102. When receiving the policy information, the search map unit 102 creates a policy list screen as a new screen, that is, as a separate screen from the startup screen selection screen.
The screen is created as a separate screen from the startup screen selection screen, but the policy name designation screen and policy list screen, which are the first screens of the policy creation wizard, cannot be opened at the same time. This control takes account of operability, but may be dealt with by naming the screen that is opened from the startup screen selection screen. Subsequent policy creation wizard display processing and policy list display processing will be described later.

  On the other hand, when the operator of the client 11 operates the input device 112 and clicks the logout button at the bottom of the startup screen selection screen, the WEB page display unit 111 transmits a logout processing request to the WEB page transmission unit 103. When the web page transmission unit 103 receives a logout processing request from the web page display unit 111, the web page transmission unit 103 causes the CPU to execute a search map program and activates the search map unit 102. The logout screen created by the search map unit 102, that is, the WEB page of the logout screen is transmitted to the WEB page display unit 111 by the WEB page transmission unit 103 and displayed on the display device 113.

<Policy creation wizard display processing (processing related to S703 in FIG. 7)>
A display example of the policy name designation screen is shown in FIG. As shown in FIG. 11, a text box is displayed in the policy name designation field G1101 of the policy name designation screen, and the operator of the client 11 can designate the policy name. FIG. 11 illustrates a state in which “Policy01” is designated.
When the operator of the client 11 clicks the next button using the input device 112, the WEB page display unit 111 transmits the WEB page transmission unit 103 together with the screen transition request. At this time, the designated policy name is delivered by attaching a parameter (in this example, “policy = Policy01”) to the designation of the CGI.

When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. As described above, the search map unit 102 acquires file system list information from the file system management data 107 and creates a file system selection screen.
However, when the operator of the client 11 does not input the policy name, the next button is not valid and the screen cannot be changed to the file system selection screen. Even in each screen of the policy creation wizard, which will be described later, unless the necessary information is entered, transition to the next screen and execution are not possible. In this way, necessary information can be set without omission.

  When the operator of the client 11 uses the input device 112 and clicks the cancel button, the policy creation wizard is closed and the process ends. Also in each screen of the policy creation wizard described later, the operator of the client 11 can cancel the policy creation in the middle by discarding the information input / selected so far by clicking the cancel button.

A display example of the file system selection screen is shown in FIG. As shown in FIG. 12, a drop-down list is displayed in the file system selection section (G1201) of the file system selection screen, and the operator of the client 11 can select a file system to be searched. FIG. 12 illustrates a state where “filesystem01” is selected.
When the operator of the client 11 clicks the next button using the input device 112, the WEB page display unit 111 transmits a screen transition request to the WEB page transmission unit 103. At this time, the selected file system name is handed over by attaching a parameter (“filesystem = filesystem01” in this example) to the designation of CGI.
When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. The search map unit 102 creates a search condition designation screen.

When the operator of the client 11 clicks the return button using the input device 112, the WEB page display unit 111 transmits a screen transition request to the WEB page transmission unit 103 together with a parameter indicating return. When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. The search map unit 102 creates a policy name designation screen on which the stored policy names are displayed. That is, on each screen of the policy creation wizard described later, the operator of the client 11 can return to the previous screen by clicking the return button, and can confirm or correct the input information.
On the other hand, when the operator of the client 11 uses the input device 112 and clicks the cancel button, the policy creation wizard is closed, and the process ends.

A display example of the search condition designation screen is shown in FIG. As shown in FIG. 13, a drop-down list is displayed at the top (G1301) of the search condition screen, and the operator of the client 11 can select “Match All” (which satisfies all) or “ “Match Any” can be selected.
In the search condition designation part (G1302) of the search condition screen, a drop-down list, a text box, a + button, a − button, and a reset button are displayed.
The operator of the client 11 can select a search condition to be specified from the drop-down list and enter a value in the text box. Further, the operator of the client 11 can increase the search condition by one line by clicking the + button, can decrease the search condition by one line by clicking the − button, and can further search by clicking the reset button. The conditions are in the initial state ("File", "is", "All" from the left),
In other words, it is possible to return to a state meaning “all files”. In this way, the operator of the client 11 can freely add / delete the search condition and make it the initial state.
In FIG. 13, the first line of the search condition means “file extension is doc”, “File Extension”, “Is”, and “doc” from the left, and the second line of the search condition is “file”. The size means “1 MB or more”, and “Size”, “Greater than”, and “1 MB” from the left. Furthermore, a state in which “Match All” that satisfies all the search conditions is designated is illustrated.

When the operator of the client 11 clicks the next button using the input device 112, the WEB page display unit 111 transmits a screen transition request to the WEB page transmission unit 103. At this time, the parameter (in this example “logic = Logic is Match All & query1 = File Extension is
doc & query2 = Size Greater than 1MB ”) is added to pass the specified search condition.
When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. The search map unit 102 creates a schedule setting screen.
When the operator of the client 11 clicks the return button using the input device 112, the WEB page display unit 111 transmits a screen transition request to the WEB page transmission unit 103 together with a parameter indicating return. When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. The search map unit 102 creates a file system selection screen in which the stored file system name is selected.
On the other hand, when the operator of the client 11 uses the input device 112 and clicks the cancel button, the policy creation wizard is closed, and the process ends.

A display example of the schedule setting screen is shown in FIG. As shown in FIG. 14, in the upper part of the schedule setting screen (G1401), a date and time text box for designating the first execution date and time of the policy is displayed. In the lower part of the schedule setting screen (G1402), a drop-down list indicating an interval for specifying a repetition condition and a text box for specifying an execution upper limit count are displayed.
The operator of the client 11 can set the policy execution schedule using these text boxes and drop-down lists. That is, the operator of the client 11 can freely set a schedule for executing the policy.

In FIG. 14, “2011-01-11” is designated as the date and “10:00” is designated as the time for the first execution date and time of policy execution. Further, as an example of repeated policy execution, “Daily” is selected as the interval, and “10” is specified as the upper limit of execution. This indicates that “2011-01-11 10:00” is executed every day with the first execution date and time, and the policy is executed until the total number of executions reaches 10 (that is, after 10 days).
The drop-down list indicating the intervals includes “Only once” indicating only once, “Weekly” indicating week, and “Weekly” indicating the month other than “Daily” indicating everyday.

When the operator of the client 11 clicks the execute button using the input device 112, the WEB page display unit 111 transmits a similar policy list creation request to the WEB page transmission unit 103. At this time, the schedule information is handed over by adding a parameter (in this example, “date = 2011-01-11 & time = 10: 00 & unit = daily & limit = 10”) to the designation of CGI.
Upon receiving the similar policy list creation request, the WEB page transmission unit 103 causes the CPU to execute the search map program and starts the search map unit 102 with the delivered parameters. The search map unit 102 creates a similar policy list processing screen. The similar policy list creation request process will be described later.

When the operator of the client 11 clicks the return button using the input device 112, the WEB page display unit 111 transmits a screen transition request to the WEB page transmission unit 103 together with a parameter indicating return. When receiving the screen transition request, the WEB page transmission unit 103 causes the CPU to execute the search map program, and starts the search map unit 102 together with the delivered parameters. The search map unit 102 creates a search condition screen in which stored search conditions are set.
On the other hand, when the operator of the client 11 uses the input device 112 and clicks the cancel button, the policy creation wizard is closed, and the process ends.

<Policy List Screen Display Processing (Processing Related to S703 in FIG. 7)>
A display example of the policy list screen is shown in FIG. The policy list screen of FIG. 15 is displayed when the radio button of the “policy list screen” is activated and the start button is clicked on the start screen selection screen of FIG.
As shown in FIG. 15, a button for operating the policy by the operator of the client 11 is displayed on the policy operation unit (G1501), and a button for resetting the schedule from the left (hereinafter referred to as schedule reset button). ), A button for stopping a policy being executed (hereinafter referred to as a stop button), a button for re-editing a policy search condition (hereinafter referred to as a search condition re-edit button), and a button for canceling a policy schedule (hereinafter referred to as a search condition re-edit button) , Called schedule cancel button). The policy name display area (G1502) displays the policy name, and a clickable link (hereinafter referred to as policy name link) is attached to the policy name. The status display section (G1503) displays the policy status. The total number of executions of the policy is displayed in the total execution number display section (G1504).

At the bottom of the policy list screen (G1505), the operator of the client 11 performs an update button for updating the policy list to the latest state, an organization button for detecting a less frequently used policy from the policy list, and closing the policy list for processing. A close button is displayed to exit.
In FIG. 15, three policies are illustrated: the policy name on the first line is “Policy01”, the state is “scheduled”, the total number of executions is “3”, and the policy name on the second line is “Policy02”. The status is “execution”, the total execution count is “5”, the policy name on the third line is “Policy03”, the status is “no schedule”, and the total execution count is “0”. Here, the policy information displayed in the policy list is the content stored in the policy management data 108 as described above.

When the operator of the client 11 clicks the schedule reset button using the input device 112, the WEB page display unit 111 transmits a schedule reset request to the WEB page transmission unit 103. When receiving the schedule reset request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 creates a schedule reset screen. That is, the policy list screen transits to the schedule reset screen.
However, the schedule reset button is effective only when the policy is in the state of “no schedule”, and the schedule reset button cannot be clicked when the status is “running” or “scheduled”. Furthermore, when the policy schedule is reset, the state will change from “no schedule” to “scheduled” or “running”.

<Schedule reset screen display processing>
A display example of the schedule resetting screen is shown in FIG. The schedule reset screen is the same as that in FIG. 14 described above, but the return button is not displayed.
When the operator of the client 11 clicks the cancel button using the input device 112 on the schedule reset screen, the WEB page display unit 111 transmits a cancel request to the WEB page transmission unit 103. When receiving the cancel request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 creates a policy list screen in the same manner as the policy list creation process described above. That is, the screen changes from the schedule reset screen to the policy list screen.
On the schedule reset screen, when the operator of the client 11 clicks the execution button using the input device 112, the web page display unit 111 transmits an execution request to the web page transmission unit 103. When receiving the execution request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 transmits an execution request to the policy management unit 104.
The policy management unit 104 sets a policy schedule and transmits the policy information to the search map unit 102. The search map unit 102 creates the policy list screen again as in the policy list creation process described above. That is, the screen changes from the schedule reset screen to the policy list screen. (End of schedule reset screen display processing)

Return to the explanation of the policy list screen again. When the operator of the client 11 clicks the stop button using the input device 112, the WEB page display unit 111 transmits a stop request to the WEB page transmission unit 103. When receiving the stop request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 causes the CPU to execute the policy management program and activates the policy management unit 104 together with the stop request. The policy management unit 104 performs policy stop processing and transmits the policy information to the search map unit 102. The search map unit 102 creates the policy list screen again as in the policy list creation process described above. That is, it is updated to the latest policy list screen.
However, the stop button is effective only when the policy is in the “running” state. When the state is “scheduled” and “no schedule”, the stop button cannot be clicked. If the policy is stopped, the policy status will be “Scheduled” if the schedule still exists from “Being executed”, and there is no schedule after that, that is, the last schedule is being executed. Changes to “no schedule”.

  When the operator of the client 11 clicks the search condition re-edit button using the input device 112, the WEB page display unit 111 transmits a search condition re-edit request to the WEB page transmission unit 103. When receiving the search condition reediting request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 creates a search condition re-editing screen. That is, a transition is made from the policy list screen to the search condition re-edit screen. However, the search condition re-edit button is valid only when the status is “no schedule” and “scheduled” policy, and the search condition re-edit button cannot be clicked when the status is “executing”.

<Display processing of search condition re-edit screen>
A display example of the search condition re-editing screen is shown in FIG. The search condition re-editing screen is the same as in FIG. 13 described above, but the back button and the next button are not displayed, and a setting button is displayed instead.
When the operator of the client 11 clicks a cancel button using the input device 112 on the search condition re-edit screen, the WEB page display unit 111 transmits a cancel request to the WEB page transmission unit 103. When receiving the cancel request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 creates a policy list screen in the same manner as the policy list creation process described above. That is, a transition is made from the search condition re-editing screen to the policy list screen.

When the operator of the client 11 clicks a setting button using the input device 112 on the search condition re-editing screen, the WEB page display unit 111 transmits a setting request to the WEB page transmission unit 103. When receiving the setting request, the WEB page transmission unit 103 causes the CPU to execute a search map program and activates the search map unit 102. The search map unit 102 causes the CPU to execute a policy management program and activates the policy management unit 104 together with a setting request.
At this time, the search map unit 102 uses the parameter “logic = Logic is Match” to specify the CGI.
When All & query1 = File is All ”, for example, the parameters are passed as“ File is All ”and“ Logic is Match All ”so that the policy management unit 104 can understand. The policy search condition is reset, that is, the search condition 406 record of the policy management data 108 is updated, and the policy information is transmitted to the search map unit 102.
In the above example, the policy management unit 104 sets the search condition 406 record of the policy management data 108 to “File is
All, Logic is Match All ”is updated. Then, the search map unit 102 creates the policy list screen again in the same manner as the policy list creation process described above. That is, the search condition re-edit screen transitions to the policy list screen. (End of search condition edit screen display processing)

Return to the explanation of the policy list screen again. When the operator of the client 11 clicks the schedule cancel button using the input device 112, the web page display unit 111 transmits a schedule cancel request to the web page transmission unit 103. When receiving the schedule cancellation request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 causes the CPU to execute a policy management program and activates the policy management unit 104 together with a schedule cancellation request. The policy management unit 104 performs policy schedule cancellation processing and transmits the policy information to the search map unit 102. The search map unit 102 creates the policy list screen again as in the policy list creation process described above. That is, it is updated to the latest policy list screen.
However, the schedule cancel button is effective only when the policy is in the “scheduled” state, and the schedule cancel button cannot be clicked when the status is “executing” or “no schedule”. If the schedule is canceled, the policy state changes from “scheduled” to “no schedule”.

  When the operator of the client 11 clicks the policy name link using the input device 112, the WEB page display unit 111 transmits a policy details display request to the WEB page transmission unit 103. When receiving the policy detail display request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 causes the CPU to execute a policy management program, and activates the policy management unit 104 together with a policy detail display request. The policy management unit 104 acquires detailed policy information and transmits the policy information to the search map unit 102. The search map unit 102 creates a policy details display screen. That is, a policy details display screen is created as a separate screen from the policy list screen.

<Display processing of policy details display screen>
A display example of the policy detail display screen is shown in FIG. As shown in FIG. 18, a drop-down list is displayed in the upper part (G1801) of the policy details display area, and “policy details” is selected. Further, details of the policy information are displayed in the property part (G1802) of the policy detail display.
In FIG. 18, the policy name is “Policy01”, the status is “scheduled”, and the last execution date is “2011-01-10”.
11:00:00 ”, the total number of executions is“ 3 ”, and the file system is“ filesystem01. ”These are the contents stored in the policy management data 108 as described above.
Details of the schedule management information are displayed in the schedule management information part (G1803) of the policy details display. In FIG. 18, “2011-01-10 10:00:00” is illustrated as the first execution date, “Daily” is illustrated as the repetition interval, and “10” is illustrated as the upper limit of the number of executions. Although not shown, these are the contents stored by the policy schedule management function of the policy management unit 104.
The search condition is displayed in the search condition part (G1804) of the policy detail display. In FIG. 18, “Match Any” is illustrated as the relationship between search conditions, “File Extension is doc” is illustrated as the first line of the search condition, and “Size Greater than 1MB” is illustrated as the second line of the search condition. Yes. These are the contents stored in the policy management data 108 as described above.

  In the drop-down list at the top of the policy details display section (G1801), “search result data” can be selected in addition to “policy details”, and the operator of the client 11 uses the input device 112 to select “search result data”. When “” is selected, the WEB page display unit 111 transmits a search result data display request to the WEB page transmission unit 103. When receiving the search result data display request, the WEB page transmission unit 103 causes the CPU to execute a search map program and activates the search map unit 102. The search map unit 102 acquires search result data from the search result data 109 using the corresponding policy identification ID as a key, and creates a search result data screen. That is, the policy detail display screen is changed to the search result data screen. (End of the policy details display screen display process)

<Search result data screen display processing>
A display example of the search result data screen is shown in FIG. As shown in FIG. 19, a drop-down list is displayed at the top of the search result screen (G1901), and “search result data” is selected. In the search result data operation section (G1902), the number of items from the left, a drop-down list for manipulating the number of items displayed per page, a button for displaying the first page, a button for displaying the previous page, and a page number are designated. A text box to display, a button to display the next page, and a button to display the last page. In the search result data display section (G1903), search result data at the time of final execution of the policy is displayed.
In FIG. 19, the number of cases is “100”, the number of displays per page is “10”, and the page number is “1”. Search result data includes "/dir1/subdir1/file1.doc", "/dir1/subdir1/file2.doc", "/dir1/subdir2/file3.doc", "/ dir1 / subdir2 / tmp / tmp1 .txt ”,“ /dir1/subdir2/tmp/tmp2.txt ”,“ /dir1/subdir2/tmp/tmp3.txt ”,“ /dir2/project1/data.xml ”,“ /dir2/project2/data1.xml "/Dir2/project2/data2.xml", "/dir2/project2/data3.xml" are illustrated.

  In the drop-down list at the top of the search result screen (G1901), “policy details” can be selected in addition to “search result data”, and the operator of the client 11 uses the input device 112 to select “policy details”. Is selected, the WEB page display unit 111 transmits a policy detail display request to the WEB page transmission unit 103. Upon receiving the policy detail display request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. As described above, the search map unit 102 creates a policy details display screen. That is, a transition is made from the search result data screen to the policy detail display screen. (End of search result data screen display processing)

  Return to the explanation of the policy list screen again. When the operator of the client 11 clicks the update button using the input device 112, the WEB page display unit 111 transmits a screen update request to the WEB page transmission unit 103. When receiving the screen update request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 causes the CPU to execute a policy management program and activates the policy management unit 104 together with a screen update request. The policy management unit 104 acquires detailed policy information and transmits the policy information to the search map unit 102. The search map unit 102 creates a policy list screen. That is, the latest policy information is displayed on the policy list screen.

When the operator of the client 11 clicks the organization button using the input device 112, the WEB page display unit 111 transmits a deletion candidate policy list creation request to the WEB page transmission unit 103. When receiving the deletion candidate policy list creation request, the WEB page transmission unit 103 causes the CPU to execute the search map program and activates the search map unit 102. The search map unit 102 creates a deletion candidate policy list. The deletion candidate policy list creation request will be described later.
When the operator of the client 11 clicks the cancel button using the input device 112, the policy list screen is closed and the processing of the search map unit 102 ends.

<Similar policy list creation request>
FIG. 20 is a flowchart illustrating an example of the operation of the search map unit 102 when a similar policy list creation request is made.
The search map unit 102 causes the CPU to execute a policy management program, and activates the policy management unit 104 together with a similar policy list creation request and stored parameters. The policy management unit 104 receives the file system name received by the WEB page transmission unit 103, that is, the file system name selected by the operator of the client 11 on the file system selection screen of the policy creation wizard using the input device 112. It is determined by searching the file system 407 record of the policy management data 108 (S2001).
If the file system name does not match the file system 407 record of any policy management data 108 (NO in S2001), the policy management unit 104 transmits the result information to the search map unit 102, and makes a similar policy list creation request. Terminate the process. The subsequent processing of the search map unit 102 will be described later.

  If the file system name matches the file system 407 record of any policy management data 108 (YES in S2001), the process proceeds to S2002. The policy management unit 104 stores the search conditions received by the WEB page transmission unit 103, that is, the search conditions specified by the operator of the client 11 on the search condition specification screen of the policy creation wizard using the input device 112. In addition, the search condition 406 record of the policy management data 108 is searched. Specifically, it is determined whether or not there exists a policy that “the search condition is completely matched or at least one of the search conditions is matched and has an execution history twice or more” (S2002).

First, a description will be given from a case where there is a policy that “a search condition is completely matched or at least one of the search conditions matches and has an execution history more than once” (YES in S2002). The policy management unit 104 first sets a policy with completely matching search conditions as a similar policy.
For example, the policy management unit 104 uses the parameter “logic = Logic is Match All & query1 = File Extension is passed from the search map unit 102.
doc & query2 = Size Greater than 1MB ”
is Match All ”,“ File Extension is doc ”, and“ Size Greater than 1 MB. ”On the other hand, the policy management unit 104 searches and analyzes the search condition 406 record of the policy management data 108. For example,“ If “File Extension is doc, Size Greater than 1MB, Logic is Match All” is stored, “File Extension is doc”, “Size Greater than
1MB "and" Logic is Match All "are decomposed and compared with the stored search condition. In this example, the search condition stored in the policy management unit 104 and the search condition 406 record of the policy management data 108 are Since they match, the policy management unit 104 stores this policy as a similar policy.

Further, the policy management unit 104 also sets a policy that matches even one of the search conditions and has an execution history more than once as a similar policy.
For example, when the search condition is “file extension is doc” and “file size is 1 MB or more”, the policy management unit 104 selects “logic = Logic is
“Match All & query1 = File Extension is doc & query2 = Size Greater than 1MB” is stored, but as described above, it is decomposed into “Logic is Match All”, “File Extension is doc”, and “Size Greater than 1MB”. The policy management unit 104 searches and analyzes the search condition 406 record of the policy management data 108. For example, when “File Extension is txt, Size Greater than 1 MB, Logic is Match All” is stored, Extension is txt ”,“ Size Greater than
It is decomposed into “1MB” and “Logic is Match All” and matched with the stored search conditions, where the search conditions except “Logic is Match All” or “Logic is Match Any”, which represents the relationship between the search conditions. “Size Greater than 1MB” is matched by 1. Further, the policy management unit 104 searches the policy management data 108 for the total execution count 405 records for this policy, and the total execution count is “3”. , The execution history is held twice or more, and this is stored as a similar policy.
In this way, the policy management unit 104 collates the search condition with the record of the policy management data 108 and stores it as a similar policy.

  If there is no policy that “the search condition is completely matched” and “a policy that matches at least one of the search conditions and has an execution history more than once” (NO in S2002), the policy management unit 104 The result information is transmitted to the search map unit 102, and the processing for the similar policy list creation request is terminated. The subsequent processing of the search map unit 102 will be described later. (End of S2002)

If YES in step S2002, the policy management unit 104 sorts items stored as similar policies in descending order of similarity.
Here, the policy management unit 104 sets the “similarity of search conditions” among the stored similar policies to the highest similarity.
Next, if the search condition is “Logic is Match All”, which represents the relationship between the search conditions, “Logic
It is judged that the similarity is high in descending order of the number of matching search conditions from those specifying “is Match All”. Next, “Logic is Match Any” is included in the search conditions. If so, “Logic is Match
It is assumed that the similarity is high in the descending order of the number of matching search conditions from the similar policies including “All”.
On the other hand, when the search condition is “Logic is Match Any” indicating the relationship between the search conditions, the “Logic is Match Any”
It is judged that the similarity is high in the order of the number of matching search conditions from those specifying “is Match Any”. In this case, the policies specifying “Logic is Match All” are similar. Judge that it is not.
When the policy management unit 104 finishes sorting in the order of policies with high similarity, the policy management unit 104 transmits the policy information to the search map unit 102. The search map unit 102 creates a similar policy list and ends the processing for the similar policy list creation request. That is, the screen transitions from the schedule setting screen to the similar policy list screen. (End of similar policy list creation request)

Here, in FIG. 20, if the similar policy list is not created, that is, if NO in step S2001 or NO in step S2002, the search map unit 102 causes the CPU to execute the policy management program to create a new policy. The policy management unit 104 is activated together with the creation request. When the policy management unit 104 receives a new policy creation request, the policy management unit 104 creates a policy based on the value input by the operator of the client 11 using the policy creation wizard, and transmits the policy information to the search map unit 102.
At this time, the parameter “policy = Policy01 & filesystem = filesystem01 & logic = Logic is Match”
If &quot; All & query1 = File Extension is doc & query2 = Size Greater than 1MB & date = 2011-01-11 & time = 10: 00 & unit = daily & limit = 10 "is passed, the policy management unit 104 decomposes the parameter and policy of the policy management data 108 Name 402 record “Policy01”, file system 407 record “filesystem01”, search condition 406 record “File Extension is
“doc, Size Greater than 1 MB, Logic is Match All” is set, and the schedule information is delivered to the schedule management function of the policy management unit 104.
Then, the search map unit 102 creates a policy list screen, similar to the policy list creation process described above. That is, a new policy is created and the schedule setting screen is changed to the policy list screen.

A display example of the similar policy list screen is shown in FIG. The similar policy list screen is the same as that in FIG. 15 described above, but there is a new policy creation button instead of the update button, the organization button, and the close button.
In FIG. 21, the similar policy list illustrates a state in which policy names “Policy01” and “Policy03” are displayed in order from the top in order of policies with high similarity. When the operator of the client 11 clicks the create new policy button on the similar policy list screen using the input device 112, the same operation as in the case where the similar policy list is not created in FIG. . That is, the search map unit 102 causes the CPU to execute the policy management program, and activates the policy management unit 104 together with a new policy creation request. When the policy management unit 104 receives a new policy creation request, the policy management unit 104 creates a policy based on the value input by the operator of the client 11 using the policy creation wizard, and transmits the policy information to the search map unit 102. The search map unit 102 creates a policy list screen in the same manner as the policy list creation process described above. That is, a new policy is created without using a similar policy, and a transition is made from the similar policy list screen to the policy list screen.

On the other hand, the operator of the client 11 can operate the similar policy by operating the policy operation unit (G2101). For example, instead of resetting the schedule of the policy name “Policy01” having the highest similarity in the policy list and not creating a new policy, it is possible to use a similar policy. It is also possible to re-edit similar policy search conditions, edit similar policy search conditions, and then reset the schedule.
When the similar policy schedule is reset, the search map unit 102 causes the CPU to execute the policy management program, and activates the policy management unit 104 together with the similar policy schedule reset request. Upon receiving the similar policy schedule reset request, the policy management unit 104 transmits policy information to the search map unit 102 based on the value set in the similar policy and the schedule reset value of the similar policy. The search map unit 102 creates a policy list screen in the same manner as the policy list creation process described above. That is, similar policy schedule resetting is performed, and a transition is made from the schedule resetting screen to the policy list screen.

  In this way, when creating a policy, it is possible to reuse a similar policy and prevent the number of similar policies from increasing. In S2002 of FIG. 20, a policy having “execution history more than once” is determined. However, if the policy is reused as a similar policy without restriction, a policy with low usage frequency will be a candidate as a similar policy indefinitely. Therefore, the number of execution histories is also determined. Further, as will be described later, a policy having “execution history of once or less” is determined in the deletion candidate policy list creation process, and is set as a policy deletion candidate. These thresholds of X times are examples, and may be changed according to the size of the file search apparatus, the number of policies to be created, and the like.

<Delete candidate policy list creation request>
FIG. 22 is a flowchart illustrating an example of the operation of the search map unit 102 when a deletion candidate policy list creation request is made. The search map unit 102 causes the CPU to execute a policy management program, and activates the policy management unit 104 together with a deletion candidate policy list creation request. The policy management unit 104 searches the status 403 record of the policy management data 108 and searches for a policy of “no schedule” to determine (S2201).
If the “no schedule” policy does not match any state 403 record in the policy management data 108 (NO in S2201), the policy management unit 104 transmits the result information to the search map unit 102. The search map unit 102 creates an error screen (S2205) and ends the process. That is, the policy list screen transits to the error screen. If the “no schedule” policy matches the state 403 record of any policy management data 108 (YES in S2201), the process proceeds to S2202. The policy management unit 104 searches the policy management data 108 for the total number of executions 405 records, and searches for and determines a policy whose total number of executions is 1 or less (S2202).

If a policy with a total execution count of 1 or less does not exist for any 405 records in the total execution count of any policy management data 108 (NO in S2202), the policy management unit 104 transmits the result information to the search map unit 102. . The search map unit 102 creates a deletion candidate policy list screen in which no policy is displayed in the list (S2204), and ends the process. That is, a transition is made from the policy list screen to the deletion candidate policy list screen in which no policy is displayed in the list.
If there is a policy with a total execution count of 1 or less in the total execution count 405 record of any policy management data 108 (YES in S2202), the process proceeds to S2203. In step S2203, the policy management unit 104 transmits to the search map unit 102 deletion candidate policy list information that is “no schedule” and the total number of executions is one or less. The search map unit 102 creates a deletion candidate policy list screen (S2203) and ends the process. That is, a transition is made from the policy list screen to the deletion candidate policy list screen. (End of deletion candidate list creation request)

  A display example of the deletion candidate policy list screen is shown in FIG. As shown in FIG. 23, in the upper part of the policy list (G2301), a drop-down list for the operator of the client 11 to narrow down “unscheduled policies with a total execution count of X times or less” from the policy list is displayed. Is done. The policy selection unit (G2302) displays a check box for selecting a policy in each line of the policy list, and the policy name (G2303) has a clickable link (hereinafter referred to as a policy name link). It is stretched. Further, at the bottom of the policy list (G2304), a delete button for deleting the policy selected by the check box and a cancel button for completing the operation and returning to the policy list screen are displayed. In FIG. 23, the policy name “Policy03” is displayed and the check box is checked.

  When the operator of the client 11 reselects the drop-down list using the input device 112 on the deletion candidate policy list screen, the search map unit 102 causes the CPU to execute the policy management program, and requests a screen redisplay. At the same time, the policy management unit 104 is activated. The policy management unit 104 transmits to the search map unit 102 deletion candidate policy list information that is “no schedule” and the total number of executions is X times or less (X is a setting value selected from the drop-down list) as in the screen display. To do. The search map unit 102 creates a deletion candidate policy list screen and ends the process. That is, the deletion candidate policy list screen is updated. In this way, the operator of the client 11 can narrow down the unscheduled policies and widen the narrowing range according to the total number of executions. When the operator of the client 11 clicks the policy name link using the input device 112, a policy details display screen is created as in the policy list screen. That is, a policy details display screen is created as a separate screen from the policy list screen.

When the operator of the client 11 selects the check box of the policy selection unit (G2302) using the input device 112 and clicks the delete button at the bottom of the policy list (G2304), the search map unit 102 sends the policy to the CPU. The management program is executed, and the policy management unit 104 is activated together with the deletion request. When the policy management unit 104 receives the deletion request, the policy management unit 104 deletes the policy selected by the check box and transmits the policy information to the search map unit 102. The search map unit 102 creates a deletion candidate policy list screen and ends the process. That is, the deletion candidate policy list screen is updated.
When the operator of the client 11 uses the input device 112 and clicks a cancel button at the bottom of the policy list (G2304), the search map unit 102 transmits the cancel request to the policy management unit 104. When the policy management unit 104 receives the cancel request, the policy management unit 104 transmits the policy information to the search map unit 102. The search map unit 102 creates a policy list screen and ends the process. That is, a transition is made from the deletion candidate policy list screen to the policy list screen.

  In this way, a low-use policy is detected and can be deleted. Regarding the deletion process, as described above, the operator of the client 11 confirms on the screen and clicks the delete button to delete the policy. If the confirmation of the operator of the client 11 is unnecessary, It is also possible to automatically delete the list periodically without creating it. That is, periodic deletion is possible by combining a deletion candidate policy list creation request and deletion processing.

  In the above-described embodiment, the description has been made on the policy in which the search information including the policy name, the search condition, the file system name, and the like is defined. However, the definition of the policy is only an example, and different information is defined. The present invention can also be applied to policies.

  As described above, according to the present invention, similar policies are detected and reused and used under conditions where there are many policies in which predetermined search information such as search conditions and file system names are defined. By detecting and deleting a policy that satisfies a predetermined deletion condition such as a low frequency, it is possible to reduce the ratio at which unnecessary policies remain.

DESCRIPTION OF SYMBOLS 10 ... File search server 101 ... Search part 102 ... Search map part 103 ... WEB page transmission part 104 ... Policy management part 105 ... Storage device 106 ... User management data 107 ... File system management data 108 ... policy management data, 109 ... search result data, 11 ... client, 111 ... WEB page display unit, 112 ... input device, 113 ... display device, 114 ... storage device, 12 ... file server, 121 ... storage device, 122 ... search Target file, 13 ... LAN

Claims (2)

Policy management data storage means for storing policy management data in which a plurality of policies defined with predetermined search information are registered;
Policy creation request accepting means for accepting a policy creation request including predetermined search setting conditions from a client;
When a policy creation request is accepted by the policy creation request accepting means, a search condition for each policy registered in the policy management data stored by the policy management data storage means, and a search setting condition included in the policy creation request; Based on the policy management data, it is determined whether or not there is a similar policy similar to the newly created policy, and if it is determined that there is no similar policy, A new policy is created based on the search setting condition included in the policy creation request and is registered in the policy management data. When it is determined that a similar policy exists, the policy of the similar policy is determined according to the request from the client. Edit the search information, or use the search setting conditions included in the policy creation request. And policy creation means to be registered in the policy management data to create a new policy Zui,
Policy organization request accepting means for accepting a policy organization request from the client;
When a policy rearrangement request is accepted by the policy rearrangement request acceptance unit, a deletion candidate policy that satisfies a predetermined deletion condition is detected from the policies registered in the policy management data stored by the policy management data storage unit. A deletion candidate policy list presentation means for presenting a list of deletion candidate policies to the client;
Policy deletion request accepting means for accepting a policy deletion request for deleting a policy included in the list of deletion candidate policies from a client;
When a policy deletion request is received by the policy deletion request receiving unit, a policy deletion unit that deletes the policy requested to be deleted by the policy deletion request from the policy management data stored by the policy management data storage unit;
A file search apparatus comprising: Schedule receiving means for receiving schedule information indicating a schedule for executing a search based on each policy registered in the policy management data stored in the policy management data storage means;
Schedule management means for managing the schedule information received by the schedule reception means, and performing a search based on each policy according to the schedule indicated by the schedule information;
A reset request accepting unit that accepts a reset request from a client to reset the schedule information of the similar policy managed by the schedule managing unit when it is determined by the policy creating unit that a similar policy exists;
A schedule resetting unit for resetting schedule information of the similar policy managed by the schedule management unit in response to the reset request received by the resetting request receiving unit;
The file search apparatus according to claim 1, further comprising:

Images