Resource management system and resource management method

Abstract

To provide a resource management system and method for suppressing the increase of management costs such as labor or expenses to a business system.SOLUTION: In a resource distribution system which is a resource management system, a resource distribution process periodically, regularly, or irregularly starts execution when an SI manager releases a resource to an execution environment, transmits a resource corrected by an SI management work terminal to an SI management server in response to the operation, and the SI management server determines whether or not the resource includes an application resource, transmits resource distribution instruction data including a determination result to a build server when the application resource is included, and executes a build process without changing the resource distribution instruction data. When the application resource is not included, belonging information, a sequence number, and a resource type related to the distribution target resource are associated with each other, a parameter of the application resource is corrected to execute build processing, and the Web / AP server executes deployment for the application resource.SELECTED DRAWING: Figure 6A

Description

[Technical Field]

[0001] The present invention relates to a technique for managing a system such as a business system having a plurality of managed objects. [Background technology]

[0002] Currently, systems such as business systems that are configured as management units of multiple nodes are in use. In such systems, the timing of updates such as program updates for each managed node may differ, and this must be managed. There are technologies for managing updates to programs implemented in multiple managed nodes that make up such systems. For example, there is a technology described in Japanese Patent Laid-Open No. 2009-230171 (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-230171 Summary of the Invention [Problem to be solved by the invention]

[0004] Normally, releasing new features or fixing bugs during system operation requires undeploying applications and restarting services, which can temporarily halt the system. As mentioned above, a system may consist of multiple managed objects, and updates may be performed on each managed object separately. This requires integrated management of these objects, but this can impose a significant load on the system. For example, these managed objects may be used by "departments" within an organization that uses the system. In such cases, new features may be provided to certain "departments" in advance, or functions may be customized for each "department." This requires integrated management of such systems, but this can impose a significant load on the system. Such a load can disrupt the operations of a company or other organization. The "belonging department" is an example of a managed object, and in this specification, the "belonging department" is also referred to as "affiliation" or "department."

[0005] Therefore, an object of the present invention is to prevent the management costs, such as the effort and expense, of the business systems described above from increasing. Note that the objects of management in the present invention include nodes, functions, subsystems, devices, software such as programs, and the departments and people who use these. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, the present invention provides a resource management system for managing a business system related to a plurality of managed objects that executes processes using resources, the resource management system managing the business system executing functions for realizing the business, the resource management system including: a storage unit that stores resource execution source data indicating a relationship between the plurality of managed objects and the resources; a resource execution unit that determines whether to execute batch processing in the execution of the function; an affiliation determination unit that acquires affiliation information of a user of a first managed object included in the plurality of managed objects and acquires, from a DB server, executor affiliation information indicating whether affiliation-specific resources indicating resources in the department to which the user belongs that are indicated by the affiliation information; a resource execution source determination unit that determines whether the first managed object is a target for updating the affiliation-specific resources based on the executor affiliation information; and an input / output that notifies a build server of a determination result indicating the result of the determination, the build server executing update processing for the resources for the first managed object in accordance with the notified determination result.

[0007] The present invention also includes a resource management method executed by the resource management system, and further includes a resource management device constituting the resource management system and a resource management method executed by the resource management device. [Effects of the Invention]

[0008] According to the present invention, it is possible to realize more appropriate utilization of various resources depending on the situation. Problems, configurations, and effects other than those described above will become apparent from the following description of the preferred embodiment of the invention. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of the configuration of a resource distribution system according to an embodiment of the present invention. [Figure 2A] FIG. 5 is a functional block diagram of a build server 500 according to an embodiment of the present invention. [Figure 2B]FIG. 2 is a hardware configuration diagram showing an example of implementation of a build server 500 according to an embodiment of the present invention. [Figure 3A] FIG. 7 is a functional block diagram of a DB server 700 according to an embodiment of the present invention. [Figure 3B] FIG. 7 is a hardware configuration diagram showing an example of implementation of a DB server 700 according to an embodiment of the present invention. [Figure 4A] FIG. 9 is a functional block diagram of a Web / AP server 900 according to an embodiment of the present invention. [Figure 4B] FIG. 9 is a hardware configuration diagram showing an example of implementation of a Web / AP server 900 according to an embodiment of the present invention. [Figure 5A] FIG. 8 is a functional block diagram of an operation management server 800 according to an embodiment of the present invention. [Figure 5B] FIG. 8 is a hardware configuration diagram showing an example of implementation of an operation management server 800 according to an embodiment of the present invention. [Figure 6A] 10 is a flowchart illustrating a resource distribution process according to an embodiment of the present invention. [Figure 6B] 10 is a flowchart illustrating a resource distribution process according to an embodiment of the present invention. [Figure 7A] 10 is a flowchart showing a flow chart of a resource execution process by affiliation according to an embodiment of the present invention. [Figure 7B] 10 is a flowchart showing a flow chart of a resource execution process by affiliation according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. This embodiment is an example for explaining the present invention, and for clarity of explanation, appropriate omissions and simplifications have been made. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

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

[0012] Examples of various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may also be expressed using data structures other than these. For example, various types of information such as "XX table," "XX list," and "XX queue" may also be expressed as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

[0013] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. When there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0014] In the embodiments, processing performed by executing a program may be described. Here, a computer executes the program using a processor (e.g., a CPU or a GPU) and performs processing defined by the program using storage resources (e.g., a memory) and interface devices (e.g., a communication port). Therefore, the entity performing the processing by executing the program may be the processor. Similarly, the entity performing the processing by executing the program may be a controller, device, system, computer, or node having a processor. The entity performing the processing by executing the program may be any computing unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit may be, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a CPLD (Complex Programmable Logic Device).

