JP2002108838A - Device and method for carrying out agent - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a diffused transaction type integrated service which facilitates the generation of a task requiring transaction processing and the processing change of a task and allows an agent to issue commit and roll back autonomously. SOLUTION: In advance of carrying out an agent AG, a processing procedure file FL which is constituted separately from the agent AG to write a processing order is referred to and the agent AG is started to be carried out along the processing procedure.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to an agent execution device and an agent execution method, and more particularly to an agent execution device and an agent execution method for providing a distributed transaction type integrated service using a mobile agent.

[0002]

2. Description of the Related Art [1] Distributed transaction system Conventionally, a distributed transaction system has been known as a technique for realizing a distributed transaction service. FIG. 6 shows a schematic configuration of the distributed transaction system. In the following description, a case will be described in which two tasks corresponding to the first data processing and the second data processing are processed. The distributed transaction system 100 includes a user terminal 101, an application server 102, an application server 103,
It is provided with.

[0003] A user terminal 101 receives one task processing request including a first task and a second task input by a user 105. Here, the first task corresponds to first data processing in the application server 102. The second task is performed by the application server 10
3 corresponds to the second data processing. Further, the transaction manager 104 of the user terminal 101
Manages data processing results in the application server 102 or the application server 103. Next, the operation of the transaction manager 104 will be described. First, transaction manager 1
At 04, a task processing request is input from the user 105 (step S501). Transaction manager 1
04 issues a first task data processing request to the first application server 102 based on the input task processing request (step S502). It should be noted that this data processing request is only requested and does not actually start the data processing.

Next, the transaction manager 104
Sends a data processing request for the second task to the second application server 103 based on the input task processing request (step S503). It should be noted that this data processing request is also merely requested, and does not mean that actual data processing is started. Subsequently, the transaction manager 104 issues a preparation instruction necessary for data processing of the first task to the first application server 102 (step S504). Further, the transaction manager 104 issues a preparation instruction necessary for data processing of the second task to the second application server 103 (step S505).

Further, the transaction manager 104
Sends a commit instruction to the first application server 102 to outsource data processing of the first task. Thereby, the first application server 102 starts the processing of the first task. Then, the first application server 102 notifies the transaction manager 104 of the processing result of the first task. Similarly, the transaction manager 104 instructs the second application server 103 to commit the data processing of the second task. Thereby, the second application server 103 starts the processing of the second task. Then, the second application server 103 notifies the transaction manager 104 of the processing result of the second task. As a result, the transaction manager 104 notifies the user 105 of the processing results of the first task and the second task.

[0006] With the above configuration, distributed transaction processing becomes possible. Number of communication times X between the transaction manager 104 and the application server functioning as a task processing node in the above processing
Is obtained as follows. First, the number of task processing nodes is n (n ≧ 2), and the number of messages in data processing is m (m ≧ 1). Further, for each task, two communication of a preparation instruction and a commit instruction are required for each application server. Therefore, the number of communication times X
X = (2 + m) · n

[2] Mobile Agent System Next, a mobile agent system will be described.
In recent years, with the explosive spread of the Internet, the maintenance of networks has been progressing. Agent communication has been spotlighted as a new communication method that supports humans using this network. Agent communication refers to a group of software that performs processing on behalf of a human being, which is an agent, and provides communication services in cooperation with each other. Therefore, it is possible for the agent to perform the work on behalf of the agent by requesting the agent for the complicated work that has been performed by a human until now. As an agent system using such an agent, there is a mobile agent system.

FIG. 7 shows a schematic configuration of a mobile agent system. In the following description, a case will be described in which two tasks corresponding to the first data processing and the second data processing are processed. The mobile agent system 200 includes a user terminal 201, an application server 202, and an application server 203. The user terminal 201 is the user 20
5 receives one task processing request including the first task and the second task input. Here, the first task corresponds to first data processing in the application server 202. The second task corresponds to the second data processing in the application server 203.

Further, the user terminal 201 generates an agent, and attaches a processing procedure file FL describing a processing procedure of the first task and the second task. The processing procedure file also includes a task processing node designation for performing the actual task processing. Next, the operation of the mobile agent system 200 will be described. First, a task processing request is input from the user 205 to the user terminal 201 (step S601). The user terminal 201 generates an agent AG based on the input task processing request. Then, a processing procedure file FL describing a processing procedure to be performed by the agent AG is generated. The generated processing procedure file is attached to the agent AG by the user terminal 201.

