WO2015186219A1 - Distributed processing system and operation method therefor - Google Patents

Distributed processing system and operation method therefor Download PDF

Info

Publication number
WO2015186219A1
WO2015186219A1 PCT/JP2014/064932 JP2014064932W WO2015186219A1 WO 2015186219 A1 WO2015186219 A1 WO 2015186219A1 JP 2014064932 W JP2014064932 W JP 2014064932W WO 2015186219 A1 WO2015186219 A1 WO 2015186219A1
Authority
WO
WIPO (PCT)
Prior art keywords
setting change
setting
change
information
slave
Prior art date
Application number
PCT/JP2014/064932
Other languages
French (fr)
Japanese (ja)
Inventor
山本　祐介
川本　真一
馬場　恒彦
聡 勝沼
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2014/064932 priority Critical patent/WO2015186219A1/en
Publication of WO2015186219A1 publication Critical patent/WO2015186219A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/18—Error detection or correction of the data by redundancy in hardware using passive fault-masking of the redundant circuits
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/177—Initialisation or configuration control

Definitions

  • the present invention relates to a distributed processing system including a master system and a plurality of slave systems, and an operation method thereof.
  • the operation management system is a system for maintaining a state where the IT system continues to operate normally. This operation management system checks whether there is an abnormality in the IT system, performs maintenance, updates aging equipment, preserves data for failure, recovers from failure, and the like. At this time, a setting change process is performed in the operation management system.
  • the setting change processing in the operation management system may fail for various reasons.
  • the setting change information includes bugs in the setting information such as syntax errors and semantic errors, and the system does not operate due to the setting compatibility between the systems after the setting change is reflected. is there.
  • Patent Document 1 proposes a process of rolling back the setting change process by a single setting target and returning to the previously applied setting state.
  • the application has a manager that issues a setting change command and an application that is introduced to the setting target and manages the setting change and changes the setting using the setting target setting command.
  • the application manages version of the setting information for each setting, and executes a rollback process designed based on the existing command to be set. If a configuration change failure occurs, the application installed on the setting target performs a rollback, and the setting target alone returns to the previously applied setting state.
  • the object of the present invention is to, when a setting change process for at least one change object among a plurality of change objects fails, for two or more change objects related to the change object for which the setting change process has failed,
  • An object of the present invention is to provide a distributed processing system capable of returning setting information set to two or more setting targets to a state before setting change processing, and an operation method thereof.
  • the present invention provides a slave server that executes data processing according to setting information transferred from a master server, which is processing for a plurality of change target components, and is configured according to setting change information.
  • a master server which is processing for a plurality of change target components
  • setting change information for the plurality of change target components on condition that the plurality of change target components exist
  • the change process is executed and the setting change process for at least one change target component among the setting change processes fails
  • the two or more change target components related to the change target component for which the setting change process has failed are collected.
  • Two or more change setting change information set in the target component which is, and executes a rollback process to restore the original settings information set prior to receiving the indication information.
  • the two or more change objects related to the change object for which the setting change process has failed Setting information set to two or more setting targets can be returned to the state before the setting change process.
  • 1 is an overall configuration diagram of a distributed processing system showing an embodiment of the present invention. It is a block diagram of the hardware resource and software resource of a master system. It is a block diagram of the hardware resource and software resource of a slave system. It is a block diagram of the table managed by a master system. It is a block diagram of the table managed by a slave system. It is a flowchart for demonstrating the process of a distribution transaction management part. It is a flowchart for demonstrating the process of a setting change commit part. It is a flowchart for demonstrating the process of the setting change rollback part in a slave system. It is a block diagram of the hardware resource and software resource of the slave system in Example 2.
  • FIG. 10 is a flowchart for explaining processing of a distributed transaction management unit according to the second embodiment.
  • 12 is a flowchart for explaining processing of a setting change commit unit according to the second embodiment.
  • 10 is a flowchart for explaining processing of a setting change rollback unit according to the second embodiment.
  • FIG. 10 is a configuration diagram of hardware resources and software resources of a master system in Embodiment 3.
  • FIG. 10 is a configuration diagram of hardware resources and software resources of a slave system according to a third embodiment.
  • 10 is a flowchart for explaining processing of a distribution transaction management unit and an operation test management unit in the third embodiment.
  • 12 is a flowchart for explaining processing of a setting change commit unit in the third embodiment.
  • FIG. 12 is a flowchart for explaining processing of a setting change rollback unit according to the third embodiment.
  • FIG. 10 is a configuration diagram of hardware resources and software resources of a slave system according to a fourth embodiment.
  • 15 is a flowchart for explaining processing of a distributed transaction management unit according to the fourth embodiment.
  • 15 is a flowchart for explaining processing of a setting change commit unit in the fourth embodiment.
  • 14 is a flowchart for explaining processing of a setting change rollback unit according to the fourth embodiment.
  • 1 is an overall configuration diagram of a distributed processing system using a wide area network as a network.
  • the setting information set in the component is returned to the original setting information in units of groups.
  • FIG. 1 is an overall configuration diagram of a distributed processing system showing an embodiment of the present invention.
  • the distributed processing system 10 includes a master system 20, a plurality of (# 0 to # 4) slave systems 30, a network 40, and a management terminal 50.
  • the master system 20 and each slave system 30 are connected to each other via the network 40, and the master system 20 is connected to the management terminal 50.
  • the network 40 is configured using, for example, a LAN (Local Area Network).
  • Each of the slave systems 30 of # 0 to # 4 has a plurality of servers (server groups) 300, and each server 300 performs a data analysis process or the like on a user terminal (not shown) via the network 40.
  • An application program (not shown) that provides a service operates.
  • the master system 20 includes a server 200 that performs operation management of each slave system 30 and performs processing for changing setting information such as an application program running on each server 300.
  • the slave system 30 is configured by the slave systems 30 of # 0 to # 4.
  • the number of slave systems 30 is an example, and actually increases or decreases depending on the service provided to the user.
  • the server 200 of the master system 20 includes a memory 201, an I / O interface 202, a CPU (Central Processing Unit) 203, and a storage device 204. Each unit is interconnected via an internal bus 205. Connected to the management terminal 50.
  • the memory 201 is configured as a storage device that stores various programs and data.
  • the I / O interface 202 is configured as an input / output interface device that transmits / receives information to / from each server 300 of each slave system 30 via the network 40.
  • the CPU 203 is configured as a control device that performs overall control of the entire server 200.
  • the storage apparatus 204 includes a storage device that stores various types of information and various types of data.
  • the management terminal 50 is constituted by a computer device provided with information processing resources such as a CPU, a memory, and an input / output interface, for example. At this time, an operation administrator who operates and manages the distributed processing system 10 operates the management terminal 50 to input information for changing the setting of the distributed processing system 10 to the master system 20.
  • FIG. 2 is a configuration diagram of hardware resources and software resources of the master system.
  • the memory 201 of the server 200 in the master system 20 stores the operation management unit 210 that is a program for managing the operation of each slave system 30 and the configuration information 206 stored in the storage device 204.
  • a buffer 220 is constructed.
  • the operation management unit 210 includes a distribution management unit 212 which is a program for distributing setting information to each slave system 30.
  • the distribution management unit 212 is a program for performing transaction management of setting change information application processing.
  • the distribution transaction management unit 212 is configured.
  • the input information is managed by the CPU 203.
  • the CPU 203 records the input information, for example, setting information in the configuration information 206 of the storage apparatus 204 and transfers the information recorded in the configuration information 206 to the buffer 220.
  • the buffer 220 stores information such as various tables belonging to the configuration information 206.
  • FIG. 3 is a configuration diagram of hardware resources and software resources of the slave system.
  • the server 300 in each slave system 30 includes a memory 301, an I / O interface 302, a CPU 303, and a storage device 304, and each unit is interconnected via an internal bus 305.
  • the memory 301 is configured as a storage device that stores various programs and data.
  • the I / O interface 302 is configured as an input / output interface device that transmits / receives information to / from each server 300 of the other slave system 30 and the server 200 of the master system 20 via the network 40.
  • the CPU 303 is configured as a control device that performs overall control of the entire server 300.
  • the storage device 304 includes a storage device that stores various types of information, for example, setting change management information 306, setting information 307, and various types of data.
  • a setting change management unit 310 and a setting target component unit 320 configured by programs, and a buffer 330 for storing various types of information are constructed.
  • the buffer 330 stores setting change management information 306 and setting information 307 as information transferred from the storage device 304.
  • the setting change management unit 310 is a program for managing the setting command of the change target component unit 320, and the setting change commit unit 311 and the setting change commit unit 311 as programs for committing the setting change did not end normally.
  • the configuration change rollback unit 312 as a program for executing the rollback of the configuration information.
  • the setting target component unit 320 is a program to be set, and includes a system stop unit 321 that is a program for stopping the system, a setting change unit 322 that is a program for changing settings, and a program for checking settings.
  • a setting check unit 323 and a system activation unit 324 which is a program for activating the system.
  • FIG. 4 is a configuration diagram of a table managed by the master system. 4A
  • the setting change scenario information table 230 is a table stored in the storage apparatus 204 and the buffer 220, and includes a scenario ID field 230A, a process number field 230B, a group ID field 230C, and a component ID. It consists of a field 230D and a setting content ID field 230E.
  • This setting change scenario information table 230 is configured as a table for managing which setting contents of which component of which group are changed in which order, and a plurality of setting changing scenario information tables 230 exist according to the number of scenarios.
  • Scenario is a name for the operation manager to manage setting change work.
  • scenario ID field 230A for example, information “2” is stored as an identifier for uniquely identifying the scenario.
  • the process number is a number that identifies each process when the scenario is configured by a plurality of processes.
  • process number field 230B for example, information “1” to “12” is stored as a number for specifying each process of the scenario.
  • the group is a group in which each process belonging to the scenario is classified into a plurality for each process content and function.
  • group ID field 230C for example, information “1” is stored as an identifier for uniquely identifying each processing group belonging to the scenario.
  • the component is an element belonging to each slave storage 30 and is an element to be changed, for example, setting information 307 stored in the storage device 304 of the slave system 30 or a program running on each server 300.
  • the component ID field 230D for example, information “7” is stored as an identifier for uniquely identifying the element whose setting is to be changed.
  • the setting content is information indicating the setting content of the setting change information for the component to be changed.
  • information “4” is stored as an identifier for uniquely identifying the setting content of the setting change information for the element constituting the change target.
  • the component is managed in association with each slave system 30 and each server 300 belonging to each slave system 30.
  • the setting change scenario information table 230 components having the same processing contents or functions and related to each other, for example, components # 7, # 4, and # 9 belong to the group # 1, and components # 7
  • the setting contents “4”, “12”, and “34” of the setting change information are set, the setting contents “56” of the setting change information are set for the component # 4, and the setting contents “56” are set for the component # 9. This means that the setting content “68” of the setting change information is set.
  • the setting change scenario status management table 240 is a table stored in the storage device 204 and the buffer 220. From the setting change scenario ID field 240A, the group ID field 240B, and the processing field 240C. Composed.
  • the setting change scenario is information for specifying a scenario to be changed.
  • the setting change scenario ID field 240A for example, information “2” is stored as an identifier for uniquely identifying the scenario to be changed.
  • the group ID field 240B stores an identifier for uniquely identifying a group belonging to the setting change scenario.
  • the status is information for specifying the processing status of each group.
  • the processing field 240C for example, when the group # 1 is being processed, “processing in progress” is stored as information for specifying the processing state of each group, and the processing of the group # 21 has succeeded. In this case, “success” is stored.
  • the setting change group status management table 250 is a table stored in the storage apparatus 204 and the buffer 220, and includes a group ID field 250A, a component ID field 250B, and a processing field 250C. Is done.
  • the group is information for specifying a group whose setting is to be changed.
  • information “1” is stored as an identifier for uniquely identifying the group whose setting is to be changed.
  • the component ID field 250B stores an identifier for uniquely identifying a component belonging to the group whose setting is to be changed.
  • the status is information for specifying the processing status of the component belonging to each group.
  • processing field 250C for example, when the component # 7 belonging to the group # 1 is being processed, “processing in progress” is stored as information for specifying the processing state of the component belonging to each group. When the processing of the # 4 component belonging to the # 1 group is successful, “success” is stored.
  • the setting change component status management table 260 is a table stored in the storage device 204 and the buffer 220. From the component ID field 260A, the setting content ID field 260B, and the processing field 260C. Composed.
  • the component is the change target component that is the target of the setting change.
  • information “1” is stored as an identifier for uniquely identifying the change target component that is the target of the setting change.
  • the setting content ID field 260B for example, “4” is stored as information for specifying the setting content of the setting change information set in the change target component.
  • the status is information that identifies the processing status of the setting content of the setting change information set in the change target component.
  • the setting content “4” of the setting change information set in the component # 7 is set as information for specifying the processing state of the setting content of the setting change information set in the change target component.
  • “Success” is stored when the process of “12” is successful, and when the process of setting content “34” of the setting change information set in the component of # 7 is being processed, “ “Processing” is stored.
  • a new setting information table 270 is a table stored in the storage device 204 and the buffer 220, and is used for collecting and managing setting change information newly set for each change target component.
  • the table includes a setting change information field 270A.
  • a plurality of new setting information tables 270 exist for each change target component.
  • the setting change information is information indicating the setting contents of each change target component that is a new setting change target.
  • the setting change information field 270A stores a plurality of setting contents related to setting change information that are set in a change target component that is a new setting change target. For example, in the setting change information field 270A, “setting content 4”, “setting content 12”, and “setting content 34” are stored as information specifying the setting content of the component # 7. Also, each setting content entry has an identifier for identifying the contents of each setting content. For example, the “setting content 4” entry stores information “4”, and the “setting content 12” entry stores information. The information “2” is stored, and the information “6” is stored in the entry “setting content 34”.
  • the server 200 is a master server that manages the operation of each slave system 30 and manages setting information set in each slave system 30, and is an element that operates on the server 300 of each slave system 30.
  • the server 200 manages a plurality of change target components by dividing them into a plurality of groups according to the processing contents of the setting change process or the function of each change target component.
  • FIG. 5 is a configuration diagram of a table managed by each slave system.
  • a setting change version table 350 is a table stored in the storage device 304 and the buffer 330 of each slave system 30, and includes a version ID field 350A, a last use date / time field 350B, and setting change information. It consists of a field 350C. That is, the setting change version table 350 is configured as a table for managing setting information history by version, and setting change management information 306 is recorded in this table.
  • Version is information that identifies the history of setting information that is subject to setting changes.
  • version ID field 350A for example, information “1” is stored as an identifier for specifying a history of setting information to be changed.
  • the last use date and time is information specifying the last date and time when the setting information to be changed is used.
  • last use date / time field 350B information for specifying the last date / time when the setting information to be changed is used, for example, when the last date / time is 0:00 on January 1, 2000, “ “2000/1/1 0:00” is stored.
  • the setting change information is information indicating the setting contents of the setting change information that is the target of the setting change.
  • the setting change information field 350C stores a plurality of setting contents, for example, “setting contents 1” to “setting contents 45”.
  • Each setting content entry stores information “4” in the “setting content 4” entry as an identifier for identifying the contents of each setting content corresponding to each version. "2" information is stored in the "" entry, and information "6" is stored in the "setting content 45" entry.
  • the target component setting information table 360 is a table stored in the storage device 304 and the buffer 330 of each slave system 30, and is a table for managing the setting information 307 set for each component. Is composed of a setting change information field 360A.
  • the setting change information is information indicating the setting contents of the change target component that is the target of the setting change.
  • a plurality of setting contents for example, “setting contents 1” to “setting contents 45” are stored as information for specifying the setting contents of the change target component to be changed.
  • Each setting content entry stores information “4” in the “setting content 1” entry and “2” in the “setting content 2” entry as an identifier for specifying the contents of each setting content.
  • Information is stored, and information “6” is stored in the entry “setting content 45”.
  • FIG. 6 is a flowchart for explaining the processing of the distribution transaction management unit.
  • the operation administrator operates the management terminal 50 and inputs a scenario to be changed or setting change information to the server 200
  • the setting change process according to the input scenario is performed.
  • the CPU 203 starts by activating the distribution transaction management unit 212 of the memory 201.
  • the distribution transaction management unit 212 searches the buffer 220 based on the input information input from the management terminal 50, and refers to the setting change scenario information table 230 in which there is a scenario to be changed.
  • the scenario to be changed and the setting change information newly set for each component are included.
  • the instruction information for instructing execution of the setting change process according to the setting change information is transferred to each server 300, and among the servers 300 that have received the instruction information, there are a plurality of change target components belonging to the scenario to be changed.
  • the setting change commit unit 311 of the existing server 300 is executed (S10).
  • the distribution transaction management unit 212 determines that the scenario whose setting is to be changed is the scenario # 2 from the input information input from the management terminal 50, and the component whose setting is newly changed is the component # 7. If it is determined that the setting change information is included in the new setting information table 270 as the setting change information set for the component # 7, including the scenario # 2 as the scenario to be changed.
  • the instruction information including “setting contents 4”, “setting contents 12”, and “setting contents 34” is transferred to each server 300, and setting change processing according to the setting change information is instructed.
  • the distribution transaction management unit 212 fetches the management result of the setting change management unit 310 belonging to the server 300 that has executed the setting change processing, and the processing of the setting change commit unit 311 belonging to the setting change management unit 310 ends normally. If it is determined that the process has been completed normally, it is determined whether or not all the processes have been completed for the scenario whose setting is to be changed (S12). For example, when the scenario subject to setting change is the scenario # 2, the distribution transaction management unit 212 performs processing for all components recorded in the setting change scenario information table 230 in which the scenario # 2 exists. It is determined whether or not it has been completed.
  • step S12 determines in step S12 that all the processes have not been completed, the process returns to step S11, repeats the processes in steps S11 to S12, and all the processes are completed in step S12. If it is determined, the process in this routine is terminated.
  • step S11 if it is determined in step S11 that the process of the setting change commit unit 311 has not ended normally, that is, the process belongs to the scenario that is the target of the setting change, and the component belongs to any group. If the setting change process does not end normally, the server 300 of the slave system 30 that includes a component that belongs to any group and that has failed in the setting change process is specified, and the setting change management unit that belongs to the specified server 300 310 is instructed to perform setting change rollback processing, that is, processing for returning the setting information set to the component for which the setting change processing has failed to the original setting information in units of groups (S13). Exit.
  • the server 300 manages a plurality of change target components by dividing them into a plurality of groups according to the processing contents of the setting change process or the function of each change target component. Further, when the setting change process for at least one change target component among the setting change processes fails, the server 300 changes the change target component belonging to the same group as the change target component for which the setting change process has failed, for example, # 7, A rollback process is executed for each change target component of # 4 and # 9 in units of groups (group units of # 1).
  • FIG. 7 is a flowchart for explaining the processing of the setting change commit unit. This process is started when the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
  • the setting change management unit 310 when the setting change management unit 310 that has received an instruction from the distribution transaction management unit 212 of the master system 20 activates the setting change commit unit 311, the setting change commit unit 311 passes through the setting target component unit 320. Then, the system stop unit 321 is executed to stop the component to be changed (S20). Thereafter, the setting change commit unit 311 receives the execution state of the system stop unit 321 via the setting target component unit 320, and determines whether or not the system stop unit 321 has ended normally (S21).
  • step S21 If the setting change commit unit 311 obtains a negative determination result in step S21, that is, if the system stop unit 321 determines that it does not end normally, the setting change commit unit 311 proceeds to the process of step S29, and in step S21, the system change
  • the setting change unit 322 is executed via the setting target component unit 320 (S22). At this time, the setting change unit 322 starts setting change processing for the change target component according to the setting change information recorded in the new setting information table 270 and transferred from the master system 20 to the slave system 30. .
  • the setting change commit unit 311 uses the existing setting information recorded in the setting information 307 of the storage apparatus 304, for example, the setting contents recorded in the target component setting information table 360, as the setting change management information 306 of the storage apparatus 304.
  • the setting change version table 350 is added and saved (S23), and then the execution state of the setting change unit 322 is received via the setting target component unit 320, and the setting change unit 322 is normally terminated. It is determined whether or not (S24).
  • step S24 If the setting change commit unit 311 obtains a negative determination result in step S24, that is, if the setting change unit 322 determines that the processing does not end normally, the setting change commit unit 311 proceeds to the process of step S29, and the setting change commit unit 311 sets in step S24. If the change unit 322 determines that the setting has been completed normally, that is, if the setting content of the setting change information is reflected on the change target component and the setting change processing for the change target component has been completed normally, The setting check unit 323 is executed via the target component unit 320 (S25). At this time, the setting check unit 323 executes a check of the processing result of the setting change process for the change target component, for example, a check for a grammatical error or a semantic error.
  • the setting change commit unit 311 receives the execution state of the setting check unit 323 via the setting target component unit 320, and determines whether or not the setting check unit 323 has ended normally (S26).
  • step S26 the setting change commit unit 311 determines that the setting check unit 323 has ended normally, that is, if the setting change processing check for the change target component has ended normally, the setting target component unit 320, the system activation unit 324 is executed (S27), and then the setting change process for the change target component is successful for the distribution transaction management unit 212 of the master system 20 via the setting change management unit 310. This is notified (S28), and the processing in this routine is terminated.
  • step S26 if the setting change commit unit 311 obtains a negative determination result in step S26, that is, if the setting check unit 322 determines that the setting change processing check for the change target component does not end normally, The process proceeds to step S29.
  • step S29 the setting change commit unit 311 notifies the distribution transaction management unit 212 of the master system 20 through the setting change management unit 310 that the setting change processing for the change target component has failed, and then Then, the processing in this routine is terminated.
  • the distribution transaction management unit 212 notifies the operation manager of the success or failure of the setting change process for the change target component via the management terminal 50.
  • FIG. 8 is a flowchart for explaining the processing of the setting change rollback unit in the slave system.
  • the CPU 303 activates the setting change rollback unit 312 via the setting change management unit 310 based on the determination result of the setting change commit unit 311 that has determined that the setting change processing for the change target component has failed. Start by doing.
  • the setting change rollback unit 312 refers to the setting change version table 350 belonging to the setting change management information 306 stored in the buffer 330 and the target component setting information table 360 belonging to the setting information 307, and changes target component Set the setting contents corresponding to the version of the setting change information set in, for example, the setting contents of the setting change information belonging to the version # 1 (setting contents corresponding to the setting contents of the newly set setting change information)
  • the setting change unit 322 is executed via the change target component unit 320 based on the acquired setting content (setting content before setting change), which is acquired from the target component setting information table 360 in which the setting content before change is recorded. (S40).
  • the setting change unit 322 executes rollback processing for each change target component on the basis of the setting contents before the setting change (original setting contents), and the setting contents for the change target component. Is restored to the state before the setting change in group units to ensure consistency.
  • the setting change rollback unit 312 receives the processing result of the setting change unit 322 via the change target component unit 320 (S41), and on the condition that the processing of the setting change unit 322 is successful, the change target component
  • the system activation unit 324 is executed via the unit 320 (S42), and then the processing in this routine is terminated.
  • the change target component is activated in a state where the setting information is returned to the group unit before the setting change.
  • the server 300 of each slave system 30 has received instruction information from the master server 200 that is processing for a plurality of change target components and instructing execution of setting change processing according to the setting change information.
  • a setting change process according to the setting change information is executed for the plurality of change target components, and the setting change for at least one change target component among the setting change processes
  • the process fails, two or more change target components having relevance with the change target component for which the setting change process has failed are grouped as change target components belonging to the same group, and Set in two or more components to be changed
  • the setting change information configured as a slave server to perform a rollback process in groups to return to the original setting information set before receiving the indication information.
  • the rollback process is executed for the change target component in the group unit, and the setting information for the change target component is changed in the group unit. Since the previous state is restored, consistency can be ensured, and as a result, the load on the operation manager can be reduced and the system downtime can be reduced. Furthermore, even after starting the operation of the distributed system 10 after returning the setting information for the change target component to the state before the setting change in the group unit, the risk of the operation of the distributed system 10 being stopped can be reduced. The reliability of the operation of the distributed processing system 10 can be improved.
  • each slave system is arranged with a test component unit as a test program having the same function as the component unit to be changed, and the other configuration is the same as that of the first embodiment.
  • FIG. 9 is a configuration diagram of hardware resources and software resources of the slave system in the second embodiment.
  • a test component unit 340 as a test program having the same function as the change target component unit 320 is constructed in the memory 301. Similar to the change target component unit 320, the test component unit 340 includes a system stop unit 341, a setting change unit 342, a setting check unit 343, and a system activation unit 344.
  • FIG. 10 is a flowchart for explaining the processing of the distribution transaction management unit in the second embodiment. This process is started when the CPU 203 activates the distribution transaction management unit 212 of the memory 201.
  • the distribution transaction management unit 212 performs the same processing as step S10 to step S12 in FIG. 6 except that in step S50 to step S52, the setting change commit unit 311 is executed for the test component unit 340. Is executed, and instead of the setting change rollback process, the execution of the setting change commit unit 311 for the test component unit 340 is terminated (S57). The routine processing is terminated.
  • the distribution transaction management unit 212 executes the same processing as in steps S10 to S13 in FIG. 6 in steps S53 to S56.
  • the distribution transaction management unit 212 can execute the setting change commit unit 311 for the test component unit 340 and the setting change commit unit 311 for the change target component unit 320.
  • FIG. 11 is a flowchart for explaining the process of the setting change commit unit in the second embodiment. This process is the specific contents of steps S50 and S53 in FIG. 10, and the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20. Be started by.
  • steps S60 to S68 are processes for executing the setting change commit unit 311 for the test component unit 340.
  • the setting change management unit 310 activates the setting change commit unit 311, and thereafter
  • the setting change commit unit 311 activates the test component unit 340, and then the test component unit 340 sequentially activates the system stop unit 341, the setting change unit 342, the setting check unit 343, and the system activation unit 344. Is the same as the processing in steps S20 to S29 in FIG.
  • step S67 or step S68 the setting change commit unit 311 determines whether or not there has been a process start instruction from the distribution transaction management unit 212 (S69), and if a negative determination result is obtained in step S69, When the process in this routine is finished and a positive determination result is obtained in step S69, the process proceeds to step S70.
  • the setting change commit unit 311 executes the system stop unit 321 via the setting target component unit 320 to stop the change target component (S70). Thereafter, the setting change commit unit 311 receives the execution result of the system stop unit 321 via the setting target component unit 320 (S71), and on condition that the processing of the system stop unit 321 has ended normally. Similar to step S22 of FIG. 7, the setting change unit 322 is executed via the setting target component unit 320 (S72). Thereafter, the setting change commit unit 311 receives the execution result of the setting change unit 322 via the setting target component unit 320 (S73), and on condition that the processing of the setting change unit 322 has ended normally. Similar to step S27 in FIG. 7, the system activation unit 324 is executed via the setting target component unit 320 (S74).
  • the setting change commit unit 311 performs the distribution transaction of the master system 20 via the setting change management unit 310 as in step S28 in FIG.
  • the management unit 212 is notified that the setting change process for the change target component has been successful (S75), and the process in this routine is terminated.
  • FIG. 12 is a flowchart for explaining the processing of the setting change rollback unit in the second embodiment. This process is the specific content of step S56 in FIG. 10, and the CPU 303 performs setting change management based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312 via the unit 310.
  • the setting change rollback unit 312 executes the same processing as the processing in steps S40 to S42 in FIG. 8 in steps S80 to S82. Also in this case, the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). Execute this to return the setting contents for the change target component to the state before the setting change for each group and ensure consistency.
  • the same effect as that of the first embodiment can be obtained, and the setting change process for the test target component is executed before the setting change process for the change target component, thereby changing the setting for the change target component. It is possible to predict whether or not the process will be successful, and it is possible to check the grammar and the like in the setting information before the setting change process for the change target component.
  • the operation test unit 213 is arranged in the server 200 of the master system 20 and the application execution unit 325 is arranged in the server 300 of each slave system 30.
  • Other configurations are the same as those in the first embodiment. is there.
  • FIG. 13 is a configuration diagram of hardware resources and software resources of the master system in the third embodiment.
  • an operation test management unit 213 is built in the operation management unit 210 of the memory 201, and other configurations are the same as those in the first embodiment.
  • the operation test management unit 213 is configured as a program that executes an operation test of each slave system 30.
  • FIG. 14 is a configuration diagram of hardware resources and software resources of the slave system in the third embodiment.
  • an application execution unit 325 is built in the change target component unit 320 of the memory 301, and other configurations are the same as those in the first embodiment.
  • the application execution unit 325 is an application program that runs on the server 300, and is configured as an application program for running the change target component.
  • FIG. 15 is a flowchart for explaining processing of the distribution transaction management unit and the operation test management unit in the third embodiment.
  • the distribution transaction management unit 212 executes the same processing as that in steps S10 to S13 in FIG. 6 in steps S90 to S92 and S95.
  • step S92 when an affirmative determination result is obtained in step S92, that is, when all processing is completed, the distribution transaction management unit 212 activates the operation test management unit 213, and the application of the slave system 30 including the change target component.
  • the operation test management unit 213 is executed (S93).
  • the operation test management unit 213 instructs the setting change management unit 310 belonging to the server 300 of the slave system 30 including the change target component to perform an operation test by the application execution unit 325. That is, the master server 200 transfers instruction information for instructing an operation test for the change target component to the server 300 of each slave system 30.
  • the setting change management unit 310 of the server 300 that has received this instruction information activates the application execution unit 325 via the change target component unit 320.
  • the application execution unit 325 operates the change target component and executes an operation test of the change target component.
  • the change target component is an application program that executes data analysis processing
  • the application execution unit 325 executes an operation test of the data analysis processing application program whose setting has been changed.
  • the distribution transaction management unit 212 fetches the result of the operation test by the application execution unit 325 from the operation test management unit 213 belonging to the operation management unit 210, and determines whether or not the operation test has ended normally (S94). ), If a positive determination result is obtained in step S94, the processing in this routine is terminated, and if a negative determination result is obtained in step S94, the change in which the operation test has failed as in step S13 of FIG.
  • the setting change management unit 310 belonging to the server 300 of the slave system 30 including the target component has the setting change rollback process, that is, the setting information set for the change target component that failed the operation test as the original setting information for each group. Is instructed to return to (S95), and the processing in this routine is terminated.
  • the application execution unit 325 of the server 300 executes an operation test for the plurality of change target components reflecting the setting change information on the condition that the setting change processing for the plurality of change target components is successful.
  • the setting change rollback unit 312 of the server 300 selects two or more change target components having relevance to the change target component for which the operation test has failed.
  • the change target components belonging to the same group are grouped together, and the roll back process is executed in units of the change target components belonging to the same group.
  • the server 300 executes the setting change check based on the actual operation of the subsystem 30 by executing the operation test of the change target component after the setting change processing for the change target component is successful. Can do.
  • FIG. 16 is a flowchart for explaining the process of the setting change commit unit according to the third embodiment. This process is started when the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
  • the setting change commit unit 311 performs the same processes as steps S20 to S29 in FIG. 7 in steps S100 to S109.
  • FIG. 17 is a flowchart for explaining the processing of the setting change rollback unit in the third embodiment. This process is the specific content of step S95 in FIG. 15, and the CPU 303 performs setting change management based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312 via the unit 310.
  • the setting change commit unit 311 executes the system stop unit 321 via the setting target component unit 320 to stop the change target component (S120). Thereafter, the setting change commit unit 311 receives the execution result of the system stop unit 321 via the setting target component unit 320 (S121), and on condition that the processing of the system stop unit 321 has ended normally. Similar to step S40 in FIG. 8, the setting change unit 322 is executed via the setting target component unit 320 (S122). Thereafter, the setting change commit unit 311 executes the same processing as in steps S41 to S42 in FIG. 8 in steps S123 to S124.
  • the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). To return the setting contents for the change target component to the state before the setting change for each group, and ensure consistency.
  • the same effect as in the first embodiment can be obtained, and after the setting change process for the change target component is successful, the operation test of the change target component is executed, so that the subsystem 30 is actually operated. It is possible to execute a setting change check based on the operation of. In this case, since the operation test is included in the atomic processing, it is possible to confirm the setting change that guarantees the reliability of the subsystem 30.
  • the operation test management unit 213 is arranged in the memory 201 of the master system 20, and the test component unit 340 having the same function as the change target component unit 320 is arranged in the memory 301 of each slave system 30, The same as in the third embodiment.
  • FIG. 18 is a configuration diagram of hardware resources and software resources of the slave system according to the fourth embodiment.
  • a change target component unit 320 having a system stop unit 321, a setting change unit 322, a setting check unit 323, a system activation unit 324, and an application execution unit 325 is constructed.
  • a test component unit 340 as a test program having the same function as that of the change target component unit 320 is constructed. Similar to the change target component unit 320, the test component unit 340 includes a system stop unit 341, a setting change unit 342, a setting check unit 343, a system activation unit 344, and an application execution unit 345.
  • FIG. 19 is a flowchart for explaining the processing of the distribution transaction management unit in the fourth embodiment. This process is started when the CPU 203 activates the distribution transaction management unit 212 of the memory 201.
  • the distribution transaction management unit 212 executes the same processes as in steps S50 to S52 and step S57 of FIG. 10 in steps S130 to S133 and step S139, and in steps S136 to S138, the process shown in FIG. The same processing as step S54 to step S56 is executed.
  • step S134 the distribution transaction management unit 212 activates the operation test management unit 213 and executes the operation test of the test component on the application execution unit 345 of the server 300 belonging to the slave system 30 including the test component.
  • the operation test management unit 213 instructs the setting change management unit 310 belonging to the server 300 of the slave system 30 including the test component to perform an operation test by the application execution unit 345.
  • the setting change management unit 310 activates the application execution unit 345 via the test component unit 340, and the application execution unit 345 operates the test component and executes an operation test of the test component.
  • the application execution unit 345 executes an operation test of the data analysis processing test application program.
  • the distribution transaction management unit 212 fetches the result of the operation test by the application execution unit 345 from the operation test management unit 213, determines whether or not the operation test has ended normally (S135), and affirmative in step S135 If the determination result is obtained, the process proceeds to step S136. If the determination result is negative in step S135, the process in this routine is terminated.
  • the slave server 300 when the slave server 300 receives instruction information for instructing execution of the setting change process according to the setting change information from the master server 200, the slave server 300 applies to a plurality of test components corresponding to a plurality of change target components. Then, the setting change process according to the setting change information is executed, the setting change process for the plurality of change target components is executed on the condition that the setting change process for the plurality of test components is successful, and the master server 200 When the instruction information for instructing the execution of the operation test for the plurality of test components is received, the operation test for the plurality of test components reflecting the setting change information is executed.
  • the slave server 300 when the operation test for at least one test component among the operation tests fails, the slave server 300 includes two or more test components having a relationship with the test component for which the operation test has failed in the same group.
  • a rollback process is executed in units of test components that are collected as components and belong to the same group.
  • the server 300 can execute the setting change check based on the test operation of the subsystem 30 by executing the operation test of the test component after the setting change processing for the change target component is successful. it can.
  • the operation test of the setting change target component can be executed after the setting change processing for the change target component is successful.
  • the setting change check based on the actual operation of the subsystem 30 and the setting change check based on the test operation of the subsystem 30 can be executed.
  • FIG. 20 is a flowchart for explaining the process of the setting change commit unit according to the fourth embodiment. This process is the specific contents of steps S130 and S133, and is started when the CPU 303 of the slave system 30 starts the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
  • the process is the specific contents of steps S130 and S133, and is started when the CPU 303 of the slave system 30 starts the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
  • the setting change commit unit 311 performs the same processing as in steps S60 to S75 in FIG. 11 in steps S150 to S165.
  • the setting contents of the setting change information are reflected on the test component, and the setting contents of the setting change information are reflected on the change target component.
  • FIG. 21 is a flowchart for explaining processing of the setting change rollback unit in the fourth embodiment.
  • This process is the specific content of step S138, and the CPU 303 controls the setting change management unit 310 based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312.
  • the setting change rollback unit 312 performs the same processes as steps S120 to S124 of FIG. 17 in steps S170 to S174.
  • the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). To return the setting contents for the change target component to the state before the setting change for each group, and ensure consistency.
  • the same effects as those of the first and second embodiments can be obtained, and after the setting change process for the change target component is successful, the operation test of the test component is executed, so that the subsystem 30 It is possible to execute a setting change check based on the test operation.
  • an operation test of the setting change target component and the test component is executed, so that the setting change check based on the actual operation of the subsystem 30 and the test of the subsystem 30 are performed.
  • a configuration change check based on the operation can be executed. In this case, an atomic process including an operation test using the test component unit 340 can be performed for the setting change check.
  • FIG. 22 is an overall configuration diagram of a distributed processing system using a wide area network as a network.
  • a WAN Wide Area Network
  • the master system 20 and each slave system 30 can be geographically distributed.
  • the slave system 20 can be arranged in Japan, and any of the slave systems 30 can be arranged in the United States.
  • this invention is not limited to the above-mentioned Example, Various modifications are included.
  • the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
  • a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
  • each of the above-described configurations, functions, etc. may be realized by hardware by designing a part or all of them, for example, by an integrated circuit.
  • Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.
  • Information such as programs, tables, and files that realize each function is stored in memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD (Secure Digital) memory card, a DVD ( It can be recorded on a recording medium such as Digital Versatile Disc).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The master server of a master system according to the present invention transfers, to slave servers, instruction information instructing that a setting change process in accordance with setting change information be performed on a plurality of components to be changed. Upon receiving the instruction information from the master server, each slave server performs the setting change process in accordance with the setting change information on the plurality of components to be changed, wherein if the slave server fails to perform the setting change process on at least one of the components to be changed, then the slave server performs a rollback process on at least two components to be changed that belong to the same group as the at least one component to be changed, on which the slave server has failed to perform the setting change process, said rollback process resetting the at least two components to be changed back to the original setting information that was set for the components to be changed before the instruction information was received.

