JP6588961B2 - Computer system and recommended parameter value extraction method - Google Patents

Description

  The present invention relates to a computer system and a recommended parameter value extraction method, and is suitable for application to setting of parameter values used for a predetermined service, for example.

  With the increase in scale and complexity of computer systems, system operation management costs are increasing. Under such circumstances, operation management automation technology has been developed.

  In recent years, an operation automation system has been disclosed in which a user himself / herself defines processing steps and can easily create a unique service by assembling a workflow that connects the processing steps (see Patent Document 1). According to such an operation automation system, for example, a service for creating a new volume or migrating an existing volume can be created.

International Publication No. 2016/084255

  However, in the technique described in Patent Document 1, for example, when a volume is newly created in a predetermined pool and then the volume is migrated by detecting that the pool performance of the predetermined pool deteriorates, the volume When various operations related to are performed, past operations are executed based on what requirements (disk type, RAID level, etc.), and it is not possible to determine which requirements should be taken over in this migration .

  In addition, parameters are being abstracted, such as by specifying a range, and the user's intention cannot be continued, so it is difficult to set requirements that follow past requirements (parameter values with a consistent policy). There is a problem that has become.

  The present invention has been made in consideration of the above points, and intends to propose a computer system capable of presenting parameter values in a consistent policy.

  In order to solve such a problem, in the present invention, a computer system capable of receiving input of identification information capable of identifying a processing target related to a predetermined service and outputting a recommended value of a parameter used for the predetermined service, Parameter values used in the same meaning are extracted as recommended values from the task log indicating the execution contents of the predetermined service based on the resource-related information of the service provided in advance in which the attributes and the connection between the resources are defined A recommended value extracting unit and an output unit for outputting the recommended value extracted by the recommended value extracting unit are provided.

  Further, in the present invention, there is provided a recommended parameter value extraction method in a computer system that accepts input of identification information that can identify a processing target related to a predetermined service, and that can output a recommended value of a parameter used for the predetermined service, Parameters used by the recommended value extraction unit in the same meaning from the task log indicating the execution contents of the predetermined service based on the resource-related information of the service provided in advance in which the attribute of the resource and the connection between the resources are defined A first step of extracting a value as a recommended value and a second step in which the output unit outputs the recommended value extracted in the first step are provided.

  According to the above configuration, parameter values used in the same meaning from the task log are output as recommended values, so that parameter values can be set with a consistent policy.

  According to the present invention, it is possible to appropriately set parameter values used for services.

