JP6920270B2 - Operation execution system, operation execution device, operation execution method and program - Google Patents

Description

The present invention relates to an operation execution system, an operation execution device, an operation execution method, and a program.

In recent years, various business systems have been used in companies. For example, in a bank, banking business is performed using various business systems such as a core banking system and an information system. Since routine work such as maintenance work is often performed in these business systems on a regular basis, the person in charge of work needs an account ID of the business system for these works.

On the other hand, there is known a technique of collectively managing the account ID of a business system on a server and lending the account ID (and its password) to a person in charge of work or the like in response to an application from the person in charge.

By the way, in recent years, a technique for automating operations for various tasks that would normally be performed manually has become known. For example, a technique for automating work in the operation of an IT system is known (Patent Document 1). We also know the technology to automatically execute operations for various tasks that would otherwise be done manually by executing a program written in a script language (hereinafter, also simply referred to as "script"). It is also sold and distributed as a product.

Japanese Unexamined Patent Publication No. 2014-48860

Here, when the operation for maintenance work etc. for the above business system is automated by executing the script, the execution subject of this script is executed based on the account ID (and its password) of the business system. You need to grant permissions.

However, in this case, for example, the user of the terminal that executes the script may be able to refer to the account ID, which is a security problem. This is a problem, especially for companies that have strict security requirements.

An embodiment of the present invention has been made in view of the above points, and an object of the present invention is to improve security at the time of executing a script that automates a predetermined operation.

In order to achieve the above object, an embodiment of the present invention is an operation execution system including a management device for managing account information and an operation execution device for executing one or more scripts for realizing a predetermined operation. Therefore, the management device receives one or more account information used for executing each of the one or more scripts in response to an inquiry from the operation execution device or when the start date and time of the one or more scripts is reached. The operation execution device has a transmission means for transmitting to the operation execution device, and the operation execution device has a transmission means of the one or more scripts when the start date and time of the one or more scripts is reached or in response to an instruction by a user of the operation execution device. For each, of the one or more account information, the setting means for setting the account information used for executing the script and the execution for executing each of the one or more scripts for which the account information is set by the setting means. It is characterized by having means and.

It is possible to improve security when executing a script that automates a predetermined operation.

It is a figure which shows an example of the whole structure of the operation script execution system which concerns on this embodiment. It is a figure for demonstrating an example of a script group (scenario). It is a figure which shows an example of account information. It is a figure which shows an example of application information. It is a sequence diagram for explaining the flow from application to approval of a workflow. It is a sequence diagram for demonstrating the flow at the time of starting a scenario by automatic start and executing an operation script. It is a sequence diagram for demonstrating the flow at the time of starting a scenario by manual start and executing an operation script.

Hereinafter, embodiments of the present invention (the present embodiment) will be described in detail. In the present embodiment, an operation script execution system 1 that executes a script that automates a predetermined operation will be described. At this time, the operation script execution system 1 according to the present embodiment is based on the application for executing the script and its approval, with the authority specified in this application and approval and the password as it is encrypted. Execute the script. This makes it possible to improve security when executing scripts.

Hereinafter, a script that executes a predetermined operation is also referred to as an “operation script”. Further, a set of operation scripts that are composed of one or more operation scripts and realize one work content by the operations executed by these operation scripts is referred to as a "script group" or a "scenario".

<Overall configuration of operation script execution system 1>
First, the overall configuration of the operation script execution system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of the operation script execution system 1 according to the present embodiment.

As shown in FIG. 1, the operation script execution system 1 according to the present embodiment includes one or more operation script execution terminals 10, an account management device 20, one or more application terminals 30, and one or more approval terminals 40. And one or more operation target servers 50. Further, these terminals, devices and servers are communicably connected via a network N such as the Internet or a LAN (Local Area Network).

The operation target server 50 is various business systems or the like that are the operation targets of the operation script. A business system is a variety of computers or computer systems used in a company's business activities. The business system may include a computer system called a core system. Examples of business systems include accounting systems, accounting systems, information systems, sales management systems, production management systems, inventory management systems, expense settlement systems, personnel management systems, and the like.