Subsequently, the user terminal 201 executes the agent AG. Accordingly, the agent AG refers to the processing procedure file FL. Then, based on the reference result of the processing procedure file FL, the agent AG moves to the first destination, the first application server 202, together with the processing procedure file FL (step S60).
2). Thus, the user terminal 201 disconnects communication with the first application server 202. Then the first
The agent AG that has moved to the application server 202 is again running on the first application server 202.

Then, the agent AG refers to the processing procedure file FL again. Then, based on the reference result of the processing procedure file FL, the first application server performs data processing of the first task (step S60).
3). When the data processing of the first task is completed, the agent AG refers to the processing procedure file FL again. Then, based on the reference result of the processing procedure file FL, the agent AG moves to the next destination, the second application server 302, together with the processing procedure file FL (Step S604). As a result, the first application server 202 becomes the second application server 203
Disconnect communication with. Next, the agent AG that has moved to the second application server 203 is again running on the second application server 203.

Then, the agent AG refers to the processing procedure file FL again. Then, based on the reference result of the processing procedure file FL, the second application server performs data processing of the second task (step S60).
5). When the data processing of the second task is completed, the agent AG refers to the processing procedure file FL again. Then, based on the reference result of the processing procedure file FL, the agent AG sends the task processing result and the processing procedure file FL to the user terminal 201 that is the last destination,
It moves (step S606). As a result, the user terminal 201 notifies the user 205 of the processing results of the first task and the second task. With the above configuration, task processing becomes possible. The number of communications Y in the mobile agent system is obtained as follows.

Here, the number of task processing nodes is defined as n (n ≧ n).
Assuming 2), the number of communication times Y is Y = n + 1, including one communication associated with a processing result notification from the application server as the last processing node to the user terminal 201 as the processing request node. According to the mobile agent system, the agent AG performs a task process on the destination application server. Therefore, unlike the distributed transaction system, there is no need to perform communication between the transaction manager and the application server for data processing. As a result, in the above-described conventional distributed transaction system, the load on the network can be reduced even in the case of a task that involves a large amount of communication related to data processing. Further, the load on the user terminal, which is the processing request node, can be reduced. As described above, according to the present mobile agent system, after the agent generated by the user terminal moves to the application server that is the task processing node, the user terminal can disconnect the communication and reduce the communication cost. .

[0014]

In the above-mentioned conventional distributed transaction system, the TP (Transaction Pr
API (Application Prog) provided by monitor
Using a ramming interface), a process for a task group that requires transaction processing is described as a program. Therefore, in order to perform a task that requires transaction processing or to change the processing of the task, it is necessary to modify the transaction processing program itself. Therefore, there is a problem that a development period for generating a task or changing a process of the task is required. Another problem is that the maintainability of the transaction processing program is not high.

Further, in the above-mentioned conventional mobile agent system, there is a problem that transaction processing cannot be described in a processing procedure file. Accordingly, an object of the present invention is to provide a distributed transaction-type integrated service, in which a task requiring transaction processing can be easily generated and task processing can be changed easily, and a commit or rollback can be issued autonomously by an agent. It is an object of the present invention to provide an agent execution device and an agent execution method that can perform the operation.

[0016]

According to a first aspect of the present invention, there is provided an agent execution device for executing an agent, wherein the agent execution device is configured separately from the agent prior to execution of the agent.
A processing procedure file reference unit that refers to a processing procedure file in which a processing procedure is described, and an agent execution unit that activates the agent and executes the processing in accordance with the processing procedure are provided.

According to a second aspect of the present invention, in the configuration of the first aspect, the processing procedure includes a procedure for determining a destination of the agent.

According to a third aspect of the present invention, in the configuration of the first aspect, the processing procedure includes a cooperation processing procedure with an external task processing node.

According to a fourth aspect of the present invention, in the configuration of the first aspect, when the plurality of external task processing nodes that provide the same service are present, the processing result in the plurality of task processing nodes is provided. It is characterized by including an aggregation processing procedure for aggregating.

According to a fifth aspect of the present invention, in the configuration of the first aspect, the processing procedure includes an event processing procedure corresponding to an event to be performed in a normal state or an abnormal state.

According to a sixth aspect of the present invention, in the configuration of the first aspect, the processing procedure includes a transaction processing procedure for performing a transaction processing.