It is a figure which shows an example of a structure of the computer system by 1st Embodiment. It is a figure which shows an example of a structure of the management server by 1st Embodiment. It is a figure which shows an example of a structure of the management client by 1st Embodiment. It is a figure showing an example of operation of an operation automation system by a 1st embodiment. It is a figure which shows an example of the structure of the service by 1st Embodiment. It is a figure which shows an example of the component management table by 1st Embodiment. It is a figure which shows an example of the component property management table by 1st Embodiment. It is a figure which shows an example of the service management table by 1st Embodiment. It is a figure which shows an example of the service property management table by 1st Embodiment. It is a figure which shows an example of the task management table by 1st Embodiment. It is a figure which shows an example of the task log by 1st Embodiment. It is a figure which shows an example of the recommended value management table by 1st Embodiment. It is a figure which shows an example of the change history management table by 1st Embodiment. It is a figure which shows an example of the resource related figure of the component by 1st Embodiment. It is a figure which shows an example of the property mapping definition file by 1st Embodiment. It is an image figure of the property mapping by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the service resource related figure production | generation process by 1st Embodiment. It is an image figure of the resource related figure of the service by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the recommended value extraction output process by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the input parameter content determination process by 1st Embodiment. It is an image figure for pinpointing the parameter concerning the recommendation value by a 1st embodiment. It is a figure which shows an example of the process sequence which concerns on the related past task search and recommended value extraction process by 1st Embodiment. It is an image figure which concerns on the task search process by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the process (O, T) by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the process (O, T) by 1st Embodiment. It is a figure which shows an example of the process sequence which concerns on the recommended value extraction process by 1st Embodiment. It is an image figure which concerns on determination whether the object "O" by 1st Embodiment exists. It is an image figure which concerns on determination whether it is a related object by 1st Embodiment. It is a figure which shows an example of the alias management table by 1st Embodiment. It is a figure which shows an example of the service list screen by 1st Embodiment. It is a figure which shows an example of the service execution screen by 1st Embodiment. It is a figure which shows an example of the service execution screen by 1st Embodiment.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(1) Configuration of Computer System In FIG. 1, 1 indicates a computer system according to the first embodiment as a whole. The computer system 1 includes an operation automation system 10, a service execution system 20, a host computer 30, and a storage device 40. The operation automation system 10, the service execution system 20, the host computer 30, and the storage device 40 are connected to each other via a network 50 so that they can communicate with each other. In the computer system 1, parameter values used for services provided by the operation automation system 10 are recommended. Details will be described below.

  The operation automation system 10 is a system that supports automation of system operation. The operation automation system 10 includes a management server 100 and a management client 200 that is communicably connected to the management server 100. Information is output by the management client 200 based on the display information transmitted from the management server 100 to the management client 200.

  In such an operation automation system 10, for example, the user himself / herself can define processing steps (components), and can easily create a unique service by assembling a workflow that connects the processing steps. Further, for example, in the operation automation system 10, when executing a service created by a user, a parameter value used in the same meaning is extracted from an operation history related to the service and presented as a recommended parameter value (recommended value). be able to.

  More specifically, the management server 100 includes a service editing unit 101, a service holding unit 102, a service resource related diagram generation unit 103, a recommended value extraction unit 104, and a command transmission unit 105.

  For example, in response to a request from the management client 200 (user), the service editing unit 101 generates information related to a screen (service creation screen) for creating and editing a service template and transmits the information to the management client 200 To do.

  For example, the service holding unit 102 receives information from the management client 200 via a service creation screen, creates a service template based on the received information (input information), and generates and holds a service.

  The service can be arbitrarily added by the user, but as the service, a service for creating a logical volume in the storage device 40, a service for creating a secondary volume in the storage device 40, a service for moving a virtual machine on the hypervisor, a virtual machine For example, a service for changing the settings of the above application.

  The service resource related diagram generation unit 103 generates, for example, a resource related diagram of a service in which resource related diagrams (information indicating mapping relations between properties and resources) defined by the user at the time of component creation are connected. .

  For example, the recommended value extraction unit 104 extracts and presents (outputs) the parameter values used in the same meaning from the operation history related to the service that the user is trying to execute based on the resource relation diagram of the service, Information related to a screen (service execution screen) for executing the service is generated and transmitted to the management client 200.

  For example, the command transmission unit 105 receives a command to execute a service from the management client 200 via the service execution screen, and transmits the received command to the service execution system 20.

  The management client 200 includes a service editing screen display unit 201 and a service execution screen display unit 202.

  For example, the service editing screen display unit 201 receives information on the service editing screen from the management server 100 and displays the service editing screen.

  For example, the service execution screen display unit 202 receives information on the service execution screen from the management server 100 and displays the service execution screen.

  The service execution system 20 executes a service in accordance with a command from the operation automation system 10.

  The service execution system 20 includes, for example, a management computer 21 and a monitoring information display device 22.

  The management computer 21 is a computer that issues an instruction for changing the configuration of a storage system or the like, an instruction for changing the configuration of a hypervisor, a virtual machine, or the like. For example, the management computer 21 gives a predetermined instruction to the storage apparatus 40 in response to a command from the operation automation system 10. In response to the instruction, the storage apparatus 40 changes the storage configuration.

  The monitoring information display device 22 is a device that is communicably connected to the management computer 21 and displays information related to the storage system, hypervisor, etc. managed by the management computer 21. The monitoring information display device 22 displays, for example, various performance information and configuration information of the storage device 40. Note that the monitoring information display device 22 and the management computer 21 may be configured as a single computer.

  The host computer 30 includes an I / F (communication interface device), a storage resource, and a processor (not shown). The storage apparatus 40 includes a physical storage device and a controller (not shown). For example, the controller provides a logical volume to the host computer 30. The host computer 30 transmits an I / O (Input / Output) request specifying the provided logical volume to the storage device 40. The controller of the storage apparatus 40 performs data I / O for the logical volume in accordance with the received I / O request.

  FIG. 2 is a diagram illustrating an example of the configuration of the management server 100.

  The management server 100 is an example of a computer, and includes a processor 110, a memory 120, and a communication port 130 connected via an internal bus. The management server 100 communicates with the service execution system 20, the management client 200, and the like via the communication port 130.

  The processor 110 is a processor (information processing apparatus) that controls operation of the entire management server 100, and is a microprocessor such as a CPU (Central Processing Unit), for example.

  The memory 120 is a storage resource that stores various types of information. For example, the memory 120 is composed of a semiconductor memory or the like, and is used not only for storing various programs but also as a work memory for the processor 110. In addition, for example, the memory 120 includes a hard disk drive (HDD), a solid state drive (SSD), a read only memory (ROM), and the like, and stores various tables and various programs.

  The memory 120 includes a component management table 121, a component property management table 122, a service management table 123, a service property management table 124, a task management table 125, a task log 126, a recommended value management table 127, a change history management table 128, and a predefined definition. Information 129, management program 100A, etc. are stored (refer to FIGS. 6 to 18 for details).

  For example, the processor 110 reads and executes the management program 100A (service editing program 101A, service holding program 102A, service resource related diagram generation program 103A, recommended value extraction program 104A, instruction transmission program 105A, etc.) stored in the memory. Thus, a program module (service editing unit 101, service holding unit 102, service resource related diagram generation unit 103, recommended value extraction unit 104, command transmission unit 105, etc.) is realized.

  The pre-defined information 129 includes component resource-related information 129A, property mapping definition file 129B, and service resource-related information 129C.

  The communication port 130 is composed of, for example, a NIC (Network Interface Card), and performs protocol control during communication with the service execution system 20, the management client 200, and the like.

  FIG. 3 is a diagram illustrating an example of the configuration of the management client 200.

  The management client 200 is an example of a computer, and includes a processor 210 connected via an internal bus, a memory 220, a communication port 230, and an input / output device 240. The management client 200 communicates with the management server 100 and the like via the communication port 230.

  The processor 210 is a processor (information processing apparatus) that controls operation of the entire management client 200, and is, for example, a microprocessor such as a CPU.

  The memory 220 is a storage resource that stores various types of information. For example, the memory 220 is composed of a semiconductor memory or the like, and is used not only for storing various programs but also as a work memory for the processor 210. For example, the memory 220 includes an HDD, an SSD, a ROM, and the like, and stores various tables and various programs. The memory 220 stores a display program 200A and the like.

  For example, the processor 210 reads and executes the display program 200A (service editing screen display program 201A, service execution screen display program 202A, etc.) stored in the memory, thereby executing program modules (service editing screen display unit 201, service execution screen). Display unit 202 or the like) is realized.

  The communication port 230 is composed of, for example, a NIC, and performs protocol control during communication with the management server 100 and the like.

  The input / output device 240 is a liquid crystal display device for displaying various information, a pointing device for performing various operations, input, and the like, and a keyboard. For example, the input / output device 240 displays a service editing screen, a service execution screen, and the like. The operation (input) by the user is accepted.

  FIG. 4 is a diagram illustrating an operation example of the operation automation system 10. As illustrated in FIG. 4, the management server 100 includes a component group 310, a service group 320, and a task group 330.

  The component group 310 includes a plurality of components indicating one independent process. As components, provisioning, e-mail transmission, report output, local copy pair creation, OS restart, etc., pre-defined components (component A, component B, component C,...) And user-created components (users) Creation component 1, user creation component 2, ...).

  The service group 320 indicates a block of services (instantiated) that is ready to execute a service template. The service template is data in which a combination of a plurality of components is defined. The service template can be applied to data (member variables, fields (attributes)) held by the service (instance) and the service. Operations (methods, member functions) are described. Each component is also instantiated to be an executable file, and the executable file is executed in the service.

  The service managed by the management server 100 includes a service related to a predefined service template (service 1,...) And a service template created by a user by copying and editing a predefined service template. There are such services (user creation service 1, user creation service 2,...).

  The task group 330 indicates a task that is the minimum unit of work processed (executed) by the processor 110 of the management server 100. One service is realized (provided) by executing one or more tasks in the processor 110.

  FIG. 5 is a diagram illustrating an example of a configuration of a service managed by the management server 100. Here, the configuration of the service will be described using the migration service 321 as an example.

  As shown in FIG. 5, in the migration service 321, it can be seen that a plurality of service input properties, a plurality of components, and a plurality of service output properties are associated with each other.

  Here, there are two types of service properties (service properties): service input properties and service output properties. The service input property is a property relating to input of a value for a defined item (display name). The service output property is a property relating to output of a value for a defined item (display name). One service template is associated with one or more service input properties and zero or more service output properties. In addition, depending on the service template, there may be zero service output properties.

  As shown in FIG. 5, the service input property of the migration service 321 is provided with four service input properties. The display names of the four service input properties are “Primary Volume ID”, “Secondary Volume ID”, “Primary Storage Profile”, and “Secondary Storage Profile”. In the drawings, “Primary” is abbreviated as “P”, and “Secondary” is abbreviated as “S” as appropriate.

  The service output property of the migration service 321 has six service input properties. The display names of the six service input properties are “Primary Volume ID”, “Primary Pool ID”, “Primary Storage ID”, “Secondary Volume ID”, “Secondary Pool ID”, and “Secondary Storage ID”, respectively.

  Each component includes a plurality of properties (component properties). There are two types of component properties: component input properties and component output properties. The component input property is a property relating to input of a value for a defined item (display name). The component output property is a property relating to output of a value for a defined item (display name). One component is associated with one or more component input properties and zero or more component output properties. In addition, depending on the component, there may be zero output properties.

  As shown in FIG. 5, component A has four component input properties. The display names of the four component input properties correspond to the service input properties and are “Primary Volume ID”, “Secondary Volume ID”, “Primary Storage Profile”, and “Secondary Storage Profile”. The component A is provided with three component output properties. The display names of the three component output properties are “Primary Copy Pair Name”, “Secondary Copy Pair Name”, and “Volume Info”.

  The component B is provided with two component input properties. The display names of the two component input properties are “Primary Copy Pair Name” and “Secondary Copy Pair Name”, respectively. Component B does not have a component output property.

  The component C is provided with three component input properties. The display names of the three component input properties are “Primary Copy Pair Name”, “Secondary Copy Pair Name”, and “Volume Info”. The component C is provided with six component output properties. The display name of each of the six component output properties corresponds to the service output property, and “Primary Volume ID”, “Primary Pool ID”, “Primary Storage ID”, “Secondary Volume ID”, “Secondary Pool ID”, “ Secondary Storage ID ”.

  In the migration service 321, it is defined in the service template of the migration service 321 so as to be executed in the order of component A, component B, and component C. In addition, the service input property and the input property of component A are associated (mapped) with the property mapping definition file 129B, the output property of component A and the input property of component B and component C are associated, and the output of component C Information indicating that a property and a service output property are associated with each other is stored. Hereinafter, association between properties is appropriately referred to as property mapping.