Here, the account ID and password of the operation target server 50 are managed by the account management device 20 as account information. Further, when the password is changed on the operation target server 50, a new account ID is added, an existing account ID is deleted, etc., these changes, additions, and deletions are reflected in the account management device 20. Will be done.

In order to perform an operation on the operation target server 50 by the operation script, it is necessary that the execution subject of the operation script is granted the authority corresponding to the operation. Such authority is determined by the account ID used when the execution subject logs in to the operation target server 50. The account ID includes, for example, an ID having administrator authority (so-called "privileged ID") such as "root" and "administrator", and other IDs (so-called "general ID"). Further, even if it is a general ID, it may have different authority depending on the account ID.

The application terminal 30 is a terminal device that makes a workflow application as an application for executing an operation script. As the application terminal 30, for example, various terminal devices such as a PC (personal computer), a smartphone, and a tablet terminal are used.

The application terminal 30 has an application processing unit 301 as a functional unit. The application processing unit 301 executes a process for making a workflow application. The application processing unit 301 is realized by a process of causing a CPU (Central Processing Unit) to execute one or more programs installed in the application terminal 30.

Here, the workflow application includes, for example, information about each operation script constituting the scenario (hereinafter, also referred to as “script information”) and the like. The script information is information including a script file of the operation script, information indicating the operation target server 50 operated by the operation script, an account ID of the operation target server 50, parameters of the operation script, and the like.

The approval terminal 40 is a terminal device that approves (workflow approval) the workflow application applied by the application terminal 30. As the approval terminal 40, for example, various terminal devices such as a PC, a smartphone, and a tablet terminal are used.

The approval terminal 40 has an approval processing unit 401 as a functional unit. The approval processing unit 401 executes a process for approving the workflow application. The approval processing unit 401 is executed by a process of causing the CPU to execute one or more programs installed in the approval terminal 40.

The account management device 20 is a computer or computer system that manages the account information of the operation target server 50. The account management device 20 also manages workflow application information and controls execution of operation scripts.

The account management device 20 has a workflow processing unit 201, a script information control unit 202, and a manual activation instruction unit 203 as functional units. Further, the account management device 20 has a storage unit 204.

The workflow processing unit 201 executes processing related to workflow application and approval. For example, the workflow processing unit 201 stores the application information for which the workflow has been applied in the storage unit 204, or updates the application information in response to the workflow approval (that is, updates the application information to “approved”). ..

The script information control unit 202 controls to execute each operation script constituting the scenario on the operation script execution terminal 10. Here, in the present embodiment, there are two methods of "automatic start" and "manual start" as a method of starting the scenario by the operation script execution terminal 10 (that is, a method of starting the execution of the operation script constituting the scenario). Suppose there is. The "automatic start" is a method of automatically starting the corresponding scenario on the operation script execution terminal 10 when the start date and time specified in the approved application information is reached. On the other hand, "manual start" means that when the start date and time specified in the approved application information is reached, a predetermined screen (hereinafter, also referred to as "start screen") is displayed on the operation script execution terminal 10. This is a method of starting the corresponding scenario according to the user's start instruction operation after displaying it.

The script information control unit 202 transmits control information for controlling the execution of each operation script constituting the scenario and necessary information necessary for executing each of these operation scripts to the operation script execution terminal 10. Here, the control information is, for example, script information of each operation script that constitutes a scenario. Further, the necessary information is, for example, account information of the operation target server 50 operated by the operation script.

The manual start instruction unit 203 displays a predetermined start screen on the operation script execution terminal 10 when the start method of the scenario is “manual start”. That is, the manual activation instruction unit 203 transmits the display instruction of the activation screen to the operation script execution terminal 10.

The storage unit 204 stores various information. Examples of the information stored in the storage unit 204 include account information and application information. Details of account information and application information will be described later.

The workflow processing unit 201, the script information control unit 202, and the manual activation instruction unit 203 are realized by a process of causing the CPU to execute one or more programs installed in the account management device 20. Further, the storage unit 204 is a storage device (for example, an auxiliary storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive)) included in the account management device 20 or a storage device connected to the account management device 20 via a network. It can be realized by using a device or the like.

