Parameter operation management system, parameter operation management method, and computer system

Abstract

To generate check rules for checking consistency of parameters of a system constructed on a base.SOLUTION: A parameter operation management system is connected to a base system, where a plurality of service provision systems are constructed in the base system, and a plurality of attribute values are assigned to the service provision systems. The parameter operation management system is configured to: generate a plurality of groups based on grouping conditions for generating groups determined by combinations of attribute values; identify, for each of the plurality of groups, a service provision system belonging to the group; select setting parameters; identify, for each of the plurality of groups, regularity established in the selected setting parameters of a plurality of service provision systems belonging to the group; and generate candidate check rules for checking consistency of the selected setting parameters on the basis of the regularity common to the plurality of groups.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a technique for verifying the consistency of parameters of a system built on a substrate. [Background technology]

[0002] In some cases, service providers use the platform to build systems that provide specific services. As the businesses of users of the services become more globalized, the regions in which the services are provided also need to become more globalized. In this case, the system requirements differ depending on the laws and business content of each region, so the system needs to be adjusted for each region. In this case, as many systems are built as there are combinations of users and regions. Note that the basic configuration of the systems (for example, the configuration of the services) is assumed to be the same.

[0003] When building a system, infrastructure administrators need to set system parameters appropriately. In the case of the above-mentioned usage patterns, the number of parameters to be set is enormous, making it difficult to check the consistency of the parameters.

[0004] As a technique for checking the consistency of parameters, for example, the technique described in Patent Document 1 is known. Patent Document 1 discloses "a detection device including an acquisition unit that acquires a declarative model used to construct a target system, test-related information of tests executed on the target system, and execution results of the tests on the target system, and a detection unit that detects errors in parameters included in the declarative model based on information extracted from the test-related information according to the execution results of the tests." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2022-118286 A Summary of the Invention [Problem to be solved by the invention]

[0006] The technology described in Patent Document 1 does not take into consideration the consistency of parameters between systems.

[0007] The present invention provides a system and method for verifying the consistency of parameters within and between systems in a multi-system infrastructure. [Means for solving the problem]

[0008] A representative example of the invention disclosed in the present application is as follows: That is, a parameter operation management system for managing a plurality of setting parameters of a service providing system constructed on a platform system includes a processor, a storage device connected to the processor, and a network interface connected to the processor, and is connected to the platform system, in which a plurality of service providing systems for realizing applications of the same service configuration are constructed, and a plurality of attribute values ​​characterizing the service providing systems are assigned to the service providing systems, the parameter operation management system holds grouping condition information storing grouping conditions for generating groups determined by combinations of the attribute values, generates a plurality of groups based on the grouping conditions, identifies the service providing systems belonging to each of the plurality of groups, selects the target setting parameters, identifies a regularity that holds in the selected setting parameters of the plurality of service providing systems belonging to the group for each of the plurality of groups, and generates a candidate confirmation rule for confirming consistency of the selected setting parameters based on the regularity common to the plurality of groups. Effect of the Invention

[0009] According to the present invention, in a platform on which a plurality of systems are built, it is possible to check the consistency of parameters within a system and between systems. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a system configuration according to a first embodiment. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of the apparatus according to the first embodiment. [Diagram 3] 1 is a diagram illustrating an example of a functional configuration of a parameter management device according to a first embodiment; [Figure 4] FIG. 2 is a diagram illustrating an example of a data structure of system management information according to the first embodiment. [Diagram 5] FIG. 11 is a diagram illustrating an example of a data structure of grouping condition information according to the first embodiment. [Figure 6] FIG. 4 is a diagram illustrating an example of a data structure of threshold information according to the first embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of a data structure of regularity information according to the first embodiment. [Figure 8] FIG. 13 is a diagram illustrating an example of a data structure of candidate confirmation rule information according to the first embodiment. [Figure 9] FIG. 11 is a diagram illustrating an example of a data structure of confirmation rule information according to the first embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of a data structure of exclusion information according to the first embodiment. [Figure 11A] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 11B] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 12] 10 is a flowchart illustrating an example of a recommendation process executed by the parameter management device according to the first embodiment. [Figure 13] FIG. 4 is a diagram illustrating an example of a group generated by the parameter management device according to the first embodiment. [Figure 14]11 is a flowchart illustrating an example of a candidate confirmation rule generation process executed by the parameter operation management device according to the first embodiment. [Figure 15] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 16] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 17] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 18] 11 is a flowchart illustrating an example of a parameter confirmation process executed by the parameter operation management device according to the first embodiment. [Figure 19] FIG. 4 is a diagram illustrating an example of a screen presented by the parameter operation management device of the first embodiment. [Figure 20] FIG. 13 is a diagram illustrating an example of a data structure of grouping condition information according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be interpreted as being limited to the description of the embodiments shown below. The specific configurations may be changed without departing from the concept or spirit of the present invention.