Description

分散処理システム及びその運用方法Distributed processing system and operation method thereof
　本発明は、マスタシステムと複数のスレーブシステムを含む分散処理システム及びその運用方法に関する。 The present invention relates to a distributed processing system including a master system and a plurality of slave systems, and an operation method thereof.
　ＩＴ（Information　Technology）システムの大規模化、複雑化に伴ってそのシステムを効率的に管理する、運用管理システムの需要が高まってきている。運用管理システムとは、ＩＴシステムが正常に稼働し続ける状態を維持するためのシステムである。この運用管理システムは、ＩＴシステムに異常がないかの確認、メンテナンス、老朽化した設備の更新、障害に備えたデータなどの保全、障害時の復旧作業などを行う。この際、運用管理システムでは、設定変更処理が行われる。 As the IT (Information Technology) system becomes larger and more complicated, there is an increasing demand for an operation management system that efficiently manages the system. The operation management system is a system for maintaining a state where the IT system continues to operate normally. This operation management system checks whether there is an abnormality in the IT system, performs maintenance, updates aging equipment, preserves data for failure, recovers from failure, and the like. At this time, a setting change process is performed in the operation management system.
　運用管理システムにおける設定変更処理では、様々な理由で失敗することがある。例えば、ネットワーク障害が起きた場合、設定変更情報に文法エラー、意味エラー等の設定情報のバグが含まれている場合、設定変更反映後システム間の設定互換の関係でシステムが動作しない場合などである。こういった場合に設定変更の信頼性を確保するため、特許文献１では、設定変更の処理を設定対象単体でロールバックし、以前適用した設定状態に戻す処理が提案されている。 The setting change processing in the operation management system may fail for various reasons. For example, when a network failure occurs, the setting change information includes bugs in the setting information such as syntax errors and semantic errors, and the system does not operate due to the setting compatibility between the systems after the setting change is reflected. is there. In such a case, in order to ensure the reliability of the setting change, Patent Document 1 proposes a process of rolling back the setting change process by a single setting target and returning to the previously applied setting state.
　具体的には、設定変更の命令を出すマネージャと、設定対象に導入されて、設定変更を管理すると共に、設定対象の設定コマンドを用いて設定変更を行うアプリケーションを有し、設定対象に導入されたアプリケーションは、設定毎に設定情報をバージョン管理し、設定対象の既存のコマンドを元に設計されたロールバック処理を実行する。設定変更の失敗が起こった場合、設定対象に導入されたアプリケーションがロールバックを実行し、設定対象単体が以前適用した設定状態に戻る。 Specifically, it has a manager that issues a setting change command and an application that is introduced to the setting target and manages the setting change and changes the setting using the setting target setting command. The application manages version of the setting information for each setting, and executes a rollback process designed based on the existing command to be set. If a configuration change failure occurs, the application installed on the setting target performs a rollback, and the setting target alone returns to the previously applied setting state.
米国特許出願公開第2009/0216867号明細書US Patent Application Publication No. 2009/0216867
　しかしながら、特許文献１に記載された処理では、設定変更失敗時、設定対象単位でロールバックをするため、処理や機能で見たときのグループ単位での整合性が取れない。この場合、運用管理者が設定変更時のエラーを修正し、グループ単位で整合性を取ることになる。このような対応は、運用管理対象システムの大規模、複雑化にしたがい運用管理者の工数増大につながる。また、設定変更エラーの原因究明が困難な場合、システム復旧のためのダウンタイム増大する傾向がある。 However, in the process described in Patent Document 1, since the rollback is performed in the setting target unit when the setting change is unsuccessful, the consistency in the group unit when viewed in the process or function cannot be obtained. In this case, the operation administrator corrects the error at the time of setting change, and consistency is obtained in units of groups. Such a response leads to an increase in the number of operations managers as the operation management target system becomes larger and more complex. Further, when it is difficult to investigate the cause of a setting change error, there is a tendency that downtime for system recovery increases.
　本発明の目的は、複数の変更対象のうち少なくも１つの変更対象に対する設定変更処理が失敗した場合、設定変更処理が失敗した変更対象と関連性を有する２以上の変更対象に対して、当該２以上の設定対象に設定された設定情報を設定変更処理前の状態に戻すことができる分散処理システム及びその運用方法を提供することにある。 The object of the present invention is to, when a setting change process for at least one change object among a plurality of change objects fails, for two or more change objects related to the change object for which the setting change process has failed, An object of the present invention is to provide a distributed processing system capable of returning setting information set to two or more setting targets to a state before setting change processing, and an operation method thereof.
　上記課題を解決するために、本発明は、マスタ用サーバから転送された設定情報に従ってデータ処理を実行するスレーブ用サーバは、複数の変更対象コンポーネントに対する処理であって、設定変更情報に従った設定変更処理の実行を指示する指示情報を前記マスタ用サーバから受信した場合、前記複数の変更対象コンポーネントが存在することを条件に、前記複数の変更対象コンポーネントに対して前記設定変更情報に従った設定変更処理を実行し、前記設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、当該設定変更処理が失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを纏め、当該纏められた２以上の変更対象コンポーネントに対して、前記纏められた２以上の変更対象コンポーネントに設定された設定変更情報を、前記指示情報を受信する前に設定された元の設定情報に戻すためのロールバック処理を実行することを特徴とする。 In order to solve the above-described problem, the present invention provides a slave server that executes data processing according to setting information transferred from a master server, which is processing for a plurality of change target components, and is configured according to setting change information. When the instruction information for instructing execution of the change process is received from the master server, the setting according to the setting change information for the plurality of change target components on condition that the plurality of change target components exist When the change process is executed and the setting change process for at least one change target component among the setting change processes fails, the two or more change target components related to the change target component for which the setting change process has failed are collected. , For the two or more change target components collected, Two or more change setting change information set in the target component, which is, and executes a rollback process to restore the original settings information set prior to receiving the indication information.
　本発明によれば、複数の変更対象のうち少なくも１つの変更対象に対する設定変更処理が失敗した場合、設定変更処理が失敗した変更対象と関連性を有する２以上の変更対象に対して、当該２以上の設定対象に設定された設定情報を設定変更処理前の状態に戻すことができる。 According to the present invention, when the setting change process for at least one change object among a plurality of change objects fails, the two or more change objects related to the change object for which the setting change process has failed Setting information set to two or more setting targets can be returned to the state before the setting change process.
本発明の一実施例を示す分散処理システムの全体構成図である。1 is an overall configuration diagram of a distributed processing system showing an embodiment of the present invention. マスタシステムのハードウェア資源とソフトウェア資源の構成図である。It is a block diagram of the hardware resource and software resource of a master system. スレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。It is a block diagram of the hardware resource and software resource of a slave system. マスタシステムで管理されるテーブルの構成図である。It is a block diagram of the table managed by a master system. スレーブシステムで管理されるテーブルの構成図である。It is a block diagram of the table managed by a slave system. 配布トランザクション管理部の処理を説明するためのフローチャートである。It is a flowchart for demonstrating the process of a distribution transaction management part. 設定変更コミット部の処理を説明するためのフローチャートである。It is a flowchart for demonstrating the process of a setting change commit part. スレーブシステムにおける設定変更ロールバック部の処理を説明するためのフローチャートである。It is a flowchart for demonstrating the process of the setting change rollback part in a slave system. 実施例２におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。It is a block diagram of the hardware resource and software resource of the slave system in Example 2. 実施例２における配布トランザクション管理部の処理を説明するためのフローチャートである。10 is a flowchart for explaining processing of a distributed transaction management unit according to the second embodiment. 実施例２における設定変更コミット部の処理を説明するためのフローチャートである。12 is a flowchart for explaining processing of a setting change commit unit according to the second embodiment. 実施例２における設定変更ロールバック部の処理を説明するためのフローチャートである。10 is a flowchart for explaining processing of a setting change rollback unit according to the second embodiment. 実施例３におけるマスタシステムのハードウェア資源及びソフトウェア資源の構成図である。FIG. 10 is a configuration diagram of hardware resources and software resources of a master system in Embodiment 3. 実施例３におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。FIG. 10 is a configuration diagram of hardware resources and software resources of a slave system according to a third embodiment. 実施例３における配布トランザクション管理部と動作テスト管理部の処理を説明するためのフローチャートである。10 is a flowchart for explaining processing of a distribution transaction management unit and an operation test management unit in the third embodiment. 実施例３における設定変更コミット部の処理を説明するためのフローチャートである。12 is a flowchart for explaining processing of a setting change commit unit in the third embodiment. 実施例３における設定変更ロールバック部の処理を説明するためのフローチャートである。12 is a flowchart for explaining processing of a setting change rollback unit according to the third embodiment. 実施例４におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。FIG. 10 is a configuration diagram of hardware resources and software resources of a slave system according to a fourth embodiment. 実施例４における配布トランザクション管理部の処理を説明するためのフローチャートである。15 is a flowchart for explaining processing of a distributed transaction management unit according to the fourth embodiment. 実施例４における設定変更コミット部の処理を説明するためのフローチャートである。15 is a flowchart for explaining processing of a setting change commit unit in the fourth embodiment. 実施例４における設定変更ロールバック部の処理を説明するためのフローチャートである。14 is a flowchart for explaining processing of a setting change rollback unit according to the fourth embodiment. ネットワークに広域ネットワークを用いた分散処理システムの全体構成図である。1 is an overall configuration diagram of a distributed processing system using a wide area network as a network.
　以下、本発明の一実施例を図面に従って説明する。 Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
　本実施例は、シナリオに変更対象コンポーネントに対する設定変更情報の設定内容に従って、シナリオに属する複数の設定変更処理を実行し、いずれかの設定変更処理が失敗した場合、設定変更処理が失敗した変更対象コンポーネントに設定された設定情報をグループ単位で元の設定情報に戻すものである。 In this example, according to the setting contents of the setting change information for the change target component in the scenario, if multiple setting change processes belonging to the scenario are executed and one of the setting change processes fails, the change target for which the setting change process has failed The setting information set in the component is returned to the original setting information in units of groups.
　図１は、本発明の一実施例を示す分散処理システムの全体構成図である。図１において、分散処理システム１０は、マスタシステム２０と、複数（＃０～＃４）のスレーブシステム３０と、ネットワーク４０と、管理端末５０から構成される。マスタシステム２０と各スレーブシステム３０は、ネットワーク４０を介して相互に接続され、マスタシステム２０は、管理端末５０に接続される。なお、ネットワーク４０は、例えば、ＬＡＮ（Local　Area　Network）を用いて構成される。 FIG. 1 is an overall configuration diagram of a distributed processing system showing an embodiment of the present invention. In FIG. 1, the distributed processing system 10 includes a master system 20, a plurality of (# 0 to # 4) slave systems 30, a network 40, and a management terminal 50. The master system 20 and each slave system 30 are connected to each other via the network 40, and the master system 20 is connected to the management terminal 50. The network 40 is configured using, for example, a LAN (Local Area Network).
　＃０～＃４のスレーブシステム３０は、それぞれ複数のサーバ（サーバ群）３００を有し、各サーバ３００では、ネットワーク４０経由でユーザ端末（図示せず）に対して、データの分析処理等のサービスを提供するアプリケーションプログラム（図示せず）が稼働する。マスタシステム２０は、各スレーブシステム３０の運用管理を実施すると共に、各サーバ３００上で稼働するアプリケーションプログラム等の設定情報を変更するための処理を行うサーバ２００を有する。ただし、本実施例では、スレーブシステム３０は、＃０～＃４のスレーブシステム３０で構成されているが、スレーブシステム３０の数は、一例であり、実際は、ユーザに提供するサービスによって増減する。 Each of the slave systems 30 of # 0 to # 4 has a plurality of servers (server groups) 300, and each server 300 performs a data analysis process or the like on a user terminal (not shown) via the network 40. An application program (not shown) that provides a service operates. The master system 20 includes a server 200 that performs operation management of each slave system 30 and performs processing for changing setting information such as an application program running on each server 300. However, in the present embodiment, the slave system 30 is configured by the slave systems 30 of # 0 to # 4. However, the number of slave systems 30 is an example, and actually increases or decreases depending on the service provided to the user.
　マスタシステム２０のサーバ２００は、メモリ２０１と、Ｉ／Ｏインタフェース２０２と、ＣＰＵ（Central　Processing　Unit）２０３及びストレージ装置２０４を有し、各部が内部バス２０５を介して相互接続され、サーバ２００が、管理端末５０に接続される。メモリ２０１は、各種プログラムやデータを格納する記憶装置として構成される。Ｉ／Ｏインタフェース２０２は、ネットワーク４０を介して各スレーブシステム３０の各サーバ３００と情報の送受信を行う入出力インタフェース装置として構成される。ＣＰＵ２０３は、サーバ２００全体を統括制御する制御装置として構成される。ストレージ装置２０４は、各種情報や各種データを記憶する記憶デバイスで構成される。 The server 200 of the master system 20 includes a memory 201, an I / O interface 202, a CPU (Central Processing Unit) 203, and a storage device 204. Each unit is interconnected via an internal bus 205. Connected to the management terminal 50. The memory 201 is configured as a storage device that stores various programs and data. The I / O interface 202 is configured as an input / output interface device that transmits / receives information to / from each server 300 of each slave system 30 via the network 40. The CPU 203 is configured as a control device that performs overall control of the entire server 200. The storage apparatus 204 includes a storage device that stores various types of information and various types of data.
　管理端末５０は、例えば、ＣＰＵ、メモリ、入出力インタフェース等の情報処理資源を備えたコンピュータ装置で構成される。この際、分散処理システム１０を運用管理する運用管理者は、管理端末５０を操作し、マスタシステム２０に対して、分散処理システム１０の設定を変更するための情報を入力する作業を行う。 The management terminal 50 is constituted by a computer device provided with information processing resources such as a CPU, a memory, and an input / output interface, for example. At this time, an operation administrator who operates and manages the distributed processing system 10 operates the management terminal 50 to input information for changing the setting of the distributed processing system 10 to the master system 20.
　図２は、マスタシステムのハードウェア資源とソフトウェア資源の構成図である。図２において、マスタシステム２０におけるサーバ２００のメモリ２０１には、各スレーブシステム３０の運用管理を行うプログラムである運用管理部２１０と、ストレージ装置２０４に保存されている構成情報２０６を格納するためのバッファ２２０が構築される。運用管理部２１０は、各スレーブシステム３０に設定情報の配布を行うためのプログラムである配布管理部２１２を有し、配布管理部２１２は、設定変更情報の適用処理のトランザクション管理を行うプログラムとしての配布トランザクション管理部２１２から構成される。 FIG. 2 is a configuration diagram of hardware resources and software resources of the master system. In FIG. 2, the memory 201 of the server 200 in the master system 20 stores the operation management unit 210 that is a program for managing the operation of each slave system 30 and the configuration information 206 stored in the storage device 204. A buffer 220 is constructed. The operation management unit 210 includes a distribution management unit 212 which is a program for distributing setting information to each slave system 30. The distribution management unit 212 is a program for performing transaction management of setting change information application processing. The distribution transaction management unit 212 is configured.
　なお、運用管理者の操作による情報が、管理端末５０からサーバ２００に入力された場合、入力された情報は、ＣＰＵ２０３によって管理される。この際、ＣＰＵ２０３は、入力された情報、例えば、設定情報を、ストレージ装置２０４の構成情報２０６に記録すると共に、構成情報２０６に記録された情報をバッファ２２０に転送する。この場合、バッファ２２０には、構成情報２０６に属する各種テーブル等の情報が格納される。 In addition, when information by an operation manager operation is input to the server 200 from the management terminal 50, the input information is managed by the CPU 203. At this time, the CPU 203 records the input information, for example, setting information in the configuration information 206 of the storage apparatus 204 and transfers the information recorded in the configuration information 206 to the buffer 220. In this case, the buffer 220 stores information such as various tables belonging to the configuration information 206.
　図３は、スレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。図３において、各スレーブシステム３０におけるサーバ３００は、メモリ３０１と、Ｉ／Ｏインタフェース３０２と、ＣＰＵ３０３及びストレージ装置３０４を有し、各部が内部バス３０５を介して相互接続される。メモリ３０１は、各種プログラムやデータを格納する記憶装置として構成される。Ｉ／Ｏインタフェース３０２は、ネットワーク４０を介して、他のスレーブシステム３０の各サーバ３００やマスタシステム２０のサーバ２００と情報の送受信を行う入出力インタフェース装置として構成される。ＣＰＵ３０３は、サーバ３００全体を統括制御する制御装置として構成される。ストレージ装置３０４は、各種情報、例えば、設定変更管理情報３０６及び設定情報３０７や各種データを記憶する記憶デバイスで構成される。 FIG. 3 is a configuration diagram of hardware resources and software resources of the slave system. In FIG. 3, the server 300 in each slave system 30 includes a memory 301, an I / O interface 302, a CPU 303, and a storage device 304, and each unit is interconnected via an internal bus 305. The memory 301 is configured as a storage device that stores various programs and data. The I / O interface 302 is configured as an input / output interface device that transmits / receives information to / from each server 300 of the other slave system 30 and the server 200 of the master system 20 via the network 40. The CPU 303 is configured as a control device that performs overall control of the entire server 300. The storage device 304 includes a storage device that stores various types of information, for example, setting change management information 306, setting information 307, and various types of data.
　メモリ３０１には、プログラムで構成される設定変更管理部３１０及び設定対象コンポーネット部３２０と、各種情報を格納するバッファ３３０が構築される。バッファ３３０には、ストレージ装置３０４から転送された情報として、設定変更管理情報３０６と設定情報３０７が格納される。設定変更管理部３１０は、変更対象コンポーネント部３２０の設定コマンドを管理するプログラムであり、設定変更のコミットを行うプログラムとしての設定変更コミット部３１１と、設定変更コミット部３１１が正常に終了しなかった場合に、設定情報のロールバックを実行するプログラムとしての設定変更ロールバック部３１２から構成される。 In the memory 301, a setting change management unit 310 and a setting target component unit 320 configured by programs, and a buffer 330 for storing various types of information are constructed. The buffer 330 stores setting change management information 306 and setting information 307 as information transferred from the storage device 304. The setting change management unit 310 is a program for managing the setting command of the change target component unit 320, and the setting change commit unit 311 and the setting change commit unit 311 as programs for committing the setting change did not end normally. The configuration change rollback unit 312 as a program for executing the rollback of the configuration information.
　設定対象コンポーネット部３２０は、設定の対象となるプログラムであり、システムを停止するためのプログラムであるシステム停止部３２１と、設定変更を行うプログラムである設定変更部３２２と、設定チェックを行うプログラムである設定チェック部３２３と、システムを起動するためのプログラムであるシステム起動部３２４から構成される。これらのプログラムは、その処理を実行する際に、バッファ３３０に格納された情報を管理する各種テーブルを適宜参照する。 The setting target component unit 320 is a program to be set, and includes a system stop unit 321 that is a program for stopping the system, a setting change unit 322 that is a program for changing settings, and a program for checking settings. A setting check unit 323 and a system activation unit 324 which is a program for activating the system. These programs appropriately refer to various tables for managing information stored in the buffer 330 when executing the processing.
　図４は、マスタシステムで管理されるテーブルの構成図である。図４（Ａ）において、設定変更シナリオ情報テーブル２３０は、ストレージ装置２０４及びバッファ２２０に格納されるテーブルであって、シナリオＩＤフィールド２３０Ａと、処理番号フィールド２３０Ｂと、グループＩＤフィールド２３０Ｃと、コンポーネントＩＤフィールド２３０Ｄ及び設定内容ＩＤフィールド２３０Ｅから構成される。この設定変更シナリオ情報テーブル２３０は、どのグループのどのコンポーネントのどの設定内容をどの順番で変更するかを管理するためのテーブルとして構成され、シナリオの数に応じて複数存在する。 FIG. 4 is a configuration diagram of a table managed by the master system. 4A, the setting change scenario information table 230 is a table stored in the storage apparatus 204 and the buffer 220, and includes a scenario ID field 230A, a process number field 230B, a group ID field 230C, and a component ID. It consists of a field 230D and a setting content ID field 230E. This setting change scenario information table 230 is configured as a table for managing which setting contents of which component of which group are changed in which order, and a plurality of setting changing scenario information tables 230 exist according to the number of scenarios.
　シナリオは、運用管理者が、設定変更の作業を管理するための名称である。シナリオＩＤフィールド２３０Ａには、シナリオを一意に識別するための識別子として、例えば、「２」の情報が格納される。処理番号は、シナリオが、複数の処理で構成される場合、各処理を特定する番号である。処理番号フィールド２３０Ｂには、シナリオの各処理を特定する番号として、例えば、「１」～「１２」の情報が格納される。グループは、シナリオに属する各処理を、その処理内容や機能毎に複数に分類したグループである。グループＩＤフィールド２３０Ｃには、シナリオに属する各処理のグループを一意に識別するための識別子として、例えば、「１」の情報が格納される。 Scenario is a name for the operation manager to manage setting change work. In the scenario ID field 230A, for example, information “2” is stored as an identifier for uniquely identifying the scenario. The process number is a number that identifies each process when the scenario is configured by a plurality of processes. In the process number field 230B, for example, information “1” to “12” is stored as a number for specifying each process of the scenario. The group is a group in which each process belonging to the scenario is classified into a plurality for each process content and function. In the group ID field 230C, for example, information “1” is stored as an identifier for uniquely identifying each processing group belonging to the scenario.
　コンポーネットは、各スレーブストレージ３０に属する要素であって、設定変更の対象となる要素、例えば、スレーブシステム３０のストレージ装置３０４に格納される設定情報３０７や各サーバ３００上で稼働するプログラム等を意味する。コンポーネントＩＤフィールド２３０Ｄには、設定変更の対象となる要素を一意に識別するための識別子として、例えば、「７」の情報が格納される。設定内容は、設定変更の対象となるコンポーネットに対する設定変更情報の設定内容を示す情報である。設定内容ＩＤフィールド２３０Ｅには、変更対象を構成する要素に対する設定変更情報の設定内容を一意に識別するための識別子として、例えば、「４」の情報が格納される。なお、コンポーネットは、各スレーブシステム３０や各スレーブシステム３０に属する各サーバ３００に対応付けされて管理される。 The component is an element belonging to each slave storage 30 and is an element to be changed, for example, setting information 307 stored in the storage device 304 of the slave system 30 or a program running on each server 300. means. In the component ID field 230D, for example, information “7” is stored as an identifier for uniquely identifying the element whose setting is to be changed. The setting content is information indicating the setting content of the setting change information for the component to be changed. In the setting content ID field 230E, for example, information “4” is stored as an identifier for uniquely identifying the setting content of the setting change information for the element constituting the change target. The component is managed in association with each slave system 30 and each server 300 belonging to each slave system 30.
　また、設定変更シナリオ情報テーブル２３０では、処理内容または機能が同一であって、互いに関連するコンポーネント、例えば、＃７、＃４、＃９のコンポーネントが、＃１のグループに属し、＃７のコンポーネントには、設定変更情報の設定内容「４」、「１２」、「３４」が設定され、＃４のコンポーネントには、設定変更情報の設定内容「５６」が設定され、＃９のコンポーネントには、設定変更情報の設定内容「６８」が設定されていることを意味する。 In the setting change scenario information table 230, components having the same processing contents or functions and related to each other, for example, components # 7, # 4, and # 9 belong to the group # 1, and components # 7 The setting contents “4”, “12”, and “34” of the setting change information are set, the setting contents “56” of the setting change information are set for the component # 4, and the setting contents “56” are set for the component # 9. This means that the setting content “68” of the setting change information is set.
　図４（Ｂ）において、設定変更シナリオの状況管理テーブル２４０は、ストレージ装置２０４及びバッファ２２０に格納されるテーブルであって、設定変更シナリオＩＤフィールド２４０Ａと、グループＩＤフィールド２４０Ｂと、処理フィールド２４０Ｃから構成される。 In FIG. 4B, the setting change scenario status management table 240 is a table stored in the storage device 204 and the buffer 220. From the setting change scenario ID field 240A, the group ID field 240B, and the processing field 240C. Composed.
　設定変更シナリオは、設定変更の対象となるシナリオを特定するための情報である。設定変更シナリオＩＤフィールド２４０Ａには、設定変更の対象となるシナリオを一意に識別するための識別子として、例えば、「２」の情報が格納される。グループＩＤフィールド２４０Ｂには、設定変更シナリオに属するグループを一意に識別するための識別子が格納される。状態は、各グループの処理の状態を特定する情報である。処理フィールド２４０Ｃには、各グループの処理の状態を特定する情報として、例えば、＃１のグループが処理中である場合には、「処理中」が格納され、＃２１のグループの処理が成功した場合には、「成功」が格納される。 The setting change scenario is information for specifying a scenario to be changed. In the setting change scenario ID field 240A, for example, information “2” is stored as an identifier for uniquely identifying the scenario to be changed. The group ID field 240B stores an identifier for uniquely identifying a group belonging to the setting change scenario. The status is information for specifying the processing status of each group. In the processing field 240C, for example, when the group # 1 is being processed, “processing in progress” is stored as information for specifying the processing state of each group, and the processing of the group # 21 has succeeded. In this case, “success” is stored.
　図４（Ｃ）において、設定変更グループの状況管理テーブル２５０は、ストレージ装置２０４及びバッファ２２０に格納されるテーブルであって、グループＩＤフィールド２５０Ａと、コンポーネットＩＤフィールド２５０Ｂと、処理フィールド２５０Ｃから構成される。 In FIG. 4C, the setting change group status management table 250 is a table stored in the storage apparatus 204 and the buffer 220, and includes a group ID field 250A, a component ID field 250B, and a processing field 250C. Is done.
　グループは、設定変更の対象となるグループを特定するための情報である。グループＩＤフィールド２５０Ａには、設定変更の対象となるグループを一意に識別するための識別子として、例えば、「１」の情報が格納される。コンポーネットＩＤフィールド２５０Ｂには、設定変更の対象となるグループに属するコンポーネントを一意に識別するための識別子が格納される。状態は、各グループに属するコンポーネントの処理の状態を特定する情報である。処理フィールド２５０Ｃには、各グループに属するコンポーネントの処理の状態を特定する情報として、例えば、＃１のグループに属する、＃７のコンポーネントが処理中である場合には、「処理中」が格納され、＃１のグループに属する、＃４のコンポーネントの処理が成功した場合には、「成功」が格納される。 The group is information for specifying a group whose setting is to be changed. In the group ID field 250A, for example, information “1” is stored as an identifier for uniquely identifying the group whose setting is to be changed. The component ID field 250B stores an identifier for uniquely identifying a component belonging to the group whose setting is to be changed. The status is information for specifying the processing status of the component belonging to each group. In the processing field 250C, for example, when the component # 7 belonging to the group # 1 is being processed, “processing in progress” is stored as information for specifying the processing state of the component belonging to each group. When the processing of the # 4 component belonging to the # 1 group is successful, “success” is stored.
　図４（Ｄ）において、設定変更コンポーネントの状況管理テーブル２６０は、ストレージ装置２０４及びバッファ２２０に格納されるテーブルであって、コンポーネットＩＤフィールド２６０Ａと、設定内容ＩＤフィールド２６０Ｂと、処理フィールド２６０Ｃから構成される。 In FIG. 4D, the setting change component status management table 260 is a table stored in the storage device 204 and the buffer 220. From the component ID field 260A, the setting content ID field 260B, and the processing field 260C. Composed.
　コンポーネットは、設定変更の対象となる変更対象コンポーネントである。コンポーネントＩＤフィールド２６０Ａには、設定変更の対象となる変更対象コンポーネントを一意に識別するための識別子として、例えば、「１」の情報が格納される。設定内容ＩＤフィールド２６０Ｂには、変更対象コンポーネントに設定された、設定変更情報の設定内容を特定する情報として、例えば、「４」が格納される。状態は、変更対象コンポーネントに設定された、設定変更情報の設定内容の処理の状態を特定する情報である。処理フィールド２６０Ｃには、変更対象コンポーネントに設定された、設定変更情報の設定内容の処理の状態を特定する情報として、例えば、＃７のコンポーネントに設定された、設定変更情報の設定内容「４」、「１２」の処理が成功した場合には、「成功」が格納され、＃７のコンポーネントに設定された、設定変更情報の設定内容「３４」の処理が処理中である場合には、「処理中」が格納される。 The component is the change target component that is the target of the setting change. In the component ID field 260A, for example, information “1” is stored as an identifier for uniquely identifying the change target component that is the target of the setting change. In the setting content ID field 260B, for example, “4” is stored as information for specifying the setting content of the setting change information set in the change target component. The status is information that identifies the processing status of the setting content of the setting change information set in the change target component. In the processing field 260C, for example, the setting content “4” of the setting change information set in the component # 7 is set as information for specifying the processing state of the setting content of the setting change information set in the change target component. , “Success” is stored when the process of “12” is successful, and when the process of setting content “34” of the setting change information set in the component of # 7 is being processed, “ “Processing” is stored.
　図４（Ｅ）において、新規設定情報テーブル２７０は、ストレージ装置２０４及びバッファ２２０に格納されるテーブルであって、変更対象コンポーネント毎に新規に設定される設定変更情報を集計して管理するためのテーブルとして、設定変更情報フィールド２７０Ａから構成される。この新規設定情報テーブル２７０は、変更対象コンポーネント毎に複数存在する。 In FIG. 4E, a new setting information table 270 is a table stored in the storage device 204 and the buffer 220, and is used for collecting and managing setting change information newly set for each change target component. The table includes a setting change information field 270A. A plurality of new setting information tables 270 exist for each change target component.
　設定変更情報は、新規に設定変更の対象となる各変更対象コンポーネントの設定内容を示す情報である。設定変更情報フィールド２７０Ａには、新規に設定変更の対象となる変更対象コンポーネントに設定される、設定変更情報に関する複数の設定内容が格納される。例えば、設定変更情報フィールド２７０Ａには、＃７のコンポーネントの設定内容を特定する情報として、「設定内容４」、「設定内容１２」、「設定内容３４」が格納される。また、各設定内容のエントリには、各設定内容の中身を特定する識別子として、例えば、「設定内容４」のエントリには、「４」の情報が格納され、「設定内容１２」のエントリには、「２」の情報が格納され、「設定内容３４」のエントリには、「６」の情報が格納される。 The setting change information is information indicating the setting contents of each change target component that is a new setting change target. The setting change information field 270A stores a plurality of setting contents related to setting change information that are set in a change target component that is a new setting change target. For example, in the setting change information field 270A, “setting content 4”, “setting content 12”, and “setting content 34” are stored as information specifying the setting content of the component # 7. Also, each setting content entry has an identifier for identifying the contents of each setting content. For example, the “setting content 4” entry stores information “4”, and the “setting content 12” entry stores information. The information “2” is stored, and the information “6” is stored in the entry “setting content 34”.
　この際、サーバ２００は、各スレーブシステム３０の運用を管理すると共に、各スレーブシステム３０に設定される設定情報を管理するマスタ用サーバであって、各スレーブシステム３０のサーバ３００上で稼働する要素のうち複数の変更対象コンポーネントに対する処理であって、設定変更情報に従った設定変更処理の実行を指示する指示情報を少なくとも、ネットワーク４０を介して、各スレーブシステム３０のサーバ３００に転送するマスタ用サーバとして構成される。また、サーバ２００は、複数の変更対象コンポーネントを、設定変更処理の処理内容又は各変更対象コンポーネントの機能に従って複数のグループに分けて管理する。 At this time, the server 200 is a master server that manages the operation of each slave system 30 and manages setting information set in each slave system 30, and is an element that operates on the server 300 of each slave system 30. Among the plurality of change target components, and for the master that transfers at least instruction information for instructing execution of the setting change process according to the setting change information to the server 300 of each slave system 30 via the network 40 Configured as a server. Further, the server 200 manages a plurality of change target components by dividing them into a plurality of groups according to the processing contents of the setting change process or the function of each change target component.
　図５は、各スレーブシステムで管理されるテーブルの構成図である。図５（Ａ）において、設定変更バージョンテーブル３５０は、各スレーブシステム３０のストレージ装置３０４とバッファ３３０に格納されるテーブルであって、バージョンＩＤフィールド３５０Ａと、最終使用日時フィールド３５０Ｂと、設定変更情報フィールド３５０Ｃから構成される。即ち、設定変更バージョンテーブル３５０は、設定情報の履歴をバージョンで管理するテーブルとして構成され、このテーブルには、設定変更管理情報３０６が記録される。 FIG. 5 is a configuration diagram of a table managed by each slave system. In FIG. 5A, a setting change version table 350 is a table stored in the storage device 304 and the buffer 330 of each slave system 30, and includes a version ID field 350A, a last use date / time field 350B, and setting change information. It consists of a field 350C. That is, the setting change version table 350 is configured as a table for managing setting information history by version, and setting change management information 306 is recorded in this table.
　バージョンは、設定変更の対象となる設定情報の履歴を特定する情報である。バージョンＩＤフィールド３５０Ａには、設定変更の対象となる設定情報の履歴を特定する識別子として、例えば、「１」の情報が格納される。最終使用日時は、設定変更の対象となる設定情報が使用された最終の日時を特定する情報である。最終使用日時フィールド３５０Ｂには、設定変更の対象となる設定情報が使用された最終の日時を特定する情報、例えば、最終の日時が、２０００年１月１日０時００分である場合、「２０００/１/１　０：００」が格納される。設定変更情報は、設定変更の対象となる設定変更情報の設定内容を示す情報である。設定変更情報フィールド３５０Ｃには、複数の設定内容、例えば、「設定内容１」～「設定内容４５」が格納される。また、各設定内容のエントリには、各バージョンに対応した、各設定内容の中身を特定する識別子として、「設定内容４」のエントリには、「４」の情報が格納され、「設定内容２」のエントリには、「２」の情報が格納され、「設定内容４５」のエントリには、「６」の情報が格納される。 Version is information that identifies the history of setting information that is subject to setting changes. In the version ID field 350A, for example, information “1” is stored as an identifier for specifying a history of setting information to be changed. The last use date and time is information specifying the last date and time when the setting information to be changed is used. In the last use date / time field 350B, information for specifying the last date / time when the setting information to be changed is used, for example, when the last date / time is 0:00 on January 1, 2000, “ “2000/1/1 0:00” is stored. The setting change information is information indicating the setting contents of the setting change information that is the target of the setting change. The setting change information field 350C stores a plurality of setting contents, for example, “setting contents 1” to “setting contents 45”. Each setting content entry stores information “4” in the “setting content 4” entry as an identifier for identifying the contents of each setting content corresponding to each version. "2" information is stored in the "" entry, and information "6" is stored in the "setting content 45" entry.
　図５（Ｂ）において、対象コンポーネント設定情報テーブル３６０は、各スレーブシステム３０のストレージ装置３０４とバッファ３３０に格納されるテーブルであって、各コンポーネントに設定された設定情報３０７を管理するためのテーブルとして、設定変更情報フィールド３６０Ａから構成される。 In FIG. 5B, the target component setting information table 360 is a table stored in the storage device 304 and the buffer 330 of each slave system 30, and is a table for managing the setting information 307 set for each component. Is composed of a setting change information field 360A.
　設定変更情報は、設定変更の対象となる変更対象コンポーネントの設定内容を示す情報である。設定変更情報フィールド３６０Ａには、複数の設定内容、例えば、変更対象となる変更対象コンポーネントの設定内容を特定する情報として、「設定内容１」～「設定内容４５」が格納される。各設定内容のエントリには、各設定内容の中身を特定する識別子として、「設定内容１」のエントリには、「４」の情報が格納され、「設定内容２」のエントリには、「２」の情報が格納され、「設定内容４５」のエントリには、「６」の情報が格納される。 The setting change information is information indicating the setting contents of the change target component that is the target of the setting change. In the setting change information field 360A, a plurality of setting contents, for example, “setting contents 1” to “setting contents 45” are stored as information for specifying the setting contents of the change target component to be changed. Each setting content entry stores information “4” in the “setting content 1” entry and “2” in the “setting content 2” entry as an identifier for specifying the contents of each setting content. Information is stored, and information “6” is stored in the entry “setting content 45”.
　図６は、配布トランザクション管理部の処理を説明するためのフローチャートである。この処理は、運用管理者が、管理端末５０を操作し、サーバ２００に対して、設定変更の対象となるシナリオや設定変更情報等を入力した場合、入力されたシナリオに従った設定変更処理を実行するために、ＣＰＵ２０３が、メモリ２０１の配布トランザクション管理部２１２を起動することによって開始される。 FIG. 6 is a flowchart for explaining the processing of the distribution transaction management unit. In this process, when the operation administrator operates the management terminal 50 and inputs a scenario to be changed or setting change information to the server 200, the setting change process according to the input scenario is performed. To execute, the CPU 203 starts by activating the distribution transaction management unit 212 of the memory 201.
　図６において、配布トランザクション管理部２１２は、管理端末５０から入力された入力情報を基に、バッファ２２０を検索して、設定変更の対象となるシナリオが存在する設定変更シナリオ情報テーブル２３０を参照すると共に、コンポーネット毎に新規に設定された設定変更情報が記録された新規設定情報テーブル２７０を参照し、設定変更の対象となるシナリオと、コンポーネット毎に新規に設定された設定変更情報を含み、設定変更情報に従った設定変更処理の実行を指示する指示情報を各サーバ３００に転送し、指示情報を受信したサーバ３００のうち、設定変更の対象となるシナリオに属する複数の変更対象コンポーネントが存在するサーバ３００の設定変更コミット部３１１を実行させる（Ｓ１０）。 In FIG. 6, the distribution transaction management unit 212 searches the buffer 220 based on the input information input from the management terminal 50, and refers to the setting change scenario information table 230 in which there is a scenario to be changed. In addition, with reference to the new setting information table 270 in which setting change information newly set for each component is recorded, the scenario to be changed and the setting change information newly set for each component are included. The instruction information for instructing execution of the setting change process according to the setting change information is transferred to each server 300, and among the servers 300 that have received the instruction information, there are a plurality of change target components belonging to the scenario to be changed. The setting change commit unit 311 of the existing server 300 is executed (S10).
　例えば、配布トランザクション管理部２１２は、管理端末５０から入力された入力情報から、設定変更の対象となるシナリオが、＃２のシナリオであり、新規に設定変更されるコンポーネットが、＃７のコンポーネントであると判別した場合、設定変更の対象となるシナリオとして、＃２のシナリオを含み、＃７のコンポーネントに設定された設定変更情報として、新規設定情報テーブル２７０に記録された設定変更情報（「設定内容４」、「設定内容１２」、「設定内容３４」を含む情報）を含む指示情報を各サーバ３００に転送すると共に、設定変更情報に従った設定変更処理を指示する。 For example, the distribution transaction management unit 212 determines that the scenario whose setting is to be changed is the scenario # 2 from the input information input from the management terminal 50, and the component whose setting is newly changed is the component # 7. If it is determined that the setting change information is included in the new setting information table 270 as the setting change information set for the component # 7, including the scenario # 2 as the scenario to be changed. The instruction information including “setting contents 4”, “setting contents 12”, and “setting contents 34” is transferred to each server 300, and setting change processing according to the setting change information is instructed.
　この後、配布トランザクション管理部２１２は、設定変更処理を実行したサーバ３００に属する設定変更管理部３１０の管理結果を取り込み、設定変更管理部３１０に属する設定変更コミット部３１１の処理が、正常に終了したか否かを判定し（Ｓ１１）、正常に終了したと判定した場合、設定変更の対象となるシナリオについて全ての処理が終了したか否かを判定する（Ｓ１２）。例えば、設定変更の対象となるシナリオが、＃２のシナリオである場合、配布トランザクション管理部２１２は、＃２のシナリオが存在する設定変更シナリオ情報テーブル２３０に記録された全てのコンポーネントについての処理が終了したか否かを判定する。配布トランザクション管理部２１２は、ステップＳ１２で、全ての処理が終了していないと判定した場合、ステップＳ１１の処理に戻り、ステップＳ１１～ステップ１２の処理を繰り返し、ステップＳ１２で全ての処理が終了したと判定した場合、このルーチンでの処理を終了する。 Thereafter, the distribution transaction management unit 212 fetches the management result of the setting change management unit 310 belonging to the server 300 that has executed the setting change processing, and the processing of the setting change commit unit 311 belonging to the setting change management unit 310 ends normally. If it is determined that the process has been completed normally, it is determined whether or not all the processes have been completed for the scenario whose setting is to be changed (S12). For example, when the scenario subject to setting change is the scenario # 2, the distribution transaction management unit 212 performs processing for all components recorded in the setting change scenario information table 230 in which the scenario # 2 exists. It is determined whether or not it has been completed. If the distribution transaction management unit 212 determines in step S12 that all the processes have not been completed, the process returns to step S11, repeats the processes in steps S11 to S12, and all the processes are completed in step S12. If it is determined, the process in this routine is terminated.
　一方、ステップＳ１１で、設定変更コミット部３１１の処理が、正常に終了していないと判定した場合、即ち、設定変更の対象となるシナリオに属する処理であって、いずれかのグループに属するコンポーネントに関する設定変更処理が正常に終了しない場合、いずれかのグループに属するコンポーネントであって、設定変更処理が失敗したコンポーネントを含むスレーブシステム３０のサーバ３００を特定し、特定したサーバ３００に属する設定変更管理部３１０に対して、設定変更のロールバック処理、即ち、設定変更処理が失敗したコンポーネントに設定された設定情報をグループ単位で元の設定情報に戻す処理を指示し（Ｓ１３）、このルーチンでの処理を終了する。 On the other hand, if it is determined in step S11 that the process of the setting change commit unit 311 has not ended normally, that is, the process belongs to the scenario that is the target of the setting change, and the component belongs to any group. If the setting change process does not end normally, the server 300 of the slave system 30 that includes a component that belongs to any group and that has failed in the setting change process is specified, and the setting change management unit that belongs to the specified server 300 310 is instructed to perform setting change rollback processing, that is, processing for returning the setting information set to the component for which the setting change processing has failed to the original setting information in units of groups (S13). Exit.
　この際、サーバ３００は、サーバ２００と同様に、複数の変更対象コンポーネントを、設定変更処理の処理内容又は各変更対象コンポーネントの機能に従って複数のグループに分けて管理する。また、サーバ３００は、設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、設定変更処理が失敗した変更対象コンポーネントと同一のグループに属する変更対象コンポーネント、例えば、＃７、＃４、＃９の変更対象コンポーネントに対して、グループ単位（＃１のグループ単位）でロールバック処理を実行する。 At this time, like the server 200, the server 300 manages a plurality of change target components by dividing them into a plurality of groups according to the processing contents of the setting change process or the function of each change target component. Further, when the setting change process for at least one change target component among the setting change processes fails, the server 300 changes the change target component belonging to the same group as the change target component for which the setting change process has failed, for example, # 7, A rollback process is executed for each change target component of # 4 and # 9 in units of groups (group units of # 1).
　図７は、設定変更コミット部の処理を説明するためのフローチャートである。この処理は、マスタシステム２０の配布トランザクション管理部２１２からの指示に基づいて、スレーブシステム３０のＣＰＵ３０３が設定変更管理部３１０を起動することによって開始される。 FIG. 7 is a flowchart for explaining the processing of the setting change commit unit. This process is started when the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
　図７において、マスタシステム２０の配布トランザクション管理部２１２からの指示を受信した設定変更管理部３１０が、設定変更コミット部３１１を起動すると、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１を実行し、変更対象コンポーネットを停止させる（Ｓ２０）。この後、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１の実行状態を受信し、システム停止部３２１が、正常に終了したか否かを判定する（Ｓ２１）。 In FIG. 7, when the setting change management unit 310 that has received an instruction from the distribution transaction management unit 212 of the master system 20 activates the setting change commit unit 311, the setting change commit unit 311 passes through the setting target component unit 320. Then, the system stop unit 321 is executed to stop the component to be changed (S20). Thereafter, the setting change commit unit 311 receives the execution state of the system stop unit 321 via the setting target component unit 320, and determines whether or not the system stop unit 321 has ended normally (S21).
　設定変更コミット部３１１は、ステップＳ２１で、否定の判定結果を得た場合、即ち、システム停止部３２１が、正常に終了しないと判定した場合、ステップＳ２９の処理に移行し、ステップＳ２１で、システム停止部３２１が、正常に終了したと判定した場合、即ち、変更対象コンポーネットが正常に終了した場合、設定対象コンポーネット部３２０を介して設定変更部３２２を実行する（Ｓ２２）。この際、設定変更部３２２は、新規設定情報テーブル２７０に記録された設定変更情報であって、マスタシステム２０からスレーブシステム３０に転送された設定変更情報に従って変更対象コンポーネントに対する設定変更処理を開始する。 If the setting change commit unit 311 obtains a negative determination result in step S21, that is, if the system stop unit 321 determines that it does not end normally, the setting change commit unit 311 proceeds to the process of step S29, and in step S21, the system change When it is determined that the stop unit 321 has ended normally, that is, when the change target component has ended normally, the setting change unit 322 is executed via the setting target component unit 320 (S22). At this time, the setting change unit 322 starts setting change processing for the change target component according to the setting change information recorded in the new setting information table 270 and transferred from the master system 20 to the slave system 30. .
　次に、設定変更コミット部３１１は、ストレージ装置３０４の設定情報３０７に記録された既存設定情報、例えば、対象コンポーネント設定情報テーブル３６０に記録された設定内容を、ストレージ装置３０４の設定変更管理情報３０６、例えば、設定変更バージョンテーブル３５０に追加して保存し（Ｓ２３）、その後、設定対象コンポーネット部３２０を介して設定変更部３２２の実行状態を受信し、設定変更部３２２が、正常に終了したか否かを判定する（Ｓ２４）。 Next, the setting change commit unit 311 uses the existing setting information recorded in the setting information 307 of the storage apparatus 304, for example, the setting contents recorded in the target component setting information table 360, as the setting change management information 306 of the storage apparatus 304. For example, the setting change version table 350 is added and saved (S23), and then the execution state of the setting change unit 322 is received via the setting target component unit 320, and the setting change unit 322 is normally terminated. It is determined whether or not (S24).
　設定変更コミット部３１１は、ステップＳ２４で、否定の判定結果を得た場合、即ち、設定変更部３２２が、正常に終了しないと判定した場合、ステップＳ２９の処理に移行し、ステップＳ２４で、設定変更部３２２が、正常に終了したと判定した場合、即ち、変更対象コンポーネットに対して、設定変更情報の設定内容が反映され、変更対象コンポーネットに対する設定変更処理が正常に終了した場合、設定対象コンポーネット部３２０を介して設定チェック部３２３を実行する（Ｓ２５）。この際、設定チェック部３２３は、変更対象コンポーネットに対する設定変更処理の処理結果のチェック、例えば、文法エラーや意味エラー等のチェックを実行する。 If the setting change commit unit 311 obtains a negative determination result in step S24, that is, if the setting change unit 322 determines that the processing does not end normally, the setting change commit unit 311 proceeds to the process of step S29, and the setting change commit unit 311 sets in step S24. If the change unit 322 determines that the setting has been completed normally, that is, if the setting content of the setting change information is reflected on the change target component and the setting change processing for the change target component has been completed normally, The setting check unit 323 is executed via the target component unit 320 (S25). At this time, the setting check unit 323 executes a check of the processing result of the setting change process for the change target component, for example, a check for a grammatical error or a semantic error.
　次に、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介して設定チェック部３２３の実行状態を受信し、設定チェック部３２３が、正常に終了したか否かを判定する（Ｓ２６）。 Next, the setting change commit unit 311 receives the execution state of the setting check unit 323 via the setting target component unit 320, and determines whether or not the setting check unit 323 has ended normally (S26).
　設定変更コミット部３１１は、ステップＳ２６で、設定チェック部３２３が、正常に終了したと判定した場合、即ち、変更対象コンポーネットに対する設定変更処理のチェックが正常に終了した場合、設定対象コンポーネット部３２０を介してシステム起動部３２４を実行し（Ｓ２７）、その後、設定変更管理部３１０を介して、マスタシステム２０の配布トランザクション管理部２１２に対して、変更対象コンポーネットに対する設定変更処理が成功した旨を通知し（Ｓ２８）、このルーチンでの処理を終了する。 In step S26, the setting change commit unit 311 determines that the setting check unit 323 has ended normally, that is, if the setting change processing check for the change target component has ended normally, the setting target component unit 320, the system activation unit 324 is executed (S27), and then the setting change process for the change target component is successful for the distribution transaction management unit 212 of the master system 20 via the setting change management unit 310. This is notified (S28), and the processing in this routine is terminated.
　一方、設定変更コミット部３１１は、ステップＳ２６で、否定の判定結果を得た場合、即ち、設定チェック部３２２が、変更対象コンポーネットに対する設定変更処理のチェックを正常に終了しないと判定した場合、ステップＳ２９の処理に移行する。 On the other hand, if the setting change commit unit 311 obtains a negative determination result in step S26, that is, if the setting check unit 322 determines that the setting change processing check for the change target component does not end normally, The process proceeds to step S29.
　ステップＳ２９において、設定変更コミット部３１１は、設定変更管理部３１０を介して、マスタシステム２０の配布トランザクション管理部２１２に対して、変更対象コンポーネットに対する設定変更処理が失敗した旨を通知し、その後、このルーチンでの処理を終了する。なお、配布トランザクション管理部２１２は、変更対象コンポーネットに対する設定変更処理の成功又は失敗の情報を、管理端末５０を介して運用管理者に通知する。 In step S29, the setting change commit unit 311 notifies the distribution transaction management unit 212 of the master system 20 through the setting change management unit 310 that the setting change processing for the change target component has failed, and then Then, the processing in this routine is terminated. The distribution transaction management unit 212 notifies the operation manager of the success or failure of the setting change process for the change target component via the management terminal 50.
　図８は、スレーブシステムにおける設定変更ロールバック部の処理を説明するためのフローチャートである。この処理は、変更対象コンポーネットに対する設定変更処理が失敗したことを判定した設定変更コミット部３１１の判定結果に基づいて、ＣＰＵ３０３が、設定変更管理部３１０を介して設定変更ロールバック部３１２を起動することによって開始される。 FIG. 8 is a flowchart for explaining the processing of the setting change rollback unit in the slave system. In this process, the CPU 303 activates the setting change rollback unit 312 via the setting change management unit 310 based on the determination result of the setting change commit unit 311 that has determined that the setting change processing for the change target component has failed. Start by doing.
　図８において、設定変更ロールバック部３１２は、バッファ３３０に保存された設定変更管理情報３０６に属する設定変更バージョンテーブル３５０及び設定情報３０７に属する対象コンポーネント設定情報テーブル３６０を参照し、変更対象コンポーネットに設定された設定変更情報のバージョン、例えば、＃１のバージョンに属する設定変更情報の設定内容（新規に設定された設定変更情報の設定内容に相当する設定内容）に対応する設定内容を、設定変更前の設定内容が記録された対象コンポーネント設定情報テーブル３６０から取得し、取得した設定内容（設定変更前の設定内容）に基づいて、変更対象コンポーネント部３２０を介して設定変更部３２２を実行する（Ｓ４０）。この際、設定変更部３２２は、設定変更前の設定内容（元の設定内容）に基づいて、変更対象コンポーネットに対して、グループ単位でロールバック処理を実行し、変更対象コンポーネットに対する設定内容をグループ単位で設定変更前の状態に戻し、整合性を確保する。 In FIG. 8, the setting change rollback unit 312 refers to the setting change version table 350 belonging to the setting change management information 306 stored in the buffer 330 and the target component setting information table 360 belonging to the setting information 307, and changes target component Set the setting contents corresponding to the version of the setting change information set in, for example, the setting contents of the setting change information belonging to the version # 1 (setting contents corresponding to the setting contents of the newly set setting change information) The setting change unit 322 is executed via the change target component unit 320 based on the acquired setting content (setting content before setting change), which is acquired from the target component setting information table 360 in which the setting content before change is recorded. (S40). At this time, the setting change unit 322 executes rollback processing for each change target component on the basis of the setting contents before the setting change (original setting contents), and the setting contents for the change target component. Is restored to the state before the setting change in group units to ensure consistency.
　次に、設定変更ロールバック部３１２は、変更対象コンポーネント部３２０を介して設定変更部３２２の処理結果を受信し（Ｓ４１）、設定変更部３２２の処理が成功したことを条件に、変更対象コンポーネント部３２０を介してシステム起動部３２４を実行し（Ｓ４２）、その後、このルーチンでの処理を終了する。この際、変更対象コンポーネットは、設定情報が、グループ単位で設定変更前に戻った状態で起動することになる。 Next, the setting change rollback unit 312 receives the processing result of the setting change unit 322 via the change target component unit 320 (S41), and on the condition that the processing of the setting change unit 322 is successful, the change target component The system activation unit 324 is executed via the unit 320 (S42), and then the processing in this routine is terminated. At this time, the change target component is activated in a state where the setting information is returned to the group unit before the setting change.
　以上のように、各スレーブシステム３０のサーバ３００は、マスタ用サーバ２００から、複数の変更対象コンポーネントに対する処理であって、設定変更情報に従った設定変更処理の実行を指示する指示情報を受信した場合、複数の変更対象コンポーネントが存在することを条件に、複数の変更対象コンポーネントに対して設定変更情報に従った設定変更処理を実行し、設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、設定変更処理が失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを同一グループに属する変更対象コンポーネントとして纏め、纏められた２以上の変更対象コンポーネントに対して、纏められた２以上の変更対象コンポーネントに設定された設定変更情報を、指示情報を受信する前に設定された元の設定情報に戻すためのロールバック処理をグループ単位で実行するスレーブ用サーバとして構成される。 As described above, the server 300 of each slave system 30 has received instruction information from the master server 200 that is processing for a plurality of change target components and instructing execution of setting change processing according to the setting change information. In such a case, on the condition that there are a plurality of change target components, a setting change process according to the setting change information is executed for the plurality of change target components, and the setting change for at least one change target component among the setting change processes When the process fails, two or more change target components having relevance with the change target component for which the setting change process has failed are grouped as change target components belonging to the same group, and Set in two or more components to be changed The setting change information, configured as a slave server to perform a rollback process in groups to return to the original setting information set before receiving the indication information.
　本実施例によれば、変更対象コンポーネットに対する設定変更処理が失敗した場合、変更対象コンポーネットに対してグループ単位でロールバック処理を実行し、変更対象コンポーネットに対する設定情報をグループ単位で設定変更前の状態に戻すようにしたので、整合性を確保することができ、結果として、運用管理者の負荷軽減及びシステムのダウンタイムの短縮を図ることができる。さらに、変更対象コンポーネットに対する設定情報をグループ単位で設定変更前の状態に戻した後、分散システム１０の運用を開始しても、分散システム１０の運用が停止するリスクを軽減することができ、分散処理システム１０の動作の信頼性を高めることができる。 According to the present embodiment, when the setting change process for the change target component fails, the rollback process is executed for the change target component in the group unit, and the setting information for the change target component is changed in the group unit. Since the previous state is restored, consistency can be ensured, and as a result, the load on the operation manager can be reduced and the system downtime can be reduced. Furthermore, even after starting the operation of the distributed system 10 after returning the setting information for the change target component to the state before the setting change in the group unit, the risk of the operation of the distributed system 10 being stopped can be reduced. The reliability of the operation of the distributed processing system 10 can be improved.
　本実施例は、変更対象コンポーネント部と同一の機能を有するテスト用プログラムとしてのテストコンポーネント部を各スレーブシステムは配置したものであり、他の構成は、実施例１と同様である。 In this embodiment, each slave system is arranged with a test component unit as a test program having the same function as the component unit to be changed, and the other configuration is the same as that of the first embodiment.
　図９は、実施例２におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。図９において、メモリ３０１には、変更対象コンポーネント部３２０と同一の機能を有するテスト用プログラムとしてのテストコンポーネント部３４０が構築されている。テストコンポーネント部３４０は、変更対象コンポーネント部３２０と同様に、システム停止部３４１と、設定変更部３４２と、設定チェック部３４３と、システム起動部３４４から構成される。 FIG. 9 is a configuration diagram of hardware resources and software resources of the slave system in the second embodiment. In FIG. 9, a test component unit 340 as a test program having the same function as the change target component unit 320 is constructed in the memory 301. Similar to the change target component unit 320, the test component unit 340 includes a system stop unit 341, a setting change unit 342, a setting check unit 343, and a system activation unit 344.
　図１０は、実施例２における配布トランザクション管理部の処理を説明するためのフローチャートである。この処理は、ＣＰＵ２０３が、メモリ２０１の配布トランザクション管理部２１２を起動することによって開始される。 FIG. 10 is a flowchart for explaining the processing of the distribution transaction management unit in the second embodiment. This process is started when the CPU 203 activates the distribution transaction management unit 212 of the memory 201.
　図１０において、配布トランザクション管理部２１２は、ステップＳ５０～ステップＳ５２では、テストコンポーネット部３４０を対象に、設定変更コミット部３１１を実行する他は、図６のステップＳ１０～ステップＳ１２と同様の処理を実行し、ステップＳ５１で否定の判定結果を得た場合、設定変更ロールバックの処理の代わりに、テストコンポーネット部３４０を対象とする設定変更コミット部３１１の実行を終了し（Ｓ５７）、このルーチンでの処理を終了する。 In FIG. 10, the distribution transaction management unit 212 performs the same processing as step S10 to step S12 in FIG. 6 except that in step S50 to step S52, the setting change commit unit 311 is executed for the test component unit 340. Is executed, and instead of the setting change rollback process, the execution of the setting change commit unit 311 for the test component unit 340 is terminated (S57). The routine processing is terminated.
　また、配布トランザクション管理部２１２は、ステップＳ５３～ステップＳ５６では、図６のステップＳ１０～ステップＳ１３と同様の処理を実行する。 In addition, the distribution transaction management unit 212 executes the same processing as in steps S10 to S13 in FIG. 6 in steps S53 to S56.
　これにより、配布トランザクション管理部２１２は、テストコンポーネット部３４０を対象とする設定変更コミット部３１１を実行すると共に、変更対象コンポーネント部３２０を対象とする設定変更コミット部３１１を実行することができる。 Thereby, the distribution transaction management unit 212 can execute the setting change commit unit 311 for the test component unit 340 and the setting change commit unit 311 for the change target component unit 320.
　図１１は、実施例２における設定変更コミット部の処理を説明するためのフローチャートである。この処理は、図１０のステップＳ５０とステップＳ５３の具体的内容であって、マスタシステム２０の配布トランザクション管理部２１２からの指示に基づいて、スレーブシステム３０のＣＰＵ３０３が設定変更管理部３１０を起動することによって開始される。 FIG. 11 is a flowchart for explaining the process of the setting change commit unit in the second embodiment. This process is the specific contents of steps S50 and S53 in FIG. 10, and the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20. Be started by.
　図１１において、ステップＳ６０～ステップＳ６８は、テストコンポーネット部３４０を対象とする設定変更コミット部３１１を実行する処理であって、設定変更管理部３１０が、設定変更コミット部３１１を起動し、その後、設定変更コミット部３１１が、テストコンポーネット部３４０を起動し、次に、テストコンポーネント部３４０が、システム停止部３４１、設定変更部３４２、設定チェック部３４３、システム起動部３４４を順次起動する他は、図７のステップＳ２０～ステップＳ２９の処理と同様である。 In FIG. 11, steps S60 to S68 are processes for executing the setting change commit unit 311 for the test component unit 340. The setting change management unit 310 activates the setting change commit unit 311, and thereafter The setting change commit unit 311 activates the test component unit 340, and then the test component unit 340 sequentially activates the system stop unit 341, the setting change unit 342, the setting check unit 343, and the system activation unit 344. Is the same as the processing in steps S20 to S29 in FIG.
　一方、ステップＳ６７又はステップＳ６８の処理の後、設定変更コミット部３１１は、配布トランザクション管理部２１２から処理開始指示があったか否を判定し（Ｓ６９）、ステップＳ６９で否定の判定結果を得た場合、このルーチンでの処理を終了し、ステップＳ６９で肯定の判定結果を得た場合、ステップＳ７０の処理に移行する。 On the other hand, after the process of step S67 or step S68, the setting change commit unit 311 determines whether or not there has been a process start instruction from the distribution transaction management unit 212 (S69), and if a negative determination result is obtained in step S69, When the process in this routine is finished and a positive determination result is obtained in step S69, the process proceeds to step S70.
　配布トランザクション管理部２１２から処理開始指示があった場合、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１を実行し、変更対象コンポーネットを停止させる（Ｓ７０）。この後、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１の実行結果を受信し（Ｓ７１）、システム停止部３２１の処理が、正常に終了したことを条件に、図７のステップＳ２２と同様に、設定対象コンポーネット部３２０を介して設定変更部３２２を実行する（Ｓ７２）。この後、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介して設定変更部３２２の実行結果を受信し（Ｓ７３）、設定変更部３２２の処理が、正常に終了したことを条件に、図７のステップＳ２７と同様に、設定対象コンポーネット部３２０を介してシステム起動部３２４を実行する（Ｓ７４）。 When there is a processing start instruction from the distribution transaction management unit 212, the setting change commit unit 311 executes the system stop unit 321 via the setting target component unit 320 to stop the change target component (S70). Thereafter, the setting change commit unit 311 receives the execution result of the system stop unit 321 via the setting target component unit 320 (S71), and on condition that the processing of the system stop unit 321 has ended normally. Similar to step S22 of FIG. 7, the setting change unit 322 is executed via the setting target component unit 320 (S72). Thereafter, the setting change commit unit 311 receives the execution result of the setting change unit 322 via the setting target component unit 320 (S73), and on condition that the processing of the setting change unit 322 has ended normally. Similar to step S27 in FIG. 7, the system activation unit 324 is executed via the setting target component unit 320 (S74).
　この後、設定変更コミット部３１１は、システム起動部３２４の処理が正常に終了したことを条件に、図７のステップＳ２８と同様に、設定変更管理部３１０を介して、マスタシステム２０の配布トランザクション管理部２１２に対して、変更対象コンポーネットに対する設定変更処理が成功した旨を通知し（Ｓ７５）、このルーチンでの処理を終了する。 Thereafter, the setting change commit unit 311 performs the distribution transaction of the master system 20 via the setting change management unit 310 as in step S28 in FIG. The management unit 212 is notified that the setting change process for the change target component has been successful (S75), and the process in this routine is terminated.
　このように、設定変更チェックの別のパターンとして、変更対象コンポーネントに対する設定変更処理の前に、テストコンポーネントに対する設定変更処理を実行することで、変更対象コンポーネントに対する設定変更処理が成功するか否かを予測することができる。 In this way, as another pattern of the setting change check, whether or not the setting change process for the change target component succeeds by executing the setting change process for the test component before the setting change process for the change target component. Can be predicted.
　図１２は、実施例２における設定変更ロールバック部の処理を説明するためのフローチャートである。この処理は、図１０のステップＳ５６の具体的内容であって、変更対象コンポーネットに対する設定変更処理が失敗したことを判定した設定変更コミット部３１１の判定結果に基づいて、ＣＰＵ３０３が、設定変更管理部３１０を介して設定変更ロールバック部３１２を起動することによって開始される。 FIG. 12 is a flowchart for explaining the processing of the setting change rollback unit in the second embodiment. This process is the specific content of step S56 in FIG. 10, and the CPU 303 performs setting change management based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312 via the unit 310.
　図１２において、設定変更ロールバック部３１２は、ステップＳ８０～ステップＳ８２では、図８のステップＳ４０～ステップＳ４２の処理と同様の処理を実行する。この場合も、設定変更ロールバック部３１２の実行による設定変更部３２２は、設定変更前の設定内容（元の設定内容）に基づいて、変更対象コンポーネットに対して、グループ単位でロールバック処理を実行し、変更対象コンポーネットに対する設定内容をグループ単位で設定変更前の状態に戻し、整合性を確保する。 In FIG. 12, the setting change rollback unit 312 executes the same processing as the processing in steps S40 to S42 in FIG. 8 in steps S80 to S82. Also in this case, the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). Execute this to return the setting contents for the change target component to the state before the setting change for each group and ensure consistency.
　本実施例によれば、実施例１と同様の効果を奏することができると共に、変更対象コンポーネントに対する設定変更処理の前に、テストコンポーネントに対する設定変更処理を実行することで、変更対象コンポーネントに対する設定変更処理が成功するか否かを予測することができると共に、変更対象コンポーネントに対する設定変更処理の前に、設定情報のうち文法等のチェックを行うことができる。 According to the present embodiment, the same effect as that of the first embodiment can be obtained, and the setting change process for the test target component is executed before the setting change process for the change target component, thereby changing the setting for the change target component. It is possible to predict whether or not the process will be successful, and it is possible to check the grammar and the like in the setting information before the setting change process for the change target component.
　本実施例は、マスタシステム２０のサーバ２００に動作テスト部２１３を配置し、各スレーブシステム３０のサーバ３００にアプリケーション実行部３２５を配置したものであり、他の構成は、実施例１と同様である。 In this embodiment, the operation test unit 213 is arranged in the server 200 of the master system 20 and the application execution unit 325 is arranged in the server 300 of each slave system 30. Other configurations are the same as those in the first embodiment. is there.
　図１３は、実施例３におけるマスタシステムのハードウェア資源及びソフトウェア資源の構成図である。図１３において、メモリ２０１の運用管理部２１０に、動作テスト管理部２１３が構築されており、他の構成は、実施例１と同様である。 FIG. 13 is a configuration diagram of hardware resources and software resources of the master system in the third embodiment. In FIG. 13, an operation test management unit 213 is built in the operation management unit 210 of the memory 201, and other configurations are the same as those in the first embodiment.
　動作テスト管理部２１３は、各スレーブシステム３０の動作テストを実行するプログラムとして構成されている。 The operation test management unit 213 is configured as a program that executes an operation test of each slave system 30.
　図１４は、実施例３におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。図１４において、メモリ３０１の変更対象コンポーネント部３２０に、アプリケーション実行部３２５が構築されており、他の構成は、実施例１と同様である。 FIG. 14 is a configuration diagram of hardware resources and software resources of the slave system in the third embodiment. In FIG. 14, an application execution unit 325 is built in the change target component unit 320 of the memory 301, and other configurations are the same as those in the first embodiment.
　アプリケーション実行部３２５は、サーバ３００上で稼働するアプリケーションプログラムであって、変更対象コンポーネントを稼働するためのアプリケーションプロラムとして構成されている。 The application execution unit 325 is an application program that runs on the server 300, and is configured as an application program for running the change target component.
　図１５は、実施例３における配布トランザクション管理部と動作テスト管理部の処理を説明するためのフローチャートである。 FIG. 15 is a flowchart for explaining processing of the distribution transaction management unit and the operation test management unit in the third embodiment.
　図１５において、配布トランザクション管理部２１２は、ステップＳ９０～ステップＳ９２、ステップＳ９５では、図６のステップＳ１０～ステップＳ１３と同様の処理を実行する。 15, the distribution transaction management unit 212 executes the same processing as that in steps S10 to S13 in FIG. 6 in steps S90 to S92 and S95.
　一方、ステップＳ９２で肯定の判定結果を得た場合、即ち、全ての処理が終了した場合、配布トランザクション管理部２１２は、動作テスト管理部２１３を起動し、変更対象コンポーネントを含むスレーブシステム３０のアプリケーション実行部３２５による動作テストを行うために、動作テスト管理部２１３を実行する（Ｓ９３）。この際、動作テスト管理部２１３は、変更対象コンポーネントを含むスレーブシステム３０のサーバ３００に属する設定変更管理部３１０に、アプリケーション実行部３２５による動作テストを指示する。即ち、マスタ用サーバ２００は、変更対象コンポーネントに対する動作テストを指示する指示情報を各スレーブシステム３０のサーバ３００に転送する。 On the other hand, when an affirmative determination result is obtained in step S92, that is, when all processing is completed, the distribution transaction management unit 212 activates the operation test management unit 213, and the application of the slave system 30 including the change target component. In order to perform an operation test by the execution unit 325, the operation test management unit 213 is executed (S93). At this time, the operation test management unit 213 instructs the setting change management unit 310 belonging to the server 300 of the slave system 30 including the change target component to perform an operation test by the application execution unit 325. That is, the master server 200 transfers instruction information for instructing an operation test for the change target component to the server 300 of each slave system 30.
　この指示情報を受信したサーバ３００の設定変更管理部３１０は、変更対象コンポーネント部３２０を介してアプリケーション実行部３２５を起動する。これにより、アプリケーション実行部３２５は、変更対象コンポーネントを稼働し、変更対象コンポーネントの動作テストを実行する。この場合、アプリケーション実行部３２５は、例えば、変更対象コンポーネントが、データの分析処理を実行するアプリケーションプログラムである場合、設定変更されたデータ分析処理用アプリケーションプログラムの動作テストを実行する。 The setting change management unit 310 of the server 300 that has received this instruction information activates the application execution unit 325 via the change target component unit 320. As a result, the application execution unit 325 operates the change target component and executes an operation test of the change target component. In this case, for example, when the change target component is an application program that executes data analysis processing, the application execution unit 325 executes an operation test of the data analysis processing application program whose setting has been changed.
　この後、配布トランザクション管理部２１２は、運用管理部２１０に属する動作テスト管理部２１３から、アプリケーション実行部３２５による動作テストの結果を取り込み、動作テストが正常に終了したか否かを判定し（Ｓ９４）、ステップＳ９４で肯定の判定結果を得た場合、このルーチンでの処理を終了し、ステップＳ９４で否定の判定結果を得た場合、図６のステップＳ１３と同様に、動作テストに失敗した変更対象コンポーネントを含むスレーブシステム３０のサーバ３００に属する設定変更管理部３１０に、設定変更のロールバック処理、即ち、動作テストに失敗した変更対象コンポーネントに設定された設定情報をグループ単位で元の設定情報に戻す処理を指示し（Ｓ９５）、このルーチンでの処理を終了する。 Thereafter, the distribution transaction management unit 212 fetches the result of the operation test by the application execution unit 325 from the operation test management unit 213 belonging to the operation management unit 210, and determines whether or not the operation test has ended normally (S94). ), If a positive determination result is obtained in step S94, the processing in this routine is terminated, and if a negative determination result is obtained in step S94, the change in which the operation test has failed as in step S13 of FIG. The setting change management unit 310 belonging to the server 300 of the slave system 30 including the target component has the setting change rollback process, that is, the setting information set for the change target component that failed the operation test as the original setting information for each group. Is instructed to return to (S95), and the processing in this routine is terminated.
　この場合、サーバ３００のアプリケーション実行部３２５は、複数の変更対象コンポーネントに対する設定変更処理が成功したことを条件に、設定変更情報が反映された複数の変更対象コンポーネントに対する動作テストを実行する。動作テストのうち少なくとも１つの変更対象コンポーネントに対する動作テストが失敗した場合、サーバ３００の設定変更ロールバック部３１２は、動作テストが失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを、同一のグループに属する変更対象コンポーネントとして纏め、同一のグループに属する変更対象コンポーネントに対して、グループ単位でロールバック処理を実行する。 In this case, the application execution unit 325 of the server 300 executes an operation test for the plurality of change target components reflecting the setting change information on the condition that the setting change processing for the plurality of change target components is successful. When the operation test for at least one change target component of the operation test fails, the setting change rollback unit 312 of the server 300 selects two or more change target components having relevance to the change target component for which the operation test has failed. The change target components belonging to the same group are grouped together, and the roll back process is executed in units of the change target components belonging to the same group.
　以上のように、サーバ３００は、変更対象コンポーネントに対する設定変更処理が成功した後、変更対象コンポーネントの動作テストを実行することで、サブシステム３０の実際の動作を踏まえた設定変更チェックを実行することができる。 As described above, the server 300 executes the setting change check based on the actual operation of the subsystem 30 by executing the operation test of the change target component after the setting change processing for the change target component is successful. Can do.
　図１６は、実施例３における設定変更コミット部の処理を説明するためのフローチャートである。この処理は、マスタシステム２０の配布トランザクション管理部２１２からの指示に基づいてスレーブシステム３０のＣＰＵ３０３が設定変更管理部３１０を起動することによって開始される。 FIG. 16 is a flowchart for explaining the process of the setting change commit unit according to the third embodiment. This process is started when the CPU 303 of the slave system 30 activates the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20.
　図１６において、設定変更コミット部３１１は、ステップＳ１００～ステップＳ１０９では、図７のステップＳ２０～ステップＳ２９と同様の処理を実行する。 In FIG. 16, the setting change commit unit 311 performs the same processes as steps S20 to S29 in FIG. 7 in steps S100 to S109.
　この場合も、設定変更処理が正常に終了したと判定した場合には、変更対象コンポーネットに対して、設定変更情報の設定内容が反映される。 Also in this case, when it is determined that the setting change process has been completed normally, the setting contents of the setting change information are reflected on the change target component.
　図１７は、実施例３における設定変更ロールバック部の処理を説明するためのフローチャートである。この処理は、図１５のステップＳ９５の具体的内容であって、変更対象コンポーネットに対する設定変更処理が失敗したことを判定した設定変更コミット部３１１の判定結果に基づいて、ＣＰＵ３０３が、設定変更管理部３１０を介して設定変更ロールバック部３１２を起動することによって開始される。 FIG. 17 is a flowchart for explaining the processing of the setting change rollback unit in the third embodiment. This process is the specific content of step S95 in FIG. 15, and the CPU 303 performs setting change management based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312 via the unit 310.
　図１７において、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１を実行し、変更対象コンポーネットを停止させる（Ｓ１２０）。この後、設定変更コミット部３１１は、設定対象コンポーネット部３２０を介してシステム停止部３２１の実行結果を受信し（Ｓ１２１）、システム停止部３２１の処理が、正常に終了したことを条件に、図８のステップＳ４０と同様に、設定対象コンポーネット部３２０を介して設定変更部３２２を実行する（Ｓ１２２）。この後、設定変更コミット部３１１は、ステップＳ１２３～ステップＳ１２４では、図８のステップＳ４１～ステップＳ４２と同様の処理を実行する。 In FIG. 17, the setting change commit unit 311 executes the system stop unit 321 via the setting target component unit 320 to stop the change target component (S120). Thereafter, the setting change commit unit 311 receives the execution result of the system stop unit 321 via the setting target component unit 320 (S121), and on condition that the processing of the system stop unit 321 has ended normally. Similar to step S40 in FIG. 8, the setting change unit 322 is executed via the setting target component unit 320 (S122). Thereafter, the setting change commit unit 311 executes the same processing as in steps S41 to S42 in FIG. 8 in steps S123 to S124.
　以上のように、設定変更ロールバック部３１２の実行による設定変更部３２２は、設定変更前の設定内容（元の設定内容）に基づいて、変更対象コンポーネットに対して、グループ単位でロールバック処理を実行し、変更対象コンポーネットに対する設定内容をグループ単位で設定変更前の状態に戻し、整合性を確保する。 As described above, the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). To return the setting contents for the change target component to the state before the setting change for each group, and ensure consistency.
　本実施例によれば、実施例１と同様の効果を奏することができると共に、変更対象コンポーネントに対する設定変更処理が成功した後、変更対象コンポーネントの動作テストを実行することで、サブシステム３０の実際の動作を踏まえた設定変更チェックを実行することができる。この場合、動作テストがアトミック処理に含まれているので、サブシステム３０の信頼性を保証する設定変更の確認を行うことができる。 According to the present embodiment, the same effect as in the first embodiment can be obtained, and after the setting change process for the change target component is successful, the operation test of the change target component is executed, so that the subsystem 30 is actually operated. It is possible to execute a setting change check based on the operation of. In this case, since the operation test is included in the atomic processing, it is possible to confirm the setting change that guarantees the reliability of the subsystem 30.
　本実施例は、マスタシステム２０のメモリ２０１に動作テスト管理部２１３を配置し、各スレーブシステム３０のメモリ３０１に、変更対象コンポーネント部３２０と同一機能を有するテストコンポーネント部３４０を配置した他は、実施例３と同様である。 In this embodiment, the operation test management unit 213 is arranged in the memory 201 of the master system 20, and the test component unit 340 having the same function as the change target component unit 320 is arranged in the memory 301 of each slave system 30, The same as in the third embodiment.
　図１８は、実施例４におけるスレーブシステムのハードウェア資源及びソフトウェア資源の構成図である。 FIG. 18 is a configuration diagram of hardware resources and software resources of the slave system according to the fourth embodiment.
　図１８において、メモリ３０１には、システム停止部３２１と、設定変更部３２２と、設定チェック部３２３と、システム起動部３２４と、アプリケーション実行部３２５を有する変更対象コンポーネント部３２０が構築されていると共に、変更対象コンポーネント部３２０と同一の機能を有するテスト用プログラムとしてのテストコンポーネント部３４０が構築されている。テストコンポーネント部３４０は、変更対象コンポーネント部３２０と同様に、システム停止部３４１と、設定変更部３４２と、設定チェック部３４３と、システム起動部３４４と、アプリケーション実行部３４５から構成される。 In FIG. 18, in the memory 301, a change target component unit 320 having a system stop unit 321, a setting change unit 322, a setting check unit 323, a system activation unit 324, and an application execution unit 325 is constructed. A test component unit 340 as a test program having the same function as that of the change target component unit 320 is constructed. Similar to the change target component unit 320, the test component unit 340 includes a system stop unit 341, a setting change unit 342, a setting check unit 343, a system activation unit 344, and an application execution unit 345.
　図１９は、実施例４における配布トランザクション管理部の処理を説明するためのフローチャートである。この処理は、ＣＰＵ２０３が、メモリ２０１の配布トランザクション管理部２１２を起動することによって開始される。 FIG. 19 is a flowchart for explaining the processing of the distribution transaction management unit in the fourth embodiment. This process is started when the CPU 203 activates the distribution transaction management unit 212 of the memory 201.
　図１９において、配布トランザクション管理部２１２は、ステップＳ１３０～ステップＳ１３３と、ステップＳ１３９では、図１０のステップＳ５０～ステップＳ５２と、ステップＳ５７と同様の処理を実行し、ステップＳ１３６～ステップＳ１３８では、図１０のステップＳ５４～ステップＳ５６と同様の処理を実行する。 In FIG. 19, the distribution transaction management unit 212 executes the same processes as in steps S50 to S52 and step S57 of FIG. 10 in steps S130 to S133 and step S139, and in steps S136 to S138, the process shown in FIG. The same processing as step S54 to step S56 is executed.
　一方、ステップＳ１３４では、配布トランザクション管理部２１２は、動作テスト管理部２１３を起動し、テストコンポーネントを含むスレーブシステム３０に属するサーバ３００のアプリケーション実行部３４５に対して、テストコンポーネントの動作テストを実行する（Ｓ１３４）。この際、動作テスト管理部２１３は、テストコンポーネントを含むスレーブシステム３０のサーバ３００に属する設定変更管理部３１０に、アプリケーション実行部３４５による動作テストを指示する。これにより、設定変更管理部３１０が、テストコンポーネント部３４０を介してアプリケーション実行部３４５を起動し、アプリケーション実行部３４５は、テストコンポーネントを稼働し、テストコンポーネントの動作テストを実行する。この場合、アプリケーション実行部３４５は、例えば、テストコンポーネントが、データの分析処理を実行するテスト用アプリケーションプログラムである場合、データ分析処理テスト用アプリケーションプログラムの動作テストを実行する。 On the other hand, in step S134, the distribution transaction management unit 212 activates the operation test management unit 213 and executes the operation test of the test component on the application execution unit 345 of the server 300 belonging to the slave system 30 including the test component. (S134). At this time, the operation test management unit 213 instructs the setting change management unit 310 belonging to the server 300 of the slave system 30 including the test component to perform an operation test by the application execution unit 345. Accordingly, the setting change management unit 310 activates the application execution unit 345 via the test component unit 340, and the application execution unit 345 operates the test component and executes an operation test of the test component. In this case, for example, when the test component is a test application program that executes data analysis processing, the application execution unit 345 executes an operation test of the data analysis processing test application program.
　この後、配布トランザクション管理部２１２は、動作テスト管理部２１３から、アプリケーション実行部３４５による動作テストの結果を取り込み、動作テストが正常に終了したか否かを判定し（Ｓ１３５）、ステップＳ１３５で肯定の判定結果を得た場合、ステップＳ１３６の処理に移行し、ステップＳ１３５で否定の判定結果を得た場合、このルーチンでの処理を終了する。 Thereafter, the distribution transaction management unit 212 fetches the result of the operation test by the application execution unit 345 from the operation test management unit 213, determines whether or not the operation test has ended normally (S135), and affirmative in step S135 If the determination result is obtained, the process proceeds to step S136. If the determination result is negative in step S135, the process in this routine is terminated.
　この場合、スレーブ用サーバ３００は、マスタ用サーバ２００から、設定変更情報に従った設定変更処理の実行を指示する指示情報を受信した場合、複数の変更対象コンポーネントに相当する複数のテストコンポーネントに対して、設定変更情報に従った設定変更処理を実行し、複数のテストコンポーネントに対する設定変更処理が成功したことを条件に、複数の変更対象コンポーネントに対する設定変更処理を実行し、且つ、マスタ用サーバ２００から、複数のテストコンポーネントに対する動作テストの実行を指示する指示情報を受信した場合、設定変更情報が反映された、複数のテストコンポーネントに対する動作テストを実行する。 In this case, when the slave server 300 receives instruction information for instructing execution of the setting change process according to the setting change information from the master server 200, the slave server 300 applies to a plurality of test components corresponding to a plurality of change target components. Then, the setting change process according to the setting change information is executed, the setting change process for the plurality of change target components is executed on the condition that the setting change process for the plurality of test components is successful, and the master server 200 When the instruction information for instructing the execution of the operation test for the plurality of test components is received, the operation test for the plurality of test components reflecting the setting change information is executed.
　さらに、スレーブ用サーバ３００は、動作テストのうち少なくとも１つのテストコンポーネントに対する動作テストが失敗した場合、動作テストが失敗したテストコンポーネントと関連性を有する２以上のテストコンポーネントを、同一のグループに属するテストコンポーネントとして纏め、同一のグループに属するテストコンポーネントに対して、グループ単位でロールバック処理を実行する。 In addition, when the operation test for at least one test component among the operation tests fails, the slave server 300 includes two or more test components having a relationship with the test component for which the operation test has failed in the same group. A rollback process is executed in units of test components that are collected as components and belong to the same group.
　以上のように、サーバ３００は、変更対象コンポーネントに対する設定変更処理が成功した後、テストコンポーネントの動作テストを実行することで、サブシステム３０のテストの動作を踏まえた設定変更チェックを実行することができる。また、本実施例において、実施例３と同様に、変更対象コンポーネントに対する設定変更処理が成功した後、設定変更対象コンポーネントの動作テストを実行することができる。この場合、サブシステム３０の実際の動作を踏まえた設定変更チェック及びサブシステム３０のテストの動作を踏まえた設定変更チェックを実行することができる。 As described above, the server 300 can execute the setting change check based on the test operation of the subsystem 30 by executing the operation test of the test component after the setting change processing for the change target component is successful. it can. In the present embodiment, as in the third embodiment, after the setting change processing for the change target component is successful, the operation test of the setting change target component can be executed. In this case, the setting change check based on the actual operation of the subsystem 30 and the setting change check based on the test operation of the subsystem 30 can be executed.
　図２０は、実施例４における設定変更コミット部の処理を説明するためのフローチャートである。この処理は、ステップＳ１３０とステップＳ１３３の具体的内容であって、マスタシステム２０の配布トランザクション管理部２１２からの指示に基づいてスレーブシステム３０のＣＰＵ３０３が設定変更管理部３１０を起動することによって開始される。 FIG. 20 is a flowchart for explaining the process of the setting change commit unit according to the fourth embodiment. This process is the specific contents of steps S130 and S133, and is started when the CPU 303 of the slave system 30 starts the setting change management unit 310 based on an instruction from the distribution transaction management unit 212 of the master system 20. The
　図２０において、設定変更コミット部３１１は、ステップＳ１５０～ステップＳ１６５では、図１１のステップＳ６０～ステップＳ７５と同様の処理を実行する。 In FIG. 20, the setting change commit unit 311 performs the same processing as in steps S60 to S75 in FIG. 11 in steps S150 to S165.
　以上のように、設定変更処理が正常に終了した場合、テストコンポーネットに対して、設定変更情報の設定内容が反映され、変更対象コンポーネットに対して、設定変更情報の設定内容が反映される。 As described above, when the setting change process ends normally, the setting contents of the setting change information are reflected on the test component, and the setting contents of the setting change information are reflected on the change target component. .
　図２１は、実施例４における設定変更ロールバック部の処理を説明するためのフローチャートである。この処理は、ステップＳ１３８の具体的内容であって、変更対象コンポーネットに対する設定変更処理が失敗したことを判定した設定変更コミット部３１１の判定結果に基づいて、ＣＰＵ３０３が、設定変更管理部３１０を介して設定変更ロールバック部３１２を起動することによって開始される。 FIG. 21 is a flowchart for explaining processing of the setting change rollback unit in the fourth embodiment. This process is the specific content of step S138, and the CPU 303 controls the setting change management unit 310 based on the determination result of the setting change commit unit 311 that has determined that the setting change process for the change target component has failed. This is started by activating the setting change rollback unit 312.
　図２１において、設定変更ロールバック部３１２は、ステップＳ１７０～ステップＳ１７４では、図１７のステップＳ１２０～ステップＳ１２４と同様の処理を実行する。 In FIG. 21, the setting change rollback unit 312 performs the same processes as steps S120 to S124 of FIG. 17 in steps S170 to S174.
　以上のように、設定変更ロールバック部３１２の実行による設定変更部３２２は、設定変更前の設定内容（元の設定内容）に基づいて、変更対象コンポーネットに対して、グループ単位でロールバック処理を実行し、変更対象コンポーネットに対する設定内容をグループ単位で設定変更前の状態に戻し、整合性を確保する。 As described above, the setting change unit 322 by executing the setting change rollback unit 312 performs rollback processing in units of groups for the change target component based on the setting contents before the setting change (original setting contents). To return the setting contents for the change target component to the state before the setting change for each group, and ensure consistency.
　本実施例によれば、実施例１、２と同様の効果を奏することができると共に、変更対象コンポーネントに対する設定変更処理が成功した後、テストコンポーネントの動作テストを実行することで、サブシステム３０のテストの動作を踏まえた設定変更チェックを実行することができる。また、変更対象コンポーネントに対する設定変更処理が成功した後、設定変更対象コンポーネント及びテストコンポーネントの動作テストを実行することで、サブシステム３０の実際の動作を踏まえた設定変更チェック及びサブシステム３０のテストの動作を踏まえた設定変更チェックを実行することができる。この場合、設定変更チェックにテストコンポーネント部３４０を用いた動作テストを含むアトミック処理を行うことができる。 According to the present embodiment, the same effects as those of the first and second embodiments can be obtained, and after the setting change process for the change target component is successful, the operation test of the test component is executed, so that the subsystem 30 It is possible to execute a setting change check based on the test operation. In addition, after the setting change processing for the change target component is successful, an operation test of the setting change target component and the test component is executed, so that the setting change check based on the actual operation of the subsystem 30 and the test of the subsystem 30 are performed. A configuration change check based on the operation can be executed. In this case, an atomic process including an operation test using the test component unit 340 can be performed for the setting change check.
　図２２は、ネットワークに広域ネットワークを用いた分散処理システムの全体構成図である。図２２において、分散処理システム１０におけるネットワーク４０として、ＬＡＮの他に、広域ネットワークとしてのＷＡＮ（Wide　Area　Network）を用いることができる。この場合、マスタシステム２０と各スレーブシステム３０を地理的に分散して配置することができる。例えば、スレーブシステム２０を日本に配置し、スレーブシステム３０のいずれかを米国に配置することもできる。 FIG. 22 is an overall configuration diagram of a distributed processing system using a wide area network as a network. In FIG. 22, a WAN (Wide Area Network) as a wide area network can be used as the network 40 in the distributed processing system 10 in addition to the LAN. In this case, the master system 20 and each slave system 30 can be geographically distributed. For example, the slave system 20 can be arranged in Japan, and any of the slave systems 30 can be arranged in the United States.
　なお、本発明は上記した実施例に限定されるものではなく、様々な変形例が含まれる。例えば、上記した実施例は本発明を分かりやすく説明するために詳細に説明したものであり、必ずしも説明した全ての構成を備えるものに限定されるものではない。また、ある実施例の構成の一部を他の実施例の構成に置き換えることが可能であり、また、ある実施例の構成に他の実施例の構成を加えることも可能である。また、各実施例の構成の一部について、他の構成の追加・削除・置換をすることが可能である。 In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.
　また、上記の各構成、機能等は、それらの一部又は全部を、例えば、集積回路で設計する等によりハードウェアで実現してもよい。また、上記の各構成、機能等は、プロセッサがそれぞれの機能を実現するプログラムを解釈し、実行することによりソフトウェアで実現してもよい。各機能を実現するプログラム、テーブル、ファイル等の情報は、メモリや、ハードディスク、ＳＳＤ（Solid　State　Drive）等の記録装置、または、ＩＣ（Integrated　Circuit）カード、ＳＤ（Secure　Digital）メモリカード、ＤＶＤ（Digital　Versatile　Disc）等の記録媒体に記録して置くことができる。 Also, each of the above-described configurations, functions, etc. may be realized by hardware by designing a part or all of them, for example, by an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files that realize each function is stored in memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD (Secure Digital) memory card, a DVD ( It can be recorded on a recording medium such as Digital Versatile Disc).
　１０　分散処理システム、２０　マスタシステム、３０　スレーブシステム、４０　ネットワーク、５０　管理端末、２００　バッファ、２０１　メモリ、２０３　ＣＰＵ、２０４　ストレージ装置、２０６　構成情報、２１０　運用管理部、２１１　配布管理部、２１２　配布トランザクション管理部、２１３　動作テスト管理部、２２０　バッファ、２３０　設定変更シナリオ情報テーブル、２４０　設定変更シナリオの状況管理テーブル、２５０　設定変更グループの状況管理テーブル、２６０　設定変更コンポーネントの状況管理テーブル、２７０　新規設定情報テーブル、３００　サーバ、３０１　メモリ、３０３　ＣＰＵ、３０４　ストレージ装置、３０６　設定変更管理情報、３０７　設定情報、３１０　設定変更管理部、３１１　設定変更コミット部、３１２　設定変更ロールバック部、３２０　変更対象コンポーネント部、３２１　システム停止部、３２２　設定変更部、３２３　設定チェック部、３２４　システム起動部、３２５　アプリケーション実行部、３３０　バッファ、３４０　テストコンポーネント部、３５０　設定変更バージョンテーブル、３６０　対象コンポーネント設定情報テーブル。 10 distributed processing system, 20 master system, 30 slave system, 40 network, 50 management terminal, 200 buffer, 201 memory, 203 CPU, 204 storage device, 206 configuration information, 210 operation management unit, 211 distribution management unit, 212 distribution transaction Management unit, 213 Operation test management unit, 220 buffer, 230 setting change scenario information table, 240 setting change scenario status management table, 250 setting change group status management table, 260 setting change component status management table, 270 new setting information Table, 300 server, 301 memory, 303 CPU, 304 storage device, 306 setting change management information, 307 setting information, 310 setting change management section, 11 Setting change commit part, 312 Setting change rollback part, 320 Change target component part, 321 System stop part, 322 Setting change part, 323 Setting check part, 324 System start part, 325 Application execution part, 330 buffer, 340 Test component Part, 350 setting change version table, 360 target component setting information table.