The operation script execution terminal 10 is a terminal device that executes each operation script that constitutes a scenario. As the operation script execution terminal 10, for example, various terminal devices such as a PC, a smartphone, and a tablet terminal are used.

The operation script execution terminal 10 has a screen display unit 101, an activation control unit 102, and an execution control unit 103 as functional units. Further, the operation script execution terminal 10 has a storage unit 104.

The screen display unit 101 displays the startup screen in response to an instruction (display instruction of the startup screen) from the account management device 20. In addition, the screen display unit 101 displays a screen for the user to select a scenario (hereinafter, also referred to as a “target scenario list”). When the corresponding scenario is selected from the target scenario list, the scenario is activated. The target scenario list includes UI parts such as buttons for selecting and activating a scenario.

The activation control unit 102 controls the activation of the scenario. Here, the start control unit 102 differs in the method of starting the scenario between "automatic start" and "manual start". When activating the "automatic activation" scenario, the activation control unit 102 inquires the account management device 20 of the existence of control information and necessary information at predetermined time intervals, and controls control information and necessary information as a response to this inquiry. Is returned, the scenario based on the control information is activated. On the other hand, when activating the "manual start" scenario, the start control unit 102 selects after the start instruction operation from the user (that is, the "scenario selection operation" or the "scenario selection operation" is performed. When the required information (and control information) is transmitted from the account management device 20 and the operation to activate the scenario is performed, the scenario based on the control information is activated.

When the scenario is started by the start control unit 102, the execution control unit 103 executes each operation script constituting the scenario. At this time, the execution control unit 103 executes the operation script represented by the script information according to, for example, among the parameters included in the script information, the parameters representing the execution timing (for example, the execution date and time, the execution order, etc.). As a result, each operation script that constitutes the scenario performs a predetermined operation on the operation target (for example, the operation target server 50).

Here, the operation target of the operation script may be not only the operation target server 50 but also various application programs (hereinafter, also referred to as “local application 60”) installed in the operation script execution terminal 10. Examples of the local application 60 include various utilities such as file compression / decompression software, document applications such as spreadsheet software and document creation software, and the like. By targeting the local application 60, for example, the operation result for the operation target server 50 can be processed by the local application 60 (for example, decompression of a compressed file by file compression / decompression software, processing by spreadsheet software, etc.). Will be able to.

The storage unit 104 stores various information. Examples of the information stored in the storage unit 104 include control information and necessary information. In addition, the storage unit 104 also stores the execution results and the like of each operation script that constitutes the scenario.

The screen display unit 101, the activation control unit 102, and the execution control unit 103 are realized by a process of causing the CPU to execute one or more programs installed in the operation script execution terminal 10. Further, the storage unit 104 can be realized by using a storage device (for example, an auxiliary storage device such as an HDD or SSD, various memories, etc.) included in the operation script execution terminal 10.

The configuration of the operation script execution system 1 shown in FIG. 1 is an example and may be another configuration. For example, the application terminal 30 and the approval terminal 40 do not have to be separated, and the same terminal may function as either the application terminal 30 or the approval terminal 40 depending on the user who logs in to the account management device 20. Further, the application terminal 30 may function as the operation script execution terminal 10. Further, for example, the storage unit 204 of the account management device 20 may be realized by a plurality of storage units or DBs (databases).

<Script group (scenario)>
Here, as a specific example of the script group (scenario), a certain operation target server 50 (hereinafter, also referred to as "operation target server A") and another operation target server 50 (hereinafter, "operation target server"). FIG. 2 shows a scenario (scenario name: “performance information acquisition scenario”) in which performance information is acquired from (also referred to as “B”) and a report is created. FIG. 2 is a diagram for explaining an example of a script group (scenario).

The performance information acquisition scenario shown in FIG. 2 is composed of three operation scripts, an operation script 1, an operation script 2, and an operation script 3, and is executed in the order of the operation script 1, the operation script 2, and the operation script 3. It shall be done.

The operation script 1 executes, for example, the following operations 1-1 to 1-4 in order.

Operation 1-1: Operation to log in to the operation target server A Operation 1-2: Operation to execute the performance information output command Operation 1-3: Operation to compress the execution result of the performance information output command and create a compressed file Operation 1-4: Operation of transmitting the compressed file to the operation script execution terminal 10 Next, the operation script 2 executes, for example, the following operations 2-1 to 2-5 in order.

Operation 2-1: Log in to the operation target server B Operation 2-2: For example, an operation to acquire a file list by using a dir command or an ls command Operation 2-3: An operation to acquire performance monitor information Operation 2-4: A file Operation to compress the list and performance monitor information to create a compressed file Operation 2-5: Operation to send the compressed file to the operation script execution terminal 10 Finally, the operation script 3 is, for example, the following operations 3-1 to. Operations 3-2 are executed in order.

Operation 3-1: Decompress the compressed file received from the operation target server A and the compressed file received from the operation target server B Operation 3-2: Decompress the decompressed file with the local application 60 (for example, table calculation software, etc.) ) To create a report showing the performance information of the operation target server A and the operation target server B. In this way, the operation script execution terminal 10 executes each operation script that constitutes the scenario. The work content represented by the scenario is realized.