[0015] A program may be installed on a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in the embodiments, two or more programs may be realized as one program, or one program may be realized as two or more programs. Specific examples using such programs will be described later.

[0016] The present embodiment will be described in detail below with reference to the drawings. In this embodiment, a business system used by a company with multiple departments is used as an example of a managed object. In this example, different functions may be used by each department (branch office) within a company using the same business system. In such a case, conditional branching must be established within the application's programs and jobs to separate the processing corresponding to each function for each department. This increases the cost of this implementation when there are a large number of departments. Furthermore, for example, during service operation hours, an attempt may be made to pre-release new or modified features of an application as a new version of the application to some departments (branch offices). In this case, the application must be re-released, which requires undeploying the application and restarting the service. This results in a period when the application is unavailable across the entire business system. In the following, applications and jobs are examples of resources, and these may also be referred to as application resources and job-related resources, respectively.

[0017] Furthermore, managing different resources for each department using a business system results in a large number of departments (branches), resulting in an increase in the number of resources equal to the number of departments (branches), resulting in a dramatic increase in resources and management costs. Therefore, it is possible to release applications early during business system operation. Furthermore, it is desirable to use different versions of applications for each department (e.g., branch offices) to reduce resource management costs. Therefore, in this embodiment, in a business system having multiple managed objects for each department, resources used to perform business in some of the managed objects are updated early. Note that updating includes distributing and using the latest versions of resources (including previous resources such as previous applications) and making the resources available to the departments. Resources are also referred to as execution resources and include applications, jobs, operating systems, software, etc. Details of this are described below. As described above, a business system is related to multiple managed objects, such as departments and nodes. In other words, it may have multiple nodes or be used by multiple departments. Details of this embodiment are described below.

[0018] First, FIG. 1 is a diagram showing an example of the configuration of a resource distribution system according to this embodiment. The resource distribution system includes an SI management terminal 100, an SI management server 300, a build server 500, a DB server 700, an operation management server 800, a Web / AP server 900, and a business terminal 1000, which are connected via respective networks (200, 400, 600). Here, the resource distribution system may be used as a business system, or a business system may be configured using the DB server 700, the operation management server 800, the Web / AP server 900, and the business terminal 1000. Note that resource distribution systems also include those that do not distribute resources themselves. For this reason, they can be referred to as resource management systems. Furthermore, each device that constitutes a resource management system can be referred to as a resource management device.

[0019] The SI management work terminal 100 is a terminal that has the function of connecting to and activating the SI management server 300 via the network 200. The SI management work terminal 100 can be configured from one or more computers (electronic calculators), such as PCs or tablets.

[0020] The SI management server 300 can also be called an SI management system, and has the function of managing the above-mentioned resources and issuing resource export / import and resource update / creation instructions to the build server 500 in accordance with instructions from the SI management work terminal 100. Therefore, the SI management server 300 can be realized by a computer, and each of its hardware components can be singular or plural. The SI management server 300 can be one or more physical computers having hardware such as a processor, memory, input device, output device, interface device, and storage device, or it can be a system (e.g., a cloud computing system) realized on one or more physical computers (e.g., a cloud platform).

[0021] Furthermore, each device included in the SI management server 300 may be located on one physical computer, or may be distributed across multiple physical computers. Each program and information included in the storage device may be stored in one storage device, or may be distributed across multiple storage devices.

[0022] The build server 500 is also connected to the SI management server 300 via a network 400. The build server 500 is also connected to a DB server 700, an operations management server 800, and a Web / AP server 900 via a network 600. The build server 500 updates and creates resources in accordance with instructions from the SI management server 300. The build server 500 also has the function of transferring execution resources to the DB server 700, the operations management server 800, and the Web / AP server 900. Therefore, the build server 500 can be implemented by a computer, and each of its hardware components may be singular or plural. The build server 500 may be one or more physical computers having hardware such as a processor, memory, input device, output device, interface device, and storage device, or may be a system (e.g., a cloud computing system) implemented on one or more physical computers (e.g., a cloud platform). Each device included in the build server 500 may be located on a single physical computer, or may be distributed across multiple physical computers. The programs and information contained in the storage devices may be stored in a single storage device, or may be distributed and stored in multiple storage devices. The detailed configuration of the build server 500 will be described later with reference to Figures 2A and 2B.

[0023] The DB server 700 is also connected to the build server 500, the operations management server 800, and the Web / AP server 900 via the network 600. The DB server 700 is an example of a resource executed by the Web / AP server 900, and has a DB that applications register, update, delete, and reference in order to realize business operations in the business system. For this reason, the DB server 700 can be realized by a computer having a DB (database), and each of the hardware components may be singular or plural.

[0024] Furthermore, the DB server 700 may be one or more physical computers having hardware such as a processor, memory, input device, output device, interface device, and storage device, or may be a system (e.g., a cloud computing system) implemented on one or more physical computers (e.g., a cloud infrastructure). Each device included in the DB server 700 may be located on one physical computer, or may be distributed across multiple physical computers. Each program and each piece of information included in the storage device may be stored in one storage device, or may be distributed and stored across multiple storage devices. Details of the DB server 700 will be described later using Figures 3A and 3B.

