JP7220763B1 - Virtual environment system and virtual environment control method - Google Patents

Abstract

A virtual environment system and a virtual environment control method are provided for efficiently and accurately taking over information in a VDI environment. A VDI server (20) is connected to a customer management system (30), a virtualization server (40), and a cooperation destination system (50). The VDI server 20 executes initialization processing to permit the creation of temporary files in the VDI area 21 used by the client, and accesses the customer management system 30 from the VDI area 21 using the first application. The VDI server 20 acquires the handover information to be provided from the customer management system 30 to the cooperation destination system 50, records it in a temporary file, and activates the second application for accessing the cooperation destination system 50 on the virtualization server 40. . The VDI server 20 provides the second application with the takeover information recorded in the temporary file, and provides the takeover information to the cooperation destination system 50 via the second application of the virtualization server 40 . [Selection drawing] Fig. 1

Description

The present invention relates to a virtual environment system and a virtual environment control method for taking over information from another system in a virtual environment.

VDI (Virtual Desktop Infrastructure) is a technique for realizing a thin client environment. Instead of installing an OS and applications in local client terminals, these are centralized on a server and operated remotely (see, for example, Patent Document 1). The remote desktop system described in this document includes a client terminal, a first server that outputs the result of executing an application, and a second server that is communicably connected to the client terminal and the server and has a virtual machine installed. And prepare.

JP 2016-189127 A

However, in the VDI environment, data cannot be stored in memory at the client terminal. Therefore, the data acquired by the preceding server cannot be handed over to the succeeding server. In this case, information necessary for subsequent use of the server must be input at the client terminal, which imposes an operational burden. In addition, there is a possibility of erroneous input at the time of input on the client terminal.

A virtual environment system that solves the above problems is connected to a first system, a virtualization server, and a second system. Then, the virtual environment system executes initialization processing that permits creation of a temporary file in the VDI area used by the client, accesses the first system from the VDI area using the first application, Takeover information to be provided from the first system to the second system is acquired, recorded in a temporary file, a second application for accessing the second system is started on the virtualization server, and the second application is transferred to the second application. Providing takeover information recorded in a temporary file, and providing the takeover information to the second system via the second application of the virtualization server.

According to the present invention, information can be inherited efficiently and accurately in a VDI environment.

System schematic of embodiment. FIG. 2 is an explanatory diagram of a hardware configuration example of the embodiment; Explanatory drawing of the processing procedure of embodiment.

An embodiment embodying a virtual environment system and a virtual environment control method will be described below with reference to FIGS. 1 to 3. FIG. In this embodiment, it is assumed that information acquired by a customer management system is used by a linked system in a VDI environment.

As shown in FIG. 1, in this embodiment, a client terminal 10, a VDI server 20, a customer management system 30, a virtualization server 40, and a cooperation destination system 50 connected via a network are used.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of the information processing apparatus H10 functioning as the client terminal 10, the VDI server 20, the customer management system 30, the virtualization server 40, the cooperation destination system 50, and the like.

The information processing device H10 has a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is an example, and other hardware may be included.

The communication device H11 is an interface that establishes a communication path with another device and executes data transmission/reception, such as a network interface or a wireless interface.

The input device H12 is a device that receives user input, such as a mouse or a keyboard.
The display device H13 is a display, a touch panel, or the like that displays various information.

The storage device H14 stores data and various programs for executing various functions of the client terminal 10, the VDI server 20, the customer management system 30, the virtualization server 40, and the cooperation destination system 50. FIG. Examples of the storage device H14 include ROM, RAM, hard disk, and the like.

The processor H15 controls each process in the client terminal 10, the VDI server 20, the customer management system 30, the virtualization server 40, and the cooperation destination system 50 using programs and data stored in the storage device H14. Examples of the processor H15 include a CPU, an MPU, and the like. The processor H15 develops a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processes. For example, when the application programs of the client terminal 10, the VDI server 20, the customer management system 30, the virtualization server 40, and the cooperation destination system 50 are started, the processor H15 operates a process for executing each process described later.