<Account information>
Next, the account information will be described with reference to FIG. FIG. 3 is a diagram showing an example of account information. One or more account information is stored in the storage unit 204 of the account management device 20.

As shown in FIG. 3, the account information includes "operation target server", "account ID", "password" and the like as data items (also referred to as information items or attributes).

Information that identifies the operation target server 50 (for example, a server name, etc.) is set in the "operation target server". The account ID of the operation target server 50 is set in the "account ID". A password corresponding to the account ID is set in the "password". The password is encrypted and then set in the account information.

As described above, the account information is information in which the information indicating the operation target server 50, the account ID, and the password are associated with each other. In addition to the above data items, the account information may include, for example, data items such as a "domain" in which the domain (or group) to which the account ID belongs is set.

<Application information>
Next, the application information will be described with reference to FIG. FIG. 4 is a diagram showing an example of application information. One or more application information is stored in the storage unit 204 of the account management device 20.

As shown in FIG. 4, the application information includes data items such as "application ID", "applicant login ID", "status", "applicant", "application name", "startup method", and "execution terminal". Includes "name", "start date and time", "script information" and the like.

The application ID is set in the "application ID" as information for identifying the workflow. In the "applicant login ID", the login ID of the applicant who applied for the workflow (that is, the login ID of the user who operates the application terminal 30) is set.

In the "status", the status of the workflow, such as pending or approved, is set. "Applying" is, for example, a status indicating that the workflow has not been approved. On the other hand, "approved" is a status indicating that the workflow has been approved.

The name (for example, name, etc.) of the applicant who applied for the workflow is set in the "applicant". The application name specified at the time of application for the workflow is set in the "application name".

In the "starting method", the starting method of the scenario specified at the time of applying for the workflow is set. As described above, the scenario activation method includes automatic activation and manual activation.

In the "execution terminal name", information indicating the operation script execution terminal 10 specified at the time of applying for the workflow (for example, the name of the operation script execution terminal 10 or the IP (Internet Protocol) address, etc.) is set. The operation script set in the "execution terminal name" The scenario is started on the execution terminal 10, and the operation script constituting the scenario is executed.

In the "start date and time", the start date and time of the scenario specified at the time of applying for the workflow is set. One or more script information specified at the time of applying for the workflow is set in the "script information". An arbitrary number of script information of one or more is set in the "script information", but an upper limit (for example, up to five script information can be set) may be set.

Here, each script information includes "script file", "operation target server", "account ID", "parameter" and the like as data items.

In the "script file", a script file (or information indicating the storage location thereof), which is the substance of the operation script, is set. A script file is a program (or source code, etc.) in which various operations are described in a predetermined script language.