According to a seventh aspect of the present invention, in the configuration according to any one of the first to sixth aspects, the processing procedure file includes a command indicating contents to be processed by each agent in each task processing node. In response to the command, and, when the agent performs cooperative processing with a plurality of external task processing nodes, a parameter described in a global format that can be referred to by the agent in any task processing node, Is described.

An eighth aspect of the invention is characterized in that, in the configuration of any one of the first to seventh aspects, the processing procedure file is described by text data.

According to a ninth aspect of the present invention, in the agent execution method for executing an agent, prior to the execution of the agent, the agent refers to a processing procedure file which is configured separately from the agent and describes a processing procedure, The method is characterized in that the agent is activated and executed according to the processing procedure.

According to a tenth aspect of the present invention, in the configuration of the ninth aspect, the destination of the agent is determined according to the processing procedure.

[0027] According to a eleventh aspect of the present invention, in the configuration of the ninth aspect, cooperative processing with an external task processing node is performed in accordance with the processing procedure.

According to a twelfth aspect of the present invention, in the configuration of the ninth aspect, when there are a plurality of external task processing nodes providing the same service in accordance with the processing procedure, the plurality of task processing nodes Is characterized by aggregating the processing results in.

According to a thirteenth aspect of the present invention, in the configuration of the ninth aspect, an event process corresponding to an event to be performed at a normal time or an abnormal time is performed according to the processing procedure.

According to a fourteenth aspect of the present invention, in the configuration of the ninth aspect, a transaction process is performed in accordance with the processing procedure.

[0030]

Next, a preferred embodiment of the present invention will be described with reference to the drawings. [1] Configuration of Embodiment FIG. 1 shows a schematic configuration block diagram of a mobile agent system of the embodiment. The mobile agent system 10 is roughly divided into a user terminal (client) 11
, A portal server 12, a transaction manager 13, and a plurality of application servers 14-1 to 14
-x. The user terminal 11 transmits a corresponding user request to the portal server 12.
The portal server 12 attaches the processing procedure (scenario) for each integrated service and the corresponding input data to the agent AG as a processing procedure file,
Activate G. Further, the portal server 12 generates a final result page from the processing result of the agent AG.
Further, the portal server 12 performs timer monitoring and rollback of the processing of the agent AG.

Further, when a user's request is made from the user terminal 11, the portal server 12 generates a processing procedure file FL corresponding to the request. Here, the processing procedure file FL defines a generated agent movement, a method of coordinating with the transaction manager 13 or the application servers 14-1 to 14-x. The transaction manager 13 is a portal server 12
And the transaction processing between the application servers 14-1 to 14-x. The application servers 14-1 to 14-x are provided by a plurality of application service providers (ASPs) for one business type. The application servers 14-1 to 14-x
The service is provided to the agent AG as a task. The contents of the services provided by the application servers 14-1 to 14-x are as follows.
Shared between 4-x.

Next, the functional configuration of the agent AG, the transaction manager 13, and the application server will be described with reference to the functional configuration diagram of FIG. FIG.
Will be described as an example in the case where the agent AG moves to the application server (AP server) 14-1. First, the internal function of the agent AG is shown in FIG.
This will be described with reference to FIG. The agent AG has an input data holding function F1 for holding data input from the user terminal 11 as input data. Further, the agent AG has a result data holding function F2 for holding data obtained by coordination processing with the application server 14-1 as result data.

Further, the agent AG has a transmission / reception function F3 for transmitting processing contents (commands and parameters) to the application server 14-1 side when cooperating with the application server 14-1, and receiving a corresponding result. Furthermore, the agent AG has an event handler function F4 for performing a process corresponding to an event that occurs between the destination determination and the transaction processing.
Further, the agent AG has a transaction client function F5 for issuing an instruction to the transaction manager such as commit / rollback, registration of a processing result, and the like. Further, the agent AG has a transfer function F6 for retrieving the application server designated by the template interpreter function F7 and moving itself to the designated application servers 14-1 to 14-x.

Further, the agent AG interprets the processing procedure file FL at the time of execution, and executes the command transmission function F
3. It has a processing procedure file interpreter F7 function for issuing instructions to other functions such as an event handler function F4, a transaction client function F5, and a movement function F6. Next, an internal function of the transaction manager 13 will be described with reference to FIG.