[0025] The operation management server 800 is also connected to the build server 500, DB server 700, and Web / AP server 900 via the network 600. The operation management server 800 manages the execution of applications on the Web / AP server 900. For this reason, the operation management server 800 can be realized by a computer, and each of the hardware components may be singular or plural. The operation management server 800 may be one or more physical computers having hardware such as a processor, memory, input device, output device, interface device, and storage device, or may be a system (e.g., a cloud computing system) realized on one or more physical computers (e.g., a cloud infrastructure).

[0026] Furthermore, each device included in operation management server 800 may be located on one physical computer, or may be distributed across multiple physical computers. Each program and each piece of information included in the storage device may be stored in one storage device, or may be distributed across multiple storage devices. Details of operation management server 800 will be described later using Figures 5A and 5B.

[0027] The Web / AP server 900 is also connected to the build server 500, the DB server 700, and the operation management server 800 via the network 600. The Web / AP server 900 executes applications. For this reason, the Web / AP server 900 can be implemented by a computer, and each of its hardware components may be singular or plural. The Web / AP server 900 may be one or more physical computers having hardware such as a processor, memory, input device, output device, interface device, and storage device, or may be a system (e.g., a cloud computing system) implemented on one or more physical computers (e.g., a cloud platform). Each device included in the Web / AP server 900 may be located on a single physical computer, or may be distributed across multiple physical computers. Each program and each piece of information included in the storage device may be stored in a single storage device, or may be distributed across multiple storage devices. Details of the Web / AP server 900 will be described later using FIGS. 4A and 4B.

[0028] The business terminal 1000 is a terminal that uses an application to carry out business. The hardware configuration of the business terminal 1000 may be configured with one or more computers (electronic calculators) such as PCs or tablets.

[0029] Furthermore, networks 200, 400, and 600 are networks that connect the above-mentioned devices. Note that networks 200, 400, and 600 may each be configured as one or two networks. Furthermore, networks 200, 400, and 600 can be realized as the Internet or an intranet.

[0030] Next, the configuration of the main devices in this embodiment will be described with reference to Figures 2A to 5B. First, an example configuration of the build server 500 will be described with reference to Figures 2A and 2B. Here, the build server 500 executes resource distribution used in the management targets.

[0031] 2A is a functional block diagram of the build server 500 in this embodiment. The build server 500 constitutes the resource distribution system as described above.

[0032] In Figure 2A, the build server 500 has a resource management unit 501, an execution resource creation unit 505, an input / output unit 511, and a storage unit 512. The resource management unit 501 manages resources. To this end, it has a resource export / import unit 502, a production resource management unit 503, and an affiliation-specific resource management unit 504. First, the resource export / import unit 502 accesses a directory that manages the latest resources for the entire business system, and extracts and updates the latest resources. While the latest resources are being extracted, the target resources are locked, and the resource export / import unit 502 prevents them from being exported until they are updated.

[0033] The production resource management unit 503 also collects the latest resources for the entire business system and changes the parameters for the production environment. The production resource management unit 503 then stores them in the production resource creation directory. The department-specific resource management unit 504 also collects the latest resources for the entire business system and adds resources that are distributed exclusively to the target department. The department-specific resource management unit 504 then stores them in the department-specific resource creation directory.

[0034] Furthermore, the execution resource creation unit 505 creates resources that operate in the execution environment. To this end, the execution resource creation unit 505 has a production execution resource creation unit 506, an affiliation-specific execution resource creation unit 507, and an execution resource distribution unit 508. First, the production execution resource creation unit 506 converts (builds) the resources in the production resource creation directory collected by the production resource management unit 503 into resources that can be executed in the execution environment.

[0035] Furthermore, the affiliation-specific execution resource creation unit 507 converts (builds) the resources in the affiliation-specific resource creation directory collected by the affiliation-specific resource management unit 504 into resources that can be executed in the execution environment. Furthermore, the execution resource distribution unit 508 transfers the execution resources created by the production resource management unit 503 and the affiliation-specific resource management unit 504 to the DB server 700, the operation management server 800, and the Web / AP server 900, respectively. At this time, the execution resource distribution unit 508 transfers (sends) the execution resources via the input / output unit 511.

[0036] As described above, the build server 500 can be realized by a computer. An example implementation of the build server 500 realized by a computer will now be described. FIG. 2B is a hardware configuration diagram showing an example implementation of the build server 500 in this embodiment. As shown in FIG. 2B, the build server 500 has a processor 51, a memory 52, an input device 53, an output device 54, an I / F 55 (interface device), and a storage device 56. These are connected to each other via a communication path such as a bus.

[0037] First, the processor 51 performs data processing to realize the functions of the resource manager 501 and the execution resource creation unit 505 in Fig. 2A in accordance with the programs loaded in the memory 52. ​​Here, the programs include a resource management program 57 for realizing the functions of the resource manager 501 and an execution resource creation program 58 for realizing the functions of the execution resource creation unit 505. These are stored in a storage medium such as the storage device 56 described below. The processor 51 is a device that performs data processing (calculation, etc.) in the build server 500, which is a computer, and can be realized by a CPU (computer processing unit) or the like.