Claims (10)

  1. 　マスタシステムと複数のスレーブシステムがネットワークを介して相互に接続される分散処理システムであって、
    　前記マスタシステムは、
    　前記各スレーブシステムの運用を管理すると共に、前記各スレーブシステムに設定される設定情報を管理するマスタ用サーバを有し、
    　前記各スレーブシステムは、
    　前記マスタ用サーバから前記ネットワークを介して転送された設定情報に従ってデータ処理を実行する１以上のスレーブ用サーバを有し、
    　前記マスタ用サーバは、
    　前記各スレーブシステムの前記スレーブ用サーバ上で稼働する要素のうち複数の変更対象コンポーネントに対する処理であって、設定変更情報に従った設定変更処理の実行を指示する指示情報を少なくとも前記ネットワークを介して前記各スレーブシステムの前記スレーブ用サーバに転送し、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントが存在することを条件に、前記複数の変更対象コンポーネントに対して前記設定変更情報に従った設定変更処理を実行し、前記設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、当該設定変更処理が失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを纏め、当該纏められた２以上の変更対象コンポーネントに対して、前記纏められた２以上の変更対象コンポーネントに設定された設定変更情報を、前記指示情報を受信する前に設定された元の設定情報に戻すためのロールバック処理を実行することを特徴とする分散処理システム。     A distributed processing system in which a master system and a plurality of slave systems are connected to each other via a network,
    The master system is
    A master server for managing operation of each slave system and managing setting information set in each slave system;
    Each slave system is
    Having one or more slave servers that execute data processing according to setting information transferred from the master server via the network;
    The master server is
    Processing for a plurality of components to be changed among elements operating on the slave server of each slave system, and instruction information for instructing execution of setting change processing according to setting change information via at least the network Transfer to the slave server of each slave system,
    The slave server of each slave system is:
    When the instruction information is received from the master server, a setting change process according to the setting change information is executed on the plurality of change target components on condition that the plurality of change target components exist. When the setting change process for at least one change target component among the setting change processes fails, the two or more change target components having relevance to the change target component for which the setting change process has failed are collected and collected. For two or more change target components, a rollback for returning the setting change information set to the two or more change target components collected to the original setting information set before receiving the instruction information A distributed processing system characterized by executing processing.
  2. 　請求項１に記載の分散処理システムであって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記複数の変更対象コンポーネントを、前記設定変更処理の処理内容又は前記各変更対象コンポーネントの機能に従って複数のグループに分けて管理し、
    　前記設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、当該失敗した変更対象コンポーネントと同一のグループに属する変更対象コンポーネントに対して、グループ単位で前記ロールバック処理を実行することを特徴とする分散処理システム。     The distributed processing system according to claim 1,
    The slave server of each slave system is:
    The plurality of change target components are divided into a plurality of groups according to the processing content of the setting change process or the function of each change target component, and are managed.
    When the setting change process for at least one change target component among the setting change processes fails, the rollback process is executed in group units for the change target components belonging to the same group as the failed change target component. A distributed processing system characterized by that.
  3. 　請求項１に記載の分散処理システムであって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントに相当する複数のテストコンポーネントに対して、設定変更情報に従った設定変更処理を実行し、前記複数のテストコンポーネントに対する設定変更処理が成功したことを条件に、前記複数の変更対象コンポーネントに対する前記設定変更処理を実行することを特徴とする分散処理システム。     The distributed processing system according to claim 1,
    The slave server of each slave system is:
    When the instruction information is received from the master server, a setting change process according to setting change information is executed for a plurality of test components corresponding to the plurality of change target components, and A distributed processing system, wherein the setting change processing is executed for the plurality of change target components on condition that the setting change processing is successful.
  4. 　請求項１に記載の分散処理システムであって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記複数の変更対象コンポーネントに対する動作テストの実行を指示する指示情報を受信した場合、前記複数の変更対象コンポーネントに対する設定変更処理が成功したことを条件に、前記設定変更情報が反映された前記複数の変更対象コンポーネントに対する動作テストを実行し、前記動作テストのうち少なくとも１つの変更対象コンポーネントに対する動作テストが失敗した場合、当該動作テストが失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを、同一のグループに属する変更対象コンポーネントとして纏め、当該同一のグループに属する変更対象コンポーネントに対して、グループ単位で前記ロールバック処理を実行することを特徴とする分散処理システム。     The distributed processing system according to claim 1,
    The slave server of each slave system is:
    When the instruction information instructing execution of the operation test for the plurality of change target components is received from the master server, the setting change information is obtained on condition that the setting change processing for the plurality of change target components is successful. When an operation test is performed on the reflected change target components and at least one of the operation tests fails, the operation test is related to the change target component that has failed. A distributed processing system characterized in that the above change target components are grouped as change target components belonging to the same group, and the rollback process is executed in units of the change target components belonging to the same group.
  5. 　請求項１に記載の分散処理システムであって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントに相当する複数のテストコンポーネントに対して、設定変更情報に従った設定変更処理を実行し、前記複数のテストコンポーネントに対する設定変更処理が成功したことを条件に、前記複数の変更対象コンポーネントに対する前記設定変更処理を実行し、且つ、前記マスタ用サーバから、前記複数のテストコンポーネントに対する動作テストの実行を指示する指示情報を受信した場合、前記設定変更情報が反映された前記複数のテストコンポーネントに対する動作テストを実行し、前記動作テストのうち少なくとも１つのテストコンポーネントに対する動作テストが失敗した場合、当該動作テストが失敗したテストコンポーネントと関連性を有する２以上のテストコンポーネントを、同一のグループに属するテストコンポーネントとして纏め、当該同一のグループに属するテストコンポーネントに対して、グループ単位で前記ロールバック処理を実行することを特徴とする分散処理システム。     The distributed processing system according to claim 1,
    The slave server of each slave system is:
    When the instruction information is received from the master server, a setting change process according to setting change information is executed for a plurality of test components corresponding to the plurality of change target components, and Instruction information for instructing execution of operation tests on the plurality of test components from the master server is executed on the condition that the setting change processing is successful. If received, the operation test is performed on the plurality of test components reflecting the setting change information, and if the operation test on at least one of the operation tests fails, the test component on which the operation test has failed Is related to Distributed processing system and executes or more test components, collectively as a test component belonging to the same group, with respect to the test component belonging to the same group, the rollback process in groups.
  6. 　マスタシステムと複数のスレーブシステムがネットワークを介して相互に接続され、前記マスタシステムは、前記各スレーブシステムの運用を管理すると共に、前記各スレーブシステムに設定される設定情報を管理するマスタ用サーバを有し、前記各スレーブシステムは、前記マスタ用サーバから前記ネットワークを介して転送された設定情報に従ってデータ処理を実行する１以上のスレーブ用サーバを有する分散処理システムの運用方法であって、
    　前記マスタ用サーバは、
    　前記各スレーブシステムの前記スレーブ用サーバ上で稼働する要素のうち複数の変更対象コンポーネントに対する処理であって、設定変更情報に従った設定変更処理の実行を指示する指示情報を少なくとも前記ネットワークを介して前記各スレーブシステムの前記スレーブ用サーバに転送するステップを実行し、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントが存在することを条件に、前記複数の変更対象コンポーネントに対して前記設定変更情報に従った設定変更処理を実行するステップと、
    　前記設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、当該設定変更処理が失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを纏め、当該纏められた２以上の変更対象コンポーネントに対して、前記纏められた２以上の変更対象コンポーネントに設定された設定変更情報を、前記指示情報を受信する前に設定された元の設定情報に戻すためのロールバック処理を実行するステップと、を実行することを特徴とする分散処理システムの運用方法。     A master system and a plurality of slave systems are connected to each other via a network, and the master system manages a master server that manages operation of each slave system and manages setting information set in each slave system. Each of the slave systems is a method for operating a distributed processing system having one or more slave servers that execute data processing according to setting information transferred from the master server via the network,
    The master server is
    Processing for a plurality of components to be changed among elements operating on the slave server of each slave system, and instruction information for instructing execution of setting change processing according to setting change information via at least the network Performing a transfer step to the slave server of each slave system;
    The slave server of each slave system is:
    When the instruction information is received from the master server, a setting change process according to the setting change information is executed on the plurality of change target components on condition that the plurality of change target components exist. Steps,
    When the setting change process for at least one change target component in the setting change process fails, two or more change target components having relevance to the change target component for which the setting change process has failed are collected and the combined 2 Rollback processing for returning the setting change information set in the two or more change target components collected to the original setting information set before receiving the instruction information for the above change target components And a step of executing a distributed processing system operation method.
  7. 　請求項６に記載の分散処理システムの運用方法であって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記複数の変更対象コンポーネントを、前記設定変更処理の処理内容又は前記各変更対象コンポーネントの機能に従って複数のグループに分けて管理するステップと、
    　前記設定変更処理のうち少なくとも１つの変更対象コンポーネントに対する設定変更処理が失敗した場合、当該失敗した変更対象コンポーネントと同一のグループに属する変更対象コンポーネントに対して、グループ単位で前記ロールバック処理を実行するステップと、を実行することを特徴とする分散処理システムの運用方法。     An operation method of the distributed processing system according to claim 6,
    The slave server of each slave system is:
    Managing the plurality of change target components by dividing them into a plurality of groups according to the processing content of the setting change process or the function of each change target component;
    When the setting change process for at least one change target component among the setting change processes fails, the rollback process is executed in group units for the change target components belonging to the same group as the failed change target component. And a step of executing the distributed processing system.
  8. 　請求項６に記載の分散処理システムの運用方法であって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントに相当する複数のテストコンポーネントに対して、設定変更情報に従った設定変更処理を実行するステップと、その後、前記複数のテストコンポーネントに対する設定変更処理が成功したことを条件に、前記複数の変更対象コンポーネントに対する前記設定変更処理を実行するステップと、を実行することを特徴とする分散処理システムの運用方法。     An operation method of the distributed processing system according to claim 6,
    The slave server of each slave system is:
    When the instruction information is received from the master server, executing a setting change process according to setting change information for a plurality of test components corresponding to the plurality of change target components; And a step of executing the setting change processing for the plurality of change target components on condition that the setting change processing for the test component is successful.
  9. 　請求項６に記載の分散処理システムの運用方法であって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記複数の変更対象コンポーネントに対する動作テストの実行を指示する指示情報を受信した場合、前記複数の変更対象コンポーネントに対する設定変更処理が成功したことを条件に、前記設定変更情報が反映された前記複数の変更対象コンポーネントに対する動作テストを実行するステップと、
    　前記動作テストのうち少なくとも１つの変更対象コンポーネントに対する動作テストが失敗した場合、当該動作テストが失敗した変更対象コンポーネントと関連性を有する２以上の変更対象コンポーネントを、同一のグループに属する変更対象コンポーネントとして纏め、当該同一のグループに属する変更対象コンポーネントに対して、グループ単位で前記ロールバック処理を実行するステップと、を実行することを特徴とする分散処理システムの運用方法。     An operation method of the distributed processing system according to claim 6,
    The slave server of each slave system is:
    When the instruction information instructing execution of the operation test for the plurality of change target components is received from the master server, the setting change information is obtained on condition that the setting change processing for the plurality of change target components is successful. Performing an operation test on the reflected plurality of change target components;
    When an operation test for at least one change target component among the operation tests fails, two or more change target components having relevance to the change target component for which the operation test has failed are set as change target components belonging to the same group. In summary, a step of executing the rollback processing in units of groups for the change target components belonging to the same group.
  10. 　請求項６に記載の分散処理システムの運用方法であって、
    　前記各スレーブシステムの前記スレーブ用サーバは、
    　前記マスタ用サーバから、前記指示情報を受信した場合、前記複数の変更対象コンポーネントに相当する複数のテストコンポーネントに対して、設定変更情報に従った設定変更処理を実行するステップと、
    　前記複数のテストコンポーネントに対する設定変更処理が成功したことを条件に、前記複数の変更対象コンポーネントに対する前記設定変更処理を実行するステップと、
    　前記マスタ用サーバから、前記複数のテストコンポーネントに対する動作テストの実行を指示する指示情報を受信した場合、前記設定変更情報が反映された前記複数のテストコンポーネントに対する動作テストを実行するステップと、
    　前記動作テストのうち少なくとも１つのテストコンポーネントに対する動作テストが失敗した場合、当該動作テストが失敗したテストコンポーネントと関連性を有する２以上のテストコンポーネントを、同一のグループに属するテストコンポーネントとして纏め、当該同一のグループに属するテストコンポーネントに対して、グループ単位で前記ロールバック処理を実行するステップと、を実行することを特徴とする分散処理システムの運用方法。     An operation method of the distributed processing system according to claim 6,
    The slave server of each slave system is:
    When receiving the instruction information from the master server, executing a setting change process according to setting change information for a plurality of test components corresponding to the plurality of change target components;
    Executing the setting change process for the plurality of change target components on the condition that the setting change process for the plurality of test components is successful;
    When receiving instruction information for instructing execution of operation tests for the plurality of test components from the master server, executing the operation tests for the plurality of test components reflecting the setting change information;
    When an operation test for at least one test component among the operation tests fails, two or more test components having relevance to the test component for which the operation test has failed are collected as test components belonging to the same group, and the same And a step of executing the rollback processing in units of groups for test components belonging to the group.