Information (for example, a server name, etc.) that identifies the operation target server 50 that is the operation target of the operation script is set in the "operation target server". In the "account ID", an account ID of the operation target server 50, which is used for executing the operation script, is set. Various parameters of the script file are set in the "parameter". Examples of such parameters include the execution conditions of the operation script (for example, execution date and time, execution order, etc.), the output destination of the execution result of the operation script, and the like. At least one of the "operation target server", "account ID", and "parameter" included in the script information may be directly specified in the script file.

Here, when the operation target of the operation script is the local application 60, for example, information for identifying the operation target local application 60 is set in the "operation target server", and an empty value is set in the "account ID". (Null) may be set.

As described above, the application information is information including various information (including script information) designated at the time of applying for the workflow. For example, among the above data items, the "execution terminal name", "start date and time", and the like may be set only when automatic startup is set in the "starting method". In addition to the above data items, the application information includes, for example, a "start type" that sets a repetition method (for example, daily or weekly) when the scenario is repeatedly started, and the scenario is repeatedly started. In this case, data items such as "end date" for setting the end date (or end date and time) of the scenario may be included.

<Processing flow>
Next, the flow of processing executed by the operation script execution system 1 according to the present embodiment will be described.

≪Application and approval of workflow≫
Hereinafter, the flow when applying for and approving the workflow will be described with reference to FIG. FIG. 5 is a sequence diagram for explaining the flow from application to approval of the workflow.

First, the application processing unit 301 of the application terminal 30 displays the workflow application screen (step S101). The workflow application screen is a screen for making a workflow application. On the workflow application screen, among the data items included in the application information, at least "application name", "startup method", "execution terminal name", "start date and time", and "script information" are specified in the specification fields. Is included. The user (applicant) of the application terminal 30 can specify a desired value or information in these designation fields. The script file included in the script information may be specified in the form of an attached file, for example.

Next, the application processing unit 301 of the application terminal 30 accepts the workflow application operation on the workflow application screen (step S102). The applicant specifies various information (for example, application name, start method, execution terminal name, start date and time, script information, etc.) on the workflow application screen, and then presses the application button or the like to perform the workflow application operation. It can be carried out. In addition to the above-mentioned various information, a user (approver) who can approve the workflow may be specified on the workflow application screen.

When the application processing unit 301 of the application terminal 30 receives the workflow application operation, it transmits the workflow application to the account management device 20 (step S103). The workflow application includes various information specified by the applicant on the workflow application screen (for example, application name, activation method, execution terminal name, start date and time, script information, etc.) and information indicating the applicant (for example, login). ID, name, etc.) are included.

When the workflow processing unit 201 of the account management device 20 receives the workflow application, various information included in the workflow application (for example, application name, activation method, execution terminal name, start date and time and script information, applicant's login ID, etc. Create application information from (name, etc.) (step S104). That is, the workflow processing unit 201 generates the application ID, and then creates the application information including the application ID and the above-mentioned various information. At this time, in the "status" of the application information, for example, an application in progress indicating that the application has not been approved is set.

Although the application information is created by the account management device 20, the application information may be created by the application terminal 30.

Next, the workflow processing unit 201 of the account management device 20 stores the application information in the storage unit 204 (step S105). As a result, for example, the application information whose status is being applied for is stored in the storage unit 204.

When approving the workflow, the approval processing unit 401 of the approval terminal 40 displays the workflow approval screen (step S106). The workflow approval screen is a screen for performing workflow approval. On the workflow approval screen, a list of workflows that can be approved by the user (approver) of the approval terminal 40 is displayed.

Next, the approval processing unit 401 of the approval terminal 40 accepts the workflow approval operation on the workflow approval screen (step S107). The approver can perform the workflow approval operation by designating or selecting a desired workflow from the list of approvable workflows and then pressing the approval button or the like.

When the approval processing unit 401 of the approval terminal 40 receives the workflow approval operation, the approval processing unit 401 transmits the workflow approval to the account management device 20 (step S108). The workflow approval includes, for example, an application ID of a workflow in which a workflow approval operation is performed by an approver on the workflow approval screen.

Upon receiving the workflow approval, the workflow processing unit 201 of the account management device 20 updates the status of the corresponding application information among the application information stored in the storage unit 204 to approved (step S109). That is, for example, the workflow processing unit 201 updates the status of the application information indicated by the application ID included in the workflow approval among the application information stored in the storage unit 204 to approved.

As described above, the workflow for invoking the scenario (that is, executing each operation script constituting the scenario) on the operation script execution terminal 10 is applied for and approved. When the workflow is applied for and approved, the scenario is automatically created on the corresponding operation script execution terminal 10 according to the start instruction operation when the start method is automatic start and when the start method is manual start. It will be started.

≪Scenario start by automatic start and execution of operation script≫
Hereinafter, the flow when the scenario is started by automatic start and each operation script constituting this scenario is executed will be described with reference to FIG. FIG. 6 is a sequence diagram for explaining the flow when the scenario is started by the automatic start and the operation script is executed.

The activation control unit 102 of the operation script execution terminal 10 inquires the account management device 20 of the existence of control information and necessary information of the scenario to be activated on the own terminal at predetermined time intervals (for example, every minute) (step S201). ). This inquiry includes, for example, the name of the execution terminal (for example, the name of the operation script execution terminal 10, the IP address, etc.).