[0038] Furthermore, the memory 52 temporarily stores data and programs for data processing by the processor 51. Specifically, the memory 52 temporarily stores a resource management program 57, an execution resource creation program 58, resource import / export instruction data 509, and resource distribution instruction data 510. The memory 52 can be realized by a RAM (random access memory) or the like. The memory 52 and the storage device 56 correspond to the storage unit 512 in FIG. 2A. The input device 53 receives input from a user. For this reason, the input device 53 can be realized by a keyboard, a mouse, or the like. The output device 54 outputs data processing results, etc., from the build server 500. For this reason, the output device 54 can be realized by a display device, or the like. The input device 53 and the output device 54 may be integrated into one device, such as a touch panel. In this embodiment, it is desirable to omit at least one of the input device 53 and the output device 54. If the input device 53 and the output device 54 are provided, they correspond to the input / output unit 511 in FIG. 2A.

[0039] Furthermore, the I / F 55 connects to other devices via the network 400 and the network 600. Therefore, the I / F 55 corresponds to the input / output unit 511 in FIG. 2A. Furthermore, the storage device 56 stores a resource management program 57, an execution resource creation program 58, resource import / export instruction data 509, and resource distribution instruction data 510. Therefore, the storage device 56 enables persistent storage of data and can read and write data as needed. Therefore, the storage device 56 can be realized by a device such as an HDD (hard disk drive) or an SSD (solid state drive), or a portable storage medium.

[0040] Here, the resource import / export instruction data 509 is data instructing the resource export performed by the resource export / import unit 502. The resource distribution instruction data 510 is data instructing the resource distribution performed by the execution resource distribution unit 508.

[0041] Next, the DB server 700 will be described with reference to Figures 3A and 3B. Figure 3A is a functional block diagram of the DB server 700. The DB server 700 also constitutes the resource distribution system as described above. The DB server 700 also manages information on execution resources referenced by affiliation.

[0042] 3A, the DB server 700 includes a storage unit 701, a resource distribution unit 707, and an input / output unit 708. First, the storage unit 701 stores various business tables 702, an execution resource target affiliation determination table 703, DB update data 704, execution resource target affiliation data 705, and execution resource version determination data 706.

[0043] First, the various business table 702 holds business data for executing business functions on the Web / AP server 900. The execution resource target affiliation determination table 703 holds data for determining whether resources executed by each affiliation are subject to affiliation-specific resource distribution. Here, the execution resource target affiliation determination table 703 will be explained using Table 1.

[0044] [Table 1]

[0045] Table 1 shows the execution resource target affiliation determination table 703. In Table 1, the code identifying the affiliation of the affiliation-specific resource distribution target is registered in "Company Code" and "Affiliation Code." Also, the sequence number of the affiliation-specific distribution resource that the target affiliation should refer to is registered in "Version." Also, the resource type of the affiliation-specific distribution resource is registered in "Resource Type."

[0046] Here, at the time of batch execution and job startup, the execution resource target affiliation data 705 linked from the Web / AP server 900 and the operation management server 800, respectively, is used as input, and execution resource version determination data 706 is returned. This allows the resource distribution unit 707 to determine the application and its version to be executed in the target process.

[0047] Here, the DB server 700 can also be realized by a computer as described above. Therefore, an implementation example in which the DB server 700 is realized by a computer will be described. FIG. 3B is a hardware configuration diagram showing an implementation example of the DB server 700 in this embodiment. As shown in FIG. 3B, the DB server 700 also has a processor 71, a memory 72, an input device 73, an output device 74, an I / F 75 (interface device), and a storage device 76. These are connected to each other via a communication path such as a bus.

[0048] The processor 71, memory 72, input device 73, output device 74, I / F 75, and storage device 76 have the same functions as the processor 51, memory 52, input device 53, output device 54, I / F 55, and storage device 56 of the build server 500, respectively. Differences between each component and the build server 500 will be explained below. The processor 71 executes data processing to execute the functions of the resource distribution unit 707 in accordance with the resource distribution program 77 loaded in the memory 72.

[0049] In addition, the memory 72 temporarily stores a resource distribution program 77, data in various business tables 702, data in the execution resource target affiliation determination table 703, data for DB update 704, execution resource target affiliation data 705, and execution resource version determination data 706 for data processing by the processor 71.

[0050] It is also desirable to omit at least one of the input device 73 and the output device 74.

[0051] The I / F 75 also connects to other devices via the network 600. Therefore, the I / F 75 corresponds to the input / output unit 708 in Fig. 3A. The storage device 76 also stores a resource distribution program 77, data in a various business table 702, data in an execution resource target affiliation determination table 703, DB update data 704, execution resource target affiliation data 705, and execution resource version determination data 706.

[0052] Here, various data stored in the storage unit 701 (storage device 76) other than those mentioned above will be described. DB update data 704 is data for updating each data of the DB server 700, in particular the execution resource target affiliation determination table 703. Execution resource target affiliation data 705 is data indicating the relationship between the affiliation to be managed and the resource. Furthermore, execution resource version determination data 706 is data for managing the version of the resource distributed to each affiliation, and is used to determine whether the resource will execute a normal batch application or a batch application distributed by affiliation.

[0053] Next, the Web / AP server 900 will be described using Figures 4A and 4B. Figure 4A is a functional block diagram of the Web / AP server 900. Note that the Web / AP server 900 also constitutes a resource distribution system as described above. The Web / AP server 900 also determines information on execution resources to be referenced by affiliation and controls the applications to be executed.

[0054] 4A, the Web / AP server 900 includes an online service unit 901, a batch service unit 905, an input / output unit 913, and a storage unit 914. The online service unit 901 implements business functions on an online screen. To this end, the online service unit 901 includes an online application execution unit 902, a job caller affiliation determination unit 903, and a job call unit 904.