[0012] In the configurations of the embodiments described below, the same parts or parts having similar functions are denoted by the same reference numerals in different drawings, and duplicated explanations may be omitted.

[0013] In order to facilitate understanding of the invention, the position, size, shape, range, connection, etc. of each component shown in the drawings, etc. may not represent the actual position, size, shape, range, connection, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, connection, etc. disclosed in the drawings, etc.

[0014] As used herein, elements referred to in the singular are intended to include the plural unless the context clearly indicates otherwise.

[0015] In this specification, the information group represented in a table format does not necessarily have to be in a table format, and may be recorded in various formats such as a list or a key-value store. EXAMPLES

[0016] Fig. 1 is a diagram illustrating an example of a system configuration according to the first embodiment. Fig. 2 is a diagram illustrating an example of a hardware configuration of an apparatus according to the first embodiment.

[0017] The system of the first embodiment is composed of a board 105, a parameter management device 100, a program management device 101, a deployment device 102, a parameter operation management device 103, and a terminal 104, which are connected via a network 106 such as a WAN (Wide Area Network).

[0018] The platform 105 provides instances for constructing a service providing system 110 that realizes an application. In the service providing system 110, an application is composed of a plurality of services 120. The services 120 are realized using instances such as containers. In this embodiment, the configuration of the services 120 in each service providing system 110 is assumed to be common. However, the processing contents executed by the services 120, the number of instances that realize the services 120, etc. may be different.

[0019] The terminal 104 is a terminal operated by a platform administrator. The parameter management device 100 manages parameters of the service providing system 110. The parameter management device 100 is, for example, a database, Github, etc. The program management device 101 manages a program that realizes the service 120. The deployment device 102 deploys an instance that realizes the service 120. Specifically, the deployment device 102 obtains a program from the program management device 101, obtains parameters related to the service 120 to be deployed from the parameter management device 100, and deploys the service 120 to the platform 105. The parameters also include parameters that are adjusted according to the characteristics of the service providing system 110, etc.

[0020] The parameter operation management device 103 generates confirmation rules for confirming the consistency of parameters of the service providing system 110, and confirms the consistency of the parameters of the service providing system 110 based on the confirmation rules adopted by the platform manager.

[0021] The parameter management device 100, the program management device 101, the deployment device 102, and the parameter operation management device 103 are realized, for example, by using a computer 200 as shown in Fig. 2. The computer 200 has a processor 201, a main memory device 202, an auxiliary memory device 203, an input device 204, an output device 205, and a communication device 206. The hardware elements are connected to each other via a bus.

[0022] The processor 201 executes a program stored in the main memory device 202. The processor 201 executes processing according to the program, thereby operating as a functional unit (module) that realizes a specific function. In the following explanation, when a process is explained with a functional unit as the subject, it indicates that the processor 201 is executing a program that realizes the functional unit.

[0023] Note that a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) may be used instead of the processor 201. Also, the processor 201 may be used in combination with an FPGA or an ASIC.

[0024] The main memory 202 is a high-speed memory device such as a dynamic random access memory (DRAM), and stores programs executed by the processor 201 and data used when the programs are executed. The main memory 202 is also used as a work area. The computer 200 may also have a read only memory (ROM) that stores a BIOS and the like.

[0025] The auxiliary storage device 203 is a large-capacity storage device such as a hard disk drive (HDD) or a solid state drive (SSD), and stores data permanently. The programs and data stored in the main storage device 202 may be stored in the auxiliary storage device 203. In this case, the processor 201 reads out the programs and data from the auxiliary storage device 203 and loads them into the main storage device 202.

[0026] The input device 204 is a keyboard, mouse, touch panel, etc., and receives input from a user. The output device 205 is a display, etc., and outputs various information to the user. The communication device 206 communicates with other devices via a network according to a predetermined protocol.

[0027] Each device may be realized using a virtualization technology such as a virtual machine and a container. The functions of each device may be realized using a computer system composed of multiple computers 200. The functions of a certain device may be included in another device.

[0028] FIG. 3 is a diagram illustrating an example of a functional configuration of the parameter operation management device 103 according to the first embodiment.

[0029] The parameter operation management device 103 has a user interface unit 300, a group generation unit 301, a parameter acquisition unit 302, a confirmation rule generation unit 303, and a parameter confirmation unit 304. The parameter operation management device 103 also holds system management information 310, grouping condition information 311, threshold information 312, regularity information 313, candidate confirmation rule information 314, confirmation rule information 315, and exclusion information 316.