(2) Various data (files, tables, etc.) used by the management server
FIG. 6 is a diagram illustrating an example of the component management table 121. The component management table 121 has information regarding components. The component management table 121 has a record for each component, and information on a component uk, a component name, a version, a resource relation diagram file path, and an execution file path is stored in each record.

  The component uk is a unique key (management number) of the component. Uk “1”, “2”,... Are examples of identification information. The component name is the name of the component. The version represents the version of the component. The resource relation diagram file path represents a path (path name) to a file indicating the resource relation diagram of the component. The execution file path represents a path to the execution file of the component.

  FIG. 7 is a diagram illustrating an example of the component property management table 122. The component property management table 122 has information regarding component properties. The component property management table 122 has a record for each component property, and information on the component property uk, component uk, key name, and display name is stored in each record.

  The component property uk is a unique key of the component property. The component uk is a unique key of the component. The key name is a name for uniquely identifying a component property, and is an example of component property identification information. The display name is a component property name.

  FIG. 8 is a diagram illustrating an example of the service management table 123. The service management table 123 has information regarding services. The service management table 123 has a record for each service, and information of service uk, service name, version, and property mapping definition file path is stored in each record.

  The service uk is a service unique key. The service name is the name of the service. The version represents the version of the service. The property mapping definition file path represents a path to the property mapping definition file 129B.

  FIG. 9 is a diagram illustrating an example of the service property management table 124. The service property management table 124 has information on service properties. The service property management table 124 has a record for each service property, and information on the service property uk, service uk, key name, and display name is stored in each record.

  The service property uk is a unique key of the service property. The service uk is a service unique key. The key name is a name for uniquely identifying a service property, and is an example of service property identification information. The display name is a service property name that can be displayed on the screen, and corresponds to, for example, an input item and an output item.

  FIG. 10 is a diagram illustrating an example of the task management table 125. The task management table 125 has information regarding tasks. The task management table 125 has a record for each task, and information on task uk, service uk, execution date and time, and task log path is stored in each record.

  Task uk is a unique key for the task. The service uk is a service unique key. The execution date and time is the date and time when the task was executed. The task log file path represents the path to the task execution content (task log 126).

  FIG. 11 is a diagram illustrating an example of the task log 126. The task log 126 has information regarding the execution contents of the task. The task log 126 is a file created for each task, and includes information such as a task uk, a service uk, a service name, an execution date, a component uk, a component property uk, and a value.

  FIG. 12 is a diagram illustrating an example of the recommended value management table 127. The recommended value management table 127 includes information regarding recommended values. The recommended value management table 127 has a record for each service input property, and each record stores service property uk, service uk, object ID, resource, attribute, user input value, and recommended value information.

  The service property uk is a unique key of the service property. The service uk is a service unique key. The object ID is identification information that can identify the object. The object IDs “D”, “E”,... Are examples of identification information. A resource represents an element of a component. The attribute represents the nature of the resource. In this embodiment, a resource and attributes of the resource are collectively referred to as an object. The user input value represents a value input by the user. The recommended value represents the latest parameter value used in the same meaning extracted from the task log 126.

  FIG. 13 is a diagram illustrating an example of the change history management table 128. The change history management table 128 has information related to a change history of recommended values. The change history management table 128 includes information indicating a change history for each service property, and information on the service property uk, execution date, recommended value, and service display name is stored in the information.

  The service property uk is a unique key of the service property. The execution date is the date on which the service was executed. The recommended value represents the latest parameter value used in the same meaning extracted from the task log 126. The service display name is a display name of the service.

