WO2011018827A1 - 実行環境におけるアプリケーションの適性を評価するシステム及び方法 - Google Patents
実行環境におけるアプリケーションの適性を評価するシステム及び方法 Download PDFInfo
- Publication number
- WO2011018827A1 WO2011018827A1 PCT/JP2009/003893 JP2009003893W WO2011018827A1 WO 2011018827 A1 WO2011018827 A1 WO 2011018827A1 JP 2009003893 W JP2009003893 W JP 2009003893W WO 2011018827 A1 WO2011018827 A1 WO 2011018827A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- evaluation
- value
- type
- execution environment
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 50
- 238000011156 evaluation Methods 0.000 claims abstract description 323
- 230000008859 change Effects 0.000 claims description 74
- 230000000694 effects Effects 0.000 claims description 71
- 230000014509 gene expression Effects 0.000 claims description 67
- 238000012545 processing Methods 0.000 claims description 65
- 230000006870 function Effects 0.000 claims description 17
- 238000004891 communication Methods 0.000 claims description 15
- 238000005516 engineering process Methods 0.000 claims description 11
- 238000013500 data storage Methods 0.000 claims description 4
- 230000001419 dependent effect Effects 0.000 claims 1
- 238000009434 installation Methods 0.000 claims 1
- 238000011548 physical evaluation Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 description 85
- 238000010586 diagram Methods 0.000 description 77
- 238000010606 normalization Methods 0.000 description 16
- 238000013508 migration Methods 0.000 description 10
- 230000005012 migration Effects 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 238000012937 correction Methods 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000001771 impaired effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2101—Auditing as a secondary aspect
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2135—Metering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2149—Restricted operating environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1433—Vulnerability analysis
Definitions
- the present invention relates to a technique for performing evaluation using a computer.
- an operation management apparatus collects information about applications from a client and centrally manages the information, and performs a security check, a license check, and the like.
- Application virtualization technology is a technology that makes an application available without depending on a client-specific environment (for example, a device and / or an operating system (hereinafter referred to as “OS”) of a client). .
- OS operating system
- the first method is a method of executing an application distributed from an application server in a client environment in which access by an application to a native resource provided by the OS is separated.
- This type of method is disclosed in Patent Document 2, for example.
- this type of method is particularly called “streaming type”.
- the second method is a method in which the client executes the application remotely on the application server.
- This type of method is disclosed in Patent Document 3, for example.
- this type of method is particularly referred to as “host type”.
- an object of the present invention is to enable selection of an appropriate application execution environment.
- the evaluation system evaluates the suitability of the application in a plurality of types of application execution environments based on the characteristics of the application and / or the usage status of the application by the user.
- the evaluation system displays information representing the result of the evaluation.
- application execution environment refers to an environment in which an application is executed so that a client user can use the application.
- Examples of the application execution environment include a physical environment, one or more virtual environments, and one or more cloud environments (an environment in which a client uses an application function provided by a cloud system).
- the one or more virtual environments include, for example, a streaming type virtual environment and a host type virtual environment. It doesn't matter where the application actually runs.
- the application execution environment is a physical environment or a streaming virtual environment
- the application is executed by the client.
- the application execution environment is a host-type virtual environment
- the application is executed on the application server.
- the application execution environment is a cloud environment
- the application is executed by the cloud system.
- “displaying information” may include sending information to the remote display device by the evaluation system.
- the remote display device displays the information received from the evaluation system.
- FIG. 1 is a diagram illustrating an overall configuration of the first embodiment.
- FIG. 2 is a diagram illustrating the configuration of the management server 100 according to the first embodiment.
- FIG. 3 is a diagram illustrating the configuration of the application server 101 according to the first embodiment.
- FIG. 4 is a diagram illustrating the configuration of the client 102 according to the first embodiment.
- FIG. 5 is a diagram for explaining the outline of the first embodiment.
- FIG. 6 is a diagram illustrating the inventory table 418 according to the first embodiment.
- FIG. 7 is a diagram illustrating the usage history table 419 according to the first embodiment.
- FIG. 8 is a diagram illustrating the characteristic table 211 according to the first embodiment.
- FIG. 9 is a diagram illustrating the usage status table 212 according to the first embodiment.
- FIG. 10 is a diagram illustrating the evaluation formula table 214 according to the first embodiment.
- FIG. 11 is a diagram illustrating a normalization expression table 215 according to the first embodiment.
- FIG. 12 is a diagram illustrating the suitability evaluation table 216 according to the first embodiment.
- FIG. 13 is a diagram illustrating an effect evaluation table 217 according to the first embodiment.
- FIG. 14 is a diagram illustrating the evaluation viewpoint priority table 219 according to the first embodiment.
- FIG. 15 is a diagram illustrating the change priority table 220 according to the first embodiment.
- FIG. 16 is a diagram illustrating the client list table 221 according to the first embodiment.
- FIG. 17 is a diagram illustrating a processing procedure of the collection program 207 according to the first embodiment.
- FIG. 18 is a diagram illustrating a processing procedure of the aptitude evaluation program 208 according to the first embodiment.
- FIG. 19 is a diagram illustrating a processing procedure of the effect evaluation program 209 according to the first embodiment.
- FIG. 20 is a diagram illustrating a processing procedure of the priority calculation unit 210 according to the first embodiment.
- FIG. 21 is a diagram illustrating a processing procedure of the data update program 223 according to the first embodiment.
- FIG. 22 shows a priority list screen 2200 according to the first embodiment.
- FIG. 23 is a diagram illustrating an operation management policy setting screen 2300 according to the first embodiment.
- FIG. 24 is a diagram illustrating an application information registration screen 2400 according to the first embodiment.
- FIG. 25 is a diagram illustrating the configuration of the application server 2501 according to the second embodiment.
- FIG. 26 is a diagram for explaining the outline of the second embodiment.
- FIG. 27 is a diagram illustrating a usage history table 2601 according to the second embodiment.
- FIG. 28 is a diagram illustrating a usage status table 2612 according to the second embodiment.
- FIG. 29 is a diagram illustrating an evaluation formula table 2914 according to the second embodiment.
- FIG. 30 is a diagram illustrating an aptitude evaluation table 3016 according to the second embodiment.
- FIG. 31 is a diagram illustrating an effect evaluation table 3117 according to the second embodiment.
- FIG. 32 is a diagram illustrating a change priority table 3220 according to the second embodiment.
- FIG. 33 is a diagram showing a collection program 3307 according to the second embodiment.
- FIG. 34 is a diagram illustrating a billing information table 224 according to the third embodiment.
- FIG. 35 is a diagram showing an overall configuration of the fourth embodiment.
- FIG. 36 is a diagram illustrating a usage status table 3612 according to the fourth embodiment.
- FIG. 37 is a diagram illustrating an evaluation formula table 3714 according to the fourth embodiment.
- FIG. 38 shows a priority list screen 3800 according to the fifth embodiment.
- FIG. 39 is a diagram illustrating a threshold value table 225 according to the sixth embodiment.
- FIG. 40 is a diagram illustrating a processing procedure of the aptitude evaluation program 4008 according to the sixth embodiment.
- xxx table various types of information are described using the expression “xxx table”, but the various types of information may be expressed using a data structure other than a table. In order to show that it does not depend on the data structure, the “xxx table” can be called “xxx information”.
- identification information may be represented by the expressions “name” and “ID”, but the type of identification information may be any type, Various types of identification information can be replaced with different types of identification information.
- the process may be described using “program” as the subject.
- the program is executed by the processor, so that the determined process can be appropriately performed with storage resources (for example, memory) and communication control.
- the subject of processing may be a processor.
- the processing described with the program as the subject may be processing performed by the management system.
- part or all of the program may be realized by dedicated hardware.
- the processing described with the program as the subject may be processing performed by the controller.
- the controller may include a processor and a storage resource that stores a computer program executed by the processor, or may include the dedicated hardware described above.
- the computer program may be installed in each computer from a program source.
- the program source may be, for example, a program distribution server or a storage medium.
- the management system is one or more computers, for example, a management computer, or a combination of a management computer and a display computer. Specifically, for example, when the management computer displays display information, the management computer is a management system. In addition, in order to increase the processing speed and reliability, a function equivalent to that of the management computer may be realized by a plurality of computers. In this case, the plurality of computers (in the case where the display computer performs display, the display is displayed). A management system).
- the first embodiment relates to a network system in which a physical environment and a streaming virtual environment are mixed.
- This network system is based on a technique for separating access by an application to a specific information resource including setting information (for example, a registry) and an execution library (for example, DLL (Dynamic Link Library)).
- setting information for example, a registry
- execution library for example, DLL (Dynamic Link Library)
- This network system has an application server, and the application server distributes a virtual application described later to the client.
- FIG. 1 is a diagram showing an overall configuration of the present embodiment.
- the network system 10 includes a management server 100, an application server 101, and a client group including one or more clients 102, and these are connected to the network 103.
- the network 103 is a communication network that connects the management server 100, the application server 101, and a client group so that they can communicate with each other.
- the network 103 may be, for example, a LAN (Local Area Network) in a company, or a WAN (Wide Area Network). Network).
- the application server 101 is one or more computers, and delivers an application to the client 102 in response to a request from the client 102.
- the client 102 is an information processing terminal (for example, a desktop PC (Personal Computer) or a notebook PC), and is used by a user (for example, an employee of a company).
- the client 102 can receive an application from the application server 101 and execute it.
- the physical application is an application installed in the client 102 and depends on a client-specific environment (for example, a device and / or an OS).
- the virtual application is a package (archive) including specific information resources including setting information (for example, a registry) and an execution library (for example, DLL (Dynamic Link Library)) and an execution program, and does not depend on a client-specific environment.
- the physical application and the virtual application are collectively referred to as “application”.
- Management server 100 is an example of a management system to which an evaluation system according to an embodiment of the present invention is applied.
- the management server 100 collects information indicating the characteristics of the applications used in the network system 10 and the usage status thereof, and manages the information centrally. Details will be described later.
- FIG. 2 is a diagram showing the configuration of the management server 100.
- the management server 100 includes a communication interface 203 and a controller, and the controller includes a CPU (Central Processing Unit) 200, a main storage device (for example, memory) 201, a disk interface 202, and a screen interface 204.
- the network 103 is connected to the communication interface 203, the disk device 205 is connected to the disk interface 202, and the display device 206 is connected to the screen interface 204.
- the display device 206 is a device having a display screen (LCD (Liquid Crystal Display) screen), and information output from the management server 100 (for example, client information, application information, and application priority for changing the execution environment). Information about the effects of degrees and changes).
- LCD Liquid Crystal Display
- the disk device 205 is a storage device and may be built in the management server 100 or a large-capacity disk array device.
- the storage medium of the “disk device” referred to in this specification is a disk such as a hard disk, but other types of storage media such as a flash memory may be employed.
- the disk device 205 stores programs and data used by the management server 100.
- the disk device 205 includes, for example, a collection program 207, aptitude evaluation program 208, effect evaluation program 209, priority calculation program 210, screen control program 222, data update program 223, characteristic table 211, usage status
- the table 212, the evaluation policy 213, the aptitude evaluation table 216, the effect evaluation table 217, the operation management policy 218, the change priority table 220, and the client list table 221 are stored.
- a program stored in the disk device 205 is loaded into the main storage device 201 and executed by the CPU 200.
- the characteristic table 211 is a table in which information representing the characteristics of each application is stored.
- the “application characteristics” referred to here are, for example, specific characteristics of the application, and specifically, for example, version, support OS, and the like.
- the usage status table 212 is a table in which information indicating the usage status of each application user is stored.
- the “information indicating the usage status” referred to here is, for example, information that can change depending on how the application is used, and specifically includes, for example, the number of users of the application and usage history.
- the evaluation policy 213 is information representing a policy for evaluating the suitability of the application in each execution environment from the viewpoint of operation management.
- the evaluation policy 213 includes, for example, an evaluation expression table 214 and a normalization expression table 215.
- the suitability of an application in a certain execution environment represents how appropriate it is that the application is used in the execution environment. For example, an execution environment for an application with a large number of users is more suitable for a virtual environment than a physical environment in terms of costs required for operation management such as security checks.
- the suitability of an application in a certain execution environment is evaluated from the three viewpoints of operation management evaluation, which are security, operation cost, and user convenience.
- the evaluation formula table 214 is a table in which formulas for quantitatively evaluating and calculating the suitability of an application in a certain execution environment are stored.
- the normalization expression table 215 is a table in which expressions for aligning the range of values calculated by the respective expressions in the evaluation expression table 214 are stored.
- the aptitude evaluation table 216 is a table in which information indicating the evaluation result of the aptitude of the application is stored.
- the effect evaluation table 217 is a table in which information indicating the evaluation result of the effect of changing the execution environment of the application is stored.
- the operation management policy 218 is information indicating a guideline for operation management when evaluating the suitability of an application or determining the priority of changing the execution environment.
- the operation management policy 218 includes an evaluation viewpoint priority table 219.
- the evaluation viewpoint priority table 219 is a table in which information representing viewpoints to be emphasized when calculating the priority of changing the execution environment is stored.
- information indicating the priority of the evaluation viewpoint in operation management is stored in the table 219.
- the change priority table 220 is a table in which information representing the priority order of the application whose execution environment is to be changed is stored.
- the client list table 221 is a table in which information regarding all clients 102 in the network system 10 is stored.
- the collection program 207 collects information on applications used by the client group from an agent program 407 (to be described later) of the client 102 and stores the collected information in the usage status table 212.
- the aptitude evaluation program 208 evaluates the aptitude of the application in each application execution environment based on the characteristic table 211, the usage situation table 212, and the evaluation policy 213, and stores information indicating the evaluation result in the aptitude evaluation table 216. Store.
- the effect evaluation program 209 evaluates the effect of changing the execution environment of the application based on the aptitude evaluation table 216, and stores information representing the result of the evaluation in the effect evaluation table 217.
- the priority calculation program 210 calculates the priority of the application whose execution environment is to be changed based on the effect evaluation table 217 and the operation management policy 218, and stores the calculated priority in the change priority table 220. Store.
- the screen control program 222 updates the display screen in response to the shaping of screen information displayed on the display device 206 and the operation of the administrator of the network system 10.
- examples of screens that the screen control program 222 displays on the display device 206 include, for example, the priority order list screen 2200 described with reference to FIG. 22, the operation management policy setting screen 2300 described with reference to FIG.
- the data update program 223 updates various tables held by the management server 100.
- the data update program 223 executes the collection program 207, the aptitude evaluation program 208, the effect evaluation program 209, and the priority order calculation program 210 in order, and inventory information (for example, information indicating the application name, version, and execution environment) from all clients. ) To evaluate the suitability of the application and calculate the priority.
- the data update program 223 can be executed when the update button 2205 on the priority list screen 2200 described with reference to FIG. 22 is pressed. Further, the management server 100 may periodically execute the data update program 223.
- FIG. 3 is a diagram showing the configuration of the application server 101.
- the application server 101 includes a communication interface 303 and a controller.
- the controller includes a CPU 300, a main storage device (for example, a memory) 301, and a disk interface 302.
- a disk device 304 is connected to the disk interface 302, and a network 103 is connected to the communication interface 303.
- the disk device 304 is a storage device that stores programs and data used by the application server 101, and may be built in the application server 101.
- the disk device 304 stores an application distribution program 305 and a virtual application group managed by the application server 101.
- the virtual application group includes virtual applications 306A and 306B.
- the number of virtual applications included in the virtual application group is not limited to two, and may be one or three or more.
- the virtual application 306A will be representatively described.
- a program stored in the disk device 304 is loaded into the main storage device 301 and executed by the CPU 300.
- the virtual application 306A is a package (archive) including an application program 307A, setting information 308A and a library 309A used by the application program 307A.
- the virtual application 306A has both the setting information 308A and the library 309A, but the present invention can be applied to a virtual application that does not have one or both of them.
- the virtual application may include information other than the setting information and the library.
- the virtual application may be registered by an administrator or may be registered by the management server 100.
- the application program 307A is an application program main body, for example, an application execution file.
- the application program 307A may be a program for installing an application.
- the setting information 308A is information used when the application program 307A is executed, and is, for example, a registry and / or a setting file.
- the library 309A is information used as a library when an application is executed, and is, for example, a DLL (Dynamic Link Library).
- the virtual application 306B is the same as the virtual application 306A.
- the application distribution program 305 In response to a request from the client 102, the application distribution program 305 distributes the virtual application managed by the application server 101 to the client 102 via the network 103.
- the application distribution program 305 may have a function other than the function to distribute, for example, an access control function that restricts access of the client 102 and / or a log management function that stores an access history of the client 102.
- a virtual application is distributed to the client 102 in response to a request from the client 102.
- FIG. 4 is a diagram showing the configuration of the client 102.
- the client 102 has a communication interface 403 and a controller, and the controller has a CPU 400, a main storage device 401, a disk interface 402, and a screen interface 404.
- a disk device 405 is connected to the disk interface 402
- the network 103 is connected to the communication interface 403
- a display device 406 is connected to the screen interface 404.
- the display device 406 is a device having a display screen such as an LCD screen, and displays information output from the client 102 (for example, information for a user to use an OS or an application on the client 102).
- the disk device 405 is a storage device that stores programs and data used by the client 102 and may be built in the client 102.
- the disk device 405 includes an agent program 407, a client program 408, an application program 409A, setting information 410A used by the application program 409A, a library 411A and data 412A, an application program 409B, and setting information used by the application program 409B.
- 410B, library 411B and data 412B, virtual application 413A, virtual application 413B, data 417A used by virtual application 413A, data 417B used by virtual application 413B, inventory table 418, and usage history table 419 Remember.
- the application program 409A is a physical application installed in the client 102, and is an application program body such as an executable file.
- the setting information 410A is information such as a registry and a setting file used by the application program 409A during execution.
- the library 411A is a library such as a DLL read by the application program 409A at the time of execution.
- the data 412A is a file output as a processing result by the application program 409A. Further, the data 412A may be a file serving as an input for processing by the application program 409A.
- Application program 409B, setting information 410B, library 411B, and data 412B are the same as application program 409A, setting information 410A, library 411A, and data 412A, respectively.
- the data 412A has one configuration, but the present invention can also be applied to an application in which a plurality of data exists for each document, such as a document tool.
- the virtual application 413A is a virtual application received by the client 102 from the application server 101. As described in FIG. 3, the virtual application 413 includes an application program 414A, setting information 415A, and a library 416A.
- the virtual application 413B is a virtual application received from the application server 101 by the client 102, like the virtual application 413A.
- the data 417A is a file that the virtual application 413A outputs as a processing result.
- the data 417A may be a file serving as an input for processing by the virtual application 413A.
- the data 417A is not included in the virtual application 413A, but may be included in the virtual application 413A.
- the data 417B is, for example, a file that becomes an input or output of processing of the virtual application 413B, similarly to the data 417A.
- the inventory table 418 is a table in which information (for example, name, version, etc.) related to the application used in the client 102 is stored.
- the usage history table 419 is a table in which an application usage history (for example, application execution time) is stored.
- the agent program 407 is a program for collecting application information and usage history. Further, as described with reference to FIG. 2, the agent program 407 is called from the collection program 207 of the management server 100 and returns the collected information to the management server 100.
- the client program 408 is a program for executing a virtual application, and is executed on the OS (not shown) of the client 102. Since the client program 408 hides the OS from the application program 414A (414B) in the virtual application 413A (413B), it is possible to execute the virtual application 413A (413B) without depending on the client-specific environment (for example, OS). It is.
- the application program 414A (414B) operates using the archived setting information 415A (415B) and the library 416A (416B). Note that the present invention is also applicable to a case where an application program in a virtual application does not use setting information and / or a library, or a case where an application program in a virtual application uses other information.
- the present invention can also be applied to a case where the client program 408 is included in a virtual application and a case where the client program 408 is a program (for example, a Web browser) that is normally installed in the OS. Since the virtual application is executed without depending on the environment unique to the client, it can be executed even when the OS of the client 102 is not an OS supported by the application program (414A, 414B). It is also possible to execute different versions of the same application on the same client or without causing conflicts with other applications.
- FIG. 5 is a diagram showing an outline of the present embodiment.
- the virtual application is abbreviated as “VAP” and the physical application is abbreviated as “PAP”.
- the administrator registers information related to the application from the application information registration screen 2400 described with reference to FIG.
- the management server 100 updates the characteristic table 211 based on the registered information (step s1).
- the management server 100 collects the information stored in the inventory table 418 and the information stored in the usage history table 419 from all clients of the network system 10, and uses the information based on the collected information.
- the table 212 is updated (step s2).
- the management server 100 evaluates the characteristics of the application in each execution environment based on the characteristic table 211 and the usage situation table 212, and calculates the priority of the application that changes the execution environment (step s3).
- the management server 100 displays the calculated priority order and the effect of changing the execution environment on the screen (step s4).
- the administrator determines an application whose execution environment should be changed based on the priority displayed on the screen in step s4 and the effect of the change of the execution environment.
- FIG. 6 is a diagram showing the inventory table 418.
- Each line of the inventory table 418 has an ID 601, an application name 602, a version 603, and an execution environment 604, and corresponds to one application used by the client 102.
- ID 601 is information (for example, a numerical value and / or a character string) for uniquely identifying an application used in the client 102.
- Application name 602 is information indicating the name of the application.
- Version 603 is information indicating the version of the application.
- the execution environment 604 is information representing the execution environment of the application.
- “standard” is set as the execution environment 604.
- “virtual” is set as the execution environment 604.
- the virtual environment in the present embodiment is a streaming virtual environment.
- a host-type virtual environment may also exist in the network system 10 (that is, the second embodiment described later with this embodiment).
- a value that can distinguish the type of virtual environment such as “virtual (streaming)” and “virtual (host)” is stored as the execution environment 604.
- the network system 10 includes an environment other than the physical environment and the virtual environment, for example, a cloud environment described later (when the fourth embodiment is combined with the present embodiment)
- a value “Cloud” is stored as the execution environment 604.
- a value that can distinguish the cloud environments such as “cloud A” and “cloud B” is stored as the execution environment 604.
- various information in the inventory table 418 is acquired and set by using a program that is installed in the OS as standard, such as acquiring list information of installed applications and file list information. can do.
- FIG. 7 is a diagram showing the usage history table 419.
- Each row of the usage history table 419 has an application ID 701, a start time 702, and an end time 703, and corresponds to one application used by the client 102.
- the application ID 701 is information for uniquely identifying an application used by the client 102. Specifically, for example, the application ID 701 is the same value as the ID 601 of the inventory table 418.
- the start time 702 is information indicating the time when the use of the application is started.
- the end time 703 is information indicating the time when the use of the application is ended.
- the various information in the application history table 419 can be acquired and set from, for example, a program that is normally installed in the OS or a client program 408 that monitors the execution state of the process.
- FIG. 8 is a diagram showing the characteristic table 211.
- Each row of the characteristic table 211 has an ID 801, an application name 802, a version 803, a patch release count 804, and a support OS 805, and corresponds to one application used in the network system 10.
- ID 801 is information for uniquely identifying an application used in the network system 10.
- Application name 802 is information indicating the name of the application.
- Version 803 is information representing the version of the application.
- the patch release count 804 is information representing the number of times a correction program (hereinafter referred to as “patch”) for updating an application program has been released.
- patch a correction program
- the patch release count 804 stored in the added row a value obtained by adding 1 to the original patch release count 804 is stored.
- the support OS 805 is information representing an OS (support OS) in which the operation of the application is guaranteed.
- information representing the plurality of support OSs for example, character strings concatenated by commas
- the character strings representing the support OS are concatenated by commas, but it is also possible to employ a method in which the support OS 805 is managed by another table and the table is normalized.
- information stored in the characteristic table 211 is input from the administrator via the application information registration screen 2400 described with reference to FIG.
- the present invention is not limited to this.
- information stored in the characteristic table 211 may be acquired from an application, may be acquired from various files included in an execution file of the application, or the network system 10. (For example, a service provided by an application vendor or other organization) or may be incorporated in the management server 100.
- FIG. 9 is a diagram showing the usage status table 212.
- Each row of the usage status table 212 has an application ID 901, an execution environment 902, and the number of users 903, and corresponds to one application used in the network system 10.
- the application ID 901 is information that uniquely identifies an application used in the network system 10, and specifically, for example, is the same value as the value of the ID 801 in the characteristic table 211 described with reference to FIG.
- the execution environment 902 is information representing the execution environment of the application.
- the type of value stored as the execution environment 902 is the same as the execution environment 604 of the inventory table 418 in FIG.
- the number of users 903 is information indicating the number of users using the same application in the network system 10. Specifically, the number of users 903 is, for example, the number of identical information sets included in information collected from all the clients 102.
- the information set here is a combination of the application name 602, version 603, and execution environment 604.
- FIG. 10 is a diagram showing the evaluation formula table 214.
- Each row of the evaluation expression table 214 has an execution environment 1001, convenience 1002, security 1003, and operation cost 1004, and corresponds to one execution environment.
- the execution environment 1001 is information representing the execution environment of the application.
- the types of values stored as the execution environment 1001 are the same as the execution environment 604 of the inventory table 418 in FIG.
- the convenience 1002, security 1003, and operation cost 1004 are evaluation formulas for evaluating the suitability of the application in the application execution environment represented by the execution environment 1001, respectively. At least one of the convenience 1002, security 1003, and operation cost 1004 may be information of a type different from the evaluation formula.
- Convenience 1002 is an evaluation formula prepared according to the viewpoint of the convenience of the user who uses the application.
- the convenience 1002 may be a table or column value other than those described above, a combination thereof may be an input, or a fixed value.
- values including evaluation formulas and fixed values depending on the execution environment May be set.
- a value for example, “100” indicating high suitability for the user's convenience may be set as the convenience 1002.
- a value for example, “50” indicating that the user's convenience is low may be set as the convenience 1002.
- the information related to the application support OS is used as an input of an evaluation formula for convenience 1002.
- the execution environment 1001 is “standard”, that is, when the application is a physical application, the smaller the number of clients having an OS corresponding to the support OS, the fewer users can use the application. For this reason, user convenience is low.
- the execution environment 1001 is “virtual”, that is, when the application is a virtual application, the application can be executed without depending on the OS of the client. For this reason, the convenience for the user is high.
- a large value or an evaluation formula that calculates a large value
- a small value or an evaluation formula that calculates a small value
- the security 1003 is an evaluation formula prepared according to the viewpoint of the security level of the entire network system 10.
- “$ Patch release count @ characteristic table” in the figure indicates that the value of the patch release count 804 of the characteristic table 211 is set, and “$ user count @ use status table” It represents that the value of the number of users 903 is set.
- “Min (A, B)” represents the smaller value of A and B.
- the security 1003 may be input from a column of another table, a combination thereof, or a fixed value.
- a large value may be set as the security 1003 when the security risk is high, and a small value may be set as the security 1003 when the security risk is low.
- the security 1003 may be an expression or a value based on at least one of the number of application patch publications and the number of users of the application.
- the number of times that an application patch is disclosed is input to the security 1003 evaluation formula. It can be determined that the more frequently the patches are published, the more security vulnerabilities are found and the higher the security risk.
- the execution environment 1001 is “standard”, an application is installed in each client. Therefore, it can be determined that the security risk is higher as the number of users is larger (in this case, the security evaluation value is lower).
- the execution environment 1001 is “virtual”, the application is solely managed by the application server 101, and patches are applied as necessary. Therefore, it can be determined that the security risk is low.
- a large value or an evaluation formula that calculates a large value
- a small value or an evaluation formula that calculates a small value
- the operation cost 1004 is an evaluation formula according to the viewpoint of the cost (operation cost) necessary for operation management of the network system 10.
- the “$ user count @ usage status table” in the figure represents the user count 903 in the usage status table 212.
- the operation cost 1004 may be input from a column of another table, a combination thereof, or a fixed value.
- the man-hours related to operation management work such as daily security checks performed by the administrator are input to the evaluation formula. Assuming that the number of man-hours required for operation management work per application is 0.01 man-days, when the execution environment 1001 is “standard”, man-hours proportional to the number of users are required (that is, the operation cost tends to increase). ). On the other hand, when the execution environment 1001 is “virtual”, since the application is only managed by the application server 101, only the man-hour for one application is necessary (that is, the operation cost can be easily reduced). In this embodiment, when the operation cost is high, a large value (or an evaluation formula that calculates a large value) may be set as the operation cost 1004. When the operation cost is low, a small value (or an evaluation formula that calculates a small value) may be set as the operation cost 1004.
- a value calculated according to an evaluation formula of a certain evaluation viewpoint represents suitability (evaluation value) according to the certain evaluation viewpoint of the application execution environment.
- evaluation viewpoints examples of convenience, security, and operation costs are illustrated as evaluation viewpoints, but other evaluation viewpoints may be adopted, and the evaluation viewpoint may be made finer.
- the suitability of the application is a numerical value calculated from the evaluation formula, it can be a character string or a symbol representing the suitability.
- FIG. 11 is a diagram showing the normalization formula table 215.
- Each row of the normalization expression table 215 has an evaluation viewpoint 1101 and a normalization expression 1102 and corresponds to one evaluation viewpoint.
- the evaluation viewpoint 1101 is information representing an evaluation viewpoint in operation management.
- “convenience”, “security”, and “operation cost” are set as the evaluation viewpoint 1101.
- the normalization expression 1102 is an expression for correcting the value calculated from each evaluation expression in the evaluation expression table 214 to a range of 0 to 100.
- the convenience for the user when the value after correction is close to 0, the convenience for the user is low, and when the value after correction is close to 100, the convenience for the user is high.
- security when the value after correction is close to 0, the security level of the entire network system 10 is low, and when the value after correction is close to 100, the security level of the entire network system 10 is high.
- the operating cost when the corrected value is close to 0, the operating cost is high, and when the corrected value is close to 100, the operating cost is low.
- the evaluation policy 213 includes the evaluation expression table 214 and the normalization expression table 215, but the evaluation expression table 214 and the normalization expression table 215 may be configured as one table.
- the evaluation policy 213 may be previously stored in the management server 100, may be input from the administrator, or may be provided from outside the network system 10 as in the characteristic table 211. Further, the management server 100 may have evaluation formula candidates, and one or a combination thereof may be input as the evaluation policy 213 by the administrator.
- FIG. 12 is a diagram showing the aptitude evaluation table 216.
- Each row of the aptitude evaluation table 216 has an application ID 1201, an execution environment 1202, convenience 1203, security 1204, and an operation cost 1205, and corresponds to one application used in the network system 10.
- Application ID 1201 is information for uniquely identifying an application used in the network system 10, and specifically, for example, is the same value as the value of ID 801 in the characteristic table 211.
- the execution environment 1202 is information representing the execution environment of the application.
- the type of value set as the execution environment 1202 is the same as the execution environment 604 of the inventory table 418 in FIG.
- the convenience 1203, security 1204, and operation cost 1205 are values calculated by the aptitude evaluation program 208 based on the evaluation policy 213, respectively.
- the convenience 1203 included in the line including the application ID “1” and the execution environment “standard” is an evaluation formula of the convenience 1002 included in the line including the execution environment “standard” (the evaluation formula in the evaluation formula table 214).
- a normalization expression of the normalization expression 1102 included in the line including the evaluation viewpoint “convenience”. The same applies to the security 1204 and the operation cost 1205.
- evaluation values for all application execution environments are stored for each application.
- the evaluation value is an evaluation value for each evaluation viewpoint.
- FIG. 13 is a diagram showing the effect evaluation table 217.
- Each row of the effect evaluation table 217 has an application ID 1301, a pre-change 1302, a post-change 1303, a convenience 1304, a security 1305, and an operation cost 1306, and corresponds to the application execution environment change candidate. Yes.
- the application ID 1301 is information for uniquely identifying an application used in the network system 10, and specifically, for example, is the same value as the value of ID 801 in the characteristic table 211.
- the pre-change 1302 is information (for example, a character string) indicating the current execution environment of the application.
- the value set as the pre-change 1302 is the same as the execution environment 604 of the inventory table 418 in FIG.
- the post-change 1303 is information representing the execution environment after the application is changed. Similar to the pre-change 1302, “standard” or “virtual” is set as the post-change 1303. However, in the same row, the post-change 1303 and the pre-change 1302 do not have the same value. This is because the application execution environment is not changed when the same value is reached.
- Convenience 1304, security 1305, and operation cost 1306 are values representing the effects in each evaluation viewpoint when the execution environment of the application is changed from the execution environment represented by the pre-change 1302 to the execution environment represented by the post-change 1303, respectively. It is.
- the difference between the operation costs 1205 is calculated as the effect of changing the execution environment.
- a numerical value from ⁇ 100 to +100 is set as the difference. The closer the difference is to ⁇ 100, the lower the effect of the change, and the closer the difference is to +100, the higher the effect of the change.
- FIG. 14 is a diagram showing the evaluation viewpoint priority table 219.
- Each row of the evaluation viewpoint priority table 219 has an evaluation viewpoint 1401 and a priority 1402 and corresponds to one evaluation viewpoint.
- Evaluation viewpoint 1401 is information representing an evaluation viewpoint in terms of operation management.
- the evaluation viewpoint 1401 any one of “convenience”, “security”, and “operation cost” is set.
- the priority 1402 is information (typically a numerical value) representing the priority of the evaluation viewpoint.
- the priority 1402 is used as a coefficient for weighting each evaluation viewpoint when calculating the priority order of the application whose execution environment is to be changed.
- a high priority 1402 is set for an evaluation viewpoint with a high priority
- a low priority 1402 is set for an evaluation viewpoint with a low priority. If the administrator or the network system 10 has different viewpoints that are important for operation management, the priority 1402 is set, so that the application priority order (the target of the execution environment to be changed) that matches the operation policy of the network system 10 is set.
- Application priority can be calculated. For example, in the network system 10 in which security is particularly important, the value of the priority 1402 corresponding to the evaluation viewpoint “security” may be higher than the value of the priority 1402 corresponding to the other evaluation viewpoints 1401.
- the administrator sets the priority 1402 via the operation management policy setting screen 2200 described in FIG.
- the priority is set to “high”
- “3” is set as the priority 1402.
- 2 is set for “medium” and 1 for “low”.
- FIG. 15 is a diagram showing the change priority order table 220.
- Each row of the change priority table 220 has a priority 1501, an application ID 1502, a pre-change 1503, and a post-change 1504, and corresponds to a candidate for changing the execution environment of the application.
- the priority 1501 is set with a numerical value indicating the priority of the application that changes the execution environment. 1 is the highest priority, and the lower the priority, the larger the set numerical value.
- Application ID 1502 is information for uniquely identifying an application used in the network system 10, and specifically, for example, the same value as the value of ID 801 in the characteristic table 211 is set.
- the pre-change 1503 is information representing the current execution environment of the application.
- the type of value to be set is the same as the type of execution environment 604 in the inventory table 418 in FIG.
- the changed 1504 is information representing the execution environment after changing the application. As with the pre-change 1503, “standard” or “virtual” is set. In one row, the value of 1504 after change and the value of 1503 before change are not the same.
- FIG. 16 is a diagram illustrating the client list table 221.
- Each row of the client list table 221 has a host name 1601, an IP address 1602, and an OS 1603, and corresponds to one client 102.
- the host name 1601 is information indicating the name of the client 102.
- the IP address 1602 is information for uniquely identifying the client 102 in the network system 10.
- the value of the IP address 1602 is used when communicating with the client 102.
- the IP address of the client 102 is set as the IP address 1602.
- the OS 1603 is information representing the OS of the client 102.
- FIG. 17 is a diagram illustrating a processing procedure of the collection program 207.
- the collection program 207 acquires a list of applications and application usage histories used by each client 102 from all clients, and updates the usage status table 212.
- the program 207 deletes all the rows in the usage status table 212 (step 1701).
- the program 207 repeats the following steps 1703 to 1707 for each row of the client list table 221 (step 1702).
- the program 207 acquires the inventory table 418 (specifically, all information stored in the table 418) of the target client 102 from the agent program 407 of the target client 102 ( Step 1703).
- the “target client 102” referred to here is the client 102 having the IP address 1602 in the current processing target row (row in the table 221).
- the program 207 obtains the usage history table 419 (specifically, all information stored in the table 419) of the target client 102 from the agent program 407 of the target client 102. .
- the program 207 stores the inventory table 418 acquired in step 1703 and the usage history table 419 acquired in step 1704 in the main storage device 201.
- Step 1705 The program 207 repeats Step 1706 for each row of the inventory table 418 acquired in Step 1703.
- Step 1706 For example, the value of application name 602 is “application name 17a”, the value of version 603 is “version 17a”, and the value of execution environment 604 is “ It is assumed that the execution environment 17a ".
- the program 207 stores application information in the main storage device 201. Specifically, the program 207 stores an application name “application name 17a”, a version “version 17a”, an execution environment “execution environment 17a”, and the number of users “1”. If a combination that matches the combination of the application name, version, and execution environment is already stored in the main storage device 201 in step 1706, the program 207 stores the combination in the main storage device 201 corresponding to the combination. 1 is added to the value of the number of stored users.
- Step 1707 When the program 207 has processed all the rows in the inventory table 418 acquired in Step 1703, the program 207 proceeds to the next step (Step 1707).
- step 1708 the program 207 repeats step 1702 to step 1704 for all rows in the client list table 211.
- step 1710 for each application information stored in the main storage device 201 in step 1706 (step 1709).
- Step 1710 For example, in the information of the application currently being processed, the application name is “application name 17b”, the version is “version 17b”, the execution environment is “execution environment 17b”, and the number of users is “number of users 17b”.
- the program 207 acquires the value “ID17” of the ID 801 in the row where the value of the application name 802 matches “application name 17b” and the value of version 803 matches “version 17b” from the characteristic table 211, Thereafter, a new line is registered in the usage status table 212. In the new row, “ID17” is set as the application ID 901, “execution environment 17b” is set as the execution environment 902, and “user number 17b” is set as the number of users 903.
- step 1711 When processing has been performed for all application information stored in the main storage device 201 in step 1706, the processing of the program 207 ends (step 1711).
- FIG. 18 is a diagram showing the processing procedure of the aptitude evaluation program 208.
- the aptitude evaluation program 208 calculates the aptitude of the application in each execution environment based on the characteristic table 211, the usage status table 212, and the evaluation policy 213, and updates the aptitude evaluation table 216.
- the aptitude evaluation program 208 repeats step 1802 to step 1808 for each row of the evaluation formula table 214 (step 1801).
- Step 1802 For example, it is assumed that the value of the execution environment 1001 in the currently processed row (the row in the table 214) is “execution environment 18”.
- the program 208 repeats step 1803 to step 1807 for each column (convenience 1002, security 1003, operation cost 1004) representing the evaluation viewpoint in the currently processed row (step 1802).
- Step 1803 For example, it is assumed that the column name currently being processed is “evaluation viewpoint 18” and the column value is “evaluation expression 18”.
- the program 208 repeats step 1804 to step 1806 for each row of the usage status table 212 (step 1803).
- Step 1804 For example, it is assumed that the application ID 901 in the currently processed row is “application ID 18”.
- the program 208 calculates “evaluation formula 18” and thereby calculates an evaluation value (step 1804).
- there may be a character string for example, “$ support OS @ characteristic table”) indicated by “$ ⁇ column name> @ ⁇ table name>” in “evaluation formula 18”.
- ⁇ table name> is either a “characteristic table” or a “usage status table”.
- ⁇ table name> is “characteristic table”
- the value of the column in which the column name matches ⁇ column name> is “ $ ⁇ Column name> @ ⁇ table name> ”.
- usage status table 212 a row where the application ID 901 matches “application ID 18” is selected, and the column name matches the ⁇ column name>. Is replaced with “$ ⁇ column name> @ ⁇ table name>”. Further, the character string indicated by “NUM (@ ⁇ table name>)” is replaced with the number of rows in the table of ⁇ table name>.
- Step 1805 The program 208 calculates the normalization expression 1102 in the line where the value of the evaluation viewpoint 1101 matches the “evaluation viewpoint 18” in the normalization expression table 215, thereby calculating the value (step 1805). At this time, since there is a character string (for example, “$ convenience”) indicated by “$ ⁇ evaluation viewpoint>” in the normalization formula, the evaluation value calculated in step 1804 is replaced.
- Step 1806 The program 208 selects, from the aptitude evaluation table 216, a row in which the application ID 1201 matches “application ID 18” and the execution environment 1202 matches “execution environment 18”.
- the value calculated in step 1805 is set as the value of the column whose name matches “evaluation viewpoint 18”. If there is no corresponding line, the program 208 registers a new line. In a new row, “application ID 18” is set as the application ID 1201, and “execution environment 18” is set as the execution environment 1202.
- step 1807 When the program 208 has processed all the rows in the usage status table 212, the program 208 proceeds to the next step (step 1807).
- step 1808 When the program 208 has processed all columns (convenience 1002, security 1003, operation cost 1004) representing the evaluation viewpoint in the current processing target row of the evaluation formula table 214, the program 208 proceeds to the next step (step 1808).
- step 1809 If all rows in the evaluation expression table 214 have been processed, the processing of the aptitude evaluation program 208 ends (step 1809).
- FIG. 19 is a diagram illustrating a processing procedure of the effect evaluation program 209.
- the effect evaluation program 209 calculates the effect when the application execution environment is changed based on the aptitude evaluation table 216, and updates the effect evaluation table 217.
- the program 209 repeats Step 1902 to Step 1908 for each row of the usage status table 212 (Step 1901).
- Step 1902 For example, it is assumed that the application ID 901 in the currently processed row (row in the table 212) is “application ID 19” and the execution environment 902 is “execution environment 19a”.
- the program 209 selects, from the suitability evaluation table 216, a row in which the application ID 1201 matches “application ID 19” and the execution environment 1202 matches “execution environment 19a”.
- the value of (convenience 1203, security 1204, operation cost 1205) is acquired. It is assumed that the value of the acquired convenience 1203 is “convenience 19a”, the value of the security 1204 is “security 19a”, and the value of the operation cost 1205 is “operation cost 19a”.
- Step 1903 The program 209 repeats from Step 1904 to Step 1907 for each row in the suitability evaluation table 216 where the application ID 1201 matches the “application ID 19” and the execution environment 1202 does not match the “execution environment 19a”.
- Step 1904 For example, the execution environment 902 in the current processing target row (row in the table 216) is “execution environment 19b”, convenience 1203 is “convenience 19b”, and security 1204 is “security 19b”. It is assumed that the operation cost 1205 is “operation cost 19b”.
- the program 209 repeats Step 1905 for each column (convenience 1203, security 1204, operation cost 1205) representing the evaluation viewpoint in the currently processed row.
- Step 1905 The program 209 subtracts the value acquired in Step 1902 from the value of the current processing target column, and calculates the difference between the values in the “execution environment 19a” and “execution environment 19b”. Specifically, for example, the program 209 includes a difference between “convenience 19a” and “convenience 19b”, a difference between “security 19a” and “security 19b”, and “operation cost 19a” and “operation cost”. 19b "is calculated.
- Step 1906 In the effect evaluation table 217, the program 209 matches the application ID 1301 with “application ID 19”, the pre-change 1302 with “execution environment 19a”, and the post-change 1303 with “execution environment 19b”. Select matching rows.
- the program 209 sets the value calculated in step 1905 to the column whose column name matches the name of the column currently being processed in the selected row. If there is no corresponding line, the program 209 registers a new line. In the new line, “application ID 19” is set as the application ID 1301, “execution environment 19a” is set as the pre-change 1302, and “execution environment 19b” is set as the post-change 1303.
- step 1907 When the program 209 has processed all the columns representing the evaluation viewpoints in the current processing target row of the suitability evaluation table 216, the program 209 proceeds to the next step (step 1907).
- the program 209 moves to the next step when the application ID 1201 matches “application ID 19” and the execution environment 1202 does not match “execution environment 19a” in the suitability evaluation table 216. (Step 1908).
- FIG. 20 is a diagram illustrating a processing procedure of the priority order calculation program 210.
- the priority order calculation program 210 calculates the priority order of the application whose execution environment is changed based on the effect evaluation table 217 and the operation management policy 218, and updates the change priority order table.
- the program 210 acquires the priority of the evaluation viewpoint from the evaluation viewpoint priority table 219 (step 2001).
- the program 210 calculates the ratio of the priority of each evaluation viewpoint to the sum of the priority of the evaluation viewpoint acquired in Step 2001 (Step 2002).
- “3” is set as “operation cost”
- “2” is set as “security”
- “1” is set as “convenience”. Therefore, the priority ratio of “operation cost” to the sum of priority is “0.5”, the priority ratio of “security” is “0.33”, and the priority ratio of “convenience” is “0.17”.
- the program 210 repeats step 2004 for each row of the effect evaluation table 217 (step 2003).
- Step 2004 The program 210 calculates the column value and the step 2002 for each column (convenience 1304, security 1305, operation cost 1306) indicating the evaluation viewpoint in the currently processed row (row in the table 217).
- the sum of the results of multiplication for each column is calculated.
- the value of convenience 1304 is “13”
- the value of security 1305 is “24”
- the value of operation cost 1306 is “66”.
- the calculated value is 13 ⁇ 0.17 + 24 ⁇ 0.33 + 66 ⁇ 0.5 ⁇ 43.
- the program 210 stores in the main storage device 201 the information on the current processing target row and the value calculated in step 2004.
- step 2005 When the program 210 executes the process for all the rows in the effect evaluation table 217, the program 210 proceeds to the next step (step 2005).
- the program 210 stores the information of each row stored in the main storage device 201 in step 2004 in the change priority table 220 (step 2006). At that time, the program 210 performs the order of the rows to be processed in descending order of the values (calculated values) stored in the main storage device 201 in step 2004. If the value of the application ID 1301 in the current processing target row is “application ID 20”, the value of the pre-change 1302 is “pre-change 20”, and the value of the post-change 1303 is “post-change 20”, the program 210 "Application ID 20" is set as the application ID 1502, "Before change 20” is set as the before change 1503, and "After change 20” is set as the changed 1504. As the priority order 1501, “1” is set in the first row, and a value obtained by adding 1 in order is set in the subsequent rows.
- the priority order calculation method is not limited to the above example.
- the evaluation priority set in the effect evaluation table 217 may be stored in the change priority table 220 in descending order.
- priority may be calculated and stored in the table 220 instead of consecutive numbers called priority.
- the value calculated in step 2004 may be adopted as the priority of the application.
- FIG. 21 is a diagram illustrating a processing procedure of the data update program 223.
- the data update program 223 updates information such as an application held by the management server 100 when the update button 2205 is pressed in the priority order list screen 2200 described in FIG.
- the program 223 calls the collection program 207 (step 2101).
- the program 223 calls the aptitude evaluation program 208 (step 2102).
- the program 223 calls the effect evaluation program 209 (step 2103).
- the program 223 calls the priority calculation program 210 (step 2104).
- the data update program 223 is executed when the update button 2205 is pressed.
- other triggers such as a method that the management server 100 periodically executes may be adopted.
- FIG. 22 is a diagram showing a priority order list screen 2200.
- the priority order list screen 2200 is a screen for displaying applications whose execution environment can be changed according to the priority order calculated by the priority order calculation program 210.
- the screen 2200 is displayed on the display device 206 by the screen control program 222.
- an application name 2201, an effect 2203 due to a change in the execution environment, and an execution environment 2204 are displayed. Rows including the items 2201, 2203, and 2204 are displayed in order of descending application priority. If the priority order of the application is known, it may be displayed by another method.
- Application name 2201 is a value acquired from the application name 802 in the characteristic table 211.
- the priority order 2202 indicates that the higher the priority of the execution environment change is, the lower the priority of the change is for the lower priority application. That is, the order of applications to be displayed is determined based on the priority 1501 of the change priority table 220.
- the effect 2203 by changing the execution environment represents the effect by changing the execution environment for each evaluation point in terms of operation management.
- the effect is displayed with arrows so that it can be grasped visually and intuitively. The more the arrow is upward (the closer the angle of the arrow is to 90 degrees), the higher the effect of the change, and the closer the arrow is to the horizontal (the closer the angle of the arrow is to 0 degree), the less effective the change. ing.
- the direction (angle) of the arrow for each evaluation viewpoint is determined based on the evaluation value in each evaluation viewpoint in the effect evaluation table 217. Instead of or in addition to the arrow, a numerical value (for example, an evaluation value from each evaluation viewpoint in the effect evaluation table 217) may be displayed.
- the execution environment 2204 represents the execution environment before the change (that is, the execution environment of the current application) and the execution environment after the change.
- the update button 2205 is a button for updating the display content of the screen.
- the administrator presses an update button 2205 to collect information from the client again and update the priority information.
- the data update program 223 of the management server 100 is called by the screen control program 222, for example.
- FIG. 23 is a diagram showing an operation management policy setting screen 2300.
- the operation management policy setting screen 2300 is a screen for setting the priority of each evaluation viewpoint.
- the operation management policy setting screen 2300 is displayed on the display device 206 by the screen control program 222.
- a priority desired by the administrator is selected from among a plurality of priorities included in the priority 2304.
- the setting button 2305 is a button for reflecting the priority selected for each evaluation viewpoint in the evaluation viewpoint priority table 219.
- “3” is set as the priority 1402 of the table 219, and when “medium” is selected, “2” is set, and “low”.
- “1” is set.
- FIG. 24 is a diagram showing an application information registration screen 2400.
- Application information registration screen 2400 is a screen for registering information representing the characteristics of an application in management server 100.
- the application name, version, patch release count, and support OS are input to the application name input field 2401, the version input field 2402, the patch release count input field 2403, and the support OS input field 2404, respectively.
- the registration button 2405 is pressed, the input information is stored in the characteristic table 211.
- the registered application list 2406 represents a list of information related to already registered applications.
- the information included in the list 2406 is the same as the information stored in the characteristic table 211.
- the list 2406 may not have all the information stored in the characteristic table 211 (for example, it may not have information on some items).
- the information used as the input of the evaluation formula can be variously changed in addition to the information shown in the present embodiment.
- the example of the input information of an evaluation formula is shown for every evaluation viewpoint on each operation management.
- (A) Convenience (a1) Application version When there are many types of application versions and there is no compatibility between different versions, the data exchanged between users cannot be handled or the behavior of the application changes. In this case, it is considered that user convenience is impaired.
- a virtual application that can execute a plurality of different versions on the same client 102 is more suitable.
- the version of the application is stored in the characteristic table 211.
- the aptitude evaluation program 208 Based on the evaluation policy 213, the aptitude evaluation program 208 has high aptitude in the virtual environment for an application having the same application name and having many types of versions (for example, an application having more than a predetermined number of version types). It is judged that the environmental suitability is low.
- the aptitude evaluation program 208 can determine that the aptitude in the virtual environment is higher.
- the number of users for each version is stored in the usage status table 212 as described with reference to FIG. (A2)
- Use of shared library When an application uses a shared library, it may conflict with a shared library used by another application, and the application cannot be executed. It is done. As such an application, a virtual application that can execute the application without being aware of the conflict of the shared library is more suitable.
- the presence or absence of the shared library may be stored in the characteristic table 211.
- the table 211 may store specific names of shared libraries.
- the aptitude evaluation program 208 determines that aptitude as a virtual application is high and aptitude as a physical application is low.
- A3 Introduction time In the case of a physical application, the user can install it on the client 102 himself / herself, but for a virtual application, it takes time for the administrator to create a virtual application and start providing it to the client 102 It becomes.
- the value representing the introduction time may be set in the evaluation policy 213 as a fixed value depending on the execution environment. Based on the evaluation policy 213, the aptitude evaluation program 208 determines that an application with a short introduction time has low aptitude in the virtual environment, and an application with a long introduction time has high aptitude in the virtual environment.
- a security risk increases when the application of the patch is delayed.
- the patch application frequency is lower than that of a virtual application that is uniquely managed by the application server 101.
- the value representing the patch application frequency may be set in the evaluation policy 213 as a fixed value depending on the execution environment. For example, once / month for a physical application, once / week for a virtual application. Based on the evaluation policy 213, the aptitude evaluation program 208 determines that an application with a high patch application frequency has high aptitude in the virtual environment.
- the patch application frequency tends to decrease as the number of users increases. Therefore, the aptitude evaluation program 208 determines that an application with a large number of users has low aptitude in the physical environment. You can also.
- the number of application users is stored in the usage status table 212 as described with reference to FIG.
- (C) Operation cost (c1) Man-hours for introduction An application that requires more work to introduce an application has a higher cost. In the case of a physical application, the user can install it on the client 102 by himself / herself. However, in the case of a virtual application, there is a work cost for creating a virtual application by an administrator. Further, in the case of a virtual application, since the procedure for making a virtual application differs depending on the application, the number of man-hours for introduction can vary depending on the application. The value representing the introduction man-hour may be set in the evaluation policy 213 as a fixed value depending on the embodiment. In addition, the difference in introduction man-hours for each application may be stored in the characteristic table 211. Based on the evaluation policy 213, the aptitude evaluation program 208 can determine that an application with a small introduction man-hour (for example, an application with an introduction man-hour lower than a predetermined value) has high aptitude in the virtual environment.
- a small introduction man-hour for example, an application with an introduction man-hour lower than
- the storage destination of the value prepared according to the above-described modification is illustrated, but the storage destination of the value is not limited to the above description.
- a value representing the introduction time may be set in another information.
- the second embodiment is an embodiment relating to a network system in which a host-type virtual environment exists.
- the client executes the application remotely on the application server.
- FIG. 25 is a diagram showing a configuration of the application server 2501 in the present embodiment.
- the application server 2501 in the second embodiment is different from the first embodiment in that the application is not distributed to the client 102 but is executed on the OS of the application server 101, and the screen information is transmitted to the client 102. It is in the point of transmitting and receiving. Therefore, the configuration of programs and data stored in the disk device 2504 is different.
- the disk device 2504 is a storage device similar to the disk device 304 of the first embodiment, and stores an application execution program 310, a screen information transmission / reception program 311, an application 312A, and an application 312B.
- the application 312A may be a physical application or a virtual application according to a streaming-type application virtualization technology.
- the application 312B is a physical application or a virtual application like the application 312A.
- the application has two configurations, that is, the application 312A and the application 312B, but the present invention can be applied to one configuration or three or more configurations.
- the application execution program 310 is a program for executing the application 312A or the application 312B, and transmits an execution result to the screen information transmission / reception program 311. Also, the client 102 receives a request from the screen information transmission / reception program 311 that has received input information (hereinafter referred to as input information) for screen operation using an input device (for example, a mouse or a keyboard), and is similar to the operation at the client 102. To operate the application.
- input information input information
- the screen information transmission program 311 receives input information from the client 102 and transmits a screen (hereinafter referred to as response information) of the execution result of the application to the client 102.
- the screen information transmission / reception program 306 serves as an interface with the client group, but the screen information transmission / reception program 306 and the application execution program 305 may be integrated.
- the screen information transmission / reception program 306 and / or the application execution program 305 may also have an access control function that restricts client access, a log management function that stores client access history, and the like.
- FIG. 25 is a diagram showing an outline of the present embodiment.
- the application is abbreviated as “AP”, and the physical application is abbreviated as “PAP”.
- the application execution program 311 of the application server 101 executes the application, and the screen information transmission / reception program 310 transmits the response information of the application to the client program 408 of the client 102.
- FIG. 27 is a diagram showing a usage history table 2601.
- FIG. 7 is different from the first embodiment described in FIG. 7 in that a network state 704 is added.
- the network status 704 is set with information indicating the network status of the client 102 when the application is used. “Online” is set as the network state 704 if the network is connected while the application is being executed, and “offline” is set as the network state 704 if the network is not connected while the application is being executed. Is set.
- the network status 704 can be acquired and set from a program that is normally installed in the OS, for example, to check the network connection status.
- FIG. 28 is a diagram showing a usage status table 2612.
- each row of the table 2612 has an offline usage rate 904.
- the offline usage rate 904 is a numerical value indicating the ratio of the state in which the network is disconnected when the application is used.
- a numerical value indicating the ratio of rows in which the network state 704 is “offline” with respect to the application usage history stored in the usage history table 411 of all clients 102 is set as the offline usage rate 904.
- the offline usage rate 904 of the row with the application ID 901 of “4” is “0.30”. This is because 30% of the execution of the application with the application ID 901 of “4” It means that it was done in the state where it was disconnected from.
- FIG. 29 is a diagram showing an evaluation formula table 2914.
- the network state of the client at the time of executing the application is used as an input for the evaluation formula.
- the execution environment 1001 is “virtual”, that is, when an application is executed on the application server 101, “0” is set as convenience 1002 because it cannot be used offline.
- the convenience 1002 is set such that an application with a higher offline usage rate has a higher convenience evaluation value.
- the aptitude evaluation program 208 determines that a physical application that can be used without depending on the network state is more convenient for the user.
- the network state is not input as an evaluation expression, but in this embodiment, the network state is input.
- the information that becomes the input of the evaluation formula can also change.
- FIG. 30 is a diagram showing an aptitude evaluation table 3016.
- the difference from the first embodiment described with reference to FIG. 12 is that, as described with reference to FIG. 28, in the usage status table 2612, the offline usage rate of the row whose application ID 901 is “1”, “2”, or “3”. Since the value of 904 is “0”, the value of the convenience 1203 in the row where the value of the application ID 1201 is “1”, “2” or “3” in this table 3016 is “0”. It is a point. On the other hand, the value of the convenience 1203 of the row where the value of the application ID 1201 matches “4” and the value of the execution environment 1202 matches “standard” is “30”. This indicates that the application with the application ID 1201 value of “4” has a tendency to be used offline, so that the physical application is more suitable in terms of user convenience.
- FIG. 31 is a diagram showing an effect evaluation table 3117.
- the value of the convenience 1304 in the row where the value of the application ID 1301 is “1”, “2” or “3” is “0”, and the application ID 1301
- the value of convenience 1304 in the row where the value is “4” is “ ⁇ 30”. This is because an application whose application ID 1301 is “4” tends to be used offline, and therefore, from the viewpoint of user convenience, the physical application is more suitable, and the effect of changing to the virtual application is low. It represents that.
- the value “ ⁇ 30” is the value “0” for “virtual” in the table 3016 in FIG. 30 to the value “standard” in the table 3016 in FIG. 30 for the application with the application ID “4”. This is a value obtained by subtracting 30 ”.
- FIG. 32 is a diagram showing a change priority table 3220.
- the values of the application IDs 1502 in the rows with the priority order 1501 of “3” and “4” are interchanged due to the difference from the first embodiment described in FIG. This means that the application ID 1502 “4” has a lower priority for changing the execution environment because the current execution environment is more suitable from the viewpoint of user convenience.
- FIG. 33 is a diagram showing the processing procedure of the collection program 3307.
- step 17 is different from the first embodiment described in FIG. 17 in step 1712, step 1706, and step 1710.
- the collection program 3307 calculates the total number of executions of each application and the number of executions when offline from the usage history table 2601 acquired in step 1704.
- the specific processing procedure is as follows. Hereinafter, it is assumed that the ID 601 in the row of the inventory table 418 selected in step 1705 is “ID33”.
- the collection program 3307 counts the number of rows in which the value of the application ID 701 is “ID33” in the usage history table 419 acquired in step 1704. Assume that the count value is “total execution count 33a”. Of these rows, the collection program 3307 counts the number of rows in which the value of the network status 704 is “offline”. Assume that the count value is “offline execution count 33a”.
- the collection program 3307 stores application information in the main storage device 201 (step 1706).
- the total number of executions and the number of offline executions are stored. It is assumed that the stored total execution count is “total execution count 33” and the stored offline execution count is “offline execution count 33”. If, in step 1706, information on an application having the same application name, version, and execution environment is already stored in the main storage device 201, “total execution count 33a” is added to the stored total execution count value. The "offline execution count 33a" is added to the stored offline execution count.
- total number of executions is “total number of executions 33b” and the number of offline executions is “offline execution number 33b” in the information of the current processing target application selected in step 1709.
- step 1710 the collection program 3307 registers a new line in the usage status table 212.
- a value obtained by dividing “offline execution count 33b” by “total execution count 33b” is set as the offline usage rate 904.
- the information used as the input of the evaluation formula can be variously changed in addition to the information shown in this embodiment.
- the example of the input information of an evaluation formula is shown for every evaluation viewpoint on each operation management.
- (D) Convenience Application processing performance in the execution environment When the application processing performance in the execution environment is less than the processing performance required by the application, user convenience is impaired.
- the “application processing performance in the execution environment” is the processing performance of the client 102 in the case of a physical application, and the processing performance of the application server 2501 in the case of a virtual application.
- the processing performance represents the ability of a computer that executes an application (for example, the capacity of a CPU or a main storage device). Specifically, for example, in the case of a CPU, it can be expressed as “2.0 GHz”.
- the processing performance value requested by the application may be stored in the characteristic table 211.
- the processing performance of the client 102 may be set in the evaluation policy 213 as a fixed value common to the client 102, or may be stored in the client list table 221 as a value for each client 102.
- the agent program 407 of the client 102 collects processing performance information of the client 102 using a standard program installed in the OS, and the collection program 3307 starts from the agent program 407 of each client 102. The information may be acquired.
- the processing performance of the application server 2501 may be set in the evaluation policy 213 as a fixed value depending on the execution environment. Information may be acquired from the application server 2501.
- the aptitude evaluation program 208 compares the processing performance required by the application with the application processing performance in the execution environment based on the evaluation policy 213. If the processing performance required by the application is satisfied, the aptitude evaluation program 208 has high aptitude. If not, it may be judged that the suitability is low.
- D2 Application concurrency Even when it is preferable to execute the application on the server, the method of installing the physical application on the server is not recommended for simultaneous execution by multiple users. Since the user cannot use it simultaneously, the convenience for the user is low.
- the concurrency of applications may be stored in the characteristic table 211. Further, whether or not the application server 2501 has a function corresponding to an application that is not assumed to be executed simultaneously may be set in the evaluation policy 213 as a value depending on the execution environment. Based on the evaluation policy 213, the aptitude evaluation program 208 is a virtual application when the application does not have simultaneous executability and the application server 2501 has the above function (a function corresponding to an application that does not assume simultaneous execution). It can be judged that the aptitude of the is high.
- (E) Security (e1) Data storage environment
- an application handles some confidential information as data, if the data is distributed to clients (especially mobile terminals such as notebook PCs), the security risk is high. it is conceivable that. It is considered that such an application is more centrally managed by the application server 2501.
- the value of the data storage environment may be set in the evaluation policy 213 as a value depending on the application usage method. For example, a value that determines that the suitability as the physical application is low and the suitability as the virtual application is high may be set as the value of the data storage environment. Further, whether or not the application handles confidential information as data differs depending on the application, and therefore whether or not the handled data is confidential may be stored in the characteristic table 211.
- the storage destination of the value prepared according to the above-described modification is illustrated, but the storage destination of the value is not limited to the above description.
- the processing performance value requested by the application may be set in another information instead of the characteristic table 211.
- the network system 2610 having the host type virtual environment has been described.
- the network system 2610 may include a streaming type virtual environment. That is, the first embodiment and the second embodiment may be combined.
- the usage history table 2601 and the usage status table 2612 can be used for evaluating the suitability of the application execution environment in a network system in which a streaming type virtual environment and a host type virtual environment are mixed.
- the evaluation expression table is stored in the information stored in the evaluation expression table 214 shown in FIG. 10 and the evaluation expression table 2914 shown in FIG. Including both stored information.
- At least one of a plurality of examples described in the first embodiment and a plurality of examples described in the second embodiment can be employed as the “example of changing the evaluation viewpoint”.
- target application when the current execution environment is “virtual (streaming type)”, change from “virtual (streaming type)” to “standard”.
- target application when the current execution environment is “virtual (streaming type)”, change from “virtual (streaming type)” to “standard”.
- the aptitude evaluation system 208 calculates an evaluation value from each evaluation viewpoint for each of “standard”, “virtual (streaming type)”, and “virtual (host type)”. For each evaluation point, the effect of changing from “virtual (streaming type)” to “standard” (difference in evaluation value) and the effect of changing from “virtual (streaming type)” to “virtual (host type)” (Evaluation value difference) is calculated. This result is displayed on the priority list screen.
- the processing performance required by the application may not be satisfied by the client but may be satisfied by the application server.
- the data handled by the application is data including confidential information, and it is preferable to manage it on the application server side for security.
- the suitability of the application in each execution form is evaluated based on charging information such as a license fee determined for each application and execution environment.
- FIG. 34 is a diagram showing the billing information table 224 in the present embodiment.
- the table 224 is stored in the disk device 205 of the management server 100, for example.
- This table 224 has information relating to a license fee when using an application in each execution environment.
- each row of the table 224 has an application ID 3401, a standard 3402, and a virtual 3403, and corresponds to one application.
- Application ID 3401 is information for uniquely identifying an application used in the network system 10, and is set to the same value as the value of ID 801 in the characteristic table 211 in FIG. 8, for example.
- Standard 3402 and virtual 3403 are numerical values representing license fees in each execution environment.
- the standard 3402 is a license fee when installed on the client 102 as a physical application
- the virtual 3403 represents a license fee when installed on the application server 101 or distributed to the client 102 as a virtual application.
- the information included in the billing information table 224 is used when evaluating the operation cost in consideration of the license fee required when using the application.
- the evaluation expression for the operation cost 1004 can be expressed as follows when the execution environment 1001 is “standard” and “virtual”, and the operation cost corresponding to each execution form can be evaluated. it can.
- “$ simultaneous execution user count @ usage status table” represents the total number of users who simultaneously used the application in a certain time period.
- the usage status table 212 includes a column of “simultaneous execution user count”. Suppose that it is provided.
- the collection program 207 described in FIG. 17 calculates the maximum value of the total number of users used in the same time zone based on the information in the usage history table 419 acquired in step 1704, and calculates the maximum value as “simultaneously. It can be set as a value of “the number of execution users”.
- the license fee is taken as an example in this embodiment, other types of costs that vary depending on the application execution environment can be considered instead of or in addition to the license fee.
- a variable related to another type of cost may be included in the evaluation formula for the operation cost.
- the operation cost 1004 may be an expression or value based on at least one of the charging method for each execution environment and the number of users of the application.
- the fourth embodiment relates to a network system that uses one or more cloud systems.
- FIG. 35 is an overall configuration diagram showing this embodiment.
- a cloud system group including a cloud system A 105 and a cloud system B 106 is connected to the network system 10 via the second network 104.
- cloud system any one of the cloud system A 105 or the cloud system B 106 of the cloud system group, it is simply referred to as “cloud system”.
- the second network 104 is a communication network (for example, the Internet, LAN, or WAN) that connects the network system 10 and the cloud system group so that they can communicate with each other.
- a communication network for example, the Internet, LAN, or WAN
- the cloud system A 105 and the cloud system B 106 are systems that provide functions equivalent to the applications used in the network system 10 as services via the network.
- a service provided by the cloud system is referred to as a “cloud service”.
- the cloud system charges the network system 10 according to the usage status of the cloud service. In this embodiment, it is assumed that the user is charged according to the number of users. In the case of the cloud system A105, the monthly charge is 3000 yen per user, and in the case of the cloud system B106, the monthly charge is 7000 yen per user.
- a fixed amount charge that is fixedly charged according to the number of users as in this embodiment may be used, or charged according to the usage amount of the cloud service such as the usage time and the amount of data to be stored. Pay as you go.
- the present invention can be applied to a cloud system that does not charge.
- the operation rate varies depending on the cloud system.
- “Occupancy rate” is a value that quantitatively indicates the availability of the cloud system, and represents the ratio of the time during which the cloud system is functioning within a certain period of time. It is assumed that the operation rate of the cloud system A105 is 0.96 and the operation rate of the cloud system B105 is 0.99.
- information on the operating rate of the cloud system for example, information disclosed to users of the cloud service on the Web or the like can be used.
- the cloud system A105 has a low fee, but has low reliability in terms of availability and security
- the cloud system B106 has a high fee, but has high reliability in terms of availability and security.
- the client 102 uses the cloud service via the second network 104.
- the cloud service provides the same function as all applications used in the network system 10 with the same charging system.
- the application and charging system provided by the cloud service are different. May be different.
- FIG. 36 is a diagram showing a usage status table 3612 in the present embodiment.
- each row of the table 3612 has a usage rate 903.
- the usage rate 903 is a numerical value representing the ratio of the usage time of the application in all clients to the operation period of the network system 10. In other words, the usage rate 903 quantitatively represents how frequently the application is used.
- FIG. 37 is a table showing an evaluation formula table 3714 in the present embodiment.
- Cloud 10 is different from the evaluation expression table 214 described in FIG. 10 in that “cloud A” and “cloud B” are added as the execution environment 1001. “Cloud A” represents that the cloud service of the cloud system A 105 is used as an application execution environment, and “Cloud B” represents that the cloud service of the cloud system B 106 is used.
- the convenience 1002 of the execution environment “cloud A” (“cloud B”) is an evaluation formula for calculating an evaluation value according to the operating rate of the cloud system A (cloud system B) and the usage rate of the application. According to this evaluation formula, the higher the application usage rate, the lower the possibility that the cloud system is stopped when using the application. Further, according to the evaluation formulas of “Cloud A” and “Cloud B”, the operating rate of the cloud system A 105 is lower than the operating rate of the cloud system B 106, and the cloud system A stops even when the application usage rate is the same. Therefore, even if the application utilization rate is the same, it may be determined that the suitability in the cloud system A is low.
- the application usage rate can be acquired from the usage rate 903 in the usage status table 212.
- the client 102 can be used as long as the client 102 does not physically fail or a logical failure of the application occurs.
- “100” is used as the convenience 1002 of the execution environment “standard”. (For example, the highest value) is set.
- a fixed value depending on the characteristics of the cloud system is set.
- the cloud system A 105 has low security reliability
- a value indicating low aptitude is set
- the cloud system B 106 has high security reliability, and thus a value indicating high aptitude is set.
- a fixed value that depends on the cloud system is set.
- an evaluation formula that evaluates suitability according to the confidentiality of data handled by the application may be set. it can.
- the execution environment 1001 sets an evaluation formula for calculating a value according to the number of application users and the billing amount of the cloud system. This is because each cloud service is charged according to the number of users, and the operation cost varies depending on the cloud service to be used. Information related to charging for each cloud system can be registered in the charging information table 224 as described in the third embodiment, for example.
- the execution environment 1001 is “standard”, as described in the third embodiment, a charging amount per user when installing the application in the client 102 is set.
- the evaluation formula the charging amount and the number of users are set. A value obtained by multiplying can be calculated.
- This embodiment makes it possible to evaluate the execution environment in consideration of the application usage rate, cloud service operation rate, and billing system.
- the information used as the input of the evaluation formula can be variously changed in addition to the information shown in the present embodiment.
- the example of the input information of an evaluation formula is shown for every evaluation viewpoint on each operation management.
- Operational cost (F) Operational cost (f1) Network traffic volume, data volume, usage time
- the application network The suitability can be evaluated based on the amount of traffic, the amount of data to be stored, and the execution time of the application.
- the network traffic volume, data volume, and execution time of data used by the application may be stored in the usage status table 212.
- the aptitude evaluation program 208 evaluates the operation cost necessary for using the cloud service based on this information and the billing system of the cloud service. When the operation cost is high, it can be determined that the suitability of the cloud service is low.
- the present invention can be applied to other resources such as the number of servers.
- the present invention not only supports application migration between the network system 10 and the cloud system, but can also be applied to migration between cloud systems, based on the operating rate and billing system of each cloud system.
- the optimal cloud system that provides the functions of each application can be selected. In this case, information such as application usage status is acquired from the cloud system.
- the physical application installed in the client 102 is exemplified, but the present invention is also applicable to an application such as an in-house work leave system or a Web system.
- the administrator inputs characteristic information such as the required specifications of the system and allowable downtime in the characteristic table 211.
- the usage status table 212 information such as the number of users using the system and the amount of stored data can be acquired from the system and set. Thereby, it becomes possible to compare the system in the network system 10 with the system on the cloud service and make a more appropriate execution environment.
- the priority list screen is different from the priority list screen 2200 in the first to fourth embodiments.
- FIG. 38 is a diagram showing a priority order list screen 3800 in the present embodiment.
- a migration target check box 2206 and a migration button 2207 are provided.
- the migration target check box 2206 is a check box for selecting an application whose execution environment is to be changed from among the applications displayed on the priority order list screen 2200.
- a method for selecting an application a method other than using a check box may be employed (for example, a method of inputting an application ID may be employed).
- the migration button 2207 is a button for changing the execution environment of the application selected in the migration target check box 2206.
- the management server for example, an environment change program executed by the CPU in the management server
- the management server 100 automatically transfers a client application or data to the cloud service by executing a predetermined program. Thereby, for example, the transition from “standard” to “cloud environment” has been performed.
- the administrator can change the execution environment by simply referring to the priority list screen 3800 and selecting an application for changing the execution environment according to the displayed priority order. For this reason, it can be expected to reduce the cost of application migration.
- a condition for narrowing down applications to be evaluated is provided. For applications that do not meet these conditions, the suitability of the application is not evaluated.
- the condition is configured with a threshold corresponding to one or more types of application information (for example, the number of users), for example.
- FIG. 39 is a diagram illustrating the threshold value table 225 in the present embodiment.
- the table 225 is stored in, for example, the disk device of the management server, and specifically, for example, included in the evaluation policy 213.
- Each row of the table 225 has an execution environment 3901 and a conditional expression 3902, and corresponds to one execution environment.
- the execution environment 3901 is information representing the execution environment of the application.
- the set value is, for example, the same value as the execution environment 604 of the inventory table 418 in FIG.
- the conditional expression 3902 is information representing a conditional expression indicating whether or not the suitability in the application execution environment 3901 is evaluated. When the conditional expression is satisfied, the suitability of the application is evaluated, and when not satisfied, the suitability of the application is not evaluated. That is, when the condition is not satisfied, the priority order of the application to the execution environment is not displayed on the priority order list screen 2200.
- the virtualization possibility of the application when the value of the execution environment 3901 is “virtual”, the virtualization possibility of the application, the number of users, the scheduled use period, the final use time, and the presence / absence of the related application are set as conditional expressions. Applicability is evaluated only when the number of applications that can be converted to an application is 1000 or more, the application has been used in less than 6 months, and there is no linkage with another application. .
- This can be a virtual application, when the number of users is small, or when there is no cost merit by migrating a less frequently used application, or because there is an application to be linked, the execution environment is changed. If this is not possible, it indicates that there is no point in assessing suitability in the first place. Therefore, the conditional expression can be a conditional expression corresponding to an application that does not require evaluation of suitability.
- Information indicating the possibility of virtualization may be set in the characteristic table 211.
- the number of users, the last usage time, and the presence / absence of related applications may be set in the usage status table 212.
- the presence / absence of a related application can be detected by the agent program 407 of the client 102 by monitoring the communication status such as communication between processes in the client 102 and HTTP communication, and detecting the presence / absence of a cooperating application. It is also possible to detect the presence or absence of a linked application from the information. Examples of applications that perform inter-application cooperation include an integrated development environment (IDE), a web server, and a database server.
- IDE integrated development environment
- conditional expression is used, but the conditional expression can be changed in addition to the above.
- table information is omitted in the conditional expression 3902 such as “user name” and “last usage time”, it is more accurately described as “$ ⁇ column name> @ ⁇ table name” described in FIG. Column names and table names can be described as “>”.
- conditional expression 3902 may be normalized to be a separate table.
- the evaluation policy 213 is stored in the management server 100 in advance, but may be input by the administrator.
- FIG. 40 is a diagram showing the processing procedure of the aptitude evaluation program 4008 in this embodiment.
- step 1810 determines whether or not the suitability of the application is evaluated based on the threshold value table 225. This will be described in detail below.
- step 1810 the conditional expression 3902 of the line in which the value of the execution environment 3901 in the threshold value table 225 matches “execution environment 18” is evaluated. If the result of the evaluation is true, the process proceeds to step 1804. If the evaluation result is false, the process proceeds to step 1807, and the processing target is transferred to the next application.
- the applications whose suitability is evaluated are limited. For example, aptitude is not evaluated for an application whose necessity of changing the execution environment is low. As a result, information (application options) displayed on the priority order list screen 2200 is narrowed down. For this reason, it is possible to reduce the burden required for the administrator to determine whether or not to migrate the application.
- the effect of changing the execution environment is displayed.
- an evaluation value representing suitability for each type of execution environment for each application (For example, the evaluation value of each evaluation viewpoint) may be displayed.
- the priority of the evaluation viewpoint does not necessarily have to be used for calculating the priority of the candidate for changing the execution environment (the priority of the application).
- the first and second embodiments can be combined, but not limited thereto, and any two or more embodiments of the first to sixth embodiments can be combined.
- the number of execution environment types may be more or less than four as long as it is two or more.
- N is an integer of 2 or more
- (N-1) change effects are evaluated for each application by the effect evaluation program.
- the management server when there are four types of execution environments X1, X2, X3, and X4 and the current execution environment is X1, the management server performs three types of change effects (X1 to X2, X1 to X3, and X1 to X4).
- the effect of each change to is evaluated.
- Each change effect has a change effect evaluation value for each evaluation viewpoint (for example, respective values for the evaluation viewpoints 1304 to 1306 in FIG. 13).
- at least one change effect may have a comprehensive evaluation value calculated based on change effect evaluation values according to a plurality of evaluation viewpoints (for example, a sum of a plurality of change effect evaluation values).
- a change from one execution environment to the other execution environment is performed.
- the execution environment any of a physical environment, a virtual environment (streaming type), a virtual environment (host type), and a cloud environment can be adopted.
- the management server causes the client 102 to execute the uninstallation of the physical application, and the virtual application including the application program executed as the physical application is displayed on the application server. To the client 102. In this way, the management server can execute processing according to what execution environment is changed to what execution environment.
- the aptitude evaluation program calculates, for an application (hereinafter referred to as “application T”), an evaluation value indicating aptitude for each application type (for example, an evaluation value for each evaluation viewpoint).
- an application type for example, a “physical type” meaning a physical application, a “virtual type S” meaning a virtual application conforming to a streaming type application virtualization technology, and a virtual conforming to a host type application virtualization technology
- virtual type H meaning an application
- cloud type meaning an application executed in a cloud system.
- the effect evaluation program calculates a difference between an evaluation value of the current application type (for example, physical type) and an evaluation value of one or more other application types (for example, virtual type S).
- the effect according to the difference for example, the direction (angle) of the arrow is displayed.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Stored Programmes (AREA)
Abstract
Description
Network)でも良い。
(a1)アプリケーションのバージョン
アプリケーションのバージョンの種類が多く、異なるバージョン間で互換性がない場合など、ユーザ間でやり取りするデータが扱えなかったり、アプリケーションの挙動が変わったりしてしまう場合、ユーザの利便性が損なわれると考えられる。そのようなアプリケーションは、ユーザが異なる複数のバージョンを同一のクライアント102上で実行できる仮想アプリケーションの方が適している。図8で説明した通り、アプリケーションのバージョンは、特性テーブル211に格納される。適性評価プログラム208は、評価ポリシー213を基に、同一のアプリケーション名を持ちバージョンの種類が多いアプリケーション(例えば、バージョンの種類が所定数より多いアプリケーション)については、仮想環境での適性が高く、物理環境での適性は低いと判断される。さらに、バージョン毎にユーザ数の偏りがなく、いずれのバージョンもよく利用されているアプリケーションについては、適性評価プログラム208により、仮想環境での適性がより高いと判断することもできる。バージョン毎のユーザ数は、図9で説明した通り、利用状況テーブル212に格納される。
(a2)共有ライブラリの利用有無
アプリケーションが共有ライブラリを利用する場合、別のアプリケーションが利用する共有ライブラリとの競合が起きる場合があり、アプリケーションが実行できなくなるため、ユーザの利便性が損われると考えられる。そのようなアプリケーションは、共有ライブラリの競合を意識せずにアプリケーションを実行できる仮想アプリケーションの方が適している。共有ライブラリの有無は、特性テーブル211に格納されてよい。また、テーブル211には、共有ライブラリの具体的な名称が格納されてよい。評価ポリシー213において、アプリケーションが共有ライブラリを利用する場合には、適性評価プログラム208により、仮想アプリケーションとしての適性が高く、物理アプリケーションとしての適性は低いと判断される。
(a3)導入時間
物理アプリケーションの場合は、ユーザが自らクライアント102にインストールすることができるが、仮想アプリケーションについては、管理者が仮想アプリケーションを作成してクライアント102に提供を開始するまでの時間が必要となる。導入時間を表す値は、実行環境に依存する固定値として評価ポリシー213に設定されてよい。適性評価プログラム208は、評価ポリシー213を基に、導入時間が短いアプリケーションについては、仮想環境での適性が低く、導入時間が長いアプリケーションについては、仮想環境での適性が高いと判断する。
(b1)パッチ適用頻度
アプリケーションにパッチを適用する必要がある場合、パッチの適用が遅れるとセキュリティ上のリスクが高くなる。物理アプリケーションの場合、アプリケーションがインストールされる各クライアント102においてパッチを適用する必要があるため、アプリケーションサーバ101で唯一管理されている仮想アプリケーションと比較して、パッチの適用頻度が低くなる。パッチ適用頻度を表す値は、実行環境に依存する固定値として評価ポリシー213に設定されてよい。例えば、物理アプリケーションの場合、1回/月、仮想アプリケーションの場合、1回/週などである。適性評価プログラム208は、評価ポリシー213を基に、パッチの適用頻度の高いアプリケーションについては、仮想環境での適性が高いと判断する。さらに、物理アプリケーションの場合は、ユーザ数が多いほどパッチの適用頻度が低くなる傾向にあるため、適性評価プログラム208は、ユーザ数が多いアプリケーションについては、物理環境での適性が低いと判断することもできる。アプリケーションのユーザ数は、図9で説明した通り、利用状況テーブル212に格納される。
(c1)導入工数
アプリケーションを導入するために必要な作業が多いアプリケーションほど、コストが高くなる。物理アプリケーションの場合は、ユーザが自らクライアント102にインストールすることができるが、仮想アプリケーションの場合は、管理者による仮想アプリケーション作成の作業コストがかかる。また、仮想アプリケーションの場合、アプリケーションによって仮想アプリケーションにするための手順が異なるため、導入工数がアプリケーションによっても変わりうる。導入工数を表す値は、実施形態に依存する固定値として評価ポリシー213に設定されてよい。また、アプリケーション毎の導入工数の違いは、特性テーブル211に格納されてよい。適性評価プログラム208は、評価ポリシー213を基に、導入工数が少ないアプリケーション(例えば、導入工数が所定の値より低いアプリケーション)については、仮想環境での適性が高いと判断することができる。
本実施形態によれば、物理環境とストリーミング型の仮想環境とが混在するネットワークシステム10において、各実行環境におけるアプリケーションの適性が運用管理上の評価観点に基づいて評価され、実行環境を変更するアプリケーションの優先順位と、実行環境の変更の効果とが表示される。これにより、管理者は、アプリケーションの適切な実行環境を選択することができる。
(d1)実行環境におけるアプリケーション処理性能
実行環境におけるアプリケーション処理性能が、アプリケーションが要求する処理性能に満たない場合、ユーザの利便性が損なわれる。「実行環境におけるアプリケーション処理性能」とは、物理アプリケーションの場合、クライアント102の処理性能であり、仮想アプリケーションの場合は、アプリケーションサーバ2501の処理性能である。処理性能とは、アプリケーションを実行する計算機の能力(例えば、CPUや主記憶装置の容量など)を表し、具体的には、例えば、CPUの場合「2.0GHz」などと表せる。実行環境におけるアプリケーション処理性能が、アプリケーションが要求する処理性能を満たしている場合は、その実行環境での適性が高く、満たしていない場合は、その実行環境での適性が低いと判断できる。アプリケーションが要求する処理性能の値は、特性テーブル211に格納されてよい。クライアント102の処理性能は、クライアント102に共通の固定値として評価ポリシー213に設定されてよいし、クライアント102毎の値として、クライアント一覧テーブル221に格納されてよい。その場合は、クライアント102のエージェントプログラム407が、OSに搭載されている標準的なプログラムを利用して、クライアント102の処理性能の情報を収集し、収集プログラム3307が各クライアント102のエージェントプログラム407から該情報を取得してよい。アプリケーションサーバ2501の処理性能は、実行環境に依存する固定値として評価ポリシー213に設定されてよい。また、アプリケーションサーバ2501から情報が取得されてもよい。適性評価プログラム208は、評価ポリシー213を基に、アプリケーションが要求する処理性能と実行環境におけるアプリケーション処理性能とを比較し、アプリケーションが要求する処理性能が満たされている場合は、適性が高く、満たさない場合は適性が低いと判断してよい。
(d2)アプリケーション同時実行性
アプリケーションをサーバで実行することが好ましい場合であっても、サーバに物理アプリケーションをインストールする方法では、アプリケーションが複数のユーザによる同時実行を想定していない場合は、複数のユーザが同時に利用することができないため、ユーザの利便性が低い。そのようなアプリケーションの場合であっても、ホスト型のアプリケーション仮想化技術に従う仮想アプリケーションの方が適していると考えられる。アプリケーションの同時実行性は、特性テーブル211に格納されてよい。また、アプリケーションサーバ2501が、同時実行を想定していないアプリケーションへ対応する機能を有するか否かは、実行環境に依存する値として、評価ポリシー213に設定されてよい。適性評価プログラム208は、評価ポリシー213を基に、アプリケーションに同時実行性がなく、アプリケーションサーバ2501が上記機能(同時実行を想定していないアプリケーションへ対応する機能)を有する場合には、仮想アプリケーションとしての適性が高いと判断することができる。
(e1)データ保存環境
アプリケーションが何らかの機密情報をデータとして扱うような場合、データがクライアント(特にノートPCなどのモバイル端末など)に分散している場合は、セキュリティ上のリスクが高いと考えられる。そのようなアプリケーションは、アプリケーションサーバ2501で集中管理する方が適していると考えられる。データ保存環境の値は、アプリケーションの利用方式に依存する値として、評価ポリシー213に設定されてよい。例えば、データ保存環境の値として、物理アプリケーションとしての適性が低く仮想アプリケーションとしての適性が高いと判断されるような値が設定されてよい。さらに、アプリケーションが機密情報をデータとして扱うか否かは、アプリケーションによって異なるため、扱うデータの機密性の有無が特性テーブル211に格納されてよい。これにより、アプリケーションごとに、アプリケーションが機密情報をデータとして扱うか否かを判断することができる。たとえば、地図や辞書などのアプリケーションの場合は、機密情報を扱うことはないが、メールやドキュメント類を扱うアプリケーションの場合は、機密情報を扱う可能性が高いため、仮想アプリケーションとしての適性が高いと判断される。
本実施形態によれば、物理環境とホスト型の仮想環境とが混在するネットワークシステム2610において、各実行環境におけるアプリケーションの適性が運用管理上の評価観点に基づいて評価され、実行環境を変更するアプリケーションの優先順位と、実行環境の変更の効果とが表示される。これにより、管理者は、アプリケーションの適切な実行環境を選択することができる。
$標準@課金情報テーブル × $ユーザ数@利用状況テーブル
「仮想」の場合:
$仮想@課金情報テーブル × $同時実行ユーザ数@利用状況テーブル。
本実施形態によれば、アプリケーションの実行環境によって異なるライセンス料の違いを運用コストの評価に反映することができ、以って、アプリケーション実行環境をより適切に選択することが期待できる。
(f1)ネットワークトラフィック量、データ量、利用時間
クラウドサービスが、ネットワークのトラフィック量や、クラウドシステムに保存するデータ量、クラウドサービスの利用時間によって課金する場合、それぞれ、アプリケーションのネットワークトラフィック量や、保存するデータ量、アプリケーションの実行時間に基づいて適性を評価することができる。アプリケーションが利用するデータのネットワークトラフィック量、データ量、実行時間は、利用状況テーブル212に格納されてよい。評価ポリシー213において、これらの情報とクラウドサービスの課金体系に基づいて、適性評価プログラム208は、クラウドサービスの利用に必要な運用コストを評価する。運用コストが高い場合は、クラウドサービスにおける適性が低いと判断することができる。
本実施形態によれば、一以上のクラウドシステムを利用するネットワークシステムにおいて、各実行環境におけるアプリケーションの適性が運用管理上の評価観点に基づいて評価され、実行環境を変更するアプリケーションの優先度および変更の効果が提示される。これにより、管理者は、アプリケーションにとって適切な実行環境を選択することができる。
本実施形態により、管理者は、優先順位一覧画面3800を参照し、表示される優先順位に従って、実行環境を変更するアプリケーションを選択するだけで、実行環境を変更することができる。このため、アプリケーションの移行にかかるコストの削減が期待できる。
本実施形態によれば、適性が評価されるアプリケーションが限定される。例えば、実行環境の変更の必要性が低いアプリケーションについては適性が評価されない。その結果、優先順位一覧画面2200に表示される情報(アプリケーションの選択肢)が絞られる。このため、管理者がアプリケーションを移行すべきか否かを判断するのに要する負担を軽減することが可能になる。
Claims (15)
- クライアントが接続されているネットワークに接続された通信インタフェース装置と、
前記通信インタフェース装置に接続されたコントローラと
を有し、
前記コントローラが、
(A)前記クライアントのユーザが利用するアプリケーションの特性、及び/又は、前記ユーザによる前記アプリケーションの利用状況に基づいて、複数種類のアプリケーション実行環境における前記アプリケーションの適性を評価し、
(B)前記(A)での評価の結果を表す情報を表示する、
評価システム。 - 請求項1記載の評価システムであって、
前記コントローラは、複数種類のアプリケーション実行環境における前記アプリケーションの適性の評価として、複数のアプリケーションタイプのうちの、前記アプリケーションのタイプの適性を評価し、
アプリケーションタイプとして、クライアントにイントールされて実行されるアプリケーションであることを意味する物理タイプと、OSにより提供されるネイティブリソースへの、アプリケーションによるアクセスを分離したクライアント環境において、アプリケーションサーバから配信されたアプリケーションを実行するアプリケーション仮想化技術に従う仮想アプリケーションであることを意味する仮想タイプSと、クライアントがアプリケーションをアプリケーションサーバで遠隔的に実行するアプリケーション仮想化技術に従う仮想アプリケーションであることを意味する仮想タイプHとがあり、
前記アプリケーションのタイプが、前記物理タイプの場合、前記クライアントで前記アプリケーションが実行され、
前記アプリケーションのタイプが、前記仮想タイプSの場合、前記クライアントがアプリケーションサーバから前記アプリケーションを受け、前記クライアントで前記アプリケーションが実行され、
前記アプリケーションのタイプが、前記仮想タイプHの場合、前記アプリケーションが前記アプリケーションサーバで実行され、
前記クライアントが、前記アプリケーションの利用履歴を表す情報である利用履歴情報と、前記アプリケーションに関する情報であるアプリケーション情報とを管理し、
前記アプリケーションの特性として、バージョン、パッチ公開回数及びサポートOSがあり、
前記アプリケーションの利用状況として、前記アプリケーションの現在のタイプ、前記アプリケーションのユーザ数、及び、前記アプリケーションがどのぐらいオフラインで利用されたかを表すオフライン利用率があり、
前記コントローラが、評価ポリシーを管理し、
前記評価ポリシーは、アプリケーションタイプ毎に複数の評価観点についての式又は値を含み、
評価観点として、ユーザ利便性、セキュリティ、及びコストがあり、
前記ユーザ利便性に対応した前記式又は値は、サポートOSに該当するOSを前記クライアントが有するか否かと、前記アプリケーションのオフライン利用率との少なくとも一方に基づく式又は値であり、
前記セキュリティに対応した前記式又は値は、前記アプリケーションのパッチ公開回数と前記アプリケーションのユーザ数との少なくとも一方に基づく式又は値であり、
前記コストは、前記アプリケーションのユーザ数に基づく値であり、
前記コントローラは、前記(A)において、
(a1)前記クライアントから、前記アプリケーション情報及び前記利用履歴情報を含んだ情報を取得し、
(a2)前記取得した情報から、前記アプリケーションの特性と、前記アプリケーションの利用状況とを把握し、
(a3)前記アプリケーションの特性及び利用状況と、前記評価ポリシーとを基に、前記アプリケーションのアプリケーションタイプ毎の適性を表す評価値を各評価観点について算出し、
(a4)現在のアプリケーションタイプについての評価観点毎の評価値と、一以上の別のアプリケーションタイプについての評価観点毎の評価値との差分を算出し、
前記コントローラは、前記(B)において、前記アプリケーションのアプリケーションタイプを現在のアプリケーションタイプから一以上の別のアプリケーションタイプに変更することの効果を、前記(a4)で算出された差分に基づいて表示する、
評価システム。 - 請求項2記載の評価システムであって、
前記コントローラは、前記(A)において、前記ユーザ利便性、前記セキュリティ及び前記コストの優先度と、前記(a3)で算出された評価値とに基づいて、タイプ変更候補の優先順位を算出し、前記(B)において、複数のタイプ変更候補を、タイプ変更候補の優先順位の高い順に並べて表示し、
タイプ変更候補は、アプリケーションと、そのアプリケーションの現在のアプリケーションタイプと、そのアプリケーションの変更後のアプリケーションタイプとで定義される、
評価システム。 - 請求項3記載の評価システムであって、
前記評価ポリシーでは、
(U1)物理タイプに対応した前記ユーザ利便性の式又は値は、サポートOSに該当するOSを持つクライアントの数に基づく式又は値であり、
(U2)仮想タイプSに対応した前記ユーザ利便性の式又は値は、サポートOSに該当するOSを持つクライアントの数に依存しない式又は値であり、
(U3)仮想タイプHに対応した前記ユーザ利便性の式又は値は、前記アプリケーションのオフライン利用率に依存しない式又は値であり、
(S1)物理タイプに対応した前記セキュリティの式又は値は、前記アプリケーションのパッチ公開回数とユーザ数との両方に基づく式又は値であり、
(S2)仮想タイプSに対応した前記セキュリティの式又は値は、前記アプリケーションのユーザ数に基づき、且つ、前記アプリケーションのパッチ公開回数に依存しない式又は値であり、
(S3)仮想タイプHに対応した前記セキュリティの式又は値は、前記アプリケーションのユーザ数に基づき、且つ、前記アプリケーションのパッチ公開回数に依存しない式又は値であり、
(C1)物理タイプに対応した前記コストの式又は値は、前記アプリケーションのユーザ数に基づく式又は値であり、
(C2)仮想タイプSに対応した前記コストの式又は値は、前記アプリケーションのユーザ数に依存しない式又は値であり、
(C3)仮想タイプHに対応した前記コストの式又は値は、前記アプリケーションのユーザ数に依存しない式又は値であり、
前記(a3)で算出された評価値について、
(u1)サポートOSに該当するOSを持つクライアントの数が多い場合、前記物理タイプ及び前記ユーザ利便性についての評価値は高く、サポートOSに該当するOSを持つクライアントの数が少ない場合、前記物理タイプ及び前記ユーザ利便性についての評価値は低く、
(s1)前記アプリケーションのパッチ公開回数が多い場合、前記セキュリティの評価値は低く、前記アプリケーションのパッチ公開回数が少ない場合、前記セキュリティの評価値は高く、
(s2)前記アプリケーションのユーザ数が多い場合、前記セキュリティ及び前記物理タイプについての評価値は低く、前記アプリケーションのユーザ数が少ない場合、前記セキュリティ及び前記物理タイプについての評価値は高く、
(c1)前記アプリケーションのユーザ数が多い場合、前記コスト及び前記物理タイプについての評価値は低く、前記アプリケーションのユーザ数が少ない場合、前記コスト及び前記物理タイプについての評価値は高い、
評価システム。 - 請求項1記載の評価システムであって、
前記コントローラが、評価ポリシーを管理しており、
前記評価ポリシーは、アプリケーション実行環境毎に用意された一以上の評価観点に従う式又は値を含んだ情報であり、
前記コントローラが、前記(A)において、前記アプリケーションの特性、及び/又は、前記アプリケーションの利用状況と、評価ポリシーとに基づいて、各種アプリケーション実行環境における前記アプリケーションの適性を表す評価値を評価観点毎に算出する、
評価システム。 - 請求項5記載の評価システムであって、
前記一以上の評価観点は、ユーザ利便性を含み、
前記ユーザ利便性について、以下の(6-1)~(6-8):
(6-1)アプリケーションのサポートOSに該当するOSを持つクライアントの数;
(6-2)アプリケーションのバージョンの種類の数;
(6-3)共有ライブラリの利用の有無;
(6-4)アプリケーションの導入時間;
(6-5)アプリケーションがどのぐらいオフラインで利用されたかを表すオフライン利用率;
(6-6)特定の運用期間に対する、全てのクライアントにおけるアプリケーションの利用時間の比率である利用率;
(6-6)実行環境におけるアプリケーション処理性能が、アプリケーションが要求する処理性能を満たすか否か;
(6-8)アプリケーションの同時実行性、
のうちの少なくとも一つに基づいて評価値が算出される
評価システム。 - 請求項5記載の評価システムであって、
前記一以上の評価観点は、セキュリティを含み、
前記セキュリティについて、以下の(7-1)~(7-4):
(7-1)アプリケーションのパッチ公開回数;
(7-2)アプリケーションのユーザ数;
(7-3)アプリケーションのパッチ適用頻度;
(7-4)データ保存環境、
のうちの少なくとも一つに基づいて評価値が算出される
評価システム。 - 請求項5記載の評価システムであって、
前記一以上の評価観点は、コストを含み、
前記コストについて、以下の(8-1)~(8-6):
(8-1)アプリケーションのユーザ数;
(8-2)アプリケーションの導入工数;
(8-3)課金方式;
(8-4)アプリケーションが利用する機能であるクラウドサービスを提供するクラウドシステムからの前記クラウドサービスが経由するネットワークのトラフィック量;
(8-5)前記クラウドシステムに保存されるデータの量;
(8-6)前記クラウドサービスの利用時間、
のうちの少なくとも一つに基づいて評価値が算出される
評価システム。 - 請求項5記載の評価システムであって、
前記複数種類のアプリケーション実行環境は、
アプリケーションが前記クライアントにインストールされて前記クライアントで実行される環境である物理環境と、
アプリケーション仮想化技術に従うアプリケーションが実行される環境である1以上の仮想環境と、
アプリケーションが備える機能をクライアントに提供するクラウドシステムでアプリケーションが実行される環境である1以上のクラウド環境と
のうちの少なくとも二つを含む、
評価システム。 - 請求項5記載の評価システムであって、
前記コントローラは、前記算出された評価値に基づいて、タイプ変更候補の優先順位を算出し、前記(B)において、複数のタイプ変更候補を、タイプ変更候補の優先順位の高い順に並べて表示し、
タイプ変更候補は、アプリケーションと、そのアプリケーションの現在のアプリケーション実行環境と、そのアプリケーションの変更後のアプリケーション実行環境とで定義される、
評価システム。 - 請求項1記載の評価システムであって、
前記コントローラは、前記(A)において、
(a1)前記クライアントのユーザが利用するアプリケーションの特性、及び/又は、前記ユーザによる前記アプリケーションの利用状況に基づいて、前記アプリケーションについての複数種類のアプリケーション実行環境の適性を評価し
(a2)前記アプリケーションについて、現在のアプリケーション実行環境ついての適性と、一以上の別のアプリケーション実行環境の適性との差分を算出し、
前記コントローラは、前記(B)において、前記アプリケーションのアプリケーション実行環境を現在のアプリケーション実行環境から一以上の別のアプリケーション実行環境に変更することの効果を、前記(a2)で算出された差分に基づいて表示する、
評価システム。 - 請求項11記載の評価システムであって、
前記コントローラは、前記(A)において、環境変更候補の優先順位を算出し、前記(B)において、複数の環境変更候補を、環境変更候補の優先順位の高い順に並べて表示し、
環境変更候補は、アプリケーションと、そのアプリケーションの現在のアプリケーション実行環境と、そのアプリケーションの変更後のアプリケーション実行環境とで定義される、
評価システム。 - 請求項11評価システムであって、
前記コントローラは、前記(B)での情報の表示後に、管理者所望の環境変更候補の指定を受け付け、指定された環境変更候補に従って、前記アプリケーションの実行環境を現在の実行環境から別の実行環境に変更する、
評価システム。 - 請求項1記載の評価システムであって、
前記コントローラは、複数のアプリケーションのうち、実行環境におけるアプリケーションの適性の評価の必要性がないことを意味する条件に該当するアプリケーションを除くアプリケーションについて、適性の評価を行う、
評価システム。 - 請求項3記載の評価システムであって、
前記コントローラは、複数のアプリケーションのうち、アプリケーションのタイプの適性の評価の必要性がないことを意味する条件に該当するアプリケーションを除くアプリケーションについて、前記(a3)及び(a4)を実行する、
評価システム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011526647A JPWO2011018827A1 (ja) | 2009-08-13 | 2009-08-13 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
US12/672,704 US8566391B2 (en) | 2009-08-13 | 2009-08-13 | System and method for evaluating application suitability in execution environment |
PCT/JP2009/003893 WO2011018827A1 (ja) | 2009-08-13 | 2009-08-13 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2009/003893 WO2011018827A1 (ja) | 2009-08-13 | 2009-08-13 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011018827A1 true WO2011018827A1 (ja) | 2011-02-17 |
Family
ID=43586013
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/003893 WO2011018827A1 (ja) | 2009-08-13 | 2009-08-13 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US8566391B2 (ja) |
JP (1) | JPWO2011018827A1 (ja) |
WO (1) | WO2011018827A1 (ja) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2012226757A (ja) * | 2011-04-21 | 2012-11-15 | Zeon Networks | アプリケーションの携帯端末機間移動及びインストール方法 |
JP2014048720A (ja) * | 2012-08-29 | 2014-03-17 | Dainippon Printing Co Ltd | アプリケーションプログラムの利用実績評価システム |
JP2015001766A (ja) * | 2013-06-13 | 2015-01-05 | 株式会社日立製作所 | 資産管理システム及び資産管理方法 |
JP2015506526A (ja) * | 2012-02-06 | 2015-03-02 | エンパイア テクノロジー ディベロップメント エルエルシー | クラウドサービス間の転送時のアプリケーション性能の維持 |
JP2016095735A (ja) * | 2014-11-17 | 2016-05-26 | 富士通株式会社 | 依存情報提供プログラム、依存情報提供装置及び依存情報提供方法 |
JP2016517584A (ja) * | 2013-03-14 | 2016-06-16 | アマゾン テクノロジーズ インク | 分型インフラストラクチャのインベントリサービス |
CN106021086A (zh) * | 2016-05-26 | 2016-10-12 | 广东欧珀移动通信有限公司 | 一种自动识别沉迷应用的方法、装置及终端设备 |
JP2017027408A (ja) * | 2015-07-23 | 2017-02-02 | 富士ゼロックス株式会社 | 情報共有プログラム、情報共有装置、及び情報共有システム |
US10229362B2 (en) | 2014-11-27 | 2019-03-12 | Fujitsu Limited | Information processing method |
JP2021060700A (ja) * | 2019-10-04 | 2021-04-15 | 株式会社日立製作所 | コスト提示装置、コスト提示方法およびコスト提示プログラム |
US11646904B2 (en) | 2019-12-20 | 2023-05-09 | Fujitsu Limited | Information processing apparatus and service cost calculation method |
WO2024034001A1 (ja) * | 2022-08-09 | 2024-02-15 | 三菱電機株式会社 | 情報処理装置、情報処理方法、構成装置、及び構成方法 |
Families Citing this family (59)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100926804B1 (ko) | 2004-04-30 | 2009-11-12 | 리서치 인 모션 리미티드 | 데이터 전송을 처리하기 위한 시스템 및 방법 |
US7614082B2 (en) | 2005-06-29 | 2009-11-03 | Research In Motion Limited | System and method for privilege management and revocation |
EP2450797A4 (en) * | 2009-06-08 | 2013-03-13 | Sharp Kk | SOFTWARE UPGRADE SYSTEM, DISPLAY UNIT AND SOFTWARE UPGRADING PROCEDURE |
JPWO2011018827A1 (ja) * | 2009-08-13 | 2013-01-17 | 株式会社日立製作所 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
US9436459B2 (en) * | 2010-05-28 | 2016-09-06 | Red Hat, Inc. | Generating cross-mapping of vendor software in a cloud computing environment |
US9354939B2 (en) | 2010-05-28 | 2016-05-31 | Red Hat, Inc. | Generating customized build options for cloud deployment matching usage profile against cloud infrastructure options |
US8417578B1 (en) | 2011-03-17 | 2013-04-09 | Amazon Technologies, Inc. | Customizing component configurations for utility computing |
US8738754B2 (en) | 2011-04-07 | 2014-05-27 | International Business Machines Corporation | Systems and methods for managing computing systems utilizing augmented reality |
US20140053234A1 (en) * | 2011-10-11 | 2014-02-20 | Citrix Systems, Inc. | Policy-Based Application Management |
US20140032733A1 (en) | 2011-10-11 | 2014-01-30 | Citrix Systems, Inc. | Policy-Based Application Management |
US9280377B2 (en) | 2013-03-29 | 2016-03-08 | Citrix Systems, Inc. | Application with multiple operation modes |
US9215225B2 (en) | 2013-03-29 | 2015-12-15 | Citrix Systems, Inc. | Mobile device locking with context |
US9143530B2 (en) | 2011-10-11 | 2015-09-22 | Citrix Systems, Inc. | Secure container for protecting enterprise data on a mobile device |
US9161226B2 (en) | 2011-10-17 | 2015-10-13 | Blackberry Limited | Associating services to perimeters |
US9613219B2 (en) * | 2011-11-10 | 2017-04-04 | Blackberry Limited | Managing cross perimeter access |
US8799227B2 (en) | 2011-11-11 | 2014-08-05 | Blackberry Limited | Presenting metadata from multiple perimeters |
US20130339424A1 (en) * | 2012-06-15 | 2013-12-19 | Infosys Limited | Deriving a service level agreement for an application hosted on a cloud platform |
US9369466B2 (en) | 2012-06-21 | 2016-06-14 | Blackberry Limited | Managing use of network resources |
US9979780B1 (en) * | 2012-06-25 | 2018-05-22 | EMC IP Holding Company LLC | Method and apparatus for selection between multiple candidate clouds for job processing |
US9317709B2 (en) * | 2012-06-26 | 2016-04-19 | Google Inc. | System and method for detecting and integrating with native applications enabled for web-based storage |
EP2852889A1 (en) * | 2012-06-27 | 2015-04-01 | Qatar Foundation | An arrangement configured to allocate one or more resources of one or more computing devices to a virtual machine |
EP2853064A1 (en) * | 2012-06-27 | 2015-04-01 | Qatar Foundation | An arrangement configured to allocate network interface resources to a virtual machine |
US8930906B2 (en) * | 2012-06-27 | 2015-01-06 | International Business Machines Corporation | Selectively allowing changes to a system |
US9392077B2 (en) | 2012-10-12 | 2016-07-12 | Citrix Systems, Inc. | Coordinating a computing activity across applications and devices having multiple operation modes in an orchestration framework for connected devices |
US9774658B2 (en) | 2012-10-12 | 2017-09-26 | Citrix Systems, Inc. | Orchestration framework for connected devices |
US9516022B2 (en) | 2012-10-14 | 2016-12-06 | Getgo, Inc. | Automated meeting room |
US20140109176A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Configuring and providing profiles that manage execution of mobile applications |
US8910239B2 (en) | 2012-10-15 | 2014-12-09 | Citrix Systems, Inc. | Providing virtualized private network tunnels |
US20140108793A1 (en) | 2012-10-16 | 2014-04-17 | Citrix Systems, Inc. | Controlling mobile device access to secure data |
WO2014062804A1 (en) | 2012-10-16 | 2014-04-24 | Citrix Systems, Inc. | Application wrapping for application management framework |
US9606774B2 (en) | 2012-10-16 | 2017-03-28 | Citrix Systems, Inc. | Wrapping an application with field-programmable business logic |
US9971585B2 (en) | 2012-10-16 | 2018-05-15 | Citrix Systems, Inc. | Wrapping unmanaged applications on a mobile device |
US9239727B1 (en) * | 2012-10-17 | 2016-01-19 | Amazon Technologies, Inc. | Configurable virtual machines |
US8656016B1 (en) | 2012-10-24 | 2014-02-18 | Blackberry Limited | Managing application execution and data access on a device |
US9075955B2 (en) * | 2012-10-24 | 2015-07-07 | Blackberry Limited | Managing permission settings applied to applications |
JP5971099B2 (ja) * | 2012-12-04 | 2016-08-17 | 富士通株式会社 | 情報処理装置、方法及びプログラム |
GB2513535A (en) * | 2012-12-14 | 2014-11-05 | Ibm | Software installer with built-in hypervisor |
US9455886B2 (en) | 2013-03-29 | 2016-09-27 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9985850B2 (en) | 2013-03-29 | 2018-05-29 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9355223B2 (en) | 2013-03-29 | 2016-05-31 | Citrix Systems, Inc. | Providing a managed browser |
US10284627B2 (en) | 2013-03-29 | 2019-05-07 | Citrix Systems, Inc. | Data management for an application with multiple operation modes |
US9413736B2 (en) | 2013-03-29 | 2016-08-09 | Citrix Systems, Inc. | Providing an enterprise application store |
US9665359B2 (en) | 2013-09-13 | 2017-05-30 | Microsoft Technology Licensing, Llc | Automatically resolving conflicts after installation of selected updates in a computer system |
US9830142B2 (en) | 2013-09-13 | 2017-11-28 | Microsoft Technology Licensing, Llc | Automatic installation of selected updates in multiple environments |
US9626176B2 (en) * | 2013-09-13 | 2017-04-18 | Microsoft Technology Licensing, Llc | Update installer with technical impact analysis |
US10026064B2 (en) | 2013-09-13 | 2018-07-17 | Microsoft Technology Licensing, Llc | Automatically recommending updates based on stored lifecycle information |
US10505864B1 (en) | 2013-09-30 | 2019-12-10 | EMC IP Holding Company LLC | Method for running HPC jobs |
US10049033B2 (en) * | 2014-06-03 | 2018-08-14 | Sap Se | Application gateway for cloud computing systems |
US9727736B1 (en) * | 2014-10-17 | 2017-08-08 | Amazon Technologies, Inc. | Tracking developer behavior with respect to software analysis tools |
US10528449B2 (en) | 2014-12-04 | 2020-01-07 | Micro Focus Llc | Grouping event reports |
JP6507643B2 (ja) * | 2015-01-05 | 2019-05-08 | 富士通株式会社 | アプリ提供方法、アプリ提供サーバおよびアプリ提供プログラム |
US10719608B2 (en) * | 2015-02-06 | 2020-07-21 | Honeywell International Inc. | Patch monitoring and analysis |
US9465714B1 (en) * | 2015-09-22 | 2016-10-11 | International Business Machines Corporation | Adaptive runtime for a multiprocessing API |
JP6512055B2 (ja) * | 2015-09-30 | 2019-05-15 | 富士通株式会社 | 分析プログラム、分析装置および分析方法 |
JP6801267B2 (ja) * | 2016-07-04 | 2020-12-16 | 富士通株式会社 | 評価プログラム、評価方法、評価装置および情報処理装置 |
US10496518B2 (en) * | 2016-12-01 | 2019-12-03 | International Business Machines Corporation | Objective evaluation of code based on usage |
JP6767308B2 (ja) * | 2017-05-23 | 2020-10-14 | ファナック株式会社 | 機械と相互通信可能に接続される機械制御用コンピュータ、機械システム、ベースソフトウェア、コンピュータ読取可能な記録媒体、データ構造、及び機械制御方法 |
EP3623953B1 (en) * | 2018-09-17 | 2022-01-19 | Siemens Healthcare GmbH | Technical improvement evaluation for a set of applications |
US11399057B1 (en) * | 2021-03-03 | 2022-07-26 | T-Mobile Usa, Inc. | Enabling analytics for a virtualized application |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06243097A (ja) * | 1993-02-16 | 1994-09-02 | Nippon Telegr & Teleph Corp <Ntt> | サーバプログラム実行制御方式 |
JP2008129648A (ja) * | 2006-11-16 | 2008-06-05 | Nec Corp | セキュリティリスク管理システム、セキュリティリスク管理方法およびセキュリティリスク管理用プログラム |
JP2008152591A (ja) * | 2006-12-19 | 2008-07-03 | Hitachi Ltd | 情報処理装置の割当て方法、情報処理システム及び管理サーバ |
JP2008269422A (ja) * | 2007-04-23 | 2008-11-06 | Sky Kk | インストール管理方法とインストール管理プログラムとインストール管理装置 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6538667B1 (en) | 1999-07-23 | 2003-03-25 | Citrix Systems, Inc. | System and method for providing immediate visual response to user input at a client system connected to a computer system by a high-latency connection |
JP2001222424A (ja) | 2000-02-08 | 2001-08-17 | Fujitsu Ltd | ソフトウェアライセンス管理装置,ソフトウェアライセンス管理方法およびソフトウェアライセンス管理用プログラム記録媒体 |
US7665082B2 (en) * | 2000-06-30 | 2010-02-16 | Microsoft Corporation | Methods and systems for adaptation, diagnosis, optimization, and prescription technology for network-based applications |
US7146607B2 (en) * | 2002-09-17 | 2006-12-05 | International Business Machines Corporation | Method and system for transparent dynamic optimization in a multiprocessing environment |
EP1794679A1 (en) | 2004-09-30 | 2007-06-13 | Citrix Systems, Inc. | Method and apparatus for moving processes between isolation environments |
US7680758B2 (en) | 2004-09-30 | 2010-03-16 | Citrix Systems, Inc. | Method and apparatus for isolating execution of software applications |
US7620953B1 (en) * | 2004-10-05 | 2009-11-17 | Azul Systems, Inc. | System and method for allocating resources of a core space among a plurality of core virtual machines |
US20060143715A1 (en) * | 2004-12-28 | 2006-06-29 | Motorola, Inc. | Method and apparatus for providing security policy enforcement |
US8219987B1 (en) * | 2007-08-24 | 2012-07-10 | Vmware, Inc. | Optimized virtual machine specification for provisioning application specific runtime environment |
JPWO2011018827A1 (ja) * | 2009-08-13 | 2013-01-17 | 株式会社日立製作所 | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 |
-
2009
- 2009-08-13 JP JP2011526647A patent/JPWO2011018827A1/ja active Pending
- 2009-08-13 WO PCT/JP2009/003893 patent/WO2011018827A1/ja active Application Filing
- 2009-08-13 US US12/672,704 patent/US8566391B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06243097A (ja) * | 1993-02-16 | 1994-09-02 | Nippon Telegr & Teleph Corp <Ntt> | サーバプログラム実行制御方式 |
JP2008129648A (ja) * | 2006-11-16 | 2008-06-05 | Nec Corp | セキュリティリスク管理システム、セキュリティリスク管理方法およびセキュリティリスク管理用プログラム |
JP2008152591A (ja) * | 2006-12-19 | 2008-07-03 | Hitachi Ltd | 情報処理装置の割当て方法、情報処理システム及び管理サーバ |
JP2008269422A (ja) * | 2007-04-23 | 2008-11-06 | Sky Kk | インストール管理方法とインストール管理プログラムとインストール管理装置 |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9032395B2 (en) | 2011-04-21 | 2015-05-12 | Gion Networks | Method for installing applications installed in an old mobile terminal to a new mobile terminal |
JP2012226757A (ja) * | 2011-04-21 | 2012-11-15 | Zeon Networks | アプリケーションの携帯端末機間移動及びインストール方法 |
JP2015506526A (ja) * | 2012-02-06 | 2015-03-02 | エンパイア テクノロジー ディベロップメント エルエルシー | クラウドサービス間の転送時のアプリケーション性能の維持 |
JP2014048720A (ja) * | 2012-08-29 | 2014-03-17 | Dainippon Printing Co Ltd | アプリケーションプログラムの利用実績評価システム |
JP2016517584A (ja) * | 2013-03-14 | 2016-06-16 | アマゾン テクノロジーズ インク | 分型インフラストラクチャのインベントリサービス |
US10333801B2 (en) | 2013-03-14 | 2019-06-25 | Amazon Technologies, Inc. | Inventory service for distributed infrastructure |
JP2015001766A (ja) * | 2013-06-13 | 2015-01-05 | 株式会社日立製作所 | 資産管理システム及び資産管理方法 |
JP2016095735A (ja) * | 2014-11-17 | 2016-05-26 | 富士通株式会社 | 依存情報提供プログラム、依存情報提供装置及び依存情報提供方法 |
US9699268B2 (en) | 2014-11-17 | 2017-07-04 | Fujitsu Limited | Dependency information provision program, dependency information provision apparatus, and dependency information provision method |
US10229362B2 (en) | 2014-11-27 | 2019-03-12 | Fujitsu Limited | Information processing method |
JP2017027408A (ja) * | 2015-07-23 | 2017-02-02 | 富士ゼロックス株式会社 | 情報共有プログラム、情報共有装置、及び情報共有システム |
CN106021086A (zh) * | 2016-05-26 | 2016-10-12 | 广东欧珀移动通信有限公司 | 一种自动识别沉迷应用的方法、装置及终端设备 |
JP2021060700A (ja) * | 2019-10-04 | 2021-04-15 | 株式会社日立製作所 | コスト提示装置、コスト提示方法およびコスト提示プログラム |
JP7421299B2 (ja) | 2019-10-04 | 2024-01-24 | 株式会社日立製作所 | コスト提示装置、コスト提示方法およびコスト提示プログラム |
US11646904B2 (en) | 2019-12-20 | 2023-05-09 | Fujitsu Limited | Information processing apparatus and service cost calculation method |
WO2024034001A1 (ja) * | 2022-08-09 | 2024-02-15 | 三菱電機株式会社 | 情報処理装置、情報処理方法、構成装置、及び構成方法 |
Also Published As
Publication number | Publication date |
---|---|
US8566391B2 (en) | 2013-10-22 |
US20110270963A1 (en) | 2011-11-03 |
JPWO2011018827A1 (ja) | 2013-01-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011018827A1 (ja) | 実行環境におけるアプリケーションの適性を評価するシステム及び方法 | |
US9323519B2 (en) | Packaging an application | |
CN111279320B (zh) | 实现微服务配置和管理的api储存库 | |
US10389651B2 (en) | Generating application build options in cloud computing environment | |
US10938668B1 (en) | Safe deployment using versioned hash rings | |
US9578088B2 (en) | Globally distributed utility computing cloud | |
CN106462467B (zh) | 在不同分布式网络上针对消费服务的集成api和ui | |
US8997054B2 (en) | Software application certification service | |
US8943496B2 (en) | Providing a hosted appliance and migrating the appliance to an on-premise environment | |
US8387038B2 (en) | Method and system for automatic computer and user migration | |
US9032367B2 (en) | Providing a demo appliance and migrating the demo appliance to a production appliance | |
US8584116B2 (en) | Installing method, installer, and installing program | |
US20130312055A1 (en) | Security management device and method | |
US8196137B2 (en) | Remote auto provisioning and publication of applications | |
US20070067440A1 (en) | Application splitting for network edge computing | |
TW201411368A (zh) | 本端備份之基於雲端儲存 | |
TW201403350A (zh) | 以雲端爲基礎之應用程式資源檔案 | |
US20130110905A1 (en) | File type associations for remote applications | |
JP5278924B2 (ja) | データ処理環境における動的プロビジョニングのための方法および装置 | |
US7613680B2 (en) | Computer system and the computer control method | |
JP2013077220A (ja) | コンピュータシステム及びアプリケーションのマルチバージョン管理装置 | |
US8849974B2 (en) | Social network based information discovery about network data processing systems | |
JP5508498B2 (ja) | インストーリング方法、インストーラ装置及びインストーリング用プログラム | |
EP3077903A1 (en) | Methods and systems for machine learning to discover application compatibility status |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 12672704 Country of ref document: US |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09848246 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2011526647 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09848246 Country of ref document: EP Kind code of ref document: A1 |