[0030] The system management information 310 is information for managing attributes, etc. of the service providing system 110. The grouping condition information 311 is information for managing grouping conditions for generating groups of the service providing system 110. The threshold information 312 is information for managing thresholds for determining the regularity, etc. of parameters. The regularity information 313 is information for managing the regularity of parameters.

[0031] Candidate confirmation rule information 314 is information for managing candidates for parameter confirmation rules (candidate confirmation rules). Confirmation rule information 315 is information for managing confirmation rules. Exclusion information 316 is information for managing exclusion rules of the service providing systems 110 to be excluded from confirmation targets.

[0032] The user interface unit 300 provides various user interfaces. The group generation unit 301 generates groups of the service providing systems 110 based on grouping condition information 311. The parameter acquisition unit 302 acquires parameters of the service providing systems 110. The confirmation rule generation unit 303 identifies the regularity of the parameters, and generates and outputs candidate confirmation rules for the parameters. The parameter confirmation unit 304 confirms the consistency of the parameters of the service providing systems 110 based on the confirmation rules.

[0033] Regarding the functional units of the parameter operation management device 103, multiple functional units may be integrated into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0034] FIG. 4 is a diagram illustrating an example of the data structure of the system management information 310 according to the first embodiment.

[0035] The system management information 310 stores entries including a system ID 401 and attributes 402. One entry exists for one service providing system 110. The fields included in the entry are not limited to those described above. For example, the entry may include a field for storing a database or a URL in which parameters of the service providing system 110 are stored, a field for storing authentication information required when acquiring parameters, and the like.

[0036] The system ID 401 is a field that stores the ID of the service providing system 110. Instead of the ID, a name or the like may be stored. The attribute 402 is a field that stores the value of an attribute (attribute value) that characterizes the service providing system 110. The attribute 402 includes multiple columns for each type of attribute. In this embodiment, it is assumed that there are three types of attributes: "purpose", "region", and "user". Note that a user represents a user of the platform 105.

[0037] 4 are merely examples and are not intended to be limiting. For example, vendor, security requirements, service level, industry, etc. may be treated as attributes.

[0038] FIG. 5 is a diagram illustrating an example of a data structure of the grouping condition information 311 according to the first embodiment.

[0039] The grouping condition information 311 stores entries including a condition ID 501 and an attribute 502. One entry exists for one grouping condition.

[0040] A condition ID 501 is a field that stores the ID of a grouping condition. An attribute 502 is a field that stores a condition (grouping condition) of a combination of attribute values. "A" indicates that an attribute value is not specified, and "S" indicates that an attribute value is specified.

[0041] FIG. 6 is a diagram illustrating an example of a data structure of the threshold information 312 according to the first embodiment.

[0042] The threshold information 312 stores entries including a threshold name 601 and a threshold 602. There is one entry for one threshold.

[0043] The threshold name 601 is a field for storing the name of a threshold. The threshold 602 is a field for storing a specific numerical value. In the threshold information 312 of the first embodiment, a regularity threshold for determining whether or not a regularity is established and a recommendation threshold for determining whether or not to recommend a candidate confirmation rule are registered.

[0044] FIG. 7 is a diagram illustrating an example of the data structure of the regularity information 313 according to the first embodiment.

[0045] The regularity information 313 stores entries including a regularity ID 701 and regularity details 702. One entry exists for one regularity. Note that the fields included in the entry are not limited to those described above.

[0046] A regularity ID 701 is a field for storing the ID of a regularity. A regularity detail 702 is a field for storing specific details of the regularity.

[0047] FIG. 8 is a diagram illustrating an example of the data structure of the candidate confirmation rule information 314 according to the first embodiment.

[0048] The candidate confirmation rule information 314 stores entries including a candidate confirmation rule ID 801, a condition ID 802, parameter information 803, a regularity ID 804, and an alert 805. One entry exists for one confirmation rule candidate. Note that the fields included in the entry are not limited to those described above.

[0049] Candidate confirmation rule ID 801 is a field that stores the ID of a candidate confirmation rule. Condition ID 802 is a field that stores the ID of a grouping condition used when generating a candidate confirmation rule. Parameter information 803 is a field that stores information about the parameter to be confirmed. The parameter information 803 stores the name of the parameter and the name of the service 120 that includes the parameter, etc. Regularity ID 804 is a field that stores the ID of a regularity that holds for the parameter. Alert 805 is a field that stores information indicating a service providing system 110 in which the regularity does not hold.

[0050] FIG. 9 is a diagram illustrating an example of the data structure of the confirmation rule information 315 according to the first embodiment.

[0051] The confirmation rule information 315 stores entries including a confirmation rule ID 901, a condition ID 902, parameter information 903, and a regularity ID 904. One entry exists for one confirmation rule. Note that the fields included in the entry are not limited to those described above.

