JP2011248419A - Business computer allotting method and device - Google Patents

Abstract

【Task】
Conventionally, when a user connects to a plurality of virtual machines and uses them, management of connection destination virtual machines and setting of peripheral devices are troublesome.
[Solution]
Correspondence between multiple types of virtual machines, sinker terminals connected to the virtual machines, and scripts that set network devices used by the sinker terminals as default devices, and virtual machines that allow connection of the sinker terminals In addition, a management server having a terminal management DB for managing types of terminals is installed, and a unique terminal identifier is assigned to the sinker terminal. When the sinker terminal presents the terminal identifier and the permitted business content, the management server starts the virtual machine corresponding to the business content, causes the virtual machine to execute a command, and sets the default device etc. The information for connecting to the computer is returned to the sinker terminal.
[Selection] Figure 1

Description

  The present invention relates to a method for managing allocation between a thin client terminal and a business computer.

  By displaying the desktop environment of a business computer using a thin client terminal (hereinafter referred to as a thin client terminal), it is possible to realize an environment in which the same business computer can be accessed from different locations in the organization or from different locations such as at home. Is possible. It has a terminal management DB that manages the correspondence between the business computer that is the connection destination of the sinker terminal and the user who uses the business computer, and when the user ID is presented via the sinker terminal, its use A business computer assignment device that returns an identifier of a business computer that can be used by a user has been put into practical use.

  In addition, although the function of operating the business computer is given to the sinker terminal, it is possible to reduce the risk of information leakage by not permitting data storage.

  The business computer that is the connection destination of the sinker terminal is often created in the form of a virtual computer that can be easily created, maintained, and managed, and stored in a highly secure data center.

  In order to use a peripheral device installed around the sinker terminal, such as a network printer, with a business computer connected using a business computer allocation device, it is necessary to set the identifier of the network printer in the business computer. As a method of performing this setting in the prior art, there is a method disclosed in Patent Document 1. In Patent Document 1, a PC authentication device for authenticating a client is installed in the office of the client PC. The business computer can send a print job to a printer installed in the office, but is normally set so that no printer can print. Each device operates in the following order. (1) The PC authentication device performs mutual authentication with the client PC and acquires its identifier IDa. (2) The PC authentication device notifies the server of the identifier IDa of the client PC and the identifier IDb of the PC authentication device. (3) The server registers a printer in the office where the PC authentication apparatus with the identifier IDb is installed as a printer that can be used by the client PC with the identifier IDa. According to the above flow, when the client PC is connected to the server, the printer in the office where the client PC is located can be used.

US Patent Application Publication No. 2007/0186278

  The conventional business computer assignment device can be controlled to connect to the same business computer when the user moves to another office and accesses the business computer from another sinker terminal. Furthermore, by using the method disclosed in Patent Document 1, it is possible to use a peripheral device having a function of exchanging data with a computer via a network, such as a network printer or a network scanner in an office where a sinker terminal is installed. it can.

  However, since the conventional business computer allocation device does not distinguish between sinker terminals, it is not possible to determine a business computer that can be used for each sinker terminal. For this reason, it cannot be used in a system in which the business content that can be used by the sinker terminal needs to be determined depending on the installation location and time zone of the sinker terminal.

  However, for example, in a bank office, there are cases where a setting is required so that a sinker terminal installed at a specific location (seat) can only be connected to a specific business computer. Alternatively, there are cases where the usage changes depending on the time zone, and the computers that can be connected are also required to change.

  Such a setting cannot be performed by a conventional business computer allocation apparatus. As a solution to this problem, it is conceivable to store business computer information that can be connected to the sinker terminal. However, as described above, in order to increase security, if data storage in the sinker terminal is not permitted, it is possible to store information for each sinker terminal. It is difficult to store information related to connection destination business computers.

  In addition, when there are multiple network devices of the same type in the office, it is effective to improve the work efficiency to make it possible to use the network device closer to the sinker terminal as the default device. However, the conventional technology requires user settings. there were.

  The disclosed system has a feature that the management server has a terminal management DB for managing the business contents that can be performed in each sinker terminal, and can determine a business computer that can be used for each sinker terminal.

  More specifically, in the disclosed system, a unique terminal identifier is given to each sinker terminal, and when the sinker terminal presents the terminal identifier to the management server, the management server connects the sinker terminal to the identifier of the sinker terminal. This is characterized in that a user of the sinker terminal can select a business content to be performed from the business content list.

  Also, when the type of business computer that the sinker terminal wants to connect to is presented to the management server, the management server selects one of the business computers of the presented type and performs default network device settings for the selected business computer. The identifier of the selected business computer is returned to the sinker terminal.

  According to the disclosure, the business contents that can be performed on a thin sync terminal are managed by the management server, so that the system administrator can set or change the business contents that can be performed on a specific sinker terminal by editing the list of business contents. it can. Therefore, it is possible for the system administrator to determine the business contents that can be performed by the sinker terminal according to the installation location without storing information in the sinker terminal.

  Also, when the sinker terminal presents a terminal identifier to the management server, the management server returns a list of the latest business contents so that the system administrator can update the business contents list of the management server or use it on the sinker terminal depending on the time. It is also possible to realize a system that changes the work contents to be performed.

  In response to the presentation of the terminal identifier from the sinker terminal, the default network device is set on the business computer before the management server returns the business computer identifier to the sinker terminal. For this reason, the work of setting the default network device on the business computer by the sinker terminal user can be omitted.

  According to the present invention, it is possible to realize a thin client system capable of limiting the association between a terminal and a computer in accordance with business contents.