When the script information control unit 202 of the account management device 20 receives an inquiry from the operation script execution terminal 10, whether or not the application information of the scenario to be activated on the operation script execution terminal 10 is stored in the storage unit 204. judge. That is, the script information control unit 202 determines whether or not the application information in which the execution terminal name included in the inquiry is specified and the status is approved is stored in the storage unit 204.

Then, when the corresponding application information is stored in the storage unit 204, the script information control unit 202 transmits the script information of the application information, the control information including the start date and time, and the like to the operation script execution terminal 10 of the inquiry source. Transmit (step S202). In addition to the script information and the start date and time, the control information includes arbitrary information (for example, if the application information includes "start type", "end date", etc., the start type and end date, etc.). It may be.

Next, the script information control unit 202 of the account management device 20 inquires about the necessary information including the account information corresponding to the script information of the application information among the account information stored in the storage unit 204. It is transmitted to the operation script execution terminal 10 (step S203). The account information corresponding to the script information is the account information having the same account ID as the account ID included in the script information. In addition to the account information, the required information may include arbitrary information.

When the operation script execution terminal 10 receives the control information and the necessary information transmitted in steps S202 and S203, the operation script execution terminal 10 stores the received control information and the necessary information in the storage unit 104.

Here, if the corresponding application information is not stored in the storage unit 204 in step S202, the steps S202 to S203 described above and steps S203 to S205 described later are not executed. After that, it is assumed that the above steps S202 and S203 are executed, and the control information and the necessary information are stored in the storage unit 104 of the operation script execution terminal 10.

The activation control unit 102 of the operation script execution terminal 10 refers to the control information stored in the storage unit 104, and when the current date and time becomes the start date and time included in the control information, the control information is added to the control information. Invokes a scenario based on each included script information (step S204). The activation of the scenario is to start the execution of each operation script represented by each script information included in the control information. The activation control unit 102 requests the execution control unit 103 to execute each operation script constituting the scenario in response to the activation of the scenario.

Next, the execution control unit 103 of the operation script execution terminal 10 uses various information such as account information (the script file is used) for the script file of each script information included in the control information stored in the storage unit 104. Set the password corresponding to the account ID to be executed (step S205). That is, the execution control unit 103 sets the password (and account ID) included in the account information in the script file, for example, by using the account information corresponding to the account ID used by the script file. At this time, since the password is encrypted, the execution control unit 103 decrypts the password and sets the decrypted password in the script file, for example, on the memory. As a result, the password used for executing the operation script can be hidden from the user of the operation script execution terminal 10 that executes the operation script represented by this script file.

In step S205 described above, various information necessary for executing the operation script is set in the script file in addition to the password.

Next, the execution control unit 103 of the operation script execution terminal 10 executes each operation script constituting the scenario (that is, executes the script file in which various information is set in the above step S205) (step S206). At this time, the execution control unit 103 executes each script file according to, for example, the execution date and time, the execution order, etc. specified as the parameters of the script file.