[0052] A confirmation rule ID 901 is a field that stores the ID of a confirmation rule. A condition ID 902, parameter information 903, and regularity ID 904 are the same fields as the condition ID 802, parameter information 803, and regularity ID 804.

[0053] FIG. 10 is a diagram illustrating an example of the data structure of the exclusion information 316 according to the first embodiment.

[0054] The exclusion information 316 stores entries including a condition ID 1001 and an attribute 1002. One entry exists for one exclusion condition. The condition ID 1001 is a field that stores the ID of a grouping condition to which the exclusion condition applies. The attribute 1002 is a field that stores a condition (exclusion condition) of a combination of attribute values ​​of the service providing system 110 to be excluded. When an attribute value is stored in the attribute type, a combination (group) of attribute values ​​including that attribute value is not generated.

[0055] In the first embodiment, the description will be given assuming that the exclusion information 316 is not set. The process when the exclusion information 316 is set will be described in the second embodiment.

[0056] 11A and 11B are diagrams showing examples of the screens presented by the parameter management device 103 of the first embodiment.

[0057] The user interface unit 300 presents a screen 1100 for setting the system management information 310. The screen 1100 includes an input field 1102, an operation button 1103, a row 1101 including an operation button 1104, an operation button 1105, an operation button 1106, and an operation button 1107.

[0058] The operation button 1105 is an operation button for adding a row 1101. The operation button 1104 is an operation button for deleting the row 1101. The input field 1102 is a field for inputting the ID of the service providing system 110.

[0059] An operation button 1103 is an operation button for editing the attributes of the service providing system 110. An operation button 1106 is an operation button for registering the contents set via the screen 1100. An operation button 1107 is an operation button for canceling the registration of information via the screen 1100.

[0060] When the operation button 1103 is operated, the user interface unit 300 displays a screen 1110 .

[0061] The screen 1110 includes input fields 1111 , 1112 , and 1113 , and operation buttons 1114 and 1115 .

[0062] The input field 1111 is a field for inputting a purpose. The input field 1112 is a field for inputting a region. The input field 1113 is a field for inputting a user. The operation button 1114 is a button for registering attribute settings.

[0063] The user interface unit 300 may present a screen for setting the grouping condition information 311, the threshold information 312, and the exclusion information 316.

[0064] Fig. 12 is a flowchart illustrating an example of a recommendation process executed by the parameter operation management device 103 according to the first embodiment. Fig. 13 is a diagram illustrating an example of a group generated by the parameter operation management device 103 according to the first embodiment.

[0065] The parameter operation management device 103 executes the recommendation process described below when an execution instruction is received or periodically.

[0066] The parameter management device 103 acquires parameters of all the service providing systems 110 from the parameter management device 100 (step S1201).

[0067] The parameter operation management device 103 refers to the grouping condition information 311 and selects one grouping condition (step S1202).

[0068] The parameter operation management device 103 generates groups based on the grouping conditions and the system management information 310 (step S1203).

[0069] Specifically, the parameter management device 103 acquires the attribute value of each attribute, and generates a group by combining the attribute values ​​of each attribute based on the grouping conditions.

[0070] Here, a method of generating groups will be described with reference to Fig. 13. Here, an example will be described in which a grouping condition with a condition ID 501 of "Con5" is selected. In the selected grouping condition, a group is generated by specifying a purpose and a region. In the system management information 310 shown in Fig. 4, the attribute "purpose" has three attribute values, namely, "development," "staging," and "commercial," and the attribute "region" has two attribute values, namely, "Japan" and "Europe." Therefore, the parameter operation management device 103 generates six groups.

[0071] The parameter operation management device 103 identifies the service providing systems 110 belonging to each group (step S1204). For example, the service providing systems 110 belonging to each group are identified as shown in FIG.

[0072] The parameter operation management device 103 executes a candidate confirmation rule generation process (step S1205). The candidate confirmation rule generation process will be described in detail later.

[0073] The parameter management device 103 judges whether or not the processing has been completed for all grouping conditions (step S1206).

[0074] If the processing has not been completed for all grouping conditions, the parameter management device 103 returns to step S1202 and executes the same processing.

[0075] When the processing is completed for all grouping conditions, the parameter management device 103 displays the results (step S1207).

[0076] FIG. 14 is a flowchart illustrating an example of a candidate confirmation rule generation process executed by the parameter operation management device 103 according to the first embodiment.

[0077] The parameter operation management device 103 refers to the regularity information 313 and selects one regularity (step S1401).

[0078] The parameter management device 103 selects a parameter for which regularity is to be confirmed (step S1402). For example, a method of selecting a parameter for each service 120 is considered. In the following description, the selected parameter is referred to as a target parameter.

[0079] The parameter management device 103 selects one group from the groups generated in step S1203 (step S1403).