(2-1) Information Defined at Component Creation Information defined by the user at the time of component creation includes component resource-related information 129A (component-related resource-related diagram and component processing contents).

  FIG. 14 is a diagram illustrating an example of a resource-related diagram of components. The component resource relation diagram 400 will be described by taking the component A resource relation diagram 400 as an example.

  In the resource relation diagram 400 of component A, the resource 401 and the attribute 402 are defined by the user. Further, the mapping relation 403 between the component property uk of the component A, the resource 401, and the attribute 402 is defined by the user. Moreover, the relationship 404 between resources is defined by the user. In addition, the resource 401 and the object ID 405 of the attribute 402 are defined by the user.

  In addition, component processing contents include ID creation (target object) for creating an ID that can identify a processing target related to a predetermined service, ID deletion (target object) for deleting the ID, and ID change for changing the ID There is a change that does not change the ID (an object before change, an object after change). The processing content of the component is defined by the user, and is included (managed) in the resource-related information 129A of the component together with the resource-related diagram of the component.

(2-2) Information defined at the time of service creation As information defined by the user at the time of service creation, there is a property mapping definition file 129B.

  FIG. 15 is a diagram illustrating an example of the property mapping definition file 129B. The property mapping definition file 129B will be described using the property mapping definition file 500 corresponding to the service uk (001) as an example.

  The property mapping definition file 500 indicates that the service input property uk501 and the component input property uk502 are defined (described) in association with each other.

  The property mapping definition file 129B is not limited to an xml (Extensible Markup Language) file, and may be a file of another format. The defined information is not limited to a configuration managed by a file, but may be a configuration managed by a table or the like.

  FIG. 16 shows an image diagram of property mapping by the property mapping definition file 500. In FIG. 16, the property mapping definition file 500 shows the association 503 between the service input property uk501 and the component input property uk502.

  The mapping between other service properties and component properties, and the mapping between component properties are similarly defined in the property mapping definition file 129B.

(2-3) Other information to be defined Processing to create a resource related diagram of a service at a predetermined timing (after component creation, service creation, specified time, user operation, etc.) (service resource related diagram creation processing) ) Is performed, service resource related information 129C is generated.

  In the following description, the processing entity of various processes is described as a “program module”. However, in practice, the processor 110 of the management server 100 executes the process based on the program module.

  FIG. 17 is a diagram illustrating an example of a processing procedure related to the service resource relation diagram generation processing. In the service resource relation diagram generation process, input (X, Y) is performed. X is a resource relation diagram of all components constituting the service. Y is the property mapping definition file 129B.

  First, based on the property mapping definition file 129B, the service resource related diagram generation unit 103 connects the resource related diagrams by overlapping the same resources in the component resource related diagrams (step S1).

  Subsequently, the service resource relation diagram generation unit 103 reassigns the object ID (step S2), and ends the service resource relation diagram generation process.

  FIG. 18 shows an image diagram of a resource relation diagram of the service 600. As shown in FIG. 18, the service 600 is provided by the component A and the component B.

  Here, the connection between the properties (resources) is confirmed from the property mapping definition file 129B, and the resource 601A of the resource related diagram of component A and the resource 601B of the resource related diagram of component B are connected. 601 are connected together.

  Further, the connection between the properties (resources) is confirmed from the property mapping definition file 129B, and the resource 602A of the resource related diagram of component A and the resource 602B of the resource related diagram of component B are connected. Connected as 602.

  Then, the object ID (“A”, “B”, “C”, “D”, “E”, “F” in this example) is reassigned to the object corresponding to each resource, and as shown in FIG. A resource relationship diagram for service 600 is created.

(3) Recommended value extraction output processing (Recommended parameter value extraction method)
FIG. 19 is a diagram illustrating an example of a processing procedure related to the recommended value extraction / output processing. The recommended value extraction / output process starts when a recommended parameter display button 717 (FIG. 31) on the service execution screen described later is pressed.

  First, the recommended value extraction unit 104 performs input parameter content determination processing (step S11). Although details will be described later, in the input parameter content determination process, a service input property (a parameter related to the recommended value) to be recommended based on the resource relation diagram of the service, the property mapping definition file 129B, and the user input value. Is identified.

  Subsequently, the recommended value extraction unit 104 performs related past task search and recommended value extraction processing (step S12). Although details will be described later, in the related past task search and recommended value extraction process, a recommended value is extracted from the task log 126 based on the resource related information 129C of the service.

  Subsequently, the recommended value extraction unit 104 transmits screen information relating to a screen for displaying the recommended value and the change history to the management client 200 (an example of output) (step S13). Upon receiving the screen information, the management client 200 displays a service execution screen (FIG. 32) on the input / output device 240 (an example of output), and ends the recommended value extraction / output process.

  FIG. 20 is a diagram illustrating an example of a processing procedure related to the input parameter content determination processing.

  First, the recommended value extraction unit 104 specifies the service uk of the service item (target service) selected on the service list screen (FIG. 30) described later (step S21).

  Subsequently, the recommended value extraction unit 104 identifies the service properties uk of all the service input properties and their resources and attributes from the resource relation diagram of the target service and the property mapping definition file 129B, and stores them in the recommended value management table 127 ( Step S22).

  More specifically, the recommended value extraction unit 104 identifies service properties uk of all service input properties from the property mapping definition file 129B. Next, the recommended value extraction unit 104 identifies the component property uk associated with the identified service property uk from the property mapping definition file 129B. Then, the recommended value extraction unit 104 identifies the resource and attribute defined in the identified component property uk from the resource relation diagram of the target service. FIG. 21 shows an image diagram related to this processing (image diagram for specifying a parameter related to a recommended value).

  Subsequently, the recommended value extraction unit 104 stores the input value of the service input property having the user input value in the recommended value management table 127, stores “−” in the recommended value (step S23), and the input parameter content determination processing Exit.

  FIG. 21 shows an image diagram for specifying a parameter relating to a recommended value.

  FIG. 21 shows a property mapping definition file 611 of the target service (pair volume batch migration service in this example) and a resource relation diagram 612 of the target service.

  Regarding the specification of the parameter relating to the recommended value, the component property uk associated with the service input property is specified from the property mapping definition file 611, and the resource and attribute defined in the component property uk from the resource relation diagram of the target service are determined. It is done by being specified.

  Here, since a recommended value is not required for a parameter that must be input, a recommended value is basically obtained for a parameter that is input arbitrarily.

  However, in the pair volume batch migration service, at least one of the storage ID and volume ID of the storage device 40 related to the primary volume and the storage ID and volume ID of the storage device 40 related to the secondary volume is a parameter that must be input. Therefore, recommended values are obtained for parameters that have not been input, storage profile parameters for the primary volume, and storage profile parameters for the secondary volume.

  In this example, since the user input values are set for the storage ID and volume ID of the primary volume, the storage ID and volume ID parameters of the secondary volume, the storage profile parameters of the primary volume, and the storage profile of the secondary volume The parameter is specified as a parameter related to the recommended value.

  FIG. 22 is a diagram illustrating an example of a processing procedure related to related past task search and recommended value extraction processing.

  First, the recommended value extraction unit 104 identifies an object (Object) corresponding to the resource that has received the user input value from the resource relation diagram of the target service (step S31).

  Subsequently, the recommended value extraction unit 104 executes processing (O, T) for each object, where O is an object and T is the current time (step S32), and processes (O) for all the objects identified in step S31. , T) ends the related past task search and recommended value extraction processing.

  Details of the process (O, T) will be described with reference to FIGS. 24 to 26. The process (O, T) is an example of a task process indicating a process related to a task, and the process (O, T). Then, the task search process (future task search process) is performed on the object “O” in order from the task log 126 of the latest future (the time closest to T and future from T) from the task execution time T. Subsequently, task search processing (past task search processing) is performed in order from the task log 126 of the latest past (time after T. T is included).