[0055] Here, the online application execution unit 902 executes business functions on a browser from the business terminal 1000. Furthermore, when a batch function is called from the online application execution unit 902, the job caller affiliation determination unit 903 identifies the affiliation information that will be the executor of the batch function from the input contents on the online screen, and links the execution resource target affiliation data 705 to the DB server 700. Furthermore, after linking, the job caller affiliation determination unit 903 receives execution resource version determination data 706 from the DB server 700.

[0056] Furthermore, the job calling unit 904 calls either a normal job or a job distributed by department from the operation management server 800 based on the result of the job caller affiliation determination unit 903. In other words, the job calling unit 904 calls either a normal job or a job distributed by department as an example of resource update processing, depending on the result of the determination as to whether the resource is subject to an affiliation-based resource update.

[0057] Furthermore, the batch service unit 905 realizes business processing. To this end, the batch service unit 905 includes a batch application execution unit 906, a batch application executor affiliation determination unit 907, and an affiliation-specific batch application execution unit 908. First, the batch application execution unit 906 receives an execution instruction from the operation management server 800 and executes business processing.

[0058] Furthermore, when the batch application execution unit 906 is executed, the batch application executor affiliation determination unit 907 identifies information about the affiliation that will be the executor of the batch function from the application execution source data 910 linked from the operation management server 800, and links the execution resource target affiliation data 705 to the DB server 700. After linking, the batch application executor affiliation determination unit 907 receives execution resource version determination data 706 from the DB server 700 and determines whether to execute a normal batch application or a batch application distributed by affiliation. In other words, similar to the job invocation unit 904, the batch application executor affiliation determination unit 907 determines whether to execute a normal batch application or a batch application distributed by affiliation as an example of resource update processing, depending on the result of the determination as to whether the affiliation-specific resource is to be updated.

[0059] The batch application execution unit 908 executes a batch application distributed by affiliation based on the result of the batch application execution source affiliation determination unit 907. In other words, similar to the job invocation unit 904, the batch application execution unit 908 executes either a normal batch application or a batch application distributed by affiliation as an example of resource update processing, depending on the result of the determination as to whether the resource is subject to update by affiliation. If the resource is not subject to distribution by affiliation, the batch application execution unit 908 executes a normal batch application.

[0060] The input / output unit 913 is connected to the network 600 and the business terminal 1000. The input / output unit 913 may be configured to be connected to the business terminal 1000 via the network 600.

[0061] The storage unit 914 also stores application execution data 909, application execution source data 910, and application execution version determination data 911. In this embodiment, it is desirable that the execution resources 912 are also stored in the storage unit 914. First, the application execution data 909 is data for executing an application, which is an example of a resource. Furthermore, the application execution source data 910 is data related to the department that is the execution source of the application. Furthermore, the application execution version determination data 911 is data for determining the version of the application in the department, and a version for each department can be used. Furthermore, the execution resources 912 are used to realize a business such as an application. This concludes the explanation of FIG. 4A.

[0062] Here, the Web / AP server 900 can also be realized by a computer, as described above. An implementation example of the Web / AP server 900 realized by a computer will now be described. FIG. 4B is a hardware configuration diagram showing an implementation example of the Web / AP server 900 in this embodiment. As shown in FIG. 4B, the Web / AP server 900 also has a processor 91, memory 92, an input device 93, an output device 94, an I / F 95 (interface device), and a storage device 96. These are connected to each other via a communication path such as a bus.

[0063] The processor 91, memory 92, input device 93, output device 94, I / F 95, and storage device 96 each have the same functions as those of the build server 500 and DB server 700. Below, the differences between each component and the build server 500 and DB server 700 will be explained. The processor 91 executes data processing to execute the functions of the online service unit 901 and batch service unit 905 in accordance with the online program 97 and batch service program 98 loaded in the memory 92.

[0064] The memory 92 also temporarily stores an online program 97, a batch service program 98, application execution data 909, application execution source data 910, and application execution version determination data 911 for data processing by the processor 91. It is also desirable to omit at least one of the input device 93 and the output device 94.

[0065] The I / F 95 also connects to other devices via the network 600. It is also connected to the business terminal 1000. Therefore, the I / F 95 corresponds to the input / output unit 913 in FIG. 4A. The storage device 96 also stores an online program 97, a batch service program 98, application execution data 909, application execution source data 910, and application execution version determination data 911. Preferably, the storage device 96 also stores execution resources 912.

[0066] Next, the operation management server 800 will be described with reference to Figures 5A and 5B. Figure 5A is a functional block diagram of the operation management server 800. The operation management server 800 also constitutes the resource distribution system as described above. The operation management server 800 also determines information about jobs to be executed by each department and controls the execution of the jobs.

[0067] 5A, the operation management server 800 has a job group processing unit 801, a memory unit 805, and an input / output unit 809. The job group processing unit 801 links instruction information for executing business processing to a batch application. To this end, the job group processing unit 801 has a job execution unit 802, a batch application executor affiliation determination unit 803, and an affiliation-specific job execution unit 804.

[0068] First, the job execution unit 802 starts a job for executing a batch application based on information from the job calling unit 904 or an alarm. When the job execution unit 802 is executed, the batch application execution source affiliation determination unit 803 identifies information about the affiliation that is the source of starting the job from job execution version determination data 807 linked from the Web / AP server 900, and determines whether to execute a normal job or a job distributed by affiliation.