[0080] The parameter management device 103 determines whether the selected regularity holds for the target parameters of the service providing systems 110 belonging to the selected group (step S1404). For example, if the ratio of the service providing systems 110 for which the regularity holds is greater than the regularity threshold, the parameter management device 103 determines that the selected regularity holds. Note that if the number of service providing systems 110 belonging to the group is 1, the process of step S1404 is skipped.

[0081] If no regularity is established, the parameter management device 103 proceeds to step S1406.

[0082] If the regularity is established, the parameter management device 103 sets an established flag for the group (step S1405).

[0083] The parameter management device 103 judges whether the processing has been completed for all groups (step S1406).

[0084] If the processing has not been completed for all groups, the parameter management device 103 returns to step S1403 and executes the same processing.

[0085] When the process is completed for all groups, the parameter management device 103 determines whether or not the selected regularity needs to be recommended as a candidate confirmation rule (step S1407). For example, when the ratio of groups in which the regularity holds is greater than a recommendation threshold, the parameter management device 103 determines that the regularity needs to be recommended as a candidate confirmation rule.

[0086] If the regularity does not need to be recommended as a candidate confirmation rule, the parameter management device 103 proceeds to step S1410.

[0087] If the regularity needs to be recommended as a candidate confirmation rule, the parameter operation management device 103 identifies a group or a service providing system 110 that does not satisfy the regularity (step S1408). The parameter operation management device 103 stores the identified group or service providing system 110 as alert information.

[0088] The parameter operation management device 103 registers the entry in the candidate confirmation rule information 314 (step S1409). After that, the parameter operation management device 103 proceeds to step S1410.

[0089] Specifically, the parameter management device 103 adds an entry to the candidate confirmation rule information 314, and sets an ID to the candidate confirmation rule ID 801 of the added entry. The parameter management device 103 sets the ID of the grouping condition selected in step S1202 to the condition ID 802 of the added entry, sets information of the target parameter to the parameter information 803, and sets the ID of the regularity selected in step S1401 to the regularity ID 804. The parameter management device 103 also sets the alert information stored in step S1408 to the alert 805 of the added entry.

[0090] In step S1410, the parameter operation management device 103 determines whether or not the processing has been completed for all parameters (step S1410).

[0091] If the processing has not been completed for all parameters, the parameter management device 103 returns to step S1402 and executes the same processing.

[0092] When the processing has been completed for all parameters, the parameter operation management device 103 judges whether the processing has been completed for all regularities (step S1411).

[0093] If the processing has not been completed for all the regularities, the parameter management device 103 returns to step S1401 and executes the same processing.

[0094] When the processing has been completed for all the regularities, the parameter operation management device 103 ends the candidate confirmation rule generation processing.

[0095] After completing the recommendation process, the parameter operation management device 103 displays various screens. The screens displayed by the parameter operation management device 103 will now be described.

[0096] 15, 16, and 17 are diagrams showing examples of screens presented by the parameter operation management device 103 according to the first embodiment.

[0097] The parameter operation management device 103 presents a screen 1500 for confirming and editing a candidate confirmation rule, as shown in FIG 15. The screen 1500 includes a table 1501 and operation buttons 1502.

[0098] Table 1501 is a table that displays candidate confirmation rule information 314. A selection field in table 1501 includes check boxes for selecting candidate confirmation rules to be registered as confirmation rules. An edit field in table 1501 includes operation buttons for editing the candidate confirmation rules. When an operation button in the edit field is operated, a screen (not shown) for editing grouping conditions, parameter information, regularities, alerts, etc. is displayed.

[0099] The operation button 1502 is an operation button for registering a candidate confirmation rule selected in the selection field as a confirmation rule. When the operation button 1502 is operated, information about the selected candidate confirmation rule is registered in the confirmation rule information 315. For example, when one candidate confirmation rule is selected, the parameter operation management device 103 adds an entry to the confirmation rule information 315 and sets an ID to the confirmation rule ID 901 of the added entry. The confirmation rule information 315 sets the condition ID 902, parameter information 803, and regularity ID 804 of the entry corresponding to the selected candidate confirmation rule to the condition ID 902, parameter information 903, and regularity ID 904 of the added entry.

[0100] 16, the parameter operation management device 103 presents a screen 1600 for confirming and editing the confirmation rules. The screen 1600 includes a table 1601 and operation buttons 1602.

[0101] Table 1601 is a table that displays the confirmation rule information 315. The selection column of table 1601 includes check boxes for selecting the confirmation rule to be deleted. The edit column of table 1601 includes an operation button for editing the confirmation rule. When the operation button is operated, a screen (not shown) for editing the grouping condition, parameter information, regularity, alerts, etc. is displayed.

[0102] The operation button 1602 is an operation button for deleting a confirmation rule selected in the selection field. When the operation button 1602 is operated, the parameter operation management device 103 deletes the selected confirmation rule from the confirmation rule information 315.