(Overview of task search process)
The recommended value extraction unit 104 specifies the service (execution service) that executed the task from the task log 126 including the user input value, and specifies the resource relation diagram of the specified execution service. The recommended value extraction unit 104 determines whether or not the object “O” exists in the identified resource relation diagram. When it is determined that the object “O” exists in the identified resource relation diagram, the recommended value extraction unit 104 stores the attribute value of the object “O”, and extracts the recommended value if it is the latest value.

  Further, the recommended value extraction unit 104 determines whether or not a related object of the object “O” exists in the identified resource related diagram. When it is determined that the related object exists, the recommended value extraction unit 104 uses the object argument as the related object and the time (time) argument as the execution date and time of the task log 126 related to the related object, and performs processing (related Obj, current task T ).

  Also, the recommended value extraction unit 104 refers to the resource-related information 129A (component processing content) of the component relating to the object “O” and determines whether or not the ID has been changed. When it is determined that the ID change has been performed, the recommended value extraction unit 104 sets the object argument as the alias object before the ID change, and executes the process (alias, T of the current task).

FIG. 23 shows an image diagram related to task search processing (image diagram of a procedure for searching the task log 126 and extracting a recommended value). Here, the current time is T ₁ (Now), the object that has received the user input value (“10051”, “00:01”) is the object 631, and the object related to the parameter for obtaining the recommended value is the object “A ”,“ E ”, and“ H ”(objects 631, T ₁ ) will be described as an example.

First, the object 631, although the future task retrieval processing is carried out, the task log 126 of new time than the current time T ₁ does not exist, so that the past task search process is performed.

  Therefore, the recommended value extraction unit 104 searches the past task log 126 including the user input value, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, and has the same resource as the object 631. The attribute object 632 is specified.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 632, and in this example, determines that the object 633 exists as a related object.

Subsequently, the recommended value extraction unit 104 executes processing (objects 633 and T ₂ ) with the object argument as the object 633 and the time argument as T ₂ . The object 633, although the future task retrieval processing is performed, a new time of task logs 126 than time T _2, which includes a user input value is not present, so that the past task search process is performed.

  Therefore, the recommended value extraction unit 104 searches the past task log 126 including the user input value, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, and has the same resource as the object 633. The attribute object 633 is specified. At this time, the recommended value extraction unit 104 stores the attribute value (“10051”, “00:02”) of the object 633 and extracts it as a recommended value.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 633, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 633 and determines whether or not the ID has been changed. In this example, the recommended value extraction unit 104 determines that the ID has not been changed.

  Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value, specifies an execution service from the searched task log 126, specifies a resource relation diagram of the specified execution service, and an object 633. Identifies an object 634 of the same resource and attribute.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 634, and in this example, determines that the object 635 exists as a related object.

Subsequently, the recommended value extraction unit 104 executes processing (objects 635 and T ₃ ) with the object argument as the object 635 and the time argument as T ₃ . The object 635, although the future task retrieval processing is performed, a new time of task logs 126 than the time T _3, including a user input value is not present, so that the past task search process is performed.

  Therefore, the recommended value extraction unit 104 searches the past task log 126 including the user input value, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, and has the same resource as the object 635 The attribute object 635 is specified. At this time, the recommended value extraction unit 104 stores the attribute value “Silver” of the object 635 and extracts it as a recommended value.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 635, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 635 to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

  Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value, specifies an execution service from the searched task log 126, specifies a resource relation diagram of the specified execution service, and an object 635. Identifies an object 636 of the same resource and attribute. At this time, the recommended value extraction unit 104 stores the attribute value “Gold” of the object 636, but does not update the recommended value because it is not the latest attribute value.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 636, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 636 to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value. However, since the corresponding task log 126 is not found, the process (object 635, T ₃ ) is terminated.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 634 and determines whether or not the ID change has been performed. In this example, the recommended value extraction unit 104 determines that the ID change has not been performed.

  Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value for the object 633, specifies an execution service from the searched task log 126, and specifies a resource relation diagram of the specified execution service. Then, the object 637 having the same resource and attribute as the object 633 is specified.

Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 637. In this example, the recommended value extraction unit 104 determines that the object 636 exists as a related object, the object argument is the object 636, and the time argument. as _{T 5,} it executes processing (object 636, _{T 5).} The details of the processing (objects 636, T ₅ ) are the same as described above, and thus the description thereof is omitted.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 637 and determines whether or not the ID change has been performed. In this example, the recommended value extraction unit 104 determines that the ID change has not been performed.

Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value. However, since the corresponding task log 126 is not found, the process (object 633, T ₂ ) ends.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 632 to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

  Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the user input value for the object 631, specifies an execution service from the searched task log 126, and specifies a resource relation diagram of the specified execution service Then, the object 638 having the same resource and attribute as the object 631 is specified.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 638, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 638 and determines whether or not the ID has been changed. In this example, the recommended value extraction unit 104 determines that the change has been performed.