[0069] Furthermore, the affiliation-specific job execution unit 804 starts a job distributed by affiliation based on the result of the batch application execution source affiliation determination unit 803. That is, the affiliation-specific job execution unit 804 executes either a job distributed by affiliation or a normal job as an example of resource update processing, depending on the determination result as to whether the resource is subject to affiliation-specific resource update. If the resource is not subject to affiliation-specific distribution, the normal job is executed. Furthermore, the input / output unit 809 connects to the network 600.

[0070] The storage unit 805 also stores job execution data 806 and job execution version determination data 807. In this embodiment, it is desirable that execution resources 808 are also stored in the storage unit 805. First, the job execution data 806 is data for executing a job, which is an example of a resource. Furthermore, the job execution version determination data 807 is data for determining the version of a job in the department to which the user belongs, and a version for each department can be used. Furthermore, the execution resources 808 are used to realize a business operation such as a job. This concludes the explanation of FIG. 5A.

[0071] Here, the operation management server 800 can also be realized by a computer as described above. Therefore, an implementation example of the operation management server 800 realized by a computer will be described. Fig. 5B is a hardware configuration diagram showing an implementation example of the operation management server 800 in this embodiment. As shown in Fig. 5B, the operation management server 800 also has a processor 81, a memory 82, an input device 83, an output device 84, an I / F 85 (interface device), and a storage device 86. These are connected to each other via a communication path such as a bus.

[0072] The processor 81, memory 82, input device 83, output device 84, I / F 85, and storage device 86 each have the same functions as those of the build server 500, DB server 700, and Web / AP server 900. Below, the differences between each component and the build server 500, DB server 700, and Web / AP server 900 will be explained. The processor 81 executes data processing to execute the functions of the job group processing unit 801 in accordance with a job group processing program 87 loaded in the memory 82.

[0073] Furthermore, the memory 82 temporarily stores a job group processing program 87, job execution data 806, and job execution version determination data 807 for data processing by the processor 81. Furthermore, it is desirable to omit at least one of the input device 83 and the output device 84.

[0074] Furthermore, the I / F 85 connects to other devices via the network 600. Therefore, the I / F 85 corresponds to the input / output unit 809 in Fig. 5A. The storage device 86 also stores a job group processing program 87, job execution data 806, and job execution version determination data 807. Preferably, the storage device 86 also stores execution resources 808.

[0075] The configuration of this embodiment has been described above, and an example of the processing performed in this embodiment will now be described.

[0076] 6A and 6B are flowcharts showing the resource distribution process in this embodiment, which will be described in detail below with reference to the flowcharts of FIGS.

[0077] First, the resource distribution process is started when the SI manager releases resources into the execution environment periodically, regularly, or irregularly (step S600).

[0078] First, in response to an operation by the SI manager, the SI management terminal 100 transmits the modified resource to the SI management server 300 (step S601).

[0079] The SI management server 300 also determines whether the transmitted resources include application resources (step S602). At this time, the SI management server 300 makes this determination based on the resource names and resource categories of the transmitted resources. That is, the SI management server 300 makes this determination by comparing the resource names of the resources transmitted from the SI management work terminal 100 with the registration information it holds that indicates the managed resource names and the reflection destinations for each resource category.

[0080] If the result of this determination is that the application resource is included (YES), the process proceeds to step S603, whereas if the application resource is not included (NO), the process proceeds to step S606.

[0081] The SI management server 300 also determines whether the resources to be distributed are subject to resource distribution by affiliation based on the input information from the SI management work terminal 100 (step S603). The SI management server 300 then transmits resource distribution instruction data 510 including the determination result to the build server 500 (S603). Here, the resource distribution instruction data 510 is data that instructs the execution resource distribution unit 508 to distribute resources. Here, the input information includes the reflection resource name, reflection destination environment name, distribution category, and reflection affiliation.

[0082] The resource distribution instruction data 510 is then created by adding the reflection target resource and build execution instruction file to the reflection destination environment name, distribution category, and reflection affiliation information from the SI management operation terminal 100. Here, the directory in which the build is executed differs depending on whether the determination result is that the resource is the target of affiliation-specific resource distribution or the normal case, so a determination in step S603 is required to determine the destination directory. If it is determined in step S603 that the resource is the target of distribution (YES), the process proceeds to step S611. If it is determined that the resource is not the target of distribution (NO), the process proceeds to step S604.

[0083] The build server 500 then executes the build process using the resource distribution instruction data 510 as is (S604). At this time, there is no need to modify the resources to match the affiliation information, and step S604 may be executed without modifying the resources. Furthermore, at this time, it is preferable that the DB server 700 does not register the affiliation information in the execution resource target affiliation determination table 703.

[0084] The build server 500 then transfers the application resources to the Web / AP server 900. In response to this, the Web / AP server 900 executes a deployment process for the application resources (S605).

[0085] The SI management server 300 also determines whether the modified resources (target resources) include job-related resources. At this time, as in step S602, the SI management server 300 makes this determination based on the resource name and resource classification of the transmitted resource. That is, the SI management server 300 makes its determination by comparing the managed resource names and registration information indicating the reflection destination for each resource classification held by the SI management server 300 with the resource names of the resources transmitted from the SI management work terminal 100. If the result of this determination is that job-related resources are included (YES), the process proceeds to step S607. If job-related resources are not included (NO), the process proceeds to step S609.