[0103] The parameter operation management device 103 may compile the registration status of the candidate confirmation rules and confirmation rules for the parameters based on the candidate confirmation rule information 314 and the confirmation rule information 315, and display a screen 1700 as shown in FIG.

[0104] The screen 1700 includes a table 1701, a pie chart 1702, and a table 1703. The table 1701 is a table that displays the number of parameter confirmation rules, the latest candidate confirmation rules, and the past candidate confirmation rules. To display the table 1701, a timestamp field may be provided in the entry of the candidate confirmation rule information 314. Candidate confirmation rules within a predetermined period from the current time in the time series may be counted as the latest candidate confirmation rules (recommended candidate confirmation rules), and candidate confirmation rules for other periods may be counted as past candidate confirmation rules (unapproved candidate confirmation rules).

[0105] Pie chart 1702 is a graph showing the percentage of parameters for which confirmation rules or candidate confirmation rules are set.

[0106] Table 1703 shows the change over time in the number of confirmation rules and candidate confirmation rules.

[0107] The platform administrator can check parameters for which no confirmation rule or candidate confirmation rule exists by referring to table 1701 and pie chart 1702. The platform administrator may manually set the confirmation rule for the parameter. The platform administrator can also check the convergence state of the confirmation rule by referring to table 1703. For example, when the number of candidate confirmation rules being recommended is decreasing, it can be determined that the setting of the confirmation rule is complete.

[0108] Fig. 18 is a flowchart illustrating an example of a parameter confirmation process executed by the parameter operation management device 103 according to the first embodiment. Fig. 19 is a diagram illustrating an example of a screen presented by the parameter operation management device 103 according to the first embodiment.

[0109] The parameter operation management device 103 executes the parameter confirmation process described below when an execution instruction is received or periodically.

[0110] The parameter operation management device 103 refers to the confirmation rule information 315 and selects one confirmation rule (step S1801).

[0111] The parameter operation management device 103 checks the parameters based on the check rules (step S1802). Specifically, the following process is executed.

[0112] (S1802-1) The parameter management device 103 generates groups based on grouping conditions included in the confirmation rules. The process of S1802-1 is the same as the process of step S1203.

[0113] (S1802-2) The parameter operation management device 103 identifies the service providing systems 110 that belong to each group. The process of S1802-2 is the same as the process of step S1204.

[0114] (S1802-3) The parameter management device 103 selects a group and acquires, from the parameter management device 100, parameters to be confirmed of the service providing systems 110 that belong to the group.

[0115] (S1802-4) The parameter management device 103 determines whether the parameter satisfies the regularity of the confirmation rules.

[0116] (S1802-5) The parameter operation management device 103 judges whether or not the processing has been completed for all the groups. If the processing has not been completed for all the groups, the parameter operation management device 103 returns to S1802-3.

[0117] (S1802-6) If the processing has been completed for all groups, the parameter management device 103 ends the processing of step S1802.

[0118] The parameter operation management device 103 judges whether or not the processing has been completed for all the confirmation rules (step S1803).

[0119] If the processing has not been completed for all the confirmation rules, the parameter management device 103 returns to step S1801 and executes the same processing.

[0120] When the processing is completed for all the confirmation rules, the parameter operation management device 103 displays the result (step S1804). The parameter operation management device 103 presents, for example, a screen 1900 as shown in FIG 19. The screen 1900 includes a table 1901 and operation buttons 1902.

[0121] Table 1901 is a table that displays the confirmation results. Groups and service providing systems 110 that do not satisfy the regularity for each confirmation rule are displayed as the confirmation results. Operation button 1902 is an operation button for ending the display of screen 1900.

[0122] The parameter operation management device 103 does not need to hold the system management information 310. In this case, it is sufficient to obtain attribute values ​​from a file or the like in which the parameters are set.

[0123] According to the first embodiment, it is possible to automatically set a confirmation rule that defines a regularity of confirmation including a confirmation range (group) and confirmation contents, which makes it easy to manage parameters and enables accurate detection of parameter inconsistencies. EXAMPLES

[0124] The second embodiment differs from the first embodiment in that exclusion information 316 is set. The second embodiment will be described below, focusing on the differences from the first embodiment.

[0125] The system configuration of the second embodiment is the same as that of the first embodiment. The software configuration of the parameter management device 103 of the second embodiment is the same as that of the first embodiment.

[0126] The flow of the recommendation process in the second embodiment is the same as that in the first embodiment. However, some of the process contents are different from those in the first embodiment. Specifically, the process in step S1203 is different.

[0127] When a grouping condition with a condition ID of "Con5" is selected and the attribute "Purpose" of the attribute 1002 is set to "Development", the "Development" attribute of the "Purpose" is not specified as an attribute value. Therefore, four groups are generated. The process of S1802-1 is the same.