It is a figure showing the whole system configuration of the present invention. It is a figure which illustrates the internal structure of the management server in an Example. It is a figure which illustrates the internal structure of the virtualization server in an Example. It is a figure which illustrates the internal structure of the sinker terminal in an Example. It is a figure which illustrates the structure of terminal management DB in an Example. It is a figure which illustrates the structure of the launcher display screen in an Example. It is a flowchart which illustrates the operation | movement sequence of the whole system in an Example. It is a flowchart which illustrates the starting sequence of the virtualization infrastructure in an Example. It is a flowchart which illustrates the completion | finish sequence of the virtualization infrastructure in an Example. It is a flowchart which illustrates the sequence of virtual machine utilization in an Example. It is a flowchart which illustrates the sequence of the launcher initial setting in an Example. It is a flowchart which illustrates the sequence of machine number registration in an Example. It is a flowchart which illustrates the sequence of the connection setting in an Example. It is a flowchart which illustrates the sequence of the cutting process in an Example. It is a flowchart which illustrates the sequence of the proxy terminal connection in an Example. It is a flowchart which illustrates the sequence corresponding to the virtual machine failure in the embodiment. It is a flowchart which illustrates the sequence of the response | compatibility of a sinker terminal failure in an Example.

  In the embodiment for implementing the present invention, a virtual machine is used as a business machine to which a sinker terminal is connected.

  FIG. 1 is a diagram showing the entire system configuration of the present invention. This system assumes that a so-called screen transfer type thin client system is used, and the computer that executes the application program sends the generated desktop screen information to the sinker terminal via the network. In addition to displaying the transmitted desktop screen information on the display of its own terminal, the characters and coordinate information input via the keyboard and mouse of the sinker terminal are transmitted to the computer via the network, so that Configure the machine interface.

  In the virtualization server 112, the hypervisor 141, the account system VMα 133, the account system VMβ 134, the information system VMα 135, and the information system VMβ 136 that are virtual computers operating on the hypervisor 141 operate.

  The management server 111 stores a management program 131 and a terminal management DB 132 used by the management program 131. The management program 131 performs connection control when the sinker terminal A121, the sinker terminal B124, and the like connect to the billing system VMα133, billing system VMβ134, information system VMα135, and information system VMβ136.

  In the account system VMα 133, the account system VMβ 134, the information system VMα 135, and the information system VMβ 136, a client program having a function of connecting to a server program running on the business server 113 operates. The server program that runs on the business server 113 may further communicate with a host program that runs on the host 114. A business system is configured including the above-described client program, server program, and host program. The management server 111, the virtualization server 112, the business server 113, and the host 114 are installed in the data center, are connected to the LAN 101, and are connected to the LAN 103 at a remote site via the WAN.

  The sinker terminal A121 connected to the LAN 103 at the remote site includes, for example, a terminal connection device A122 connected to the chassis using a USB interface, and a network connected to the LAN 103 that is installed at a position physically adjacent to the sinker terminal A121. The connected device A 123 is operated to execute the business system. Similarly, the sinker terminal B124 uses the terminal connection device B125 and the network connection device B126 to execute the business system.

  Assuming that the business terminal system is, for example, a bank terminal counter system, and assuming that a passbook printer or cash machine adjacent to the terminal is a network connection device, operate another bankbook printer or cash machine in the sales office by mistake. It is desirable not to be able to.

  FIG. 2 shows the internal configuration of the management server 111. The terminal 101 includes a processor 201, communication hardware 202, a memory 203, and a fixed disk 204. The processor 201 is hardware having a calculation function for processing data. The communication hardware 131 is a device for network communication such as a NIC (Network Interface Card). The fixed disk 212 is a nonvolatile storage medium (for example, a magnetic disk) that stores data and data processing software (program). The memory 203 is a storage medium used by the processor 201 when executing the program, and may be volatile.

  The fixed disk 204 stores an OS (operating system) 211, a management program 131, and a terminal management DB (database) 132. The OS 211 has a function of controlling the communication hardware 202 and managing the memory 203 and executing the management program 131.

  The server management program 131 has a function for accepting connections from the sinker terminal A121 and the sinker terminal B124 and returning virtual machine information to the sinker terminal A121 and the sinker terminal B124. The terminal management DB 132 has a function of storing data used by the management program 131. The management program 131 includes a DB management unit 221, a launcher response unit 222, and a virtual machine control unit 223.

  The DB management unit 221 has a function for the system administrator to perform initial setting or change of the terminal management DB. The launcher response unit 222 has a function of accepting a connection from the sinker terminal A121 and the sinker terminal B124 and returning the connection to the sinker terminal A121 and the sinker terminal B124. The virtual machine control unit 223 has functions for starting and ending the virtualization server 112 and monitoring connection response status. Further, the virtual machine control unit 223 has a function of monitoring the operation or stopped state of each virtual machine on the virtualization server 112.

  FIG. 3 shows the internal configuration of the virtualization server 112. The virtualization server 112 includes a processor 301, communication hardware 302, a fixed disk 304, and a memory 303. The processor 301 is hardware having a calculation function for processing data. The communication hardware 302 is a device for network communication such as a NIC. The fixed disk 304 is a storage medium (for example, a magnetic disk) that stores data and data processing software (program). A memory 303 is a storage medium used by the processor 301 when executing a program. Although only one virtualization server 112 is shown in FIG. 1, there may be a plurality of virtualization servers 112 in this system.

  The fixed disk 304 stores a hypervisor 141 and a VM group 137 that is a virtual machine used by the hypervisor 141. The VM group 137 includes an accounting system VMα 133 and an accounting system VMβ 134 introduced by accounting software, and an information system VMα 135 and an information system VMβ 136 introduced by information system software. The VM group 137 may store a group of virtual machines introduced by business software other than the account system and the information system. Also, the number of virtual machines for one business content may be two or more. The hypervisor 141 has a function of expanding virtual machines in the VM group 137 on the memory 303 and operating them as if they were one independent computer. The hypervisor 141 has a function of accepting and executing an activation or termination command from the management server 111. The hypervisor 141 has a function of starting and ending virtual machines in the VM group 137.

  The account system VM α 133 stores an OS 321, a remote USB server 322, device setting software 323, and account system software 324. The OS 321 is an operating system that operates in the virtual machine. The remote USB server 322 is software that operates on the OS 321 and has a function for controlling devices of the sinker terminal such as the sinker terminal A121 and the sinker terminal B124. The device setting software 323 is software for performing a default setting of the network device used by the accounting system VM α 133. The accounting system software 324 has a function for the user of the virtual computer α133 to execute business. The internal structure of the billing system VMβ 134, the information system VMα135, and the information system VMβ136 is the same as that of the billing system VMα133. However, information system software is stored in the information system VMα 135 and the information system VM β 136 instead of the account system software 324.

  FIG. 4 shows the internal configuration of the sinker terminal A121 used in the present invention. The internal configuration of the sinker terminal B124 is also the same. The sinker terminal A 121 includes a processor 401, communication hardware 402, memory 403, storage device 404, I / O hardware 405, terminal unique ID chip 406, and device interface 407. The processor 401 is hardware having a calculation function for processing data. The communication hardware 402 is a device for network communication such as a NIC. A memory 403 is a storage medium used by the processor 401 when executing a program. The storage device 404 is a storage medium for storing data and data processing software (program). The medium of the storage device 404 may be a removable external storage medium. Or, a general user may set that writing is impossible. The storage device 404 stores an OS 413, a launcher 412, and a remote USB client 411. The OS 413 has a minimum function for controlling the hardware of the sinker terminal A121. The launcher 412 has a function of managing the connection between the sinker terminal A121 and the virtual machine. The remote USB client 411 has a function of connecting to the remote USB server 322 and transmitting USB device data to the virtual machine. The I / O hardware 405 is a device for the user to operate the terminal, such as a monitor, a keyboard, and a mouse. The terminal unique ID chip 406 is a storage device that stores an identifier uniquely assigned to the sinker terminal. The terminal unique ID chip 406 may be, for example, a trusted platform module (TPM) or a security chip having hardware tamper resistance. The device interface 407 has a data exchange function for using a device directly connected to the sinker terminal A 121 such as a USB device.

  FIG. 5 shows the components of the terminal management DB 132. The terminal management DB 212 includes a table 501 for storing device setting information, a table 502 for storing business types, a table 503 for storing virtual computer information, a table 504 for storing connection status information, and a table 505 for storing device setting scripts. Consists of including.

  The table 501 is composed of a device number field 511 indicating the number of the shop of the sinker terminal and the number within the sales point, and various network device lists used by default in the virtual machine application used by this sinker terminal.

  The network device to be used by default is determined by the administrator according to the convenience of the installation location or the rules in the store. Specifically, the list of network devices includes a default printer field 512 indicating a printer name used by default by a user of the sinker terminal, and a default passbook printer indicating an IP address of a passbook printer used by the user of the sinker terminal by default. It includes a field 513 and a default cash machine field 514 indicating the IP address of the cash machine used by the user of the sinker terminal by default.

  The table 502 includes a business type field 521 indicating the usage of the virtual machine, such as an accounting system, information system, authentication, and foreign exchange, a used device field 522 indicating a device required for the business usage, and a script to be executed by the virtual machine. A script name field 523 for storing a name is included.

  The table 503 performs proxy terminal connection, which will be described later, to the ID field indicating the identification of the virtual machine, the IP address field 532 indicating the IP address of the virtual machine, the type field 533 indicating the use of the virtual machine, and the virtual machine. A proxy terminal connection field 534 indicating whether or not the remote desktop of the virtual machine is connectable, and a use status field 536 indicating whether or not the virtual machine is used by the sinker terminal. Consists of including.

  The table 504 includes a unique ID field 541 for storing an identifier uniquely assigned to the sinker terminal, and a machine number field 542 for storing a device number indicating which branch of which store the sinker terminal is. An accounting system field 543 indicating the identification of the accounting virtual machine used in the sinker terminal, an information system field 544 indicating the identification of the informational virtual machine used in the sinker terminal, and an authentication used in the sinker terminal An authentication system field 545 indicating the identification of the virtual machine, a foreign exchange field 546 indicating the identification of the virtual exchange computer used in the sinker terminal, and a default field 547 indicating the default type used in the sinker terminal are configured. The The default type is the business type connected when the user most recently used the sinker terminal. The next time the user uses the sinker terminal, the launcher 412 automatically connects to the virtual machine of the default business type after a certain time determined in the launcher 412 even if the business type is not selected. , It is possible to save the user input.

  When the account of the account system cannot be used by the sinker terminal, the system administrator sets “not available” in the 543 field of the sinker terminal. Similarly, when the information system, authentication, or foreign exchange is unavailable, “unusable” is set in the fields 544, 545, and 546, respectively.

  The table 505 includes a script name field 551 indicating a script name for setting a default device in the virtual machine, and a script content field 552 indicating a script corresponding to the script name.

  FIG. 6 shows a display screen of the launcher 412.

  An activation screen 601 is displayed when the launcher 412 is activated. An end button 602 has a function of terminating the launcher 412 and turning off the power of the sinker terminal A on which the launcher 412 operates.

  The machine number input screen 611 is a screen shown when the launcher 412 inputs the machine number of the sinker terminal A. The machine number input screen 611 includes an end button 612 and a machine number input box 613. The end button 612 has a function of terminating the launcher 412 and turning off the power of the sinker terminal A on which the launcher 412 operates. The machine number input box 613 has a function of accepting an input of a machine number.

  The job selection screen 621 is a screen that is displayed when the launcher 412 allows the user of the sinker terminal A121 to select a job content. The job selection screen 621 includes a proxy terminal connection button 622, a job selection button 623, a job selection button 624, an end button 625, and a machine number display box 626. The proxy terminal connection button 622 has a function of displaying a proxy terminal connection screen 631 described later. The job selection buttons 623 and 624 have a function of starting a process for connecting to a virtual machine such as an RDP client. When the user presses the job selection button 623, it is possible to connect to the accounting virtual computer corresponding to the machine number 626. Similarly, when the user presses the job selection button 624, it is possible to connect to the information virtual machine corresponding to the machine number 626. The end button 625 has a function of terminating the launcher 412 and turning off the power of the sinker terminal A on which the launcher 412 operates. The machine number display box 626 is an area for displaying a machine number corresponding to the sinker terminal A121.

  The proxy terminal connection screen 631 is a screen displayed when the user presses the proxy terminal connection button 622. The proxy terminal connection screen 631 includes a return button 632 and a business type selection box 633. The end button 632 has a function of hiding the proxy terminal connection screen 631. The business type selection box 633 has a function of displaying a list of virtual machines to which the sinker terminal A121 can connect as a proxy terminal. The proxy terminal connection will be described later. Note that the user can select one virtual machine from the business type selection box 633 and perform proxy terminal connection.

  FIG. 7 is a flow chat showing the operation of the entire system of the present invention. In step 701, the business server 113, the host 114, and the management server 111 are activated as a system activation. The management server 111 activates the management program 131 after the activation is completed. Step 702 is preparation for the management server 111. In step 701, the system administrator stores data in the device setting information table 501, the business type information table 502, the connection status information table 504, and the device setting script table 505 in the terminal management DB 132.

  The system administrator also inputs data into the ID field 531, IP address field 532, and business type 533 of the virtual machine information table 503. With the system ready, the administrator issues an end command in step 703 or starts and uses the virtualization infrastructure in step 705. If a system termination command is received, the business server 113, the host 114, and the management server 111 are terminated in step 708, and the system enters the halt state 708. If there is no administrator termination command, the system proceeds to step 705. In step 705, the virtual machine number is activated and the VM group 137 can be used. In step 706, the system user uses the system. After the system user uses the system, the system terminates the VM group 137 in step 707 and returns to the system administrator command waiting state. Hereinafter, the detailed operation in each step will be described.

  FIG. 8 is a sequence diagram showing a procedure for starting the virtualization infrastructure. First, in step 800, the administrator transmits a virtualization infrastructure usage start command to the management server 111. For example, the administrator may set the virtual infrastructure utilization start command so that the management server 111 automatically sends it to the hypervisor 141 30 minutes before the start of the sales office using the system.

  First, in step 801, the management server 111 transmits an activation command to the hypervisor 141. For example, the function of Wake On Lan can be used. In step 802, the hypervisor 141 is activated. In step 803, the hypervisor 141 activates all virtual machines in the VM group 137. All virtual machines in the VM group 137 enter the startup and connection waiting state in steps 804 and 805. On the other hand, the management server waits for a certain time in step 806 until all virtual machines in the VM group 137 are started up. This time may be about 5 minutes.

  In step 807, the management server 111 transmits a request for confirming the rise of all virtual machines in the virtual machine group 137, and receives a status report in step 808. Confirmation of the rise of the virtual machine may be performed by, for example, a method of sending and replying to Ping. If it can be confirmed that the virtual machines in the virtual machine group 137 have started up, the management server 111 updates the terminal management DB 132 in step 809.

  Specifically, in the table 503, the connection possibility / inhibition field 535 of the record corresponding to the virtual machine that has been activated is set to “OK”, and the record usage status field 536 is set to “waiting”. After confirming the state of all virtual machines, the management server 111 enters a standby state in step 813.

  FIG. 9 is a sequence diagram showing a procedure for ending the virtualization infrastructure. First, in step 901, the administrator transmits a virtual infrastructure use end command to the management server 111. For example, the administrator may set the virtual infrastructure use end command so that it is automatically sent after the end of the operation of the sales office using the system. In step 902, the management server 111 transmits an end command to the hypervisor 141 of the virtualization server 112. The management server 111 enters a standby state in step 908 after transmitting an end command to the virtualization server 112. On the other hand, the hypervisor 141 transmits an end command to all virtual machines in the VM group 137 on the virtualization server 112 in step 903, and then ends in step 907. On the other hand, when all the virtual machines in the VM group 137 receive the end command, the process ends in step 904.

  FIG. 10 is a sequence diagram showing the procedure for using the virtual machine in step 706. Assume that a system user, such as a bank employee, performs a job that uses a sinker terminal.