PCT/JP2014/064932 2014-06-05 2014-06-05 Distributed processing system and operation method therefor WO2015186219A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/064932 WO2015186219A1 (en) 2014-06-05 2014-06-05 Distributed processing system and operation method therefor

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/064932 WO2015186219A1 (en) 2014-06-05 2014-06-05 Distributed processing system and operation method therefor

Publications (1)

Publication Number Publication Date
WO2015186219A1 true WO2015186219A1 (en) 2015-12-10

Family

ID=54766315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/064932 WO2015186219A1 (en) 2014-06-05 2014-06-05 Distributed processing system and operation method therefor

Country Status (1)

Country Link
WO (1) WO2015186219A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2018174223A1 (en) * 2017-03-23 2020-01-23 日本電気株式会社 Operation management server, development operation support system, their method and program

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0464146A (en) * 1990-07-04 1992-02-28 Hitachi Ltd Optimizing system for commitment processing in distributed system
JP2005526298A (en) * 2001-07-16 2005-09-02 ビーイーエイ　システムズ，　インコーポレイテッド Data replication protocol
WO2006057061A1 (en) * 2004-11-29 2006-06-01 Fujitsu Limited Distributed transaction processing method, device, and program
JP2011197831A (en) * 2010-03-17 2011-10-06 Ricoh Co Ltd Information processing system, management apparatus, information processing apparatus, installation processing method, program and storage medium
JP2014510314A (en) * 2011-04-15 2014-04-24 株式会社日立製作所 File sharing system and file sharing method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0464146A (en) * 1990-07-04 1992-02-28 Hitachi Ltd Optimizing system for commitment processing in distributed system
JP2005526298A (en) * 2001-07-16 2005-09-02 ビーイーエイ　システムズ，　インコーポレイテッド Data replication protocol
WO2006057061A1 (en) * 2004-11-29 2006-06-01 Fujitsu Limited Distributed transaction processing method, device, and program
JP2011197831A (en) * 2010-03-17 2011-10-06 Ricoh Co Ltd Information processing system, management apparatus, information processing apparatus, installation processing method, program and storage medium
JP2014510314A (en) * 2011-04-15 2014-04-24 株式会社日立製作所 File sharing system and file sharing method

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2018174223A1 (en) * 2017-03-23 2020-01-23 日本電気株式会社 Operation management server, development operation support system, their method and program
US11500760B2 (en) 2017-03-23 2022-11-15 Nec Corporation Operation management server, development operation support system, method thereof, and non-transitory computer readable medium storing program thereof