[0128] The parameter confirmation process in the second embodiment is the same as that in the first embodiment.

[0129] According to the second embodiment, it is possible to narrow down the service providing systems 110 to be checked, thereby enabling efficient setting of check rules. EXAMPLES

[0130] The third embodiment differs from the first embodiment in that the grouping conditions and the regularity are managed in association with each other. The third embodiment will be described below, focusing on the differences from the first embodiment.

[0131] The system configuration of the embodiment 3 is the same as that of the embodiment 1. The software configuration of the parameter management device 103 of the embodiment 3 is the same as that of the embodiment 1. However, in the embodiment 3, the data structure of the grouping condition information 311 is partially different.

[0132] FIG. 20 is a diagram illustrating an example of a data structure of the grouping condition information 311 according to the third embodiment.

[0133] The entry of the grouping condition information 311 newly includes a regularity ID 503. The regularity ID 503 is a field for storing the ID of the regularity to which the grouping condition is applied.

[0134] The recommendation process of the third embodiment is the same as that of the first embodiment. However, the process contents of the candidate confirmation rule generation process are partially different in the third embodiment. Specifically, the process of step S1401 is different.

[0135] In step S1401, a regularity is selected from among the regularities associated with the selected grouping condition.

[0136] According to the third embodiment, the confirmation range can be set according to the confirmation contents, which makes it possible to generate confirmation rules efficiently.

[0137] By combining with the second embodiment, the combination of the confirmation range and confirmation contents can be controlled in more detail.

[0138] The present invention is not limited to the above-mentioned embodiment, but includes various modified examples. For example, the above-mentioned embodiment describes the configuration in detail to easily explain the present invention, and the present invention is not necessarily limited to the configuration including all the described configurations. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0139] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that realizes the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, etc.

[0140] Furthermore, the program code for realizing the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, Java (registered trademark), etc.

[0141] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed over a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read out and execute the program code stored in the storage means or storage medium.

[0142] In the above-mentioned embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all the control lines and information lines are shown in the product. All the components may be connected to each other. [Explanation of symbols]

[0143] 100 Parameter management device 101 Program Management Device 102 Deploy Device 103 Parameter operation management device 104 Terminals 105 Foundation 106 Network 110 Service Delivery System 120 Services 200 calculator 201 Processor 202 Main storage 203 Auxiliary storage device 204 Input Device 205 Output Device 206 Communication Equipment 300 User Interface Section 301 Group Generation Unit 302 Parameter Acquisition Unit 303 Confirmation rule generation unit 304 Parameter Check Section 310 System Management Information 311 Grouping Condition Information 312 Threshold Information 313 Regularity information 314 Candidate Confirmation Rule Information 315 Check rule information 316 Exclusion Information 1100, 1110, 1500, 1600, 1700, 1900 screen

Claims

1. A parameter operation management system for managing a plurality of setting parameters of a service providing system built on a platform system, a processor, a storage device connected to the processor, and a network interface connected to the processor; Connect to the infrastructure system; In the infrastructure system, a plurality of the service providing systems for realizing applications having the same service configuration are constructed, A plurality of attribute values ​​characterizing the service providing system are assigned to the service providing system; The parameter operation management system includes: Holding grouping condition information that stores grouping conditions for generating groups determined by combinations of the attribute values; generating a plurality of the groups based on the grouping conditions; Identifying the service providing system belonging to each of the plurality of groups; Selecting the configuration parameter of interest; Identifying, for each of the plurality of groups, a regularity that holds in the selected setting parameters of the plurality of service providing systems that belong to the group; A parameter operation management system, comprising: generating a candidate confirmation rule for confirming the consistency of the selected setting parameters based on the regularity common to a plurality of the groups.

2. The parameter management system according to claim 1, generating a combination of the grouping condition, the selected setting parameters, and the regularity common to a plurality of the groups as the candidate confirmation rule; presenting a user interface for receiving from a user whether or not the candidate confirmation rule is applicable; a parameter operation management system for storing the candidate confirmation rule as a confirmation rule when application of the candidate confirmation rule is permitted by the user;

3. The parameter management system according to claim 2, generating a plurality of the groups based on the grouping conditions in the confirmation rules; Identifying the service providing system belonging to each of the plurality of groups; A parameter operation management system characterized by determining, for each of a plurality of groups, whether the setting parameters in the confirmation rules of the plurality of service providing systems belonging to the group satisfy the regularity in the confirmation rules.

4. The parameter management system according to claim 1, retaining exclusion information that specifies attribute values ​​that are not to be considered in the grouping conditions; A parameter management system comprising: a plurality of groups generated using the grouping conditions so as not to include attribute values ​​specified in the exclusion information.