First, in step 1001, the user turns on the power of the sinker terminal A121.
As a result, the sinker terminal A is activated in step 1002, communicates with the management server 111 in step 1003, and initializes the launcher 412. Details of step 1003 will be described later.

  In step 1004, the sinker terminal A 121 displays the launcher task selection screen 621 and allows the user to be selected from the task selection screen 621. Assume that the user selects a billing system in step 1005. In step 1006, the sinker terminal A121, the management server 111, and the billing system VMα 133 perform connection setting. Details of step 1006 will be described later.

  In step 1007, the login screen of the account VM α 133 is displayed on the sinker terminal A121. Therefore, the user can log in and operate the application in the account system VMα 133. Subsequently, when the user selects an information system from the task selection screen 621 of the launcher 412 of the sinker terminal A121, in step 1009, the sinker terminal A121, the management server 111, and the information system VMα 135 perform connection settings. Details of 1009 will be described later.

  In step 1010, the user of the sinker terminal A121 logs in on the login screen of the information system VMα135 and uses the application of the information system VMα135.

  In step 1011, the user operates the screens of the two billing system VM 133 and the information system VM α 135 at the same time using the sinker terminal A 121 to perform business.

  When the user finishes the job, first, the screen of the accounting VM is erased in step 1012, the information VM screen is erased in step 1014, and the power of the sinker terminal is turned off in step 1016. The cutting settings 1013 and 1015 will be described later. The sinker terminal A121 ends step 1017.

  As shown in FIG. 10, the user of this system opens a plurality of business content screens such as a billing system and an information system on one sinker terminal from the business selection screen 621 displayed by the launcher 412 of the sinker terminal A121. It is possible to operate while switching the operation target.

  FIG. 11 is a sequence diagram showing a launcher initial setting procedure in step 1003.

  First, in step 1101, the sinker terminal A 121 activates the launcher 412. During startup, the launcher 412 shows a screen 601. The launcher 412 may be registered in the start menu of the sinker terminal A121 and set to call the launcher when the sinker terminal A121 is activated. Next, in step 1102, the launcher accesses the terminal unique ID chip 406 and reads the terminal unique ID in the chip. In step 1103, the launcher 412 transmits the terminal unique ID to the management server. The transmission method may use a protocol such as HTTP.

  In step 1104, the management server 111 checks whether the terminal unique ID information received from the sinker terminal A 121 has been registered in the table 504. If the unique ID of the sinker terminal A121 is not already registered in the table 504, a message that it is not registered is returned to the sinker terminal A121. An unregistered sinker terminal can only receive an unregistered message from the management server 111 and cannot connect to a business terminal.

  On the other hand, if the unique ID of the sinker terminal A 121 has already been registered in the table 504, the management server 111 proceeds to the next step 1105. In step 1105, the user registers the machine number. The machine number is information (for example, a number) for indicating the installation location of the sinker terminal. The management server 111 stores the machine number information in the connection status table 504.

  In step 1006, the management server 111 acquires a list of virtual machines used by the sinker terminal A 121 from the table 504 and creates the contents of the job selection screen 621. A method for creating the job selection screen 621 will be described later. In step 1007, the management server 111 transmits the contents of the job selection screen 621 to the sinker terminal A121.

  The management server 111 creates the job selection screen 621 from the table 504 as follows. First, the value of the machine number field 543 corresponding to the terminal unique ID information received from the sinker terminal A 121 is entered in the machine number display box 626. Next, when the value of the account field 543 corresponding to the terminal unique ID information received from the sinker terminal A 121 is not “unusable”, a job selection button 623 called account system is created, and the user presses this button. , The account system field 543 is set so that it can be connected to the account system business computer corresponding to the value. If the information field 544 is not “unusable”, a task selection button 624 for connecting to the information task computer indicated by the value of the information field 544 is created. The same operation is performed for the authentication field 545 and the foreign exchange 546.

  Each time the launcher 412 is started, the step 1103 is executed to download the job selection screen 621. However, the launcher 412 is also periodically updated to update the job selection screen 621, such as every 5 minutes, when the launcher 412 is started. It is also possible. The launcher 412 can also perform step 1103 to update the job selection screen 621 whenever there is an update request from the user, such as when the user of the sinker terminal A121 presses the F5 button.

  FIG. 12 is a sequence diagram showing the procedure for registering the machine number in step 1105. In step 1201, the management server 111 requests a machine number input. The sinker terminal A 121 displays a machine number input screen 611 in step 1202. In step 1203, the user inputs a machine number corresponding to the sinker terminal A. In step 1204, the sinker terminal A121 transmits the machine number information to the management server and hides the machine number input screen 611. In step 1205, the management server 111 uses the machine number received from the sinker terminal A121 to register it in the terminal management DB 132 of the sinker terminal A121 by the following operation.

  (1) The machine number received from the sinker terminal A 121 is stored in the table 504.

  (2) Further, each of the accounting system, information system, authentication system, and foreign exchange virtual machine used by the sinker terminal A121 is selected, and the accounting system field 543, information system field 544, authentication system field 545, and foreign exchange field of the table 504 are selected. In 546, the ID of the selected virtual machine is stored.

  However, when information regarding the sinker terminal A 121 already exists in the table 504, the management server 111 may omit step 1105.

  The sinker terminal A 121 can prevent an external terminal from entering the system by authenticating the terminal unique ID (TPM information or the like) in the chip with the management server 111. In addition, since the authentication work using the terminal unique ID is performed by software called a launcher, the user's input is saved.

  Since the work contents (contents of the work selection screen 621) that can be selected by the user at the sinker terminal are centrally managed by the table 504 of the management server 111, the work contents at the sinker terminal can be changed by the administrator editing the table 504. Easy to do. Therefore, it is possible to adjust the work contents that can be performed on a specific sinker terminal. For example, in a bank office, the sinker terminal at the training seat can be connected only to the training business computer, and the sinker terminal placed at the high counter and low counter can be connected only to the accounting business computer. It becomes like this. Further, by adopting a mechanism in which the unique ID is transmitted to the management server 111 at step 1103 every time the sinker terminal is activated, and the task content selection task selection screen 621 created by the table 504 is received at step 1107, the table 504 becomes When the change is made, the sinker terminal can update the job selection screen 621 with a single restart, thereby realizing a system in which the job contents that can be used by the sinker terminal change frequently with time.

  For example, for training that takes place after regular hours or on weekends, it is possible to temporarily set all the sinker terminals in the sales office to be able to connect only to the training business computer.

  It is necessary to change the contents of the table 504 in order to change the work contents (contents of the work selection screen 621) that can be selected by the user at the sinker terminal. To change the contents of the table 504, the system administrator can directly edit the table 504. In addition, a system administrator uses a daemon process such as cron for automatically executing a job (script), and uses a task for changing each field 543, 544, 545, 546 of the table 504 at a predetermined time. It is also possible. For example, for the training of accounting work after the scheduled time, the fields 544, 545 and 546 of all the terminals are set to “unusable” exactly at the scheduled time, and the task of deleting the “unusable” in the field 543 is executed. , By executing the task of returning the table 504 to the state before the scheduled time at the training end time, it is possible to create an environment for the accounting work training after the scheduled time.

  FIG. 13 is a sequence diagram illustrating a processing procedure for virtual machine setting in step 1006.

  In step 1301, the sinker terminal A 121 transmits an account type virtual computer issuance request to the virtual computer control unit 223 of the management server 111.

  In step 1302, the virtual machine control unit 223 of the management server 111 refers to the table 504 and acquires the ID of the account type virtual machine corresponding to the thin terminal A. In this example, the ID acquired by the virtual machine control unit 223 of the management server 111 in step 1302 is the ID of the account system VM α 133.

  In step 1303, the management server transmits a setting script to the VM. Specifically, the management server 111 acquires the script name corresponding to the account system from the information table 502, refers to the device setting script table 505 using the acquired script name, and acquires the contents of the script. The management server 111 transmits the contents of the acquired script to the account system VM α 133 and executes them.

  As a result of Step 1303, in Step 13311, the application in the account VM α 133 can use the network device corresponding to the thin terminal A in the table 501 as a default.

  In step 1305, the management server 111 changes the usage status field 536 of the accounting system VM α 133 in the virtual machine information table 503 to “in use”, and the accounting status field corresponding to the unique ID of the sinker terminal A 121 in the connection status table 504. The ID of the account system VMα 133 is described in 543.

  In step 1306, the IP address of the accounting system VMα 133 is returned to the sinker terminal A.

  In step 1307, the sinker terminal A 121 performs device connection to the billing system VMα 133. For device connection, specifically, the remote USB client 411 in the sinker terminal A 121 connects to the remote USB server 322 in the accounting system VMα 133. In step 1308, the remote USB server 322 of the billing system VM α 133 accepts connection.

  As a result, the remote USB client 411 and the remote USB server 322 transfer the data from the device connected to the sinker terminal A121 to the billing system VMα133, and transfer the data from the billing system VMα133 to the device connected to the sinker terminal A121. , A device connected to the thin terminal A can be used from the billing system VM α 133.

  In step 1309, the sinker terminal A 121 connects to the accounting system VMα 133 with a screen transfer client such as RDP. In step 1310, the screen of the accounting system VMα 133 is received.

  The processing procedure of step 1009 is the same as that of step 1006. However, in step 1009, the virtual machine to which the sinker terminal A is connected becomes the information system VMα135.

  In step 1303, before the management server 111 transmits the information on the account VM α 133 to the sinker terminal A121, the device setting of the account VM α 133 is performed remotely, so that the default network for the business application in the account VM VM 133 is set. The device uses the device corresponding to the sinker terminal A in the table 501 by default, and no device setting by the user is required.