The transaction manager 13 has a transaction client function F5 of the agent AG.
A transaction registration function F11 that receives transaction information registration request from the server and registers transaction information to a resource manager function described later. Further, the transaction manager 13 has a transaction controller function F12 for issuing a transaction processing instruction to the application servers 14-1 to 14-x.

Further, the transaction manager 14
Is an input data holding function F1 for managing input data, result data, and the like held by the agent AG.
3. It has a resource manager function F15 for the result data holding function F14 to manage. This resource manager function F15 is used for specifying the application server that has requested the rollback processing during the rollback processing. In addition, the resource manager function F15 is used for a halfway resumption process, for example, when the agent AG itself disappears due to a failure of the agent AG itself, and the processing is continued in a state before the agent AG disappears. Next, the internal functions of the application server will be described with reference to FIG. The application server 14-1 has a transmission / reception function F21 for transmitting / receiving processing contents and processing results to / from the agent AG.

Also, the application server 14-1
In response to a processing instruction from the agent AG, a business processing function F22 for performing processing specific to the business of the application server 14-1 is provided. Further, the application server 14-1 receives the transaction processing request issued by the transaction manager 13,
It has a transaction processing function F23 for executing transaction processing unique to the application server 14-1. FIG. 3 shows a schematic configuration diagram of the processing procedure file. In this case, the processing procedure file FL is constituted by a text file independent of the operation program of the agent AG.

Therefore, generation and change of the processing procedure file FL, that is, generation and change of a task can be easily performed. Generation and change of the actual processing procedure file FL can be performed by a text editor. The processing procedure file FL
Is configured as a text file when it is located on the user terminal 11 or the portal server 12. After the agent AG is activated, when the agent AG moves with the processing procedure file FL to the application server, The processing procedure file FL is in a movable format. For example, the processing procedure file FL has a data format such as an object format of “Java” at the time of movement. Further, the processing procedure file FL includes a plurality of task information TI-1 to TI-n. Next, the task information will be described with reference to FIG. 3 using the task information TI-1 as an example. The task name of the task information TI-1 is data for specifying the task information TI-1. The destination attribute information is data representing the attribute (such as the type of business) of the destination application server.

The command information describes the processing of the minimum unit in the processing with the application server. The agent AG can access a service-specific processing method of each of the application servers 14-1 to 14-x by passing commands and parameters (arguments) to the application servers 14-1 to 14-x. Then, cooperative processing with the application servers 14-1 to 14-x is performed. Multiple pieces of this command information can be described per one piece of task information. More specifically, the command information includes a command name, a parameter name (an argument name and a return value name), in-command processing information, and in-command event processing information.

The command name is name data for specifying the command information. The parameter name is name data describing the name of the parameter corresponding to each command. In this case, the argument name of the parameter name is described in a global format and a local format. Here, the global format is used to obtain a required value from the processing result of an already-existing task or user data. The local name is used to associate a value passed on the application server side with a global parameter name. The return name of the parameter name is described in a global format and a local format.

For example, the global name of the parameter argument name is “ret1@comm1.task1” and the local name is “nam
e ", the agent AG sends" ret1@comm1.task
Using the information "1", from the value management table of its own, from the command "comm1" of "task1",
The value corresponding to the parameter name “1” is, for example, “X
XX ”. And Agent AG,
In the case of the above example, the value of the parameter is delivered to the application server side with the local name “name” as “XXX”. As a result, on the application server side,
Since there is no need to unify the order of parameters, processing can be performed without worrying about the order of passed parameters, and flexible service development can be performed. The process information in the command includes whether or not to perform a sort process, a parameter name serving as a sort key (sort reference), a sort order indicating ascending or descending order, whether or not to perform a selection process, and a selection when performing a selection process. The number is described. The event processing information in the command describes an event name and an action pair of the event corresponding to the event name.

[2] Operation of the Embodiment FIG. 4 shows an outline processing sequence of an agent using a processing procedure file. As shown in FIG. 4, the agent performs the following processing according to the processing procedure file FL. Destination determination processing Cooperation processing with the application server Aggregation processing Transaction processing Event processing Each processing of the agent will be described below.