5. The parameter management system according to claim 1, A parameter operation management system, characterized in that the grouping conditions are managed in correspondence with the regularity to be confirmed.

6. The parameter management system according to claim 1, The service providing system is characterized in that attribute values ​​representing purpose, region, and infrastructure user are assigned to the service providing system.

7. A parameter operation management method executed by a parameter operation management system that manages a plurality of setting parameters of a service providing system built on a platform system, comprising: The parameter operation management system includes: a processor, a storage device connected to the processor, and a network interface connected to the processor; Connect to the infrastructure system; In the infrastructure system, a plurality of the service providing systems for realizing applications having the same service configuration are constructed, A plurality of attribute values ​​characterizing the service providing system are assigned to the service providing system; The parameter operation management system holds grouping condition information that stores grouping conditions for generating groups determined by combinations of the attribute values, The parameter operation management method includes: A first step in which the parameter management system generates a plurality of the groups based on the grouping conditions; a second step in which the parameter operation management system identifies, for each of the groups, the service providing systems that belong to the group; A third step in which the parameter management system selects the target setting parameter; a fourth step in which the parameter operation management system identifies, for each of the plurality of groups, a regularity that is established in the selected setting parameters of the plurality of service providing systems that belong to the group; A fifth step in which the parameter management system generates a candidate confirmation rule for confirming the consistency of the selected configuration parameters based on the regularity common to the plurality of groups; A parameter operation management method comprising:

8. 8. The parameter operation management method according to claim 7, The fifth step includes: The parameter management system generates, as the candidate confirmation rule, a set of the grouping condition, the selected setting parameters, and the regularity common to a plurality of the groups; The parameter management system presents a user interface for receiving a user's decision on whether or not to apply the candidate confirmation rule; A parameter operation management method comprising: a step in which the parameter operation management system stores the candidate confirmation rule as a confirmation rule when application of the candidate confirmation rule is permitted by the user.

9. 9. The parameter operation management method according to claim 8, The parameter management system generates a plurality of the groups based on the grouping conditions in the confirmation rule; The parameter operation management system specifies, for each of the groups, the service providing systems that belong to the group; A parameter operation management method characterized in that it includes a step in which the parameter operation management system determines, for each of the multiple groups, whether the setting parameters in the confirmation rules of the multiple service providing systems belonging to the group satisfy the regularity in the confirmation rules.

10. 8. The parameter operation management method according to claim 7, The parameter management system holds exclusion information that specifies attribute values ​​that are not to be considered in the grouping conditions, A parameter management method characterized in that the first step includes a step in which the parameter management system generates a plurality of the groups using the grouping conditions so as not to include attribute values ​​specified in the exclusion information.

11. 8. The parameter operation management method according to claim 7, A parameter operation management method, characterized in that the grouping conditions are managed in correspondence with the regularity to be confirmed.

12. 8. The parameter operation management method according to claim 7, A parameter operation management method, characterized in that the service providing system is assigned attribute values ​​representing purpose, region, and infrastructure user.

13. A computer system including a platform system for constructing a service providing system, a parameter management device for managing a plurality of setting parameters of the service providing system, and a parameter operation management device for managing consistency of the setting parameters, In the infrastructure system, a plurality of the service providing systems for realizing applications having the same service configuration are constructed, A plurality of attribute values ​​characterizing the service providing system are assigned to the service providing system; The parameter operation management device includes: Holding grouping condition information that stores grouping conditions for generating groups determined by combinations of the attribute values; generating a plurality of the groups based on the grouping conditions; Identifying the service providing system belonging to each of the plurality of groups; Selecting the configuration parameter of interest; acquiring the selected setting parameters of the plurality of service providing systems from the parameter management device; Identifying, for each of the plurality of groups, a regularity that holds in the selected setting parameters of the plurality of service providing systems that belong to the group; A computer system comprising: a computer that generates a candidate confirmation rule for confirming consistency of the selected setting parameters based on the regularity common to a plurality of the groups.

14. 14. The computer system of claim 13, The parameter operation management device includes: generating a combination of the grouping condition, the selected setting parameters, and the regularity common to a plurality of the groups as the candidate confirmation rule; presenting a user interface for receiving from a user whether or not the candidate confirmation rule is applicable; a candidate confirmation rule that is stored as a confirmation rule when application of the candidate confirmation rule is permitted by the user;

15. 15. The computer system of claim 14, The parameter operation management device includes: generating a plurality of the groups based on the grouping conditions in the confirmation rules; Identifying the service providing system belonging to each of the plurality of groups; A computer system comprising: a computer that determines, for each of a plurality of groups, whether or not the setting parameters in the confirmation rules of the plurality of service providing systems belonging to the group satisfy the regularity in the confirmation rules.

Images