[0086] Similarly to step S603, the SI management server 300 determines whether the resource to be distributed is a target for resource distribution by affiliation based on the input information from the SI management work terminal 100 (step S607). If it is determined that the resource is a target for distribution (YES), the process proceeds to step S613. If it is determined that the resource is not a target for distribution (NO), the process proceeds to step S608.

[0087] Here, we will explain the processing flow when it is determined in step S603 that the resource is a target for affiliation-based resource distribution (YES). The SI management server 300, build server 500, and DB server 700 link the affiliation information, sequence number, and resource type related to the resource to be distributed (S611). To do this, the build server 500 receives a notification of resource distribution instruction data 510 from the SI management server 300 indicating that the resource is a target for affiliation-based resource distribution.

[0088] In response to this, the build server 500 creates DB update data 704 based on the resource distribution instruction data 510. Here, the DB update data 704 is data for updating the execution resource target affiliation determination table 703, as described above. The build server 500 then transmits the created DB update data 704 to the DB server 700. In response to this, the DB server 700 registers the affiliation information, sequence number, and resource type of the resource to be distributed in the execution resource target affiliation determination table 703 based on the DB update data 704. Step S611 is executed as described above. Note that the affiliation information includes an affiliation ID that identifies the target affiliation.

[0089] The build server 500 also modifies the parameters of the application resources in accordance with the affiliation information ID and sequence number based on the resource distribution instruction data 510, and executes the build process (S612).Then, the process proceeds to step S605.

[0090] This concludes the explanation of Figure 6A, and the processing flow will now be explained using Figure 6B. First, we will explain step S608, which is the step to which the process transitions when step S607 is judged to be NO. The operation management server 800 registers jobs and job groups based on the resources transferred from the SI management server 300. The operation management server 800 then executes the registered jobs and job groups (S608).

[0091] The SI management server 300 also determines the contents of the resources (S609). In this step, as in steps S602 and S606, it is determined whether the target resources include DB-related resources. As a result, if DB-related resources are not included (NO), this processing flow ends. If DB-related resources are included (YES), the SI management server 300 transmits the data to the build server 500 as resource distribution instruction data 510, and the process proceeds to step S610.

[0092] Then, the build server 500 transfers the DB-related resources to the DB server 700 based on the resource distribution instruction data 510, and the DB server 700 reflects the transferred information in the various business tables 702 (S610). In other words, the DB server 700 executes SQL for the resources to be distributed.

[0093] Next, a case where step S607 transitions from YES will be described. The build server 500 creates DB update data 704 based on the resource distribution instruction data 510. The build server 500 then transmits the DB update data 704 to the DB server 700. In response to this, the DB server 700 registers the affiliation information, sequence number, and resource type in the execution resource target affiliation determination table 703 based on the DB update data 704 (S613).

[0094] The build server 500 also modifies the parameters of the job-related resources based on the resource distribution instruction data 510 to match the target affiliation ID and sequence number (S614). At this time, the build server 500 transfers the resources to the operations management server 800. Then, the process proceeds to step S608, where the operations management server 800 registers the job and job group based on the transferred resources (S608). Then, as described above, the processes from step S609 onwards are executed. This concludes the explanation of the resource distribution process in Figures 6A and 6B. Next, we will explain the process using the distributed resources.

[0095] 7A and 7B are flowcharts showing the flow of resource execution processing by department. The flow of resource execution processing by department is executed periodically or irregularly when a business person performs business processing using business terminal 1000. The operation based on the flow charts of FIGS. 7A and 7B is as follows.

[0096] First, the business terminal 1000 receives an instruction to start business processing from a business operator and starts the business processing (S700). The business terminal 1000 also starts the business processing and sends transmission information to the Web / AP server 900. That is, it executes the execution instruction (S701). In response to this, the Web / AP server 900 carries out the business processing in the application. Here, the transmission information is execution information for executing the business processing, and includes information such as what business was performed, which business operator performed which data, and to whom.

[0097] The Web / AP server 900 also determines whether the business process to be executed is batch processing based on the transmission information from the business terminal 1000 (S702). As a result, if the business process to be executed is batch processing (YES), the process proceeds to step S703. If it is not batch processing (NO), the process proceeds to step S706.

[0098] Furthermore, the Web / AP server 900 acquires information about the process executing user when the user logs in at the business terminal 1000 (S703). Furthermore, the DB server 700 acquires information indicating whether the execution of department-specific resources is registered for the department of the process executing user (S704). The DB server 700 then determines whether the worker is a target for department-specific resource distribution (S705). At this time, the DB server 700 determines the target department from the worker ID that identifies the worker of the executed work, and further determines whether the determined department is a target for department-specific resource distribution. As a result, if the department is a target for distribution (YES), the process proceeds to step S712. If the department is not a target for distribution (NO), the process proceeds to step S713. Steps S712 and S713 will be described later using FIG. 7B.

[0099] The Web / AP server 900 also determines whether the executed business process to be performed is online processing (S706). At this time, the determination is made based on a predetermined number of digits (for example, the last digit) in the business type described above. As a result, if it is online processing (YES), the process proceeds to step S707. If it is not online processing (NO), the business process ends. The Web / AP server 900 also executes the online application (S707).

[0100] This concludes the explanation of Figure 7A, and the processing flow will be explained further using Figure 7B. The Web / AP server 900 determines whether batch processing is to be executed during the execution of the online application based on the information transmitted from the business terminal 1000 (S708). As a result, if batch processing is to be executed (YES), the process proceeds to step S709. On the other hand, if batch processing is not to be executed (NO), the business processing ends. At this time, the Web / AP server 900 executes only the functions of the online application.