[2.1] Destination Determination Process First, the destination determination process (including the migration process) of the agent will be described. In this case, it is assumed that the definition information of the application server is shared between each of the application servers 14-1 to 14-x and the portal server 12. The agent AG determines the destination application server based on the attributes of the destination described in the processing procedure file FL. That is, referring to the definition information of each of the application servers 14-1 to 14-x, the application server that matches the attribute of the destination is determined as the destination application server. Then, the agent AG moves to the determined application server. In this case,
If there is a plurality of application servers that provide one service as a result of the matching of the attributes of the destination, the plurality of application servers are determined as the destination application server. Keep it as a list. Thus, the agent AG sequentially refers to the list. Then, the agent AG moves a plurality of application servers based on the list. There are the following two cases where the agent AG moves a plurality of application servers. The first case is when the agent AG moves all application servers corresponding to the list. More specifically, this is the case where the cheapest airline ticket is reserved when there are a plurality of application servers for airline reservation for each airline. In such a case, the agent AG sequentially moves all the application servers and makes a reservation with the application server corresponding to the cheapest ticket.
In the second case, the agent AG moves to an application that satisfies the conditions described in the processing procedure file FL among all the application servers corresponding to the list. More specifically, in a case where there are a plurality of application servers for airline reservations for each airline, the airline tickets are reserved by any one airline. In such a case, the agent AG moves to the application server and ends the processing when the reservation is made.

[2.2] Cooperation with Application Server The agent AG passes a command and parameter data including a parameter name and a parameter value to the destination application server. The application server performs processing specific to the application server task based on the received command and parameter data. Then, the application server passes parameter data corresponding to the processing result to the agent AG.
If the next command exists, the agent AG continues to cooperate with the application server. In the processing procedure file FL, information on cooperative processing with the application server is described as a command. Sorting / selection processing,
Event processing can also be described.

[2.3] Aggregation Processing In the aggregation processing, when there are a plurality of application servers that provide the same service, the processing of each application server is aggregated. Then, merging of processing results, sorting selection processing, and the like are performed. Processing procedure file FL
In the above, the parameter (argument) name as a key at the time of sorting, designation of the sort order (ascending or descending order), the number of selections after sorting, etc. are described. [2.4] Transaction Processing Transaction processing is processing performed when processing is performed consistently in a plurality of application servers. Specifically, when creating a travel plan using the aircraft reservation application server and the hotel reservation application server, if a hotel reservation cannot be made due to a full room, etc., it is necessary to cancel the aircraft reservation. In addition, transaction processing is performed, and contradiction does not occur in the entire processing, and consistency can be maintained.

In the processing procedure file FL, a plurality of groups of tasks to be handled as transactions can be held. When all the command processes of the transaction target task are completed, the agent registers the transaction information in the transaction manager.
Examples of the transaction information include a processing result of the task, information that can identify an application server that has processed the task, and the like. These transaction information
"Rollback" and "resend processing" of event processing described later
It will be used in.

[2.5] Event Processing Events that occur during the operation of the agent AG are defined in advance as "events" inside the agent AG. Events expected to occur during the transaction processing from the determination of the destination application server and the processing of the agent at that time ("action")
Is described in the processing procedure file FL,
Branch processing according to the type of event that has occurred at an arbitrary timing is possible. Examples of the event include events corresponding to a processing result or a processing state such as “0 search results” or “communication failure”. Actions include "Continue processing", "Roll back (transaction)", "Resend data"
It is possible to specify a routine process defined in advance inside the agent. It is also possible to specify another task as an action.

[3] Specific Operation Next, a specific operation of the mobile agent system 10 will be described with reference to FIG. First, the user terminal 11
Then, a task processing request is input from the user 15 (step S1). As a result, the user terminal 11 issues a transaction management request to the transaction manager 13 based on the input task processing request (step S2). Subsequently, the user terminal 11 generates an agent AG. Then, a processing procedure file FL describing a processing procedure to be performed by the agent AG is generated.
The generated processing procedure file FL is attached to the agent AG by the user terminal 11.

Subsequently, the user terminal 11 sends the agent A
Execute G. Accordingly, the agent AG refers to the processing procedure file FL. Then, based on the reference result of the processing procedure file FL, the agent AG starts communication with the first application server 14-1, which is the first destination. And the first application server 14-1
Move with the processing procedure file FL (step S
3). As a result, the user terminal 201 disconnects the communication with the first application server 14-1. Then the first
The agent AG that has moved to the application server 14-1 is again running on the first application server 14-1. Then, the agent AG refers to the processing procedure file FL again. Then, from the reference result of the processing procedure file FL, the first application server 1
In 4-1, data processing of the first task is performed (step S4).