Similar Documents

Publication Publication Date Title
US8230264B2 (en) System evaluation apparatus
US8910172B2 (en) Application resource switchover systems and methods
US8856592B2 (en) Mechanism to provide assured recovery for distributed application
CN108270726B (en) Application instance deployment method and device
US7496783B1 (en) Merging cluster nodes during a restore
US9716612B2 (en) Evaluation of field replaceable unit dependencies and connections
US11182253B2 (en) Self-healing system for distributed services and applications
WO2013140608A1 (en) Method and system that assist analysis of event root cause
US9753718B1 (en) Non-disruptive upgrade including rollback capabilities for a distributed file system operating within a cluster of nodes
CN111651353A (en) Fault injection method and device, electronic equipment and storage medium
CN102025778A (en) Software version upgrading work method based on Shell
US10353786B2 (en) Virtualization substrate management device, virtualization substrate management system, virtualization substrate management method, and recording medium for recording virtualization substrate management program
CN104461747A (en) Distributed type task scheduling system
US7181574B1 (en) Server cluster using informed prefetching
CN103200036A (en) Automated configuration method of electrical power system cloud computing platform
Veeraraghavan et al. Maelstrom: Mitigating datacenter-level disasters by draining interdependent traffic safely and efficiently
US20240045793A1 (en) Method and system for scalable performance testing in cloud computing environments
KR102210408B1 (en) Method for duplication of virtualization server and Virtualization control apparatus thereof
US10860431B2 (en) System and method for fault tolerant backup generation in a virtual environment
US20120036496A1 (en) Plug-in based high availability application management framework (amf)
US8468386B2 (en) Detecting and recovering from process failures
CN109002263B (en) Method and device for adjusting storage capacity
KR20180045818A (en) Program, system, and information processing method
WO2015186219A1 (en) Distributed processing system and operation method therefor
US10789129B1 (en) Rolling restoration of enterprise business services following service disruption

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14893870

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14893870

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP