JP2018133046A - Software control program, software control device, and software control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem of having the possibility of, when receiving a request message addressed to an application which is not activated in a PaaS system from a user, omitting the request message addressed to the application.SOLUTION: A software control program causes a computer to execute processing for, when receiving a request message addressed to first software from a user, storing the request message addressed to the first software in a second memory, and for, when the operating state of the first software is under suspension, and a total amount obtained by adding the resource of software whose operating state is under activation among software of a first contractor associated with the first software and the resource of the first software does not exceed a resource upper limit amount of the first contractor, requesting the activation of the first software to the system, and for transferring the request message stored in the second memory to the system after the activation of the first software, and for changing the operating state of the first software to under activation.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a software control program, a software control apparatus, and a software control method.

  Conventionally, when a developer (hereinafter also referred to as a contractor) uses a PaaS (Platform as a Service) system, a resource amount is contracted in advance, and an application program (hereinafter also referred to as an application) is set so as to be within the resource amount. Registration / deletion is performed. If you register the amount of resources that can be used to register all the apps you use, there is no need to register / delete apps. However, if you do so, the usage fee will be high. Necessary.

  The following patent documents relate to program processing.

Japanese Patent Laid-Open No. 5-224941 JP-A-8-185297 JP 2010-237972 A

  However, when a request message addressed to an application not activated in the PaaS system is received from the user, there is a problem that the request message addressed to the application may be missed.

  Accordingly, an object of the first aspect of the present disclosure is to control software (for example, an application) that can prevent a request message received from a user (for example, for an application) that is not activated in the PaaS system from being missed. To provide a program.

  According to a first aspect of the present disclosure, software that is activated in a system and operation status of the software in the system are stored in a first memory for each contractor, and software that has passed a predetermined time since the last request message was processed Requesting the system to be stopped, changing the operating status of the software after the predetermined time has passed to stop, and receiving a request message addressed to the first software from the user, the request addressed to the first software is stored in the second memory. A first process for storing a message is performed, and when the operating status of the first software is activated, a second process for transferring a request message stored in the second memory to the system is performed, and the first software When the operation status is suspended, the operation of the software of the first contractor associated with the first software is performed. If the total amount of the resources of the activated software and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, After starting the first software, the request message stored in the second memory is transferred to the system, and the third process for changing the operating status of the first software during the start is performed by the computer. Software control program.

  According to a second aspect of the present disclosure, the software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor, and the operation status is the last of the software activated as the regular software. Requests the system to start the software as a dummy software after a predetermined time has elapsed from the time when the request message was processed, and changes the operating status of the software after the predetermined time has passed during the startup as a dummy software. When a request message for the first software is received, the first process for storing the request message addressed to the first software is performed in the second memory. When the operating status of the first software is activated as the regular software, the second memory Forward the stored request message to the system When the second processing is performed and the operating status of the first software is being activated as dummy software, a request message addressed to the first software is stored in the second memory, and the first contract associated with the first software If the total amount of the software resources whose operating status is activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the authorized software of the first software After the first software is activated as authorized software, the request message stored in the second memory is transferred to the system and the operation status of the first software is activated as authorized software. The third process to change to Is a Towea control program.

  According to the first aspect and the second aspect, it is possible to suppress missing of a request message received from a user and addressed to software that is not activated in the PaaS system (for example, to an application).

1 is a schematic configuration diagram of an information processing system 10 according to a first embodiment. 2 is a diagram illustrating an example of a hardware configuration of a host computer 21. FIG. It is a figure explaining the application program execution environment in the host computer. It is a figure for demonstrating the main function of the PaaS system 20, and the table which the PaaS system 20 has. It is an example of the application information table 21n. It is an example of the developer resource restriction table 21p. 2 is a diagram illustrating an example of a hardware configuration of a host computer 31. FIG. It is a figure for demonstrating the main function of the application starting control system 30, and the table which the application starting control system 30 has. It is an example of the registered application management table 31s. It is an example of the request queue 31t. It is an example of the application change time table 31u. It is an example of a dummy application & regular application storage unit 31v 5 is a flowchart for explaining an example of an application registration process in the application activation control system 30. It is an example of a registered application management table 31s (after apr04 registration). It is an example of the application information table 21n (after apr04 registration). It is an example of the application information table 21n (after apr04 registration). (A) An example of application change time table 31u (before apr04 registration), (b) An example of application change time table 31u (after apr04 registration). 5 is a flowchart for explaining an example of a dummy application activation process in the application activation control system 30. 4 is a flowchart for explaining a request message reception process in the application activation control system 30. 4 is a flowchart for explaining a request message reception process in the application activation control system 30. It is an example of the request queue 31t. It is a figure for demonstrating the main function of the application starting control system 30, and the table which the application starting control system 30 has. It is an example of the application stop time table 31u2. It is an example of a registered application management table 31s2. It is a flowchart for demonstrating an example of the application stop process in the application starting control system 30 of 2nd Embodiment. 4 is a flowchart for explaining a request message reception process in the application activation control system 30. 4 is a flowchart for explaining a request message reception process in the application activation control system 30.

[First Embodiment]
First, an overview of the information processing system 10 according to the first embodiment will be described.

  FIG. 1 is a schematic configuration diagram of an information processing system 10 according to the first embodiment.

  As shown in FIG. 1, the information processing system 10 of this embodiment includes a PaaS system 20, an application activation control system 30, a developer terminal 40, an application user terminal 50, and the like. The developer corresponds to the contractor of the present invention, and the application user corresponds to the user of the present invention.

  The developer terminal 40 is connected to the PaaS system 20 and the application activation control system 30 via a network NW such as the Internet. The application user terminal 50 is connected to the application activation control system 30 via the network NW.

  The developer transmits a regular application registration request to the application activation control system 30 via the developer terminal 40. When the application activation control system 30 receives a registration request for a regular application from a developer, the application activation control system 30 stores the application and the operation status of the application in the PaaS system 20 for each developer in the registered application management table 31s. A regular application is an application that is less frequently used by an application user (once a day, once a week, or once a month, etc.) than a normal application. The regular application corresponds to the regular software of the present invention.

  Further, the developer registers the normal application in the PaaS system 20 via the developer terminal 40. A normal application is an application that is used more frequently by application users than a regular application. The PaaS system 20 creates a container in which the registered normal application is copied, and activates the container (and the normal application). The operation status of the normal application in the PaaS system 20 is not stored in the application activation control system 30 (registered application management table 31s).

  The application user transmits a request message addressed to the first application to the application activation control system 30 via the application user terminal 50.

  The application activation control system 30 refers to the application change time table 31u, and the time when the last request message is processed (for example, received) among the applications whose operation status is activated as a regular application (for example, the request message reception time) The PaaS system 20 is requested to start an application for which a predetermined time has passed since the application as a dummy application, and the operation status of the application in the application change time table 31u after the predetermined time has been changed to being started as a dummy application.

  The time at which the last request message is processed is not limited to the request message reception time, but may be the time at which the last request message stored in the request queue 31t is transferred to the PaaS system 20.

  A dummy app is an app that uses less resources (memory or disk) than a regular app. The dummy application corresponds to the dummy software of the present invention. The PaaS system 20 creates a container in which the dummy application is copied, and activates the container (and the dummy application).

  Further, the application activation control system 30 performs the following process when receiving a request message addressed to the first application from the application user.

  The application activation control system 30 stores a request message addressed to the first application in the request queue 31t when the operation status of the first application is activated as a dummy application with reference to the registered application management table 31s. The request queue 31t corresponds to the second memory of the present invention.

  Next, among the apps of the first contractor associated with the first app, the reserved memory amount of the app whose operation status is running (including both running as a regular app and running as a dummy app) and the first When the total amount obtained by adding the reserved memory amount of one application does not exceed the memory upper limit amount of the first contractor, the PaaS system 20 is requested to start the first application as a regular application. The PaaS system 20 activates the container (and the regular application) in which the regular application is copied (overwritten on the dummy application).

  After the first application is activated as a regular application in the PaaS system 20, the request message addressed to the first application stored in the request queue 31t is transferred to the PaaS system 20, and the first application in the registered application management table 31s is transferred. Change the operating status as a regular app while it is running. The PaaS system 20 transfers a request message addressed to the first application to the active first application as a regular application.

  Next, the PaaS system 20 will be described in detail.

  As shown in FIG. 1, the PaaS system 20 includes, for example, a host computer 21 (server device) and a storage 22. There may be one or more host computers 21 and storages 22 respectively.

  The host computer 21 provides a virtualized application execution environment by performing, for example, hypervisor type virtualization, container type virtualization, or hybrid type combination thereof.

  The storage 22 stores an OS executed by the host computer 21, application programs, data used by the application programs, and the like. Specifically, a program for generating the virtualization environments 21h and 21j executed on the host computer 21, a program for performing business processing of an application executed on the VM or the container, data, and the like are stored.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the host computer 21.

  The host computer 21 includes a CPU 21a, an input / output device interface circuit 21b, a memory 21c, a network interface circuit 21d, a storage interface circuit 21e, and a local bus interface circuit 21f.

  The CPU 21a accesses the interface circuits (21d to 21f) such as the memory 21c and the input / output device interface circuit 21b via the internal bus 21g.

  The CPU 21a is an electronic component of a processor such as a central processing unit (CPU) or a micro-processing unit (MPU). There may be one or more CPUs 21a.

  The CPU 21a reads programs and data stored in the storage 22 to the memory 21c, and executes programs related to the virtualization environments 21h and 21j and programs related to business processes of applications executed on the VM and the container. .

  The input / output device interface circuit 21b is a circuit for controlling input / output to / from peripheral devices including devices such as a mouse and a keyboard (not shown).

  The memory 21c is a storage device such as a RAM (Random Access Memory).

  The network interface circuit 21d is an interface circuit for communicating with other devices (for example, the developer terminal 40) via the network NW.

  The storage interface circuit 21 e is an interface circuit for accessing the storage 22.

  The local bus interface circuit 21f is an interface circuit for communicating with the application activation control system 30 and the like in the information processing system 10 via the local bus 21g.

  FIG. 3 is a diagram for explaining an application program execution environment in the host computer 21.

  In the host computer 21, a hybrid type virtual environment in which a hypervisor type virtual environment 21h and a container type virtual environment 21j operating on the virtual machine 21h2 operate is provided using the CPU 21a, the memory 21c, and the like. .

  The hypervisor type virtualization environment 21h includes a hypervisor 21h1 and a virtual machine 21h2 generated by the hypervisor 21h1. The hypervisor 21h1 activates and deletes the virtual machine 21h2, controls access requests to hardware resources from programs executed on the virtual machine 21h2, and the like.

  The virtual machine 21h2 is a virtualized hardware resource of the host computer 21, and an independent software execution environment is provided for each virtual machine 21h2. Although FIG. 3 shows an example in which two virtual machines 21h2 are activated, the present invention is not limited to this, and one or more (three or more) virtual machines 21h2 may be activated.

  In the example of FIG. 3, a container type virtual environment 21j is provided in the virtual machine 21h2. In the container type virtualization environment 21j, the OS 21j1 is started on the virtual machine 21h2, and the container virtualization software is installed on the OS 21j1. FIG. 3 shows an example in which two containers 21j2 are activated on the OS 21j1, but the present invention is not limited to this, and one or a plurality (three or more) of containers 21j2 may be activated on the OS 21j1.

  In the container type virtualization environment 21j, the container 21j2 that is an independent application execution environment is provided by the OS 21j1. In container-type virtualization, an application execution environment created in the past is saved as an image of a common file. A new container can be easily created by copying the saved image and adding settings for each application execution environment. Therefore, the container type virtualization environment is suitable for construction of PaaS (Platform as a Service) or the like.

  The container 21j2 includes an API (OS API), an execution environment (build pack) such as JAVA (registered trademark) installed thereon, and an application program (normal application, regular application, Or a dummy app).

  When an application is registered in the PaaS system 20, the PaaS system 20 creates a container 21j2 in which the registered application is copied, and activates the container (and the application). When registering an application in the PaaS system 20, for example, a push command is used (when registering a normal application in the PaaS system 20 via the developer terminal 40).

  In addition, when there is an application registration request for an application with the same application name (referred to as a new application) with respect to the PaaS system 20 where an application (referred to as an old application) has already been registered, the PaaS system 20 determines that the developer ( For example, if the user name) and the developer of the new application (for example, the user name) are the same, registration is permitted. On the other hand, if the developer (for example, user name) of the old application and the developer (for example, user name) of the new application are different, the PaaS system 20 does not permit registration.

  FIG. 4 is a diagram for explaining the main functions of the PaaS system 20 and the tables of the PaaS system 20.

  Each function shown in FIG. 4 is realized by the CPU 21a executing a predetermined program read from the storage 22 to the memory 21c. Details of each function shown in FIG. 4 will be described later (see FIG. 13, FIG. 18 to FIG. 20).

  FIG. 5 is an example of the application information table 21n. For example, the application information table 21n is stored in the storage 22, and is read from the storage 22 to the memory 21c as necessary.

  The application information table 21n stores an application and an operation status of the application in the PaaS system 20. The application information table 21n is prepared for each developer. FIG. 5 is an example of the application information table 21n for developer A, for example.

  As shown in FIG. 5, the application information table 21 n includes “application name”, “URL name”, “used CPU”, “used memory”, “used disk”, “reserved memory” of the “application name”. Includes items such as “Amount”, “Reserved Disk Amount”, and “Operational Status”.

  In “APP NAME”, the application name of the application registered in the PaaS system 20 is stored.

  In “URL name”, a URL for accessing an application having an application name stored in “application name” is stored.

  In “used CPU”, the CPU usage rate actually used by the application having the application name stored in “application name” is stored.

  In the “used memory”, the memory amount actually used by the application having the application name stored in the “application name” is stored.

  In “used disk”, the disk amount actually used by the application having the application name stored in “application name” is stored.

  The “reserved memory amount” stores the upper limit amount of memory that can be used by the application having the application name stored in the “application name”.

  The “reserved disk amount” stores the upper limit amount of a disk that can be used by the application having the application name stored in “application name”.

  In the “operation status”, an operation status (also referred to as an activated state) of the application having the application name stored in “application name” in the PaaS system 20 is stored.

  FIG. 6 is an example of the developer resource restriction table 21p. The developer resource restriction table 21p is stored in the storage 22, for example, and is read from the storage 22 to the memory 21c as necessary. The application activation control system 30 also includes a developer resource restriction table 21p (see FIG. 8).

  As shown in FIG. 6, the developer resource limit table 21p includes “developer name”, “memory upper limit (also referred to as memory limit)” and “disk upper limit (also referred to as disk limit) of the“ developer name ”. ")".

  The “developer name” stores the name of the developer who has contracted to use the PaaS system 20.

  The “memory upper limit amount” stores the upper limit amount of memory that can be used by the developer stored in the “developer name”. The memory upper limit amount corresponds to the resource upper limit amount (or resource contract amount) of the present invention.

  In the “disc upper limit amount”, the upper limit amount of the disc that can be used by the developer stored in the “developer name” is stored.

  Next, the application activation control system 30 will be described in detail.

  As shown in FIG. 1, the application activation control system 30 includes, for example, a host computer 31 (server device) and a storage 32. There may be one or more host computers 31 and storages 32, respectively.

  FIG. 7 is a diagram illustrating an example of a hardware configuration of the host computer 31.

  The host computer 31 includes a CPU 31a, an input / output device interface circuit 31b, a memory 31c, a network interface circuit 31d, a storage interface circuit 31e, and a local bus interface circuit 31f.

  The CPU 31a accesses the interface circuits (31d to 31f) such as the memory 31c and the input / output device interface circuit 31b via the internal bus 31g.

  The CPU 31a is an electronic component of a processor such as a central processing unit (CPU) or a micro-processing unit (MPU). There may be one CPU 31a or a plurality of CPUs 31a.

  The input / output device interface circuit 31b is a circuit for controlling input / output to / from peripheral devices including devices such as a mouse and a keyboard (not shown).

  The memory 31c is a storage device such as a RAM (Random Access Memory).

  The network interface circuit 31d is an interface circuit for communicating with other devices (for example, the developer terminal 40 and the application user terminal 50) via the network NW.

  The storage interface circuit 31 e is an interface circuit for accessing the storage 32.

  The local bus interface circuit 31f is an interface circuit for communicating with the PaaS system 20 and the like in the information processing system 10 via the local bus 31g.

  FIG. 8 is a diagram for explaining the main functions of the application activation control system 30 and the table that the application activation control system 30 has.

  Each function shown in FIG. 8 is realized by the CPU 31a executing a predetermined program read from the storage 32 to the memory 31c. Details of each function shown in FIG. 8 will be described later (see FIG. 13, FIG. 18 to FIG. 20).

  FIG. 9 is an example of a registered application management table 31s. The registered application management table 31s is stored in the storage 32, for example, and is read from the storage 32 to the memory 31c as necessary. The registered application management table 31s corresponds to the first memory of the present invention.

  The registered application management table 31s stores the application and the operation status of the application in the PaaS system 20 for each developer.

  As shown in FIG. 9, the registered application management table 31s includes “application name” and “developer name”, “URL”, “dummy flag”, “file name”, “reservation” of the “application name”. This includes items such as “Reserved Memory Amount”, “Reserved Disk Amount”, and “Operation Status”.

  In “APP NAME”, the application name of the application that is controlled by the application activation control system 30 is stored.

  “Developer name” stores the name of the application developer stored in “App name”, typically the name of the developer who developed the application name stored in “App name”. Is done.

  “URL” stores a URL for accessing the application stored in “application name”.

  In the “dummy flag”, the identification information of the operation status in the PaaS system 20 (container) of the application having the application name stored in the “application name” is stored. In FIG. 9, “Yes” indicates that the operation status of the application having the application name stored in “App name” in the PaaS system 20 (container) is being activated as a dummy application. “No” indicates that the operation status in the PaaS system 20 (container) of the application having the application name stored in “application name” is being activated as a regular application.

  In “File name”, the file name of the application (source file) having the application name stored in “App name” is stored.

  The “reserved memory amount” stores the upper limit amount of memory that can be used by the application having the application name stored in the “application name”.

  The “reserved disk amount” stores the upper limit amount of a disk that can be used by the application having the application name stored in “application name”.

  In the “operation status”, an operation status (also referred to as an activated state) of the application stored in “application name” in the PaaS system 20 is stored.

  FIG. 10 is an example of the request queue 31t. The request queue corresponds to the second memory of the present invention. The request queue 31t is generated (stored) in the memory 31c, for example.

  The request queue 31t is an application-dedicated queue prepared for each application (application name). FIG. 10A shows an example of an application-dedicated request queue 31t with an application name apr01, and FIG. 10B shows an example of an application-dedicated request queue 31t with an application name apr02.

  The request queue 31t includes items such as “application name” and “request message”.

  In “APP NAME”, the name of the application in charge of the request queue 31t is stored.

  The “request message” stores a request message addressed to the application having the application name stored in “application name”. FIG. 10A shows a state in which two request messages (reception request messages) addressed to the application with the application name apr01 are stored in the application-dedicated request queue 31t with the application name apr01. Similarly, FIG. 10B shows a state in which two request messages (reception request messages) addressed to the application with the application name apr02 are stored in the application-dedicated request queue 31t with the application name apr02.

  FIG. 11 is an example of the application change time table 31u. The application change time table 31u is stored in the storage 32, for example, and is read from the storage 32 to the memory 31c as necessary.

  As illustrated in FIG. 11, the application change time table 31u includes items such as “application name” and “application change time” and “request message reception time” of the “application name”.

  In “App name”, an application name of an application whose operation status in the PaaS system 20 is activated as a regular application is stored.

  The “app change time” stores the time until the PaaS system 20 is requested to start the app with the app name stored in “app name” as a dummy app.

  The “request message reception time” stores the time when the request message addressed to the application having the application name stored in “application name” is received.

  FIG. 12 is an example of the dummy application & regular application storage unit 31v.

  The dummy application & regular application storage unit 31v is provided in the storage 32, for example.

  A dummy application (source file such as JAVA) is stored in the dummy application & regular application storage unit 31v. Typically, one dummy application (a source file such as JAVA) prepared in advance is stored. The dummy application & regular application storage unit 31v stores a regular application (a source file such as JAVA). One regular application may be stored, and a plurality of regular applications may be stored.

  Note that, similarly to the PaaS system 20, the application activation control system 30 includes a developer resource restriction table 21p (see FIG. 6).

  FIG. 13 is a flowchart for explaining an example of the application registration process in the application activation control system 30.

  First, the application management unit 31q waits until a registration request for a regular application transmitted from the developer via the developer terminal 40 is received (step S10: NO).

  Hereinafter, an example of processing when the application management unit 31q receives a registration request (hereinafter also referred to as an application registration request) of a regular application with the application name (apr04) from the developer A (developer name Usr01) will be described.

  This application registration request includes information related to the application to be registered. Specifically, the application name (here apr04), regular application (source file such as JAVA), reserved memory amount (here 1GB), reserved disk Including the amount (here 1GB), app change time (here 20min).

  When the application management unit 31q receives an application registration request (step S10: YES), the application name (here, apr04) received in step S10 is stored in the registered application management table 31s as shown in FIG. Store (step S11).

  For example, as shown in FIG. 9, when the application name received in step S10 (here, apr04) or the like is not stored in the registered application management table 31s, the application management unit 31q displays the last line in FIG. As illustrated, the application name received in step S10 (here, apr04) and the like are stored in the registered application management table 31s.

  Specifically, the “developer name” stores the developer name (here, Usr01) input when the developer A logs in to the application activation control system 30 via the developer terminal 40.

  The “app name” stores the application name (here, apr04) received in step S10.

  In “URL”, a URL (here, apr04.paas01.dc01.net) generated by combining the application name received in step S10 and the domain name automatically assigned by the application activation control system 30 is stored. The

  In the “dummy flag”, Yes or No is stored according to the operation status of the application (application name) received in step S10 in the PaaS system 20.

  The “file name” stores the file name (here, test01.java) of the legitimate application (source file such as JAVA) received in step S10.

  The “reserved memory amount” stores the reserved memory amount (here, 1 GB) received in step S10. The “reserved memory amount” corresponds to the resource of the present invention. If the reserved memory amount is not received in step S10, the default reserved memory amount is stored in the “reserved memory amount” by the application activation control system 30.

  In the “reserved disk amount”, the reserved disk amount (1 GB in this case) received in step S10 is stored. If the reserved disk amount is not received in step S10, the default reserved disk amount is stored in the “reserved disk amount” by the application activation control system 30.

  The “operation status” stores information indicating whether the application (application name) received in step S10 is being activated or stopped according to the operation status in the PaaS system 20.

  Also, the regular application (source file such as JAVA) received in step S10 is stored in the dummy application & regular application storage unit 31v.

  Next, the application (application name) of the first contractor (here Usr01, see FIG. 14) associated with the regular application (source file such as JAVA) received by the requested application activation / deactivation unit 31n in step S10. The total amount of the “reserved memory amount” (here 1 GB) of the application whose “operation status” is activated and the “reserved memory amount” (here 1 GB) of the regular application received in step S10 ( It is determined (confirmed) whether or not 2 GB) exceeds the memory upper limit (here 3 GB, see FIG. 6) of the first contractor (Usr01 here) (step S12).

  As a result of this determination, if the total amount does not exceed the memory upper limit amount (step S13: NO), the requested application activation / deactivation unit 31n requests the PaaS system 20 to activate the regular application received in step S10 ( Step S14).

  This legitimate application launch request is information related to the application to be registered, specifically, app name (here apr04), legitimate application (source file such as JAVA), reserved memory amount (here 1GB), reserved Includes disk space (here 1GB).

  When the PaaS system 20 receives a regular application activation request (step S14) from the application activation control system 30 (requested application activation stop unit 31n), as shown in the last line in FIG. Then, apr04) is stored in the application information table 21n of the developer (here, developer A).

  Specifically, the “application name” stores the application name (here, apr04) received from the application activation control system 30 (requested application activation / stop unit 31n).

  “URL” is a URL generated by combining the application name (here, apr04) received from the application activation control system 30 (requested application activation stop unit 31n) and the domain name automatically assigned by the PaaS system 20 Is memorized.

  “Used CPU”, “Used memory”, and “Used disk” respectively store the CPU usage rate, memory amount, and disk amount actually used by the application with the application name stored in “App name”. The These are regularly updated by the PaaS system 20.

  The “reserved memory amount” stores the reserved memory amount (here, 1 GB) received from the application activation control system 30 (requested application activation stop unit 31n).

  The “reserved disk amount” stores the reserved disk amount (here, 1 GB) received from the application activation control system 30 (requested application activation / stop unit 31n).

  In addition, the PaaS system 20 creates a container 21j2 in which a regular application (a source file such as JAVA) received from the application activation control system 30 (requested application activation stop unit 31n) is copied, and the container (and regular application) is created. Start.

  Further, the PaaS system 20 notifies (transmits) the activation state of the regular application to the application activation control system 30. For example, when the container (and the regular application) starts normally, the PaaS system 20 notifies the activation as the activation state, and when it does not activate normally for some reason, the PaaS system 20 notifies the activation as the activation state.

  Further, the PaaS system 20 stores “starting” or “stopping” in the “operation status” of the “application name” (here, apr04) in the application information table 21n according to the activation state of the regular application.

  On the other hand, as a result of the determination in step S12, when the total amount exceeds the memory upper limit amount (step S13: YES), the requested application activation stop unit 31n requests the PaaS system 20 to activate the dummy application (step S15). ).

  This dummy application activation request includes information on the application to be registered: application name (here, apr04), dummy application (source file such as JAVA), reserved memory amount for dummy application (here 10MB), dummy application Includes reserved disk space for 10MB here. The dummy application, the reserved memory amount for the dummy application, and the reserved disk amount for the dummy application are stored in advance in, for example, the dummy application & regular application storage unit 31v.

  When the PaaS system 20 receives a dummy application activation request (step S15) from the application activation control system 30 (requested application activation stop unit 31n), as shown in the last line in FIG. Then, apr04) is stored in the application information table 21n of the developer (here, developer A).

  Specifically, the “application name” stores the application name (here, apr04) received from the application activation control system 30 (requested application activation / stop unit 31n).

  “URL” is a URL generated by combining the application name (here, apr04) received from the application activation control system 30 (requested application activation stop unit 31n) and the domain name automatically assigned by the PaaS system 20 Is memorized.

  “Used CPU”, “Used memory”, and “Used disk” respectively store the CPU usage rate, memory amount, and disk amount actually used by the application with the application name stored in “App name”. The These are regularly updated by the PaaS system 20.

  In the “reserved memory amount”, a reserved memory amount (in this case, 10 MB) for the dummy application received from the application activation control system 30 (requested application activation stop unit 31n) is stored.

  The “reserved disk amount” stores the reserved disk amount (in this case, 10 MB) for the dummy application received from the application activation control system 30 (requested application activation stop unit 31n).

  Also, the PaaS system 20 creates a container 21j2 in which a dummy application (source file such as JAVA) received from the application activation control system 30 (requested application activation stop unit 31n) is copied, and the container (and dummy application) is created. Start.

  Further, the PaaS system 20 notifies (transmits) the activation state of the dummy application to the application activation control system 30. For example, when the container (and the dummy application) starts normally, the PaaS system 20 notifies the activation as the activation state, and when the container (and the dummy application) does not activate normally for some reason, the PaaS system 20 notifies the activation as the activation state.

  In addition, the PaaS system 20 stores “starting” or “stopping” in the “operation status” of the “application name” (here, apr04) in the application information table 21n in accordance with the starting state of the dummy application.

  Next, the application management unit 31q requests the application monitoring control unit 31r to register in the application change time table 31u (step S16).

  Next, the application monitoring control unit 31r determines (confirms) whether or not the application name (here, apr04) received in step S10 is registered in the application change time table 31u (step S17).

  As a result of the determination, if the application name received in step S10 is not registered in the application change time table 31u (step S18: NO), the application monitoring control unit 31r stores the application change time table 31u in step S10. The received application name (here, apr04) and the like are stored (step S19).

  For example, as shown in FIG. 17A, when the application change time table 31u does not store the application name (here, apr04) received in step S10 (step S18: NO), the application monitoring control unit As shown in the last line of FIG. 17B, 31r stores the application name (here, apr04) received in step S10 in the application change time table 31u (step S19).

  Specifically, the “application name” stores the application name (here, apr04) received in step S10.

  The “application change time” stores the application change time (20 min in this case) received in step S10. When the application change time is not received in step S10, the default time is stored in the “application change time” by the application activation control system 30.

  At the “request message reception time”, since the request message has not been received yet, the time when the application name received in step S10 is registered in the registered application management table 31s (here, 2016/06/30 15 : 20) is memorized.

  On the other hand, as a result of the determination in step S17, if the application name received in step S10 is registered in the application change time table 31u (step S18: YES), the application monitoring control unit 31r receives the application received in step S10. The “application change time” of the name (here, apr04) is updated (step S20). For example, the application change time received in step S10 is overwritten on the “application change time” of the application name (here, apr04) in the application change time table 31u.

  Next, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application requested for activation in step S14 or S15 from the PaaS system 20 (step S21: YES), the registered application management The table 31s is updated (step S22).

  For example, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the authorized application from the PaaS system 20 (step S21: YES), the application activation control system 30 (for example, the application management unit 31q) registers according to the received activation state of the authorized application. “Activation status” of “App name” (here, apr04) in the completed application management table 31s is stored as being activated or stopped. Further, the application activation control system 30 (for example, the application management unit 31q) stores No in the “dummy flag” of the “application name” (here, apr04) of the registered application management table 31s.

  On the other hand, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the dummy application from the PaaS system 20 (step S21: YES), the application activation control system 30q (for example, the application management unit 31q) registers according to the received activation state of the dummy application. “Activation status” of “App name” (here, apr04) in the completed application management table 31s is stored as being activated or stopped. The application activation control system 30 (for example, the application management unit 31q) stores Yes in the “dummy flag” of the “application name” (here, apr04) of the registered application management table 31s.

  FIG. 18 is a flowchart for explaining an example of the dummy application activation process in the application activation control system 30.

  First, the application monitoring control unit 31r acquires the request message reception time and the application change time for each application from the application change time table 31u (step S30).

  Next, the application monitoring control unit 31r calculates an application change scheduled time (= request message reception time + application change time) (step S31).

  Next, when there is an application name that exceeds the scheduled application change time (step S32: YES), the application monitoring control unit 31r requests the requested application activation / deactivation unit 31n to activate the corresponding application as a dummy application (step S32). S33).

  Next, the requested application activation / deactivation unit 31n requests the PaaS system 20 to activate the corresponding application as a dummy application (step S34).

  This dummy application activation request includes an application name (for example, apr04 in FIG. 17B), a dummy application (a source file such as JAVA), a reserved memory amount for the dummy application, and a reserved disk amount for the dummy application. Including.

  When the PaaS system 20 receives a dummy application activation request (step S34) from the application activation control system 30 (requested application activation stop unit 31n), the PaaS system 20 receives the application name (in this case, apr04) in the application information table 21n. The received reserved memory amount for the dummy application and the reserved disk amount for the dummy application are stored (for example, overwritten) in “Reserved memory amount” and “Reserved disk amount”, respectively. Thereby, for example, the application information table 21n changes from the content shown in FIG. 15 to the content shown in FIG.

  In addition, the PaaS system 20 stores the container 21j2 (and dummy application) in which the dummy application (source file such as JAVA) received from the application activation control system 30 (requested application activation stop unit 31n) is copied (overwritten on the regular application). Start.

  Further, the PaaS system 20 notifies (transmits) the activation state of the dummy application to the application activation control system 30. For example, when the container (and the dummy application) starts normally, the PaaS system 20 notifies the activation as the activation state, and when the container (and the dummy application) does not activate normally for some reason, the PaaS system 20 notifies the activation as the activation state.

  In addition, the PaaS system 20 stores “starting” or “stopping” in the “operation status” of the “application name” (here, apr04) in the application information table 21n in accordance with the starting state of the dummy application.

  Next, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application requested for activation in step S34 from the PaaS system 20 (step S35: YES), the registered application management table 31s. Is updated (step S36).

  For example, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the dummy application from the PaaS system 20 (step S35: YES), the application activation control system 30 (for example, the application management unit 31q) registers according to the received activation state of the dummy application. “Activation status” of “App name” (here, apr04) in the completed application management table 31s is stored as being activated or stopped. The application activation control system 30 (for example, the application management unit 31q) stores Yes in the “dummy flag” of the “application name” (here, apr04) of the registered application management table 31s.

  The processes in steps S30 to S36 are executed at specified intervals.

  19 and 20 are flowcharts for explaining request message reception processing in the application activation control system 30. FIG.

  First, it waits until the request message receiving unit 31h receives a request message addressed to the first application transmitted from the application user via the application user terminal 50 (step S40: NO).

  Hereinafter, an example of processing when the request message receiving unit 31h receives a request message addressed to the first application (here, application name apr04, developer name Usr01) from the application user will be described.

  When the request message reception unit 31h receives a request message addressed to the first application (step S40: YES), the first application (application name) is registered in the registered application management table 31s with respect to the request message registration confirmation unit 31j. A request for confirmation (application confirmation request) is made as to whether or not it is stored (step S41).

  Next, the request message registration confirmation unit 31j determines (confirms) whether or not the first application (application name) is registered in the registered application management table 31s (step S42).

  As a result of this determination, when the first application (application name) is registered in the registered application management table 31s (step S43: YES), the following first to third processes are executed.

  The first process is a process of updating the request message reception time in the application change time table 31u.

  Specifically, first, the request message registration confirmation unit 31j notifies the application monitoring control unit 31r of the request message reception time (step S44).

  Next, the application monitoring control unit 31r updates the “request message reception time” of the first application whose “application name” in the application change time table 31u is the request message reception time notified from the request message registration confirmation unit 31j. (For example, overwriting) (step S45).

  The second process is a process of saving the request message received in step S40 in the request queue 31t.

  Specifically, first, the request message registration confirmation unit 31j requests the request message storage unit 31k to store the request message received in step S40 (step S46).

  Next, the request message storage unit 31k stores the request message received in step S40 in the request queue 31t (see FIG. 21) dedicated to the first application (step S47).

  The third process is a process of requesting the PaaS system 20 to start the first application as a regular application when the operation status of the first application in the PaaS system 20 is being started as a dummy application.

  Specifically, first, the request message registration confirmation unit 31j requests the dummy application confirmation unit 31m to confirm whether the operation status of the first application in the PaaS system 20 is being activated as a dummy application (dummy application). Confirmation request) (step S48).

  Next, the dummy application confirmation unit 31m refers to the registered application management table 31s (“dummy flag”, “operation status”) to check whether the operation status of the first application in the PaaS system 20 is running as a dummy application. It is determined (confirmed) whether or not (step S49).

  As a result of the determination, if the operation status of the first application in the PaaS system 20 is being activated as a dummy application (step S49: YES), the dummy application confirmation unit 31m activates the first application as a regular application. A request is made to the requested application start / stop unit 31n (step S50).

  Next, the requested application activation / deactivation unit 31n determines that the “operational status” is the application (application name) of the first contractor (here, Usr01) associated with the first application (here, the application name apr04). The total amount obtained by adding the “reserved memory amount” of the active application and the “reserved memory amount” of the first application received in step S10 is the memory upper limit amount of the first contractor (in this case, Usr01). It is determined (confirmed) whether or not it exceeds (step S51).

  As a result of this determination, if the total amount does not exceed the memory upper limit amount (step S52: NO), the requested application activation / deactivation unit 31n requests the PaaS system 20 to activate the first application as a regular application ( Step S53).

  Specifically, the first application activation request includes an application name (here, apr04), a regular application (source file such as JAVA), a reserved memory amount (here 1 GB), a reserved disk amount (here) 1GB).

  In addition, a regular application (a source file such as JAVA) can be obtained as follows. For example, first, a file name (here, test01) associated with the first application from the registered application management table 31s (“file name”) shown in FIG. 14 using the first application (here, application name apr04) as a key. .java). Next, a regular application (source file such as JAVA) having the searched file name is extracted from the dummy application & regular application storage unit 31v using the searched file name (here, test01.java) as a key.

  As described above, a regular application (a source file such as JAVA) can be acquired.

  Note that the reserved memory amount and the reserved disk amount are the registered application management table 31s (“reserved memory amount”, “reserved disk amount” shown in FIG. 14 with the first application (here, application name apr04) as a key. ]) From the reserved memory amount and reserved disk amount associated with the first application.

  When the PaaS system 20 receives the first application activation request (step S53) from the application activation control system 30 (requested application activation stop unit 31n), the received application name (here, apr04) is displayed in the application information table. 21n is stored (for example, overwritten).

  In addition, the PaaS system 20 uses the container 21j2 (and the regular application) in which the regular application (source file such as JAVA) received from the application activation control system 30 (the requested application activation / stop unit 31n) is copied (overwritten on the dummy application). Start.

  Further, the PaaS system 20 notifies (transmits) the activation state of the regular application to the application activation control system 30. For example, when the container (and the regular application) starts normally, the PaaS system 20 notifies the activation as the activation state, and when it does not activate normally for some reason, the PaaS system 20 notifies the activation as the activation state.

  Further, the PaaS system 20 is activated (activated as a regular application) or stopped in the “operation status” of the “application name” (here, apr04) in the application information table 21n according to the activated state of the authorized application. Remember.

  Note that, as a result of the determination in step S51, if the total amount exceeds the memory upper limit amount (step S52: YES), the process in step S51 is repeatedly executed. Even in this case, the process of step S51 is not repeated infinitely. This is because a dummy application activation process (see FIG. 18) is executed, so that a regular application (with a relatively large reserved memory amount) that has passed the scheduled application change time eventually becomes a dummy application (with a relatively reserved memory amount). This is because step S52: NO, and the processing from step S53 onward is executed.

  Next, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application requested for activation in step S50 from the PaaS system 20 (step S54: YES), the registered application management table 31s. Is updated (step S55).

  For example, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the regular application from the PaaS system 20 (step S54: YES), the application activation control system 30 (for example, the application management unit 31q) registers according to the received activation state of the regular application. “Activation status” of “App name” (here, apr04) in the completed application management table 31s is stored as being activated (activated as a regular application) or stopped. Further, the application activation control system 30 (for example, the application management unit 31q) stores No in the “dummy flag” of the “application name” (here, apr04) of the registered application management table 31s.

  Next, the request application activation / deactivation unit 31n requests the request message transfer unit 31p to transfer a request message (step S56).

  Next, the request message transfer unit 31p acquires one request message from the request queue 31t dedicated to the first application (in this case, the application name apr04), and transfers the request message to the PaaS system 20 (step S57).

  The process of step S57 is executed until the request queue 31t dedicated to the first application is emptied (step S58: NO), and the request queue 31t dedicated to the first application is emptied (step S58: YES). The message reception process ends.

  On the other hand, as a result of the determination in step S49, if the operation status of the first application in the PaaS system 20 is not activated as a dummy application (step S49: NO), that is, the operation status of the first application in the PaaS system 20 is If the application is being activated as a regular application, the processes of steps S56 to S58 are executed.

  If the first application (application name) is not registered in the registered application management table 31s as a result of the determination in step S42 (step S43: NO), the request message registration confirmation unit 31j sends to the request message transfer unit 31p. A request message transfer is requested (step S59).

  Next, the request message transfer unit 31p transfers the request message received in step S40 to the PaaS system 20 (step S60).

  As described above, according to the present embodiment, from the application user until the first application that is the destination of the request message addressed to the first application received from the application user is activated (event driven) in the PaaS system 20. It is possible to prevent the received request message addressed to the first application from being missed.

  This is provided with a request queue 31t dedicated to the first application in which the PaaS system 20 stores a request message addressed to the first application received from the application user before the first application (regular application) is activated. This is because the request message addressed to the first application stored in the request queue 31t dedicated to the first application is transferred to the PaaS system 20 after the application (regular application) is activated.

  In addition, as described above, registration / deletion of applications has been conventionally performed. However, in the PaaS system 20, when an application is deleted, information managing the application name disappears, so that other developers can use the same application. There is a problem that it is possible to register by name, and the desired application name may not be used.

  On the other hand, according to the present embodiment, instead of deleting an application, since either a dummy application or a regular application is always registered in the PaaS system 20 for a certain application name, other developers are the same. You can prevent registration by application name.

  Further, according to the present embodiment, in order to replace a regular application (relatively large reserved memory amount) that has passed the scheduled application change time with a dummy application (relatively small reserved memory amount) having the same application name, The reserved memory can be reduced.

  Further, according to the present embodiment, only when an application on the PaaS system 20 is used, the dummy application is replaced with a regular application having the same application name only when a request message addressed to the first application is received from the application user. An event-driven service that consumes resources can be realized.

[Second Embodiment]
Next, an overview of the information processing system 10A according to the second embodiment will be described.

  FIG. 1 is a schematic configuration diagram of an information processing system 10A according to the second embodiment.

  Hereinafter, the difference from the first embodiment will be mainly described, the same components as those in the first embodiment will be denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  As shown in FIG. 1, the information processing system 10A of this embodiment includes a PaaS system 20, an application activation control system 30A, a developer terminal 40, an application user terminal 50, and the like, as in the first embodiment. The developer corresponds to the contractor of the present invention, and the application user corresponds to the user of the present invention.

  The developer transmits a regular application registration request to the application activation control system 30 </ b> A via the developer terminal 40. When the application activation control system 30A receives a registration request for a regular application from a developer, the application activation control system 30A stores the application and the operation status of the application in the PaaS system 20 in the registered application management table 31s2 for each developer. Since this is the same processing as in FIG. 13, description thereof is omitted.

  The application activation control system 30A refers to the application stop time table 31u2 and processes (for example, receives) the last request message among the applications (regular applications) whose operation status is activated (for example, request message reception time). ) Requesting the PaaS system 20 to stop the application after a predetermined time has elapsed, and change the operation status of the application in the application stop time table 31u2 after the predetermined time has been stopped. The PaaS system 20 stops the container (and the regular application) to which the regular application is copied.

  The time at which the last request message is processed is not limited to the request message reception time, but may be the time at which the last request message stored in the request queue 31t is transferred to the PaaS system 20.

  Further, the application activation control system 30A performs the following processing when receiving a request message addressed to the first application from the user.

  When the operation status of the first application is stopped with reference to the registered application management table 31s2, the application activation control system 30A stores a request message addressed to the first application in the request queue 31t. The request queue 31t corresponds to the second memory of the present invention.

  Next, the total amount obtained by adding the reserved memory amount of the application whose operation status is active among the applications of the first contractor associated with the first application and the reserved memory amount of the first application is the first amount. When the memory upper limit amount of the contractor is not exceeded, the activation of the first application is requested to the PaaS system 20. The PaaS system 20 activates the container (and the regular application) in which the regular application is copied.

  Then, after the first application is activated in the PaaS system 20, the request message addressed to the first application stored in the request queue 31t is transferred to the PaaS system 20, and the operation status of the first application in the registered application management table 31s2 is displayed. Change during startup. The PaaS system 20 transfers a request message addressed to the first application to the active first application.

  FIG. 22 is a diagram for explaining a main function of the application activation control system 30A and a table included in the application activation control system 30A.

  As shown in FIG. 22, in the present embodiment, an application confirmation unit 31w is further added as compared with the first embodiment (see FIG. 8).

  In this embodiment, an application stop time table 31u2 (see FIG. 23) is used instead of the application change time table 31u (see FIG. 11).

  In the present embodiment, a registered application management table 31s2 (see FIG. 24) is used instead of the registered application management table 31s (see FIG. 9).

  FIG. 25 is a flowchart for explaining an example of the application stop process in the application activation control system 30 of the second embodiment.

  First, the application monitoring control unit 31r acquires the request message reception time and the application stop time for each application from the application stop time table 31u2 (step S60).

  Next, the application monitoring control unit 31r calculates an application stop scheduled time (= request message reception time + application stop time) (step S61).

  Next, when there is an application name that exceeds the scheduled application stop time (step S62: YES), the application monitoring control unit 31r requests the requested application start / stop unit 31n to stop the corresponding application (step S63).

  Next, the requested application start / stop unit 31n requests the PaaS system 20 to stop the corresponding application (step S64).

  This application stop request includes the application name of the corresponding application (for example, apr01 in FIG. 23).

  When the PaaS system 20 receives an application stop request (step S64) from the application start control system 30 (requested application start / stop unit 31n), the received application name (here, apr01) is copied (regular application). Stop the container 21j2 (and the regular application). Note that “stop” refers to a state where an application (regular application) exists on the memory 21c (or storage 22 such as a disk) but does not consume resources (for example, a state where the CPU used is zero).

  Further, the PaaS system 20 notifies (transmits) the activation state of the application (regular application) to the application activation control system 30. For example, when the container (and the dummy application) is normally stopped, the PaaS system 20 notifies the active state of being stopped.

  In addition, when the container (and the dummy application) is normally stopped, the PaaS system 20 stores “stopped” in the “operation status” of the “application name” (here, apr04) in the application information table 21n.

  Next, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application requested for activation in step S64 from the PaaS system 20 (step S65: YES), the registered application management table 31s2 Is updated (step S66).

  For example, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application from the PaaS system 20 (step S65: YES), the registered application according to the received activation state of the application “Activation status” of “application name” (here, apr01) in the management table 31s2 is stored as being activated or stopped.

  The processes in steps S60 to S66 are executed at specified intervals.

  26 and 27 are flowcharts for explaining request message reception processing in the application activation control system 30A.

  In the following, differences from the first embodiment (FIGS. 19 and 20) will be mainly described, and the same processes as those in the first embodiment (FIGS. 19 and 20) will be denoted by the same reference numerals, and description will be appropriately given. Omitted.

  First, it waits until the request message receiving unit 31h receives a request message addressed to the first application transmitted from the application user via the application user terminal 50 (step S40: NO).

  Hereinafter, an example of processing when the request message receiving unit 31h receives a request message addressed to the first application (here, application name apr04, developer name Usr01) from the application user will be described.

  When the request message reception unit 31h receives a request message addressed to the first application (step S40: YES), the first application (application name) is registered in the registered application management table 31s2 with respect to the request message registration confirmation unit 31j. A request for confirmation (application confirmation request) is made as to whether or not it is stored (step S41).

  Next, the request message registration confirmation unit 31j determines (confirms) whether or not the first application (application name) is registered in the registered application management table 31s2 (step S42).

  As a result of this determination, when the first application (application name) is registered in the registered application management table 31s2 (step S43: YES), the following first to third processes are executed.

  The first process is a process of updating the request message reception time in the application stop time table 31u2.

  Specifically, first, the request message registration confirmation unit 31j notifies the application monitoring control unit 31r of the request message reception time (step S44).

  Next, the application monitoring control unit 31r updates the “request message reception time” of the first application whose “application name” in the application stop time table 31u2 is the request message reception time notified from the request message registration confirmation unit 31j. (For example, overwriting) (step S45).

  The second process is a process of saving the request message received in step S40 in the request queue 31t.

  Specifically, first, the request message registration confirmation unit 31j requests the request message storage unit 31k to store the request message received in step S40 (step S46).

  Next, the request message storage unit 31k stores the request message received in step S40 in the request queue 31t dedicated to the first application (step S47).

  The third process is a process for requesting the PaaS system 20 to start the first application when the operation status of the first application in the PaaS system 20 is stopped.

  Specifically, the request message registration confirmation unit 31j first requests the application confirmation unit 31w to confirm the operation of the first application (step S70).

  Next, the application confirmation unit 31w refers to the registered application management table 31s2 (“operation status”) to determine (confirm) whether or not the operation status of the first application in the PaaS system 20 is being activated ( Step S71).

  As a result of this determination, if the operation status of the first application in the PaaS system 20 is being activated (step S49A: YES), the application confirmation unit 31w causes the requested application activation / deactivation unit 31n to activate the first application. (Step S50A).

  Next, the requested application activation / deactivation unit 31n determines that the “operational status” is the application (application name) of the first contractor (here, Usr01) associated with the first application (here, the application name apr04). The total amount obtained by adding the “reserved memory amount” of the active application and the “reserved memory amount” of the first application received in step S40 is the memory upper limit amount of the first contractor (here, Usr01). It is determined (confirmed) whether or not it exceeds (step S51).

  As a result of this determination, if the total amount does not exceed the memory upper limit amount (step S52: NO), the requested application activation / deactivation unit 31n requests the PaaS system 20 to activate the first application (step S53A).

  This first application activation request includes the application name of the first application (here, apr04).

  When the PaaS system 20 receives the first application activation request (step S53A) from the application activation control system 30 (requested application activation stop unit 31n), the container 21j2 in which the application (regular application) of the received application name is copied. (And regular app).

  Further, the PaaS system 20 notifies (transmits) the activation state of the regular application to the application activation control system 30. For example, when the container (and the regular application) starts normally, the PaaS system 20 notifies the activation as the activation state, and when it does not activate normally for some reason, the PaaS system 20 notifies the activation as the activation state.

  Further, the PaaS system 20 is activated (activated as a regular application) or stopped in the “operation status” of the “application name” (here, apr04) in the application information table 21n according to the activated state of the authorized application. Remember.

  Next, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application requested for activation in step S50A from the PaaS system 20 (step S54: YES), the registered application management table 31s. Is updated (step S55).

  For example, when the application activation control system 30 (for example, the application management unit 31q) receives the activation state of the application from the PaaS system 20 (step S54: YES), the registered application according to the received activation state of the application “Activation status” of “application name” (here, apr04) in the management table 31s is stored as being activated or stopped.

  Next, the request application activation / deactivation unit 31n requests the request message transfer unit 31p to transfer a request message (step S56).

  Next, the request message transfer unit 31p acquires one request message from the request queue 31t dedicated to the first application (in this case, the application name apr04), and transfers the request message to the PaaS system 20 (step S57).

  The process of step S57 is executed until the request queue 31t dedicated to the first application is emptied (step S58: NO), and the request queue 31t dedicated to the first application is emptied (step S58: YES). The message reception process ends.

  On the other hand, if the result of determination in step S49 is that the operation status of the first application in the PaaS system 20 is not active (step S49: NO), that is, the operation status of the first application in the PaaS system 20 is stopped. If there is, the processes in steps S56 to S58 are executed.

  If the first application (application name) is not registered in the registered application management table 31s as a result of the determination in step S43 (step S43: NO), the request message registration confirmation unit 31j is sent to the request message transfer unit 31p. A request message transfer is requested (step S59).

  Next, the request message transfer unit 31p transfers the request message received in step S40 to the PaaS system 20 (step S60).

  As described above, according to the present embodiment, from the application user until the first application that is the destination of the request message addressed to the first application received from the application user is activated (event driven) in the PaaS system 20. It is possible to prevent the received request message addressed to the first application from being missed.

  This is provided with a request queue 31t dedicated to the first application in which the PaaS system 20 stores a request message addressed to the first application received from the application user before the first application (regular application) is activated. This is because the request message addressed to the first application stored in the request queue 31t dedicated to the first application is transferred to the PaaS system 20 after the application (regular application) is activated.

  In addition, as described above, registration / deletion of applications has been conventionally performed. However, in the PaaS system 20, when an application is deleted, information managing the application name disappears, so that other developers can use the same application. There is a problem that it is possible to register by name, and the desired application name may not be used.

  On the other hand, according to the present embodiment, the application is not deleted, but a regular application that is being activated or stopped is always registered in the PaaS system 20 for a certain application name, so that other developers are the same. You can prevent registration by application name.

  In addition, according to the present embodiment, only when a request message addressed to the first application is received from the application user, the operation status in the PaaS system is changed from being stopped to being activated. It is possible to realize an event-driven service in which resources are consumed only at times.

  The above embodiment is summarized as follows.

(Appendix 1)
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
A software control program that causes a computer to execute processing.

(Appendix 2)
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. Process,
A software control program that causes a computer to execute processing.

(Appendix 3)
In Appendix 1 or 2,
When the first software is received from the user and the first software is not stored in the first memory, the first process, the second process, and the third process are performed without performing the first process, the second process, and the third process. A software control program for transferring a request message addressed to the first software to a system and performing the first process, the second process, and the third process when the first software is stored in the first memory.

(Appendix 4)
In any one of supplementary notes 1 to 3,
When receiving a software registration request from a contractor, a software control program for storing the software and the operation status of the software in the first memory for each contractor.

(Appendix 5)
The software control program according to any one of appendices 1 to 4, wherein the second memory is a memory dedicated to the first software.

(Appendix 6)
In any one of appendices 1 to 5,
The second memory is a queue;
A software control program for sequentially transferring the request messages to the system when transferring the request messages stored in the second memory to the system.

(Appendix 7)
In any one of appendices 1 to 6,
The time when the last request message was processed is a software control program which is the time when the last request message is received from a user or the time when the last request message stored in the second memory is transferred to the system.

(Appendix 8)
Memory,
A processor capable of accessing the memory,
The processor is
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
Software control device that executes processing.

(Appendix 9)
Memory,
A processor capable of accessing the memory,
The processor is
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. A software control device that performs processing and executes processing.

(Appendix 10)
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
A software control method for causing a computer to execute processing.

(Appendix 11)
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. Software control method for performing processing and causing processing to be executed by a computer

10, 10A: Information processing system 20: PaaS system

Claims (9)

Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
A software control program that causes a computer to execute processing. Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. Process,
A software control program that causes a computer to execute processing.   When the first software is received from the user and the first software is not stored in the first memory, the first process, the second process, and the third process are performed without performing the first process, the second process, and the third process. The request message addressed to the first software is transferred to the system, and when the first software is stored in the first memory, the first process, the second process, and the third process are performed. The software control program according to 2.   The software control program according to any one of claims 1 to 3, wherein the second memory is a memory dedicated to the first software.   5. The time when the last request message is processed is the time when the last request message is received from a user or the time when the last request message stored in the second memory is transferred to the system. The software control program according to any one of the above. Memory,
A processor capable of accessing the memory,
The processor is
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
Software control device that executes processing. Memory,
A processor capable of accessing the memory,
The processor is
Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. A software control device that performs processing and executes processing. Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Requesting the system to stop the software after a predetermined time has elapsed from the time when the last request message was processed, and changing the operation status of the software after the predetermined time has passed to the stop,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is running, a second process is performed to transfer the request message stored in the second memory to the system,
When the operating status of the first software is stopped, the resources of the software whose operating status is activated and the resources of the first software among the software of the first contractor associated with the first software are added When the total amount does not exceed the resource upper limit amount of the first contractor, the system requests the system to start the first software, and after the first software starts, the request message stored in the second memory Performing a third process of transferring to the system and changing the operating status of the first software during startup;
A software control method for causing a computer to execute processing. Software activated in the system and the operation status of the software in the system are stored in the first memory for each contractor;
Among the software whose operating status is being activated as regular software, the system is requested to start as software dummy software whose predetermined time has elapsed from the time when the last request message was processed, and the operating status of software whose predetermined time has elapsed is dummy Change while running as software,
When a request message addressed to the first software is received from a user, a first process of storing the request message addressed to the first software in a second memory is performed.
When the operation status of the first software is activated as regular software, a second process is performed to transfer the request message stored in the second memory to the system,
When the operation status of the first software is activated as dummy software, a request message addressed to the first software is stored in the second memory, and the operation of the software of the first contractor associated with the first software is performed. When the total amount obtained by adding the resources of the software being activated and the resources of the first software does not exceed the resource upper limit amount of the first contractor, the activation of the first software as the regular software is performed in the system. A request message stored in the second memory is transferred to the system, and the operating status of the first software is changed during activation as regular software. Software control method for performing processing and causing processing to be executed by a computer

Images