Subsequently, the agent AG issues a preparation instruction to the first application server 14-1 (step S5). Thereafter, the agent AG issues a preparation record request to the transaction manager (step S).
6). When the data processing and the preparation instruction of the first task and the preparation record request to the transaction manager are completed, the agent AG returns to the processing procedure file F again.
L. Then, based on the reference result of the processing procedure file FL, the agent AG starts communication with the second destination, the second application server 14-2. Then, it moves to the second application server 14-2 together with the processing procedure file FL (step S7). Thereby, the first application server 14-1 disconnects the communication with the second application server 14-2. Next, the agent AG that has moved to the second application server 14-2 is again running on the second application server 14-2.

Then, the agent AG refers to the processing procedure file FL again. Then, from the reference result of the processing procedure file FL, the second application server 14
In -2, the data processing of the second task is performed (step S8). Subsequently, the agent AG issues a preparation instruction to the second application server 14-2 (Step S).
9). Thereafter, the agent AG issues a preparation record request and a commit instruction request to the transaction manager 13 (step S10). As a result, the transaction manager 13 issues a commit instruction to the first application server 14-1 (step S1).
1). In addition, the transaction manager 13
A commit instruction is also issued to the application server 14-2 (step S12).

When the data processing of the second task is completed and a commit instruction is issued from the transaction manager 13, the agent AG refers to the processing procedure file FL again. Then, based on the reference result of the processing procedure file FL, the agent AG moves to the user terminal 11, which is the final destination, together with the processing result of the task and the processing procedure file FL (Step S13). As a result, the user terminal 201 notifies the user 15 of the processing results of the first task and the second task. With the above configuration, the processing of the task described in the processing procedure file FL can be performed. The number of communications Z in the mobile agent system 10 at this time is obtained as follows.

Here, the number of task processing nodes is n (n ≧ n)
If the number of messages in data processing is m, then the number of communications Z is Z = (2n + 1) + (n + 1) = 3n + 1. Therefore, according to the mobile agent system, compared with the conventional distributed transaction processing, m
In the case of> 2, the number of times of communication can be reduced. Therefore, in the above-described conventional distributed transaction system, the load on the network can be reduced even in the case of a task that involves a large amount of communication related to data processing. Further, the load on the user terminal, which is the processing request node, can be reduced.

As described above, according to the mobile agent system, after the agent generated at the user terminal moves to the application server which is the task processing node, the user terminal can disconnect the communication.
Communication costs can be reduced. In addition, after the agent generated by the user terminal moves to the application server that is the task processing node, the user terminal can disconnect the communication. The processing can be performed even on a device that is likely to be interrupted. Further, as mentioned above,
Since the processing procedure file is configured as a text file, it is possible to easily create a new task or change a task.

[4] Modifications of Embodiment [4.1] First Modification In the above description, the processing procedure file is configured as a text file. However, the processing procedure file is not limited to a text file. Independent and
The file can be in any format as long as the file can be referred to by the agent.

[4.2] Second Modification In the above description, the case where only one application server provides the same service has been mainly described. However, when there are a plurality of application servers that provide the same service, the processing is performed in the following procedure. As the agent AG of the user terminal 11 is executed, the agent AG refers to the processing procedure file FL. Then, based on the reference result of the processing procedure file FL, the agent AG starts communication with any one of the plurality of application servers. Then, it moves to the application server together with the processing procedure file FL. Thus, the user terminal disconnects communication with the application server.

Next, the agent AG is re-executed on the destination application server, and performs data processing corresponding to the processing in step S4 described above. And
If the agent AG moves all application servers corresponding to the list, the agent AG
Similarly, sequentially move a plurality of application servers, and perform data processing in each application server. Thereafter, when the processing is completed in all the application servers described in the list, the agent AG sends the above-described step S to all the application servers.
A preparation instruction corresponding to the processing of No. 5 is issued. Also,
When the agent AG moves to an application server capable of processing among the application servers corresponding to the list, the application server performs data processing. Then, the agent AG issues a preparation instruction corresponding to the processing in step S5 to all the application servers.

[4.3] Third Modification In the above description, the processing procedure file is edited with a text editor. However, by constructing an editing tool having a graphic user interface (GUI), It is also possible to configure so that the description can be performed intuitively by a drag and drop operation using a mouse.