[0101] Furthermore, the Web / AP server 900 acquires the affiliation information of the process execution user in the job caller affiliation determination unit 903 in the batch call component (S709).

[0102] Similarly to step S704, the DB server 700 also acquires information indicating whether the execution of a resource by department is registered for the affiliation of the processing executing user (S710). In this step and step S704, information stored in the execution resource target affiliation determination table 703 of FIG. 3 is acquired. Then, the DB server 700 uses the acquired information to determine whether the resource is a target for affiliation-based resource distribution (S711). Here, in this step and step S705, if the executing user's company code and affiliation code and the resource type of the function to be executed are registered in the execution resource target affiliation determination table 703, it is determined that the resource is a target for affiliation-based resource distribution. As a result, if it is determined that the resource is a target for distribution (YES), the process proceeds to step S712. If it is determined that the resource is not a target for distribution (NO), the process proceeds to step S713.

[0103] The operation management server 800 also executes the job for the target group and transmits an instruction to execute the online application to the Web / AP server 900. The Web / AP server 900 then executes the batch application for the target group based on the information transmitted from the operation management server 800 (S712). Here, the execution instruction is information that indicates an instruction to execute the batch application, transmitted from the executed job for the target group.

[0104] Furthermore, the Web / AP server 900 executes a normal batch application based on the transmitted information from the operation management server 800 (S713). Note that in the processing from step S706 onwards, the latest resources such as the preceding application can be used in both online processing and batch processing. In other words, the managed object can use the latest resources whether a job for the department to which the user belongs has been released or the job has not been released. This completes the business processing. This concludes the explanation of this embodiment, but the present invention is not limited to this embodiment. For example, this embodiment can be used in organizations other than companies, such as public organizations. Furthermore, business broadly includes the activities of organizations. [Explanation of symbols]

[0105] 100...SI management work terminal, 200...network, 300...SI management server, 400...network, 500...build server, 600...network, 700...DB server, 800...operation management server, 900...Web / AP server, 1000...business terminal

Claims

1. In a resource management system that manages a business system related to a plurality of management targets that execute processes using resources, the business system executes functions for realizing a business, a storage unit for storing resource execution source data indicating relationships between the plurality of managed objects and resources; a resource execution unit that determines whether to execute batch processing in the execution of the function; an affiliation determination unit that acquires affiliation information of a user of a first managed object included in the plurality of managed objects, and acquires, from a DB server, execution source affiliation information indicating whether affiliation-specific resources indicating resources in a department to which the user belongs indicated by the affiliation information are registered; a resource execution source determination unit that determines whether the first management target is a target for updating the affiliation-specific resources based on the execution source affiliation information; an input / output unit that notifies a build server of a determination result indicating the result of the determination; The resource management system is configured such that the build server executes update processing for the resource in the one managed object in accordance with the notified judgment result.

2. 2. The resource management system according to claim 1, the resource execution source determination unit determines whether the resource execution source is a target for distribution of the affiliation-specific resource; The update process is a resource management system that distributes the resources by affiliation.

3. 3. The resource management system according to claim 2, the resource is a Job, The resource execution source determination unit determines whether the user is a target for the distribution of the department-specific resources based on whether a job for the department to which the user belongs has been released.

4. 4. The resource management system according to claim 3, If a job for the department to which the user belongs has been released, the resource management system reads out and executes the job for the department to which the user belongs in the first management object.

5. 5. The resource management system according to claim 3, wherein: If the job for the department to which the user belongs has not been released, the resource management system executes a batch application in the first management target.

6. 6. The resource management system according to claim 5, A resource management system that enables the first management target to use the latest resources when a job for the department to which the user belongs has been released and when the job has not been released.

7. A resource management method executed by a resource management system that manages a business system related to a plurality of managed objects that execute processes using resources and that executes functions to realize a business, comprising: a storage unit stores resource execution source data indicating relationships between the plurality of managed objects and resources; the resource execution unit determines whether to execute batch processing in the execution of the function; an affiliation determination unit acquires affiliation information of a user of a first managed object included in the plurality of managed objects, and acquires, from a DB server, execution source affiliation information indicating whether affiliation-specific resources indicating resources in a department to which the user belongs indicated by the affiliation information are registered; a resource execution source determination unit that determines whether the first management target is a target for updating the resource by affiliation based on the execution source affiliation information; the input / output unit notifies the build server of a determination result indicating the result of the determination; The resource management method includes the step of causing the build server to execute update processing for the resource for the one managed object in accordance with the notified judgment result.

8. 8. The resource management method according to claim 7, the resource execution source determination unit determines whether the resource execution source is a target for distribution of the affiliation-specific resource; The update process is a resource management method for distributing the resources by affiliation.

9. 9. The resource management method according to claim 8, the resource is a Job, The resource management method, wherein the resource execution source determination unit determines whether the user is a target for the distribution of the department-specific resources based on whether a job for the department to which the user belongs has been released.

10. 10. The resource management method according to claim 9, A resource management method in which, if a job for the department to which the user belongs has been released, the job for the department to which the user belongs is read out and executed in the first managed object.

11. 11. The resource management method according to claim 9, further comprising: A resource management method for executing a batch application in the first management target when a job for the department to which the user belongs has not been released.

12. The resource management method according to claim 11, A resource management method that enables the first managed object to use the latest resources when a job for the department to which the user belongs has been released and when the job has not been released.

Images