JP2006120036A - Transaction transfer system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a transaction transfer system capable of load distribution even in an environment where all connected processing servers cannot uniformly process transactions.
In a load balancing transaction processing system configured by connecting a plurality of processing servers 10 together with a terminal 20 on a network 30, the processing server 10 transfers a transaction input from the terminal to another processing server. A transaction transfer distribution unit 102 for determining necessity, and a transaction transfer determination application 104 that can be set by a user for transaction transfer conditions in addition to the CPU load information acquisition unit 103, Even in an environment where a part of the processing server cannot process a part of the input transaction, the optimum load distribution can be performed.
[Selection] Figure 1

Description

  The present invention relates to a system for executing transaction processing for distributing a load using a plurality of computers, and more particularly to transfer control of a transaction program.

In distributed transaction processing in conventional client / server type online transaction processing, load is reduced by distributing transaction processing messages based on the CPU usage rate of multiple processing servers and the average CPU usage time for each transaction. Distributed. In addition, as an example of this kind of technique, the following patent document 1 is mentioned, for example.
JP 2003-296289 A

  By the way, the distributed transaction system according to the prior art is constructed on the assumption that a transaction can be processed in the same manner regardless of which processing server is distributed among a plurality of processing servers constituting the system. Yes. In other words, each processing server that constitutes the system must have the same processing capability as other processing servers. Therefore, when only some processing servers lack the processing capability. There is a problem that it is impossible to construct the load balancing transaction system.

  This is because, for example, there are restrictions on the databases that can be accessed by transactions, so if the processing servers that can be processed are limited, the distribution destination server cannot execute the transaction processing, so a transaction transfer system is constructed. Because it becomes impossible.

  In the distributed transaction system according to the conventional technique, for example, the CPU load information of each processing server constituting the system is collected to calculate the usage rate, and load distribution is performed based on the calculated CPU usage rate. In addition, a means for notifying CPU load information between servers in the system is necessary, and further, in order to notify the CPU load information, the CPU load increases not a little.

  In addition, in the distributed transaction system according to the conventional technique described above, transactions are distributed by an algorithm provided by the transaction transfer system for determining CPU load information of each server system. Therefore, the user cannot change the load distribution algorithm provided by the transaction transfer system. Therefore, for example, depending on the input transaction, it may be preferable for the user to select a system (server) to be distributed to. However, in the conventional distributed transaction system described above, depending on the user's judgment There is also a problem that the system (server) to be a distribution destination cannot be changed.

  Therefore, the present invention has been achieved in view of the problems in the prior art described above, and the object thereof is that all of the plurality of processing servers connected on the network are all uniform as described above. An object of the present invention is to provide a load balancing transaction system that can be constructed even in an environment where transactions cannot be processed.

  Another object of the present invention is to provide a load balancing transaction system in which a user can appropriately change the transaction transfer determined by the load balancing system.

  In order to achieve the above object, according to the present invention, first, there is provided a load balancing transaction processing system configured by connecting a plurality of processing servers together with a terminal on a network, wherein a part of the plurality of processing servers is input. In some of the transactions that cannot be processed, the processing server includes means for determining whether or not the transaction input from the terminal needs to be transferred to another processing server. There is provided a transaction transfer system including a transaction transfer determination means that can be set by a user with respect to the conditions for transferring the transaction.

  Further, according to the present invention, in the transaction transfer system described above, the transaction transfer determination means that can be set by the user is input based on an input source terminal name and / or an input transaction name that is a name of the terminal. It is possible to determine whether or not to transfer a transaction, or to set a transfer destination of a transaction that is input according to the resource in the processing server constituting the transaction transfer system, or It has definition means that can set transfer conditions in advance based on statistical data on the CPU load of the processing server that constitutes the transaction transfer system, and whether transfer of transactions is necessary or not according to the preset setting conditions by the definition means. Judgment and load balancing It is preferable that.

  Furthermore, according to the present invention, in the transaction transfer system described above, the means for determining the necessity of transfer to the other processing server is based on the CPU utilization rate of each processing server constituting the transaction transfer system. It is preferable that they are determined.

  That is, according to the transaction transfer system according to the present invention described above, in some of a plurality of processing servers constituting the processing system, for example, due to a difference in resources, depending on an input source terminal or an input transaction. Even when the system capable of processing the transaction is limited, a specific processing system can be excluded from the transaction transfer target, or only the process server that can be processed can be the transaction transfer target. As described above, it is possible to provide a load balancing transaction system that can be constructed even in an environment where all transactions cannot be processed uniformly.

  Note that the CPU load information is not used as a determination factor for determining whether or not to transfer a transaction, that is, it is possible to determine whether or not to transfer a transaction based on a definition set in advance based on statistical data related to CPU load and perform load distribution. It is possible, and according to this, it is possible to suppress an increase in CPU load especially for collecting CPU load information information.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 is a block diagram showing an example of the configuration of a transaction transfer system according to an embodiment of the present invention.

  As shown in FIG. 1, the transaction transfer system according to the present invention includes a plurality of processing servers 10 operating in parallel (parallel) and a plurality of terminals 20. Note that the plurality of processing servers 10 and the terminals 20 are connected to each other via, for example, the network 30. Each of the processing servers 10 includes, as its constituent elements, at least a main storage device 100 and a CPU (Central Processing Unit) 200 that constitutes an arithmetic processing unit, a part of which is defined in detail below. It has information 300. Here, for example, when a part of transaction processing cannot be performed due to a resource or the like, all of the plurality of processing servers 10 connected on the network 30 are uniformly transmitted from the terminal 20. Not all transactions can be processed. Specifically, for example, as will be described in detail later, the predetermined database processing is an environment in which only a part of the plurality of processing servers 10 constituting the transaction transfer system can be processed. .

  Further, as is apparent from the figure, the main storage device 100 is a communication storing a program for managing communication executed with other processing servers 10 and terminals 20 via the network 30. A transaction transfer system is configured including the management unit 101, for example, a transaction transfer distribution unit 102 that stores a program for executing transaction processing for distributed processing of loads input from the terminals 20, and the server 10. The CPU load information acquisition unit 103 storing a program for acquiring the load information of the CPU 200 constituting the other server 10, and a program for determining transaction transfer, as will be described in detail later. And a stored transaction transfer decision application 104. Communication between the processing server 10 and the terminal 20 connected to the network 30 or another processing server 10 is performed via the communication management unit 101 described above.

  The definition information 300 is also composed of a storage device, and, as shown in the figure, the details will be described later, but other system information definition 301, transfer condition definition 302, transfer destination A system definition 303 and a CPU load balance definition 304 are provided.

  In the configuration of the processing server 10 described above, the transaction transfer distribution unit 102 performs a distribution process of transactions input from the terminal 20 connected to the network 30 via the communication management unit 101 described above. However, this transaction distribution is performed based on information from the definition information 300, the CPU load information acquisition unit 103, and / or the transaction transfer determination application 104. Whether or not processing is to be performed within the server, and if processing is not performed within the server itself, is determined by determining which processing server (distribution destination) of the other processing server 20 is to transfer the transaction.

  On the other hand, the CPU load information acquisition unit 103 acquires the CPU usage rate of each processing server included in the transaction transfer system connected to the network 30, and uses the acquired CPU usage rate as the transaction transfer distribution unit 102. Is provided as information on the CPU usage rate.

  Further, the transaction transfer determination application 104 described above is based on the CPU utilization rate information of each processing server described above and / or the input transaction information based on the information on the distribution destination determined by the transaction transfer distribution unit 102. Provides an interface for changing (determining) the distribution destination. According to this, the user can create a transaction transfer determination application 104 for distributing and transferring transactions, for example, according to the business contents, which will be described later. That is, according to the transaction transfer determination application 104, the user can freely tune the transaction transfer method as appropriate in accordance with, for example, the necessity or speciality thereof.

  Next, the definition information 300 is composed of the system information definition 301, the transfer condition definition 302, the transfer destination system definition 303, and the CPU load balance definition 304, as described above. An example is shown in the attached FIGS. Each of these definitions will be described in detail below.