[4.4] Fourth Modification In the above description, the checking of the consistency of the coordination content of the processing procedure file for coordination with the application server is not described. By using a tool for performing analysis and syntax analysis, it is possible to easily and quickly check the consistency of the cooperation contents.

[4.5] Fifth Modification In the above description, the transaction manager has a resource manager. However, the resource manager is separated from the transaction manager, and one resource manager is assigned to a plurality of transaction managers. It is also possible to adopt a configuration provided. As a result of employing this configuration, the load required for the transaction processing can be distributed. Further, high fault tolerance can be provided.

[0061]

According to the present invention, an agent can autonomously issue processes such as commit and rollback simply by describing and defining a required task group as a process procedure file. In addition, by configuring the processing procedure file as an external reference file separately from the agent, it is possible to change a task requiring a transaction process or a process in the task without modifying the operation program of the agent. . Furthermore, it is possible to realize a distributed transaction service utilizing the characteristics of the mobile agent. Furthermore,
The development period for realizing the distributed transaction service can be shortened, and the maintainability can be improved.

[Brief description of the drawings]

FIG. 1 is a schematic configuration block diagram of a mobile agent system according to an embodiment.

FIG. 2 is an explanatory diagram of an internal function of an agent.

FIG. 3 is an explanatory diagram of a configuration of a job template.

FIG. 4 is an outline processing sequence of an agent based on a job template.

FIG. 5 is an explanatory diagram of a specific operation of the mobile agent system.

FIG. 6 is an explanatory diagram of a specific operation of a conventional distributed transaction system.

FIG. 7 is an explanatory diagram of a specific operation of a conventional mobile agent system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 ... Mobile agent system 11 ... User terminal (client) 12 ... Portal server 13 ... Transaction manager 14-1 to 14-x ... Application server FL ... Processing procedure file F1 ... Input data holding function F2 ... Result data holding function F3 ... Transmission / reception Function F4: Event handler function F5: Transaction client function F6: Moving function F7: Processing procedure file interpreter F11: Transaction registration function F12: Transaction controller function F13: Input data holding function F14: Result data holding function F15: Resource manager function

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B045 GG01 5B098 AA10 GA04 GC16

Claims (14)

[Claims] 1. An agent execution device for executing an agent, comprising: a processing procedure file reference unit configured to be separate from the agent and referring to a processing procedure file in which a processing procedure is described, prior to execution of the agent; An agent execution device, comprising: an agent execution unit that starts the agent and executes the agent in accordance with the processing procedure. 2. The agent execution device according to claim 1, wherein the processing procedure includes a process of determining a destination of the agent. 3. The agent execution device according to claim 1, wherein the processing procedure includes a cooperation processing procedure with an external task processing node. 4. The agent execution device according to claim 1, wherein the processing procedure is to aggregate processing results in the plurality of task processing nodes when there are a plurality of external task processing nodes providing the same service. An agent execution apparatus characterized by including an aggregation processing procedure. 5. The agent execution device according to claim 1, wherein the processing procedure includes an event processing procedure corresponding to an event to be performed in a normal state or an abnormal state. 6. The agent execution device according to claim 1, wherein the processing procedure includes a transaction processing procedure for performing a transaction processing. 7. The agent execution device according to claim 1, wherein the processing procedure file includes a command indicating contents to be processed by each task processing node by the agent, and When the agent performs cooperative processing with a plurality of external task processing nodes, the parameter is described in a global format that can be referred to by the agent in any of the task processing nodes. An agent execution device, comprising: 8. The agent execution device according to claim 1, wherein the processing procedure file is described by text data. 9. An agent execution method for executing an agent, wherein, prior to execution of the agent, the agent is referred to a processing procedure file which is formed separately from the agent and describes a processing procedure, and starts the agent. An agent execution method, which is executed according to the processing procedure. 10. The agent execution method according to claim 9, wherein the destination of the agent is determined according to the processing procedure. 11. The agent execution method according to claim 9, wherein a cooperation process with an external task processing node is performed in accordance with the processing procedure. 12. The agent execution method according to claim 9, wherein when there are a plurality of external task processing nodes that provide the same service according to the processing procedure, a processing result in the plurality of task processing nodes is determined. An agent execution method characterized by aggregation. 13. The agent execution method according to claim 9, wherein an event process corresponding to an event to be performed at a normal time or an abnormal time is performed according to the processing procedure. 14. The agent execution method according to claim 9, wherein transaction processing is performed in accordance with the processing procedure.