As described above, in the automatic start, the scenario is automatically started on the operation script execution terminal 10 when the start date and time comes, and each operation script constituting the scenario is executed. As a result, the work contents realized by the operations executed by each of these operation scripts can be automatically performed. In addition, when executing each of these operation scripts, the password is decrypted on the memory using the account information managed by the account management device 20, and the password is set in the script file of the corresponding operation script. Then, the operation script can be executed while ensuring security.

≪Scenario start by manual start and execution of operation script≫
Hereinafter, the flow when the scenario is started by manual start and each operation script constituting this scenario is executed will be described with reference to FIG. 7. FIG. 7 is a sequence diagram for explaining the flow when the scenario is started by manual start and the operation script is executed.

First, the screen display unit 101 of the operation script execution terminal 10 displays the startup screen (step S301). The startup screen is displayed by, for example, manually starting an application program for starting a scenario. At this time, the user inputs a login ID and a login password (hereinafter, also referred to as “login information”) for logging in to the account management device 20.

Next, the screen display unit 101 of the operation script execution terminal 10 transmits the login information input by the user to the account management device 20 (step S302).

The manual activation instruction unit 203 of the account management device 20 confirms whether or not the login information is correct, and refers to each application information stored in the storage unit 204, and the status has been approved and is currently present. Determine if there is application information whose date and time is the executable date and time. Here, the executable date and time is, for example, a date and time after the start date and time included in the application information and before the end date and time.

Then, when the login information is correct and the corresponding application information exists, the manual activation instruction unit 203 transmits control information including the script information of the application information to the operation script execution terminal 10 (step S303). .. As a result, on the operation script execution terminal 10, the screen display unit 101 displays a list of scenarios corresponding to the script information as a target scenario list (step S304). The control information may include arbitrary information in addition to the script information.

The operation script execution terminal 10 may be, for example, the operation script execution terminal 10 indicated by the name of the execution terminal of the application information. Further, in step S301 described above, the user enters the login ID and login password to log in to the account management device 20, but the login is not limited to this, and the login is realized by, for example, SSO (single sign-on). You may.

The screen display unit 101 of the operation script execution terminal 10 receives the start instruction of the scenario in which the start instruction operation is performed by the user performing the start instruction operation in the target scenario list (step S305). Then, the activation control unit 102 of the operation script execution terminal 10 transmits an inquiry for necessary information of the scenario to the account management device 20 (step S306).

When the script information control unit 202 of the account management device 20 receives an inquiry for necessary information, among the account information stored in the storage unit 204, the account information corresponding to the corresponding scenario (that is, the script information of the scenario) Necessary information including the corresponding account information) and the like is transmitted to the operation script execution terminal 10 (step S307). In addition to the account information, the required information may include arbitrary information.

When the operation script execution terminal 10 receives the control information and the necessary information transmitted in steps S303 and S307, the operation script execution terminal 10 stores the received control information and the necessary information in the storage unit 104.

The activation control unit 102 of the operation script execution terminal 10 requests the execution control unit 103 to execute each operation script constituting the corresponding scenario in response to the reception of the necessary information, and activates the scenario (step S308).

Next, the execution control unit 103 of the operation script execution terminal 10 is a script file of each script information included in the control information stored in the storage unit 104 (that is, a script file of each script constituting the activated scenario). In response to the above, various information such as account information (password corresponding to the account ID used by the script file, etc.) is set (step S309). That is, the execution control unit 103 sets the password (and account ID) included in the account information in the script file, for example, by using the account information corresponding to the account ID used by the script file. At this time, since the password is encrypted, the execution control unit 103 decrypts the password and sets the decrypted password in the script file, for example, on the memory. As a result, the password used for executing the operation script can be hidden from the user of the operation script execution terminal 10 that executes the operation script represented by this script file.

In step S309 described above, various information necessary for executing the operation script is set in the script file in addition to the password.

Next, the execution control unit 103 of the operation script execution terminal 10 executes each operation script constituting the scenario (that is, executes the script file in which various information is set in the above step S309) (step S310). At this time, the execution control unit 103 executes each script file according to, for example, the execution date and time, the execution order, etc. specified as the parameters of the script file.