First, an example of the system information definition 301 will be described with reference to FIG.
This system information definition 301 includes “own system name” 401 and “other system name” 402. Specifically, the “own system name 401” defines a system name used by each processing server 10 to identify its own system. In the example of FIG. 2, “SYSTEM1” is defined as “own system name”. On the other hand, “other system name” 402 defines the name of another system that is a candidate for a transaction transfer destination. In the case of the example in FIG. 2, systems that are other processing servers are defined as the names “SYSTEM2”, “SYSTEM3”,...

  Next, an example of the transfer condition definition 302 will be described with reference to FIG. In the example shown in FIG. 3, the definition regarding the terminal (“terminal definition” 501) to which the transaction is input and the transaction to be transferred (“transaction definition” 502) are displayed together with the “name” 503 and “transfer”. It is defined by “existence of target” 504.

  That is, the transfer condition definition 302 includes a “terminal definition” 501 and a “transaction definition” 502. The “terminal definition” 501 defines information about a plurality of terminals 20 connected to the processing server 10. For example, in the “name” 503 of the terminal, a terminal name for identifying the terminal is defined. In the example of FIG. 3, “TERMA”, “TERMAB”, and “TERMMC” are defined as a plurality of terminals connected to the processing server 10. Also, “TRANA”, “TRANB”, and “TRANC” are defined as the input transactions.

  Further, “Transfer target presence / absence” 504 designates whether or not a transaction input from the corresponding terminal is to be transferred. In other words, if it is not subject to transfer here (specifically, “transfer” is not defined and is left blank), the transaction input from the corresponding terminal is always in the local system of the processing server. It means that it is processed by. On the contrary, when it is a transfer target here (specifically, “transfer” is defined), it is possible to transfer a transaction including not only the own system but also other processing server systems, Therefore, it becomes possible to process the transaction with an optimum system. In the case of the example in FIG. 3, the above “TERMA” and “TERMMC” are terminals to be transferred.

  In the “transaction definition” 502, information about a transaction input from each terminal 20 is defined. More specifically, the “name” 503 includes, for example, a transaction name as information for identifying the input transaction, and the “transfer target presence / absence” 504 includes the input transaction. Specify whether or not to transfer. Note that here again, if the transaction is not to be transferred (specifically, “transfer” is not defined and is left blank), the input transaction must be processed within its own system. Means that On the other hand, when the transaction is to be transferred here, the transaction can be transferred not only in the processing server's own system but also in the other processing server's system. Can be processed. In the example of FIG. 3, “TRANA” and “TRANC” are defined as transactions to be transferred.

  Next, an example of the transfer destination system definition 303 will be described with reference to FIG. In the example shown in FIG. 4, the correspondence between the above-described transaction and the system of the work server 10 that is the transfer destination is defined as being defined.

  First, the “transaction name” 601 is defined by specifying its name from the transactions defined in the “transaction definition” 502 shown in FIG. Specifically, here, two transactions “TRANA” and “TRANB” are defined.

  On the other hand, in the “transfer destination system” 602, candidates for the transfer destination of the input transaction are defined by the system name of the work server 10. Specifically, in the example of FIG. 4, for the transaction whose name is “TRANA”, two work servers “SYSTEM2” and “SYSTEM3” are candidates for the transfer destination. For a transaction whose name is “TRANB”, only one work server “SYSTEM3” is a candidate for the transfer destination. In this way, for each input transaction, it is possible to define a transfer destination system. For example, a database required for processing a transaction named “TRANB” Such a definition is effective when it does not exist in the work server with the name “SYSTEM2” constituting the system, but exists in “SYSTEM3” which is another work server. And according to this, it is possible to construct a load balancing transaction system that can process transactions with an optimal system even in an environment where all transactions cannot be processed uniformly. Become.

  Next, an example of the CPU load balance definition 304 will be described with reference to the attached FIG. As is apparent from the figure, the CPU load balance definition 304 includes, for example, “CPU load information use / non-use” 701, “CPU load information collection interval” 702, “load distribution threshold upper limit” 703, and “load Dispersion threshold lower limit "704.

  First, in the “CPU load information use presence / absence” 701, the CPU load information from the CPU load information acquisition unit 103 described above is used to specify whether or not to perform transaction transfer. If “use” is designated in the “use / non-use of CPU load information” 701, the necessity of transaction transfer is determined based on the CPU load information of each system of the work server 20 constituting the load balancing transaction system. Judgment is made. On the contrary, when “unused” is designated here, the load information acquisition process by the CPU load information acquisition unit 103 described above does not operate, and in accordance with the instruction of the transfer condition definition 302 shown in FIG. Therefore, it is determined whether or not the transaction transfer is necessary.

  Here, when the CPU load information is used, a process for collecting the CPU load information (that is, a load information acquisition process) operates. Therefore, the load on the CPU 200 for the processing increases. Therefore, for example, when the user decides to suppress the increase in CPU load necessary for collecting the CPU load information, the “CPU load information used / not used” 701 designates “unused” to specify the CPU load information. The load information acquisition process by the acquisition unit 103 does not operate, and instead, for example, the user himself / herself creates a load distribution scenario based on the statistical data on the CPU load and the like, and the transfer condition definition 302 of FIG. It is also possible to set in advance.

  Further, when “use” is designated in the “use / non-use of CPU load information” 701, “CPU load information collection interval” 702, “load distribution threshold upper limit” 703, and “load distribution The definition of “threshold lower limit” 704 is also made. In the “CPU load information collection interval” 702, an interval time for collecting the CPU load information is specified in units of seconds, for example. The shorter this “CPU load information collection interval” is, the more real-time CPU load information can be ascertained, so that more accurate load distribution can be achieved. Therefore, the load of the CPU 200 is increased only by that amount, that is, only the processing necessary for collecting the CPU load information. On the other hand, by setting this “CPU load information collection interval” long, it is possible to reduce the increase in CPU load. However, however, it relates to CPU load information of a system constituting another work server in the transaction transfer system. As a result, a time lag occurs, making it impossible to grasp the CPU load information of each system in real time, and it is difficult to accurately distribute the load.

  Further, in the “load distribution threshold upper limit” 703, the upper limit value of the CPU utilization rate, which is a reference for determining that the own system is overloaded, is set. According to this, when the CPU usage rate of the own system exceeds the above-mentioned “load distribution threshold upper limit” 703, the transaction transfer necessity determination is performed based on the CPU usage rate of the other system. It becomes.

  In addition, the “load distribution threshold lower limit” 704 is used to determine that the overload state has ended when the CPU usage rate has decreased after the system has been determined to be overloaded as described above. Set the reference CPU utilization. In the case of FIG. 5, when the CPU usage rate exceeds 50%, it is determined that the CPU is overloaded. When the CPU usage rate is below 30%, it is determined that the CPU is released from the overload state. If it is determined that the overload state has been released, the transfer of the transaction ends.

  Next, the operation for performing transaction transfer necessity in the transaction transfer system according to the present invention, the configuration of which has been described in detail above, will be described in detail with reference to FIGS. 6 and 7. 6 and 7 are so-called flowcharts showing the flow of processing for determining whether transaction transfer is necessary, which is executed by the processing server 10 described above.

  When the process starts, as shown in FIG. 6, first, a transaction is input from the terminal 20 to the processing server 10 via the communication management unit 101 (step 801). Then, in the processing server 10, the processing of the transaction transfer distribution unit 102 runs (starts).

  First, the transaction transfer distribution unit 102 checks, based on the transfer condition definition 302, the terminal that is the input source of the transaction process and whether the input transaction satisfies the transfer condition (steps 802 and 803). . Here, in the transfer condition definition 302 used for transfer determination, as described above with reference to FIG. 3, the input source terminal and the transaction to be transferred are defined. For example, when the terminal name of the input source is “TERMA” and the name of the transaction input there is “TRANA”, both satisfy the above transaction transfer conditions (“Y” in the figure). Therefore, the process proceeds to step 804. On the other hand, if the input source terminal or the input transaction does not satisfy the above transaction transfer condition (“N” in the figure), the transaction server 10 is not transferred and the processing server 10 that has input the transaction processing However, it performs processing in its own system (step 805) and then ends.

  If it is determined in the above step 803 that the input transaction satisfies the transaction transfer condition 302 described above (“Y”), the CPU load balance definition 304 (see FIG. 5) described above is set. The defined CPU load information is checked (step 804), and further, it is determined whether or not the CPU load information should be used (step 806). As described above with reference to FIG. 5, the CPU load balance definition 304 specifies that the CPU load information is to be used ("Use" is set in "CPU load information use / not used"). In this case, the process proceeds to step 807. In step 807, the CPU load information acquisition unit 103 constituting the main storage device 100 of the processing server 10 shown in FIG. 1 is activated to acquire the current CPU utilization rate in the system of the processing server itself (step 807). 807).

  Thereafter, when it is specified that the CPU load information is to be used, the processing server further checks whether or not its own system is in an overload state (step 808). In this case as well, the “load distribution threshold upper limit” 703 in the CPU load balance definition 304 described with reference to FIG. 5 is used. That is, whether or not the own system is in an overload state is determined by the upper limit value specified in the CPU load balance definition 304 and the acquired transition of the current CPU utilization rate. As a result, if it is determined that the own system of the processing server 10 is in an overload state (“Y”), the process proceeds to step 809. On the other hand, if it is determined that the local system is not overloaded (“N”), the processing of the input transaction is determined by the local system, that is, the processing server 10 itself (step 811). The process proceeds to step 901 described below with reference to FIG. In addition, when it is specified in the above step 803 that the CPU load information is not used (“use” is not set in “use / non-use of CPU load information”), the above steps 807 and The process of 808 is skipped and the process proceeds to step 809 as described above.

  In this step 809, it is checked whether there is another system (other processing server 10) that can be transferred. As a result, if it is determined that there is another transferable system (“Y”), the transfer destination system of the input transaction is determined (step 809). At this time, if the use of the CPU load information is specified, the CPU usage rate of the transfer destination system candidate specified in the transfer destination system definition 303 (see FIG. 4) described above is the highest. A low system (work server) is determined as the transfer destination system. On the other hand, when the non-use of the CPU load information is specified, the transfer destination system (work server) specified in advance in the transfer destination system definition 303 is determined as the transfer destination system.

  On the other hand, if it is determined that there is no other transferable system (“N”), the processing system of the input transaction is determined to be the processing server 10 itself in step 811, and The process proceeds to step 901 described below with reference to FIG. Further, even when the own system is not overloaded in step 808 or when it is determined that there is no other system that can be transferred in step 809, the transaction is not transferred and processed by the own system. The decision to do is as described above.

  Next, referring to FIG. 7 attached, that is, after the system determines whether the transaction transfer is necessary, it further checks whether there is a transaction transfer determination application 104 (step 901). If determined, the transaction transfer determination application is called (step 902).

  Here, the transaction transfer determination application 104 is, for example, from the name of the transaction input at the input source (see, for example, “transaction definition” 502 in FIG. 3), as schematically shown in FIG. A transaction is determined (in the example of the figure, for example, “TRANA”, “TRANB”, “TRANC”, etc.). Thereafter, whether or not to change the transfer destination system (work server) determined by the transaction transfer system according to the name of the terminal that has input the determined transaction (see, for example, “terminal definition” 501 in FIG. 3). To decide. In this example, for example, a database (DB-A) for processing “TRANA” among the transactions “TRANA”, “TRANB”, and “TRANC” from the terminals A, B, and C is a system (work server). ) If it exists only in SYSTEMA, the process of the transaction “TRANA” is always transferred to the system “SYSTEMA” regardless of the status of other systems. The transaction transfer operation at this time is shown in FIG.

  Note that the above-described transaction transfer determination application 104 can be arbitrarily created by the user. According to the transaction transfer determination application 104, all of the plurality of processing servers 10 are uniformly transmitted from the terminal 20. Even in an environment where the transaction cannot be processed, the transaction transfer system determination determined by the transaction transfer system is changed, or the designated transfer destination system is changed as appropriate. Therefore, it is possible to realize a transaction transfer process that is optimal and suitable for the environment.

  Subsequently, when the control returns from the transaction transfer determination application 104 to the system (that is, the application is terminated), it is checked again whether or not the transaction is to be transferred to another system (step 903).

  Here, when the transaction transfer determination application 104 specifies that the transaction is transferred to another system (“Y”), the transfer destination system is changed as necessary (step 904). Then, the transaction is transferred to the other system (step 905), and the process ends. On the other hand, when the transaction transfer determination application 104 designates processing in the own system, the transaction is processed in the own system (step 906), and then ends.

  Next, an example of the input / output interface of the transaction transfer determination application 104 will be described with reference to FIG. The example shown in FIG. 10 shows the input / output interface 1000 of the transaction transfer decision application 104.

  As is apparent from FIG. 10, the input / output interface 1000 of the transaction transfer determination application 104 includes an “input source terminal name” 1001, an “input transaction name” 1002, a “transfer necessity” 1003, and a “transfer” It consists of “destination system name” 1004 and “system information” 1005.

  In the above configuration, “input source terminal name” 1001 displays the input source terminal name, and “input transaction name” 1002 displays the name of the input transaction as information. Is sent to the transaction transfer decision application 104. In the “transfer necessity / unnecessity” 1003, as indicated by step 902 in FIG. 7, the transaction determined by the transaction transfer system before the control is transferred to the transaction transfer determination application 104 (that is, the application is started). Set whether or not to execute the transfer. That is, “necessary” is set when transaction transfer is performed in advance, and “no” is set when processing is performed in the own system. Further, in the “transfer destination system name” 1004, the system name of the transfer destination determined by the transaction transfer system is set. If “No” is set in “Transfer Necessity” of the transaction, the system name of the own system is set.

  Further, according to the transaction transfer determination application 104 described above, by referring to the “transfer necessity” 1003 and the “transfer destination system name” 1004, the input transaction is about to be transferred to any system. You can know if you are.

  In the lower part of the figure, system information 1100 is shown, whereby information on each system constituting the transaction transfer system including the information on the own system is provided to the transaction transfer determination application 104. Will be. The system information 1100 includes “system name” 1101, “own / other category” 1102, “status” 1103, “load status” 1104, and “CPU usage rate” 1105.

  First, in “system name” 1101, a list of system names of each system defined in “other system information definition” 301 in FIG. 2 is set. In the “own / other category” 1102, “self” is set for the own system, and “other” is set for the other system. In the “status” 1103, it is set whether each system is in an “online” state or a “stopped” state.

  In the “load state” 1104, each system determines whether the determination result based on the information defined in the “CPU load balance definition 304” shown in FIG. 5 is an “overload” state, Whether the state is “normal” is set. Further, the “CPU usage rate” 1105 is set to the CPU usage rate of each system. However, if the “CPU load balance definition” 304 specifies that CPU load information is not collected (“use” is not set in “use / non-use of CPU load information” 701), the above “ No information is set in the “load state” 1104 and the “CPU usage rate” 1105.

  As described above, according to the transaction transfer determination application 104, all of the plurality of processing servers 10 constituting the transfer system uniformly process all transactions based on various information provided by the transaction transfer system. Even in an environment where it is not possible to do so, it is possible to check whether the transfer of the transaction is necessary and the validity of the transfer destination system. However, the area that can be set by using the transaction transfer determination application 104 is only the “transfer destination system name” 1004 as described above. Therefore, when this transfer destination system is changed, it is necessary to set the changed system name in the “transfer destination system name” 1004. On the other hand, when the transaction transfer destination system set by the transaction transfer system is not changed, the transaction transfer determination application 104 may be set so as to end without doing anything for the transaction transfer destination. Similarly, when the transaction transfer system determines that transaction transfer is unnecessary, and the processing is performed by the local system as determined by the system, the application may be terminated without doing anything as described above. It becomes.

  On the other hand, the transaction transfer system determines that the transfer of the transaction is unnecessary. However, when the transaction is changed to transfer the transaction, the transfer destination system name is set in the “transfer destination system name” 1004 described above. . As described above, according to the transaction transfer determination application 104, a detailed transaction can be performed by changing the “transfer destination system name” 1004 as necessary while referring to the state of each system constituting the transaction transfer system. The transfer can be tuned.

  As described above in detail, according to the embodiment of the present invention, not all the input transactions are subject to transaction transfer, and whether or not transaction transfer is performed is determined by the input source terminal name and the transaction name. Because it can be specified, even in some systems (work servers) that constitute the transfer system that is the transaction transfer destination, even if some transaction processing cannot be performed due to resource problems, etc. It is possible to construct a transaction transfer system that can transfer the processed transaction processing to an optimum system (work server) as appropriate. In other words, in the prior art, when trying to construct a transaction transfer system, it was assumed that all processing servers that construct the system could uniformly process the transferred transaction. On the other hand, according to the present invention, it is possible to introduce a transaction transfer system even when some input source terminals and transactions are in a situation where the transaction processing cannot be performed by some processing servers. . In addition, after all, although it was impossible with the conventional technology, some input source terminals and transactions are not subject to transaction transfer, but rather need to be processed within the local system. Even in this case, a transaction transfer system can be introduced.

  Further, according to the above-described embodiment, it is possible to construct a transaction transfer system without using CPU load information. In other words, as pointed out above, the conventional technology generally collects CPU load information of each processing server and performs load distribution based on the collected CPU utilization rate. Requires a means for collecting CPU load information and for notifying the CPU load information between systems (working servers) constructing a transfer system. It was. On the other hand, in the embodiment according to the present invention, a definition (see “CPU load balance definition” 304 in FIG. 5 above) defined in advance by using statistical data on the CPU load without using such CPU load information. ) To determine the necessity of transaction transfer, and load distribution can be achieved. According to this, the CPU can be prevented from an increase in load accompanying the notification of the CPU load information information.

  Further, according to the embodiment of the present invention, the transaction transfer necessity determined by the transaction transfer system and the transfer destination system can be changed by the application created by the user. In other words, according to the conventional technique, transactions are distributed according to an algorithm for determining CPU load information of each system provided by the transaction transfer system. Therefore, it is difficult for the user to change the load distribution algorithm provided by the system. On the other hand, according to the transaction transfer system of the present invention, the transfer system not only provides an algorithm for determining the presence or absence of transaction transfer, but also changes the determination determined by the transfer system as necessary. By providing an interface for passing control to an application that can perform the processing, a part of the transaction processing cannot be performed. Can be processed In case no, it is possible to realize a transaction forwarding system according to the user needs.

  That is, according to the transaction transfer system provided by the present invention, the user designates in advance by definition whether or not to transfer a transaction and candidates for a transfer destination processing server for each input source terminal or input transaction. In addition, it has a function of performing transaction distribution based on a definition set in advance by the user without using CPU load information as an element for determining whether or not to transfer a transaction. Further, the present invention provides an interface that allows the application to change the transaction transfer necessity determined by the transaction transfer system and the transfer destination system, and also provides a transaction transfer control program that realizes these methods.

  According to the present invention, the transaction transfer necessity determination element may determine the transaction transfer necessity based on the CPU usage rate in addition to the input source terminal name and the input transaction name. Instead, it is possible to determine whether transfer of transactions is necessary or not and perform load distribution based on a definition set in advance by statistical data relating to CPU load. Furthermore, in the above transaction transfer, the transaction transfer system not only provides an algorithm for determining whether or not the transaction is transferred, but also provides means for providing an interface for passing control to an application capable of changing the determination determined by the system, There may be provided means for changing the transaction distribution destination according to the necessity of transfer of the changed transaction and the transfer destination system.