Subsequently, the recommended value extraction unit 104 changes the user input value (“10051”, “00:01”) to the value before the change (“10057”, “00:11”) (referred to as an alias object), and sets the object The process (alias object, T ₄ ) is executed with the argument of 別名 as the alias object and the time argument as T ₄ .

Subsequently, the recommended value extraction unit 104, to the Alias object, but future task search process is performed, since the new time of the task log 126 is not present than the time T ₄ containing the value before the change, past tasks search process Will be done.

  Therefore, the recommended value extraction unit 104 searches the past task log 126 including the value before the change, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, and is the same as the alias object Identify resource and attribute alias objects.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the alias object, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the alias object to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

  Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the value before the change, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, An object 639 having the same resource and attribute as the object is specified.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 639, and in this example, determines that the object 640 exists as a related object.

Subsequently, the recommended value extraction unit 104 executes processing (objects 640 and T ₆ ) with the object argument as the object 640 and the time argument as T ₆ . The object 640, although the future task retrieval processing is performed, since the new time of task logs 126 than the time T ₆ containing the value before the change is not present, so that the past task search process is performed.

  Therefore, the recommended value extraction unit 104 searches the past task log 126 including the value before the change, specifies the execution service from the searched task log 126, specifies the resource relation diagram of the specified execution service, and is the same as the object 640 A resource and attribute object 640 is identified. At this time, the recommended value extraction unit 104 stores the attribute value “Gold” of the object 640 and extracts it as a recommended value.

  Subsequently, the recommended value extraction unit 104 determines whether or not a related object exists in the object 640, and in this example, determines that there is no related object.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 640 to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the value before the change. However, since the corresponding task log 126 is not found, the process (objects 640 and T ₆ ) is terminated.

  Subsequently, the recommended value extraction unit 104 refers to the processing content of the component related to the object 639 to determine whether or not the ID change has been performed, and in this example, determines that the ID change has not been performed.

Subsequently, the recommended value extraction unit 104 searches the next past task log 126 including the value before the change for the object 631, but ends the process (object 631, T ₁ ) because the corresponding task log 126 is not found. To do.

  As described above, the task search process is performed on the object that has received the user input value and the object related to the object, and the recommended value is extracted. Details of the processing (O, T) will be described below with reference to FIGS.

  24 and 25 are diagrams illustrating an example of a processing procedure related to the processing (O, T).

  First, the recommended value extraction unit 104 sequentially performs the processing (future task search processing) in steps S41 to S51 for the task log 126 future from T.

  In step S41, the recommended value extraction unit 104 specifies an execution service from the task log 126 including the user input value, and specifies a resource relation diagram of the specified execution service.

  Subsequently, the recommended value extraction unit 104 determines whether or not the object “O” exists (step S42). If the recommended value extraction unit 104 determines that the object “O” exists, the process proceeds to step S43. If the recommended value extraction unit 104 determines that the object “O” does not exist, the recommended value extraction unit 104 sets the processing target to the next future task log 126, The process moves to step S41. If there is no next future task log 126, the processes of steps S 61 to S 67 (past task search process) are sequentially performed on the past task log 126 before T.

  Here, FIG. 27 shows an image diagram relating to the determination of whether or not the object “O” exists. As illustrated in FIG. 27, the recommended value extraction unit 104 includes resources, attributes, and attributes corresponding to the object “O” of the resource relation diagram of the service selected by the user among the objects of the resource relation diagram of the service of the searched task log 126. If there is a predetermined object (object 640) whose attribute values all match, it is determined that the object “O” exists.

  In step S43, the recommended value extraction unit 104 performs recommended value extraction processing. Although details will be described later, a recommended value is extracted in the recommended value extraction process.

  Subsequently, the recommended value extraction unit 104 determines whether there is a related object that is desired (step S44). If the recommended value extraction unit 104 determines that there is a desired related object, the recommended value extraction unit 104 performs processing (related object, T of the current task) on the related object (step S45), and moves the process to step S46. On the other hand, if the recommended value extraction unit 104 determines that there is no related object that the user wants, the process proceeds to step S46.

  Here, FIG. 28 shows an image diagram relating to determination of whether or not there is a related object. As illustrated in FIG. 28, the recommended value extraction unit 104 has an object having a resource and an attribute that match a resource and an attribute corresponding to the related object “O ′” among the objects in the resource relation diagram of the service of the searched task log 126. When there is a specific object (object 641) having the same relationship as the relationship between the object “O” and the related object “O ′”, it is determined that the desired related object “O ′” exists.

  In other words, the recommended value extraction unit 104 determines that a case where resources are different and the attributes are the same and a case where the resources are the same but the attributes are not completely matched are not related objects.

  Also, if the related object that is desired is an object 642 that is not directly connected to the object “O”, the object between them (the object 643 in this example) is also determined. In this case, the recommended value extraction unit 104 includes the resource and attribute between the object 642 and the object 644, the resource and attribute between the object 643 and the object 645, the relationship between the object 642 and the object 643, and the object 644 and the object 645, If all of the relationships between “O” and the object 643 and the objects 640 and 645 match, it is determined that the desired related object exists.

  It should be noted that an object for which an ID change is defined in the processing contents of a component, such as the relationship between resources being migrated, in the route of the object “O” and the related object that is desired is regarded as the same resource and the object concerned. The route may be shortened by excluding from the determination target.

  In step S <b> 46, the recommended value extraction unit 104 refers to the resource-related information 129 </ b> A (component processing content) of the component related to the object “O” and determines the processing content performed on the object “O” in the task. If the recommended value extraction unit 104 determines that the ID is changed, the process proceeds to step S47. If it is determined that the ID is created, the process proceeds to step S49. If it is determined that the ID is deleted, step S50 is performed. If it is determined that there is another change, the process proceeds to step S51.

  In step S47, the recommended value extraction unit 104 updates the alias management table 650 that is temporarily stored in the memory 120.

  Here, FIG. 29 shows an example of the alias management table 650. As shown in FIG. 29, the alias management table 650 stores information on the object name and ID of the object to be processed and the object name (alias) and ID before the change.