Processor H15 is not limited to performing software processing for all the processing that it itself executes. For example, the processor H15 may include a dedicated hardware circuit (for example, an application specific integrated circuit: ASIC) that performs hardware processing for at least part of the processing performed by the processor H15. That is, the processor H15 can be configured as follows.

Circuits including (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that perform at least some of the various types of processing, and (3) combinations thereof. (circuitry)
Processor H15 includes a CPU and memory, such as RAM and ROM, which stores program code or instructions configured to cause the CPU to perform processes. Memory or computer-readable media includes any available media that can be accessed by a general purpose or special purpose computer.

(Configuration of each information processing device)
Configurations of the client terminal 10, the VDI server 20, the customer management system 30, the virtualization server 40, and the cooperation destination system 50 will be described with reference to FIG.

The client terminal 10 is a computer terminal used by each user. Using this client terminal 10, services provided by various servers are used. This client terminal 10 functions as a thin client that provides only an interface to the user. Therefore, BYOD (Bring your own device) terminals such as smartphone terminals and tablet terminals may be used.

The VDI server 20 is a computer system (virtual environment system) that implements the VDI environment of the client terminal 10 . The VDI server 20 holds user authentication information (user ID, password, etc.) for user authentication of each client terminal 10 . Furthermore, the VDI server 20 holds information on applications used by each user. The VDI server 20 then provides the client terminal 10 for which the user has been authenticated with the VDI area 21 for implementing the virtual desktop. With this VDI environment, various processes are executed without leaving data on the client terminal 10 side. The VDI server 20 holds a virtual desktop image and can be customized according to the purpose of the user of the client terminal 10 . Furthermore, the VDI server 20 holds information about access conditions in the cooperation destination system 50 .

Furthermore, the VDI server 20 has a cooperation support unit 22 . The cooperation support unit 22 is activated by executing the cooperation support program. As will be described later, the cooperation support unit 22 permits temporary writing for each application and creates temporary files in the VDI area 21 .

The customer management system 30 is a computer system (first system) that manages customer information (Customer Relationship Management). This customer management system 30 comprises a database in which customer personal information is recorded for customer identifiers that individually specify each customer.

The virtualization server 40 provides a virtual machine for accessing the cooperation destination system 50 from the VDI area 21 of the VDI server 20 . For example, an application in the VDI area 21 is used as a host application (first application). Then, an application for accessing the cooperation destination system 50 is used as a guest application (second application) to realize access to the cooperation destination system 50 . Therefore, the second application that can be used in the cooperation destination system 50 is held.
The cooperation destination system 50 is a computer system (second system) that provides various services to the client terminal 10 .

(Outline of virtual environment processing)
An outline of virtual environment processing will be described with reference to FIG. When the user does business, the client terminal 10 is activated. In this case, the client terminal 10 accesses the VDI server 20 .

First, the VDI server 20 executes VDI area startup processing (step S101). Specifically, the VDI server 20 performs user authentication of the client terminal 10 . Then, the VDI server 20 sets the VDI area 21 used by the client terminal 10 based on the user authentication result.

Next, the VDI server 20 executes initialization processing (step S102). Specifically, the VDI server 20 initializes the VDI area 21 . As a result, in this VDI area 21, the memory used can be reset and the OS and applications can be used in the initial state.

Next, the VDI server 20 executes temporary write permission processing for each application (step S103). Specifically, the cooperation support unit 22 of the VDI server 20 identifies the application used by the user of the client terminal 10 . Next, the cooperation support unit 22 sets temporary write permission for the application used by the user in the registry of the VDI area 21 for the client terminal 10 .

Next, the VDI server 20 executes temporary file creation processing (step S104). Specifically, the VDI server 20 creates a temporary file in the VDI area 21 used by the client terminal 10 .

Next, the VDI server 20 executes CRM access processing (step S105). Specifically, when the user of the client terminal 10 acquires customer information, the user inputs access to the customer management system 30 to the client terminal 10 . In this case, the VDI server 20 accesses the customer management system 30 according to instructions from the client terminal 10 . For this access, the VDI server 20 uses the first application available in the VDI area 21 .

Next, the customer management system 30 executes CRM activation processing (step S106). Specifically, the customer management system 30 provides customer management information to the VDI area 21 for the client terminal 10 .

Next, the VDI server 20 executes CRM business processing as first business processing (step S107). Specifically, the VDI server 20 executes business processing using the customer management system 30 according to instructions from the first application of the client terminal 10 . Here, for example, the user uses the customer management system 30 to obtain information on a specific customer. Then, if the user desires this customer-related cooperative process, the user selects a cooperative button for accessing the cooperative system 50 on the display screen of the first application. For example, when performing business processing related to an investment trust of a specific customer, the access button to the investment trust management system as the linked system 50 is selected on the customer information display screen.

Next, the customer management system 30 executes cooperative operation detection processing (step S108). Specifically, the customer management system 30 acquires cooperation operation information from the VDI area 21 used by the client terminal 10 . Information about the cooperation destination system 50 is included in this cooperation operation information.

Next, the customer management system 30 executes a process of providing arguments required by the cooperation destination (step S109). Specifically, the customer management system 30 identifies the handover information (here, the URL argument) required by the cooperation destination system 50 . For example, the customer management system 30 identifies the address of the linked system 50 and the customer identifier of the specific customer, and provides them to the VDI server 20 .

Next, the VDI server 20 writes the argument to the temporary file (step S110). Specifically, the cooperation support unit 22 of the VDI server 20 records the argument obtained from the customer management system 30 in the temporary file.

Next, the VDI server 20 executes cooperation instruction processing (step S111). Specifically, the collaboration support unit 22 of the VDI server 20 identifies access conditions in the collaboration destination system 50 . For example, an application that can be used is identified in the cooperation destination system 50 . Then, the cooperation support unit 22 determines whether the applications available in the VDI area 21 satisfy the access conditions of the cooperation destination system 50 . If the first application available in the VDI area 21 does not satisfy the access conditions of the cooperation destination system 50 , the cooperation support unit 22 transmits a cooperation instruction to the virtualization server 40 . In this case, the address of the cooperation destination system 50 is included.

Next, the virtualization server 40 executes cooperation start processing (step S112). Specifically, the virtualization server 40 activates the second application that satisfies the access conditions of the cooperation destination system 50 for the VDI area 21 to which the cooperation instruction has been sent.

Next, the virtualization server 40 executes an argument acquisition process from the temporary file (step S113). Specifically, the virtualization server 40 acquires the argument recorded in the temporary file of the VDI area 21 .

Next, the virtualization server 40 sets an argument and executes access processing to the cooperation destination (step S114). Specifically, the virtualization server 40 sets an argument (for example, a customer identifier) acquired from the temporary file in the VDI area 21 to the address of the cooperation destination system 50 in the second application. Then, the virtualization server 40 accesses the cooperation destination system 50 using the second application.

Next, the cooperation destination system 50 executes cooperation destination business processing as second business processing (step S115). Specifically, the cooperation destination system 50 uses the argument added to the address to execute the cooperation destination business process. For example, investment trust management information using customer identifiers is provided to the VDI server 20 via the virtualization server 40 . In this case, the user of the client terminal 10 uses the investment trust management information to execute the cooperation destination business processing in the cooperation destination system 50 .

Note that it may be determined in the cooperation instruction process (step S111) that an application that can be used in the VDI area 21 satisfies the access conditions of the cooperation destination system 50. FIG. In this case, the VDI area 21 of the VDI server 20 directly accesses the cooperation destination system 50 by setting the temporary file argument to the address of the cooperation destination system. Then, the VDI area 21 executes cooperation destination business processing with the cooperation destination system 50 without going through the virtualization server 40 .

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, the client terminal 10 is used to access the VDI server 20 . As a result, application installation, update, and troubleshooting, which have been performed for each client terminal 10, can be performed collectively in the VDI server 20. FIG. In addition, centralized desktop management enables security policies such as reliable application of patches and exclusion of unauthorized applications. In addition, it is possible to strengthen security measures and reduce the maintenance burden on users and administrators.

(2) In the present embodiment, the VDI server 20 executes temporary write permission processing (step S103) and temporary file creation processing (step S104) for each application. As a result, in a VDI environment in which memory usage is restricted, information can be handed over using a temporary file.

(3) In the present embodiment, the customer management system 30 executes a cooperative operation detection process (step S108) and an argument provision process (step S109) required by the cooperation destination. The VDI server 20 then writes the argument to the temporary file (step S110). If the information cannot be handed over via the memory, it is necessary to press a key, but by writing the temporary file, the information can be handed over efficiently and accurately.

(4) In this embodiment, the VDI server 20 executes cooperation instruction processing (step S111). If the application available in the VDI area 21 does not satisfy the access conditions of the cooperation destination system 50, the virtualization server 40 executes cooperation start processing (step S112). As a result, even if the VDI environment does not meet the access conditions of the collaboration destination system 50 , the collaboration destination system 50 can be used in the VDI area 21 via the virtualization server 40 .

(5) In the present embodiment, the virtualization server 40 acquires an argument from a temporary file (step S113), and the virtualization server 40 sets an argument and executes an access process (step S114) to the cooperation destination. Then, the cooperation destination system 50 executes the cooperation destination business process as the second business process (step S115). As a result, the information acquired in the preceding first business process can be efficiently used in the subsequent second business process.

This embodiment can be implemented with the following modifications. This embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
- In the above embodiment, the information acquired in the CRM business process as the first business process is used in the cooperation destination business process (investment trust process) as the second business process. The first and second business processes are not limited to these. It can be applied when the information acquired in the preceding process is used in the subsequent process.

- In the above embodiment, the VDI server 20 holds information about access conditions in the cooperation destination system 50 . Instead of this, information regarding whether or not relaying of the virtualization server 40 is required may be held.

- In the above embodiment, the virtualization server 40 is used when accessing the cooperation destination system 50 from the VDI area 21 . If the VDI environment satisfies the access conditions of all linked systems 50, there is no need to use the virtualization server 40. FIG. Further, even when the access condition is satisfied, the cooperation destination system 50 may be always accessed from the VDI area 21 via the virtualization server 40 .

- In the above-described embodiment, the virtualization server 40 executes the argument acquisition process from the temporary file (step S113). Alternatively, the VDI server 20 may provide the argument recorded in the temporary file to the virtualization server 40 when executing the cooperation instruction process (step S111).

10... Client terminal, 20... VDI server, 21... VDI area, 22... Cooperation support unit, 30... Customer management system, 40... Virtualization server, 50... Cooperation destination system.

Claims (5)

A virtual environment system connected to a first system, a virtualization server, and a second system,
The virtual environment system is
Execute the initialization process to allow the creation of temporary files in the VDI area used by the client,
accessing the first system from the VDI area using a first application;
Acquiring handover information to be provided from the first system to the second system and recording it in a temporary file;
starting a second application on the virtualization server for accessing the second system;
providing the second application with the takeover information recorded in the temporary file;
A virtual environment system, wherein the takeover information is provided to the second system via the second application of the virtualization server. The virtual environment system identifies access conditions to the second system,
providing the takeover information recorded in the temporary file to the virtualization server when the first application does not satisfy the access condition;
2. The method according to claim 1, wherein, if said first application satisfies said access condition, said first application is used to provide said second system with the handover information recorded in said temporary file. Virtual environment system. the virtual environment system identifies applications available to a user;
3. The virtual environment system according to claim 1, wherein the registry of the VDI area permits the identified application to create the temporary file. 4. The virtual environment system according to claim 1, wherein said virtual environment system acquires a customer identifier as handover information from said first system that manages customer information. A method for controlling a virtual environment that takes over information using a virtual environment system connected to a first system, a virtualization server, and a second system, comprising:
The virtual environment system is
Execute the initialization process to allow the creation of temporary files in the VDI area used by the client,
accessing the first system from the VDI area using a first application;
Acquiring handover information to be provided from the first system to the second system and recording it in a temporary file;
starting a second application on the virtualization server for accessing the second system;
providing the second application with the takeover information recorded in the temporary file;
A virtual environment control method, wherein the takeover information is provided to the second system via the second application of the virtualization server.

Images