It is a block diagram which shows the structure of the transaction transfer system by one Embodiment of this invention. It is a figure which shows an example of the "other system information definition" in the said transaction transfer system. It is a figure which shows an example of the "transfer condition definition" in the said transaction transfer system. It is a figure which shows an example of the "transfer destination system definition" in the said transaction transfer system. It is a figure which shows an example of "CPU load balance definition" in the said transaction transfer system. In the transaction transfer system according to the embodiment of the present invention, it is a flowchart (1/2) showing a flow of processing for determining whether or not a processing server transaction transfer is necessary. Again, in the transaction transfer system according to the embodiment of the present invention, a flowchart (2/2) showing a flow of processing for determining whether or not a processing server transaction transfer is necessary. It is a processing figure which shows an example of the transaction transfer determination application in the transaction transfer system which becomes this invention. It is a figure for demonstrating an example of the transaction transfer operation | movement by the said transaction transfer determination application. It is a figure which shows an example of the input / output interface of the transaction transfer determination application in the transaction transfer system of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Processing server, 20 ... Terminal, 30 ... Network, 100 ... Main memory, 101 ... Communication management part, 102 ... Transaction transfer distribution part, 103 ... CPU load information acquisition part, 104 ... Transaction transfer determination application, 200 ... CPU 300 ... Definition information 301 ... Other system information definition 302 ... Transfer condition definition 303 ... Transfer destination system definition 304 ... CPU load balance definition 401 ... Own system name 402 ... Other system name 501 ... Terminal definition 502 ... transaction definition, 503 ... name, 504 ... transfer target presence / absence, 601 ... transaction name, 602 ... transfer destination system, 701 ... CPU load information use / non-use, 702 ... CPU load information collection interval, 703 ... load distribution threshold upper limit 704 ... Load distribution threshold lower limit, 1 00 ... I / O interface, 1001 ... Input source terminal name, 1002 ... Input transaction name, 1003 ... Transfer required / unnecessary, 1004 ... Transfer destination system name, 1100 ... System information, 1101 ... System name, 1102 ... Own / other category, 1103 ... State, 1104... Load state, 1105... CPU utilization rate.