As described above, in the manual start, after displaying the start screen and the target scenario list on the operation script execution terminal 10, the scenario is displayed on the operation script execution terminal 10 according to the start instruction operation in the target scenario list. It is started and each operation script that composes the scenario is executed. As a result, it becomes possible to perform the work contents realized by the operations executed by each of these operation scripts in response to the user's start instruction operation. In addition, when executing each of these operation scripts, the password is decrypted on the memory using the account information managed by the account management device 20, and the password is set in the script file of the corresponding operation script. Then, the operation script can be executed while ensuring security.

The present invention is not limited to the above-described embodiment disclosed specifically, and various modifications and modifications can be made without departing from the scope of claims.

1 Operation script execution system 10 Operation script execution terminal 20 Account management device 30 Application terminal 40 Approval terminal 50 Operation target server 60 Local application 101 Screen display unit 102 Start control unit 103 Execution control unit 104 Storage unit 201 Workflow processing unit 202 Script information control Department 203 Manual start instruction unit 204 Storage unit 301 Application processing unit 401 Approval processing unit

Claims (7)

Operation execution including a management device that manages account information of the operation target server and an operation execution device that executes a script group composed of scripts that realize a series of operations including one or more operations on the operation target server. It's a system
The management device is
When the start date and time of the script group is reached in response to an inquiry from the operation execution device, one or more account information used for executing each script constituting the script group is transmitted to the operation execution device. Have a means,
The operation execution device is
When the start date and time of the script group is reached, or in response to an instruction from the user of the operation execution device, the script is used to execute the script among the one or more account information for each script constituting the script group. Setting means to set the account information to be scripted,
An execution means for executing a script group composed of each script for which account information is set by the above setting means, and an execution means.
Have a,
The operation execution system is characterized in that the script group is composed of scripts that realize a series of operations for performing maintenance work on the operation target server. The operation execution system according to claim 1, wherein the series of operations includes one or more operations for a local application operating on the operation execution device. The transmission means
The first or second claim is characterized in that the script group approved by the wharf flow and one or more account information used for executing each script constituting the script group are transmitted to the operation execution device. Described operation execution system. The account information includes an encrypted password,
The setting means is
A request for each script constituting the script group, characterized in that, among the one or more account information, the password included in the account information used for executing the script is decrypted and set in the memory. The operation execution system according to any one of items 1 to 3. An operation execution device that is connected to a management device that manages account information of an operation target server and executes a script group composed of scripts that realize a series of operations including one or more operations on the operation target server.
When the start date and time of the script group is reached, or in response to an instruction from the user of the operation execution device, the script is used to execute the script among the one or more account information for each script constituting the script group. Setting means to set the account information to be scripted,
An execution means for executing a script group composed of each script for which account information is set by the above setting means, and an execution means.
Have a,
The operation execution device is characterized in that the script group is composed of a script that realizes a series of operations for performing maintenance work on the operation target server. An operation execution device that is connected to a management device that manages account information of the operation target server and executes a script group composed of scripts that realize a series of operations including one or more operations on the operation target server.
When the start date and time of the script group is reached, or in response to an instruction from the user of the operation execution device, the script is used to execute the script among the one or more account information for each script constituting the script group. Setting procedure to set the account information to be scripted and
An execution procedure for executing a script group consisting of each script whose account information is set by the above setting procedure, and an execution procedure.
The execution,
The operation execution method is characterized in that the script group is composed of a script that realizes a series of operations for performing maintenance work on the operation target server. An operation execution device that is connected to a management device that manages account information of the operation target server and executes a script group composed of scripts that realize a series of operations including one or more operations on the operation target server.
When the start date and time of the script group is reached, or in response to an instruction from the user of the operation execution device, the script is used to execute the script among the one or more account information for each script constituting the script group. Setting means to set the account information to be scripted,
Execution means for executing a script group composed of each script for which account information is set by the above setting means,
To function as,
The script group is a program characterized in that it is composed of scripts that realize a series of operations for performing maintenance work on the operation target server.

Images