For example, in the object to be processed, information stored in the alias management table 650 is exemplified by an example in which an ID is created at time T ₁₄ , the ID is changed at time T _13, and the ID is changed at time T _12. Will be explained.

Alias management table 650, the current time T _11, column value is not set in the ID alias - a (indicating that the value is not set "." May be, etc.), the time to be processed There ID ( "10054", "00:04") in the column of alias ID when a time T ₁₂ is set, ID column aliases ID when time to be processed is a time T ₁₃ ( “10057” and “00:11”) are set (overwritten).

  With this alias management table 650, parameter values used in the same meaning can be extracted from the task log including the ID before the ID is changed.

  Subsequently, the recommended value extraction unit 104 executes a process (another name, T of the current task) (step S48), and moves the process to step S51.

  In step S49, the recommended value extraction unit 104 ends the loop (future task search process) and performs a past task search process.

  In step S50, the recommended value extraction unit 104 ends the loop (future task search processing) because the task has reached, and performs past task search processing.

  In step S51, the recommended value extraction unit 104 determines whether to end the loop (whether processing has been performed for all future task logs 126). When it is determined that the loop is to be ended, the recommended value extraction unit 104 performs past task search processing, and when it is determined that the loop is not to be ended, the processing target is set in the next future task log 126 and the process proceeds to step S41. .

  As shown in FIG. 25, past task search processing is performed. More specifically, in step S61, the processing of step S41 to step S45 is performed, and the processing is moved to step S62.

  In step S62, the recommended value extraction unit 104 determines the content of processing performed on the object “O” in the task. If the recommended value extracting unit 104 determines that the ID is changed, the process proceeds to step S63. If the recommended value extracting unit 104 determines that the ID is created, the process proceeds to step S65. If the recommended value extracting unit 104 determines that the ID is deleted, step S66 is performed. If it is determined that there is another change, the process proceeds to step S67.

  In step S63, the recommended value extraction unit 104 updates the alias management table 650.

  Subsequently, the recommended value extraction unit 104 executes a process (another name, T of the current task) (step S64), and moves the process to step S67.

  In step S65, the recommended value extraction unit 104 ends the loop (past task search process), and moves the process to step S67.

  In step S66, the recommended value extraction unit 104 ends the loop (past task search process) because the task has arrived, and moves the process to step S67.

  In step S67, the recommended value extraction unit 104 determines whether to end the loop (whether processing has been performed for all past task logs 126). If it is determined that the loop is to be ended, the recommended value extraction unit 104 ends the processing (O, T), and if it is determined that the loop is not to be ended, the processing target is set in the next past task log 126 and the process proceeds to step S61. Move processing.

  FIG. 26 is a diagram illustrating an example of a processing procedure related to the recommended value extraction processing.

  First, the recommended value extraction unit 104 determines whether or not the recommended value for the resource in the recommended value management table 127 is empty (step S71). If the recommended value extraction unit 104 determines that the value is empty, the process proceeds to step S72. If the recommended value extraction unit 104 determines that the value is not empty, the process proceeds to step S73.

  In step S72, the recommended value extraction unit 104 stores the resource information (recommended values and the like) in the recommended value management table 127 and the change history management table 128, and ends the recommended value extraction process.

  In step S73, the recommended value extraction unit 104 stores the resource information (recommended value and the like) in the change history management table 128 so that the execution date and time is in descending order.

  Subsequently, the recommended value extraction unit 104 extracts the latest recommended value from the change history management table 128, updates the recommended value in the recommended value management table 127 (step S74), and ends the recommended value extraction process.

  As described above, in the recommended value extraction / output process, parameter values used in the same meaning are extracted from the task log 126 based on the resource-related information 129C of the service, and the extracted parameter values are output as recommended values. , Parameter values can be set with a consistent policy.

(4) Display Screen FIGS. 30 to 32 are diagrams illustrating an example of a display screen in the management client 200. FIG.

  FIG. 30 is a diagram illustrating an example of a service list screen (display screen 700) for selecting a service item corresponding to a service provided in advance.

  On the display screen 700, service items corresponding to each of a plurality of services registered in the operation automation system 10 are displayed in a list form so as to be selectable.

  The user operates the input / output device 240 of the client 200 (user operation) to select a service item of a desired service. When one service item is selected by a user operation, an input required for the service is performed, and a service execution screen 701 for executing the service is displayed.

  FIG. 31 is a diagram showing an example of the service execution screen 701 (pair volume batch migration service service execution screen 710).

  Here, the pair volume batch migration service refers to each storage ID (Storage Serial No.) and each of the storage devices 40 in which the P-Vol (Primary Volume) and S-Vol (Secondary Volume) forming the local copy pair exist. A service that designates a volume ID and each storage destination storage profile (Primary Storage Profile, Secondary Storage Profile), and migrates P-Vol and S-Vol to another optimal storage device 40 at once. is there.

  In the service execution screen 710, an input field 711 in which a storage ID and a volume ID (Primary Volume ID) related to P-Vol can be input, and an input capable of inputting a storage ID and a volume ID (Secondary Volume ID) related to S-Vol. A column 712, an input column 713 in which a P-Vol migration destination storage profile can be input, and an input column 714 in which an S-Vol migration destination storage profile can be input are provided.

  In the service execution screen 710, an execution button 715 for instructing execution of the pair volume batch migration service, a cancel button 716 for canceling the use of the pair volume batch migration service, and a recommended value (recommended parameter value) are displayed. A recommended parameter display button 717 for display is provided.

  The user operates the cursor 718 by a user operation to execute a pair volume batch migration service or the like. For example, the user inputs in the input field 711, presses the recommended parameter display button 717, confirms the recommended values displayed in the input field 712 to the input field 714, and presses the execution button 715.

  Here, when the recommended parameter display button 717 is pressed, a service execution screen in which recommended values of parameters in a consistent policy are set in the input fields 712 to 714 is displayed.

  FIG. 32 is a diagram illustrating an example of the service execution screen 701 (service execution screen 720 in which recommended values are set).

  On the service execution screen 720, recommended values are set in the input fields 712 to 714, and a parameter value change history related to the recommended values can be displayed.

  Here, when using a service for collectively migrating P-Vol and S-Vol, it is necessary to set parameter values for each of P-Vol and S-Vol. There is a problem that a mistake occurs in the initial input.

  In this regard, in the computer system 1, in the case of a service for collectively migrating P-Vol and S-Vol, the service configuration of the service is analyzed. For example, S-Vol is a parameter when local copy is performed. Since it is understood that there is a parameter and the parameter value of the parameter is acquired and presented as a recommended value, it is possible to save input and reduce input errors.

  In addition, even if the recommended values of parameters in a consistent policy are presented, there is a problem that it is not possible to change the parameter values to be considered more suitable because it is not known why they are recommended.

  In this respect, the computer system 1 can present a parameter value change history related to the recommended value, so that the user can change the parameter value to a more suitable parameter value.

  According to the present embodiment, it is possible to appropriately set parameter values used for services.

(5) Other Embodiments In the above-described embodiment, the case where the present invention is applied to the computer system 1 has been described. However, the present invention is not limited to this and is widely applied to various other systems. Can be applied.

  Further, in the above-described embodiment, the parameter that must be input has been described as an example, but the present invention is not limited to this. Depending on the input value of the user, a highly accurate recommended value may not be obtained. However, an arbitrary input value may be received and processing may be performed. For example, the user may start processing by setting the storage profile of the secondary volume to “Gold” and enjoy the recommended value.

  In the above-described embodiment, the case where the future task search process is performed and the past task search process is subsequently performed has been described. However, the present invention is not limited to this, and the past task search process is performed and the future task search is performed. Processing may be performed.

  In the above-described embodiment, the case where the process of the T task log 126 (current task search process) is performed in the past task search process has been described. The process 126 may be performed, or the process (current task search process) may be performed at another timing.

  In the above-described embodiment, the case where the recommended value is displayed by the management client 200 has been described. However, the present invention is not limited to this, and the recommended value is displayed by a printer (not shown) connected to the management server 100. The recommended value may be transmitted to a predetermined mail address, the recommended value may be stored in a predetermined storage device as a CSV (Comma Separated Values) file, and others May be output. In other words, examples of output devices that can output recommended values include the management server 100, the input / output device 240, and a printer. The service execution screen display unit 202 is an example of an output unit.

  In the above-described embodiment, the case where the management server 100 and the management client 200 are provided separately has been described. However, the present invention is not limited to this, and the management server 100 and the management client 200 are provided by a single computer. May be.

  In the above-described embodiment, the case where the management server 100 and the management client 200 communicate with each other has been described. However, the management server 100 and the management client 200 may be directly connected or via an internal network. They may be connected, may be connected via an external network, may be connected via an internal network and an external network, or may be connected in other forms.

  Further, in the above-described embodiment, the case where the management server 100 and the service execution system 20 communicate with each other has been described. However, the management server 100 and the service execution system 20 may be directly connected, or an internal network may be connected. May be connected via an external network, may be connected via an internal network and an external network, or may be connected in other forms.

  In the above-described embodiment, the case where various types of data (tables, files, etc.) are stored in the management server 100 has been described. You may do it. In this case, the storage device is composed of a disk array device on which a plurality of storage devices such as hard disk devices are mounted, and holds data necessary for various processes executed by the management server 100. The storage device stores data in the storage device in response to a write request from the management server 100, or reads the requested data from the storage device and transmits it to the management server 100 in response to a read request from the management server 100. Or

  In the above embodiment, for convenience of explanation, various types of data have been described using an XX table and an XX file. However, the data structure is not limited and may be expressed as XX information.

  Moreover, about the content mentioned above, in the range which does not exceed the summary of this invention, it can combine suitably, abbreviate | omit, deform | transform, and can change order.

  DESCRIPTION OF SYMBOLS 1 ... Computer system, 10 ... Operation automation system, 20 ... Service execution system, 30 ... Host computer, 40 ... Storage apparatus, 50 ... Network, 100 ... Management server, 101 ... Service editing part, DESCRIPTION OF SYMBOLS 102 ... Service holding | maintenance part, 103 ... Service resource related figure production | generation part, 104 ... Recommended value extraction part, 105 ... Command transmission part, 200 ... Management client, 201 ... Service edit screen display part, 202 ... Service execution screen display section.

Claims (5)

A computer system capable of receiving input of identification information capable of identifying a processing target related to a predetermined service and outputting a recommended value of a parameter used for the predetermined service;
Based on the resource-related information of the service provided in advance with defined resource attributes and connection between resources, parameter values used in the same meaning are extracted as recommended values from the task log indicating the execution contents of the predetermined service A recommended value extractor,
An output unit for outputting the recommended value extracted by the recommended value extraction unit;
A computer system comprising: When the identification information has been changed, the recommended value extraction unit extracts, as a recommended value, a parameter value that is used in the same meaning from a task log that includes the identification information before being changed.
The computer system according to claim 1. The recommended value extraction unit performs task processing with an object argument as an object corresponding to a resource related to the predetermined service, and a time argument as an execution date and time of a task related to the object,
In the task processing, the recommended value extraction unit
Identify the service executed from the task log containing the identification information,
Identify resource-related information of the identified service from the resource-related information of the service provided in advance,
Based on the resource-related information of the specified service, the same predetermined object as the object to be processed is specified, the parameter value of the specified object is extracted from the task log and stored, and the parameter value is the latest value Is extracted as a recommended value,
Based on the resource-related information of the specified service, the same specific object as the related object of the object to be processed is specified, the argument of the object is the specific object, and the time argument is the task related to the specific object. Execute task processing as the execution date,
The computer system according to claim 1. When there are a plurality of extracted parameter values, the recommended value extraction unit outputs the latest parameter value as a recommended value among the plurality of parameter values, and outputs the remaining parameter value as a change history. Send instructions to
The computer system according to claim 1. A recommended parameter value extraction method in a computer system that accepts input of identification information that can identify a processing target related to a predetermined service, and that can output a recommended value of a parameter used for the predetermined service,
Parameters used by the recommended value extraction unit in the same meaning from the task log indicating the execution contents of the predetermined service based on the resource-related information of the service provided in advance in which the attribute of the resource and the connection between the resources are defined A first step of extracting values as recommended values;
A second step in which the output unit outputs the recommended value extracted in the first step;
A recommended parameter value extraction method comprising:

Images