Claims (5)

  A load balancing transaction processing system configured such that a plurality of processing servers are connected to a network together with a terminal, wherein a part of the plurality of processing servers cannot be processed. The processing server includes means for determining whether or not a transaction input from the terminal needs to be transferred to another processing server, and further, a transaction transfer determination that can be set by a user with respect to the conditions for transferring the transaction. A transaction transfer system comprising means.   2. The transaction transfer system according to claim 1, wherein the transaction transfer determination means that can be set by the user transfers a transaction input based on an input source terminal name and / or an input transaction name which is the name of the terminal. A transaction transfer system characterized by determining necessity.   2. The transaction transfer system according to claim 1, wherein the transaction transfer determination means that can be set by the user sets a transfer destination of a transaction input according to a resource in the processing server that constitutes the transaction transfer system. A transaction transfer system characterized by that.   2. The transaction transfer system according to claim 1, wherein said user-settable transaction transfer determination means can set transfer conditions in advance based on statistical data relating to CPU load of said processing server constituting said transaction transfer system. A transaction transfer system comprising a definition unit, and performing load distribution by determining whether or not a transaction transfer is necessary according to a preset condition set by the definition unit. 2. The transaction transfer system according to claim 1, wherein the means for determining whether transfer to another processing server is necessary is based on a CPU usage rate of each processing server constituting the transaction transfer system. A featured transaction transfer system.

Images