When the thin terminal A performs step 1307 before step 1310,
When the screen transfer of the account system VMα 133 is started, all the settings related to the device of the account system VM α 133 are completed. This makes it possible to prevent troubles due to incomplete device settings, such as printing to a printer in another location.

  FIG. 14 is a sequence diagram showing the disconnection process in step 1013. First, in step 1401, the thin terminal A 121 disconnects the screen transfer connection to the billing system VMα 133. The screen transfer disconnection may be performed by terminating the screen transfer RDP client. Next, in step 1402, it is detected that the connection for screen transfer is disconnected, and the billing system VMα 133 disconnects the connection for using the terminal connection device A122. The above-described connection is established by the billing system VMα 133 in step 1308. In step 1403, the sinker terminal A121 detects that the connection for using the device A from the billing system VM α 133 is disconnected. In step 1044, the sinker terminal A 121 notifies the management server 111 that the use of the billing system VMα 133 has ended. In step 1405, the management server changes the account system VMα 133 in the usage status field 536 of the virtual machine information table 503 from “in use” to “standby”.

  The processing procedure of step 1015 is the same as that of step 1013. However, in step 1015, the virtual machine to which the sinker terminal A is connected becomes the information system VMα135.

  FIG. 15 is a sequence diagram showing a so-called proxy terminal connection procedure for connecting the sinker terminal B124 as a proxy terminal (or alternative terminal) of the sinker terminal A121 to the billing system VMα 133 to which the sinker terminal A121 is connected. . The proxy terminal connection is a connection from another sinker terminal to the virtual machine instead of a certain sinker terminal.

  First, it is assumed that the user operates the screen of the billing system VM α 133 using the sinker terminal A 121 in step 1500 to execute the business. In step 1521, the user leaves the sinker terminal A121 and moves to the installation location of the sinker terminal B124.

  In step 1501, the user activates the sinker terminal B124.

  In step 1502, the launcher of the sinker terminal B starts up, connects to the management server 111, and performs initial settings. The processing content of step 1502 is the same as that of step 1003.

  Next, the sinker terminal B124 displays the job selection screen 621 received from the management server 111 in step 1503.

  In step 1504, the user presses the proxy terminal connection button 622 in the job selection screen 621.

  In step 1505, when the proxy button 622 is pressed, the sinker terminal B requests the management server for a list of virtual machines that are permitted to connect to the proxy terminal.

  In step 1506, the management server transmits a list 633 of VMs permitted to connect to the proxy terminal to the sinker terminal B 124. The VM that permits proxy terminal connection is a VM whose proxy terminal connection field 534 is “permitted” in the table 503.

  In step 1507, the sinker terminal B124 that has received the list 633 displays the proxy terminal connection screen 631.

  In step 1508, the user selects a billing system VM α 133 from the VM list 633 in the proxy terminal connection screen 631.

  In step 1509, the sinker terminal B 124 transmits a proxy terminal connection request to the accounting system VMα 133 to the management server 111.

  In step 1510, the management server 111 disconnects the sinker terminal A121. The processing at step 1510 is the same as that at step 1013.

  Next, in step 1511, the management server 111 connects the sinker terminal B 124 to the billing system VMα 133. The processing in step 1511 is the same as in step 1006.

  In step 1512, the user logs in to the account system VMα 133, and in step 1513, the user uses an application in the account system VMα. On the other hand, the sinker terminal A disconnects the connection with the accounting system VMα 133 in step 1510, displays the launcher task selection screen in step 1514, and enters a task content selection waiting state.

  Note that a user who can log in to a specific virtual machine is determined by the system administrator, and therefore, one user cannot take another user's virtual machine without the permission of the system administrator. A directory service may be used to determine who can log in to a specific virtual machine.

  With the proxy terminal connection function, the user can connect to the virtual machine in use from another thin terminal, away from the used sinker terminal, and continue the business. Further, in step 1511, the device used in the virtual machine is also switched to the sinker terminal connected to the proxy terminal, so that the user is not required to manually set the device.

  If a salesclerk operates the sinker terminal A121 and the sinker terminal A121 breaks down while handling a customer, the conventional system continues to handle the customer while waiting for repair or replacement of the sinker terminal A Can not. Therefore, the agent terminal connection function allows the bank clerk to guide the customer to the counter next to the sinker terminal B124 and call the business screen being used at the sinker terminal B124 to continue the customer service smoothly. .

  FIG. 16 shows a processing flow of the system when the information system VMα135 is stopped due to a failure or an urgent system change while the sinker terminal A121 is connected to the information system VMα135.

  First, in step 1601, it is assumed that the user is using the information system VM α 135 at the sinker terminal A121. In addition, it is assumed that the information system VM β 136 has been activated and is in a standby state in step 1602. Therefore, in step 1604, the operating information system VMα 135 is stopped due to a failure or an administrator's operation. In step 1604, the sinker terminal A121 disconnects the screen transfer connection, and the screen of the information system VM α 135 stops. In step 1605, the user's work is interrupted. On the other hand, the virtual machine control unit 223 of the management server 111 finds that the connection of the information system VM α 135 is impossible in step 1606 by the VM monitoring function. For monitoring the VM, for example, a mechanism for periodically checking the response of the VM with a Ping command may be used. In step 1607, an information system VMβ 136 for the sinker terminal A is prepared. The processing procedure of step 1607 is the same as that of step 1006.

  In step 1608, the sinker terminal A121 that has been disconnected from the information system VM α 135 makes a request for the information system VM to the management server 111 again. In step 1609, the management server 111 connects the sinker terminal A 121 to the information system VM β 136. The processing procedure of step 1609 is the same as that of step 1006. In step 1610, the sinker terminal A 121 connected to the information system VM β 136 develops the screen of the information system VM β 136 to the user, and the user logs in to the information system VM β 136. In step 1611, the user resumes the work on the screen of the information system VM β 136.

  When the management server 111 finds that the virtual machine being used is stopped, it prepares a virtual machine having the same job as the virtual machine stopped in step 1607 and switches the connection destination of the sinker terminal to the newly prepared virtual machine for a short time. This eliminates the need for settings by system users and administrators, and allows users to continue their work.

  FIG. 17 shows a processing procedure in the case of replacing a sinker terminal being used by a user.

  In step 1701, the user uses the sinker terminal A121 to operate the screen of the billing system VM α 133 for business. In step 1702, the sinker terminal A121 stops due to failure or termination by the user. In step 1703, the connection from the sinker terminal A121 to the billing system VMα 133 is disconnected. In step 1704, the billing system VMα 133 in which the connection from the sinker terminal A is disconnected enters a standby state.

  On the other hand, the user who notices the failure of the sinker terminal A121 in step 1705 or who has finished the sinker terminal A121 replaces the sinker terminal A with the sinker terminal B in step 1706 and activates the sinker terminal B. In step 1707, the sinker terminal B is activated, and in step 1708, TPM information is transmitted to the management server 111. In step 1709, the user registers the machine number of the sinker terminal A. The processing content of step 1709 is the same as that of step 1104.

  In step 1710, the management server 111 that has received the machine number of the sinker terminal A121 transmits the job selection screen 621 of the sinker terminal A121 to the sinker terminal B124. In step 1711, the user selects business contents at the sinker terminal B, connects to the accounting system VMα 133, and operates the screen immediately before replacing the sinker terminal 121 again.

  When the sinker terminal is replaced, the user can restore the business environment before the replacement with the new sinker terminal only by inputting the machine number in step 1709. In this system, the job selection screen 621 is not stored in the sinker terminal, but is managed by the management server 111, so that the job environment can be restored in a short time even if the sinker terminal is replaced.

  As described above, in the present embodiment, a virtual machine capable of performing a selected job can be connected simply by selecting a job content presented by the user of the sinker terminal. It is also possible to select multiple business contents and perform business simultaneously on multiple screens.

  In addition, each identification / recognition information is stored in the sinker terminal and authentication is performed by software when the sinker terminal is activated, so that an unregistered sinker terminal can be prevented from entering the system.

  Further, since the task selection screen 621 of the sinker terminal is centrally managed by the management server, the administrator can easily change it.

  Further, the IP network compatible device that is used by default by the virtual machine without the need for user settings is optimal for the location of the thin-filmer terminal that is the connection source.

  In addition, even if the virtual machine is changed, the device is reconfigured on the management server, so no user settings are made.

  Further, according to the proxy terminal connection function of the present embodiment, it is possible to take over the business screen being used from a sinker terminal installed at a location away from the sinker terminal being used by the user.

  In addition, when a failure occurs in a virtual machine that is connected to a sinker terminal, the management server switches the sinker terminal to another virtual machine, so the user's work interruption time is short and no user settings are required.

  In addition, if the sinker terminal needs to be replaced due to a failure or device change, after replacing the sinker terminal, it is possible to connect to the business screen before replacement simply by entering the machine number indicating the location of the sinker terminal. it can.

  In this embodiment, the connection destination of the sinker terminal is a virtual computer, but the connection destination is not limited to the virtual computer. For example, if the connection destination of the terminal is a general-purpose computer or a terminal server that can be shared by a plurality of users, this embodiment may be applied to functions other than the virtualization platform activation and termination functions.

Claims (9)

A computer system comprising an operated computer connected to the operated computer and an operated computer for operating the operated computer, and a management server for managing a connection between the operated computer and the operated computer Because
The management server
A management DB that manages the correspondence between identification information for identifying the operating computer, business content that can be operated on the operating computer, and the operated computer that processes the business content;
Refer to the management DB,
For the identification information acquired from the operation side computer, present the business contents that can be operated by the operation side computer,
According to the business content selected by the operating computer, determine the operated computer to which the operating computer is connected,
A computer system, characterized in that the operating computer is connected to the determined operated computer. The computer system according to claim 1,
The management server
Connect one operating computer to multiple operated computers in parallel,
The operating computer receives and displays a screen of processing results in each of the operated computers from a plurality of the operated computers. The computer system according to claim 1 or 2,
The operating computer is
With a unique terminal identifier,
The unique terminal identifier is registered in the management server before the use of the operating computer, and the operating computer obtains connection permission to the computer by presenting the unique terminal identifier to the management server. A featured computer system. A computer system according to any one of claims 1 to 3,
The management server manages a list of one or more business contents that can be operated by the operating computer with the management server,
A computer system, wherein the list is downloaded from the management server when the operating computer starts, when requested by the operating computer, or periodically. A computer system according to claim 4, wherein
Before the management server connects the operating computer to the operated computer, a network connection device determined in advance by an administrator for the operating computer can be used as a default in the operated computer. A computer system characterized by setting. A computer system according to claim 5, wherein
Before the operation side computer transfers the screen from the operated side computer, the terminal connection device of the operating side computer can be used as if it were directly connected from the operated side computer to the operated side computer. A computer system characterized by setting as follows. A computer system according to claim 6, wherein
An alternative operation side computer is provided, and the operation side computer can be connected to the operated side computer instead of the operation side computer while the operation side computer is connected to the operated side computer. Computer system to do. A computer system according to claim 7, wherein
When the operating computer is stopped while the operating computer is connected to the operated computer,
A computer system, wherein the management server prepares an alternative operated computer that provides the same business as the computer, and connects the operating computer to the alternative operated computer. A computer system according to claim 7 or 8,
While the operating computer is connected to the operated computer, if it is necessary to replace the operating computer with a spare terminal due to a failure or a device change, A computer system characterized in that the spare terminal can be connected to the operated computer only by inputting information.

Images