JP2003141069A - Application cooperation server, application server, and dynamic cooperation system of distributed application using them - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an application cooperation server capable of dynamically increasing various applications. SOLUTION: This system comprises a task server 12. A DB 14 is connected to the task server 12, and a user computer 18 and application servers 20 and 22 are also connected thereto through a network 16. The application servers 20 and 22 comprise application adaptors (AA) responding to each application in their internal DB, and only minimum information is mounted (defined) in AA. The application servers 20 and 22 further comprise application engines, which control the start/stop of the applications according to the instruction from the task server 12 based on a user's request.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application cooperation server, an application server, and a dynamic cooperation system for distributed applications using the same, and in particular, for executing a task in response to a request from an arbitrary user computer and executing the task. The present invention relates to an application cooperation server, an application server, and a dynamic cooperation system for distributed applications, which cooperates with accompanying applications and provides a desired result to a user computer.

[0002]

2. Description of the Related Art In a conventional distributed processing system of this type,
For example, a plurality of databases that form a distributed processing system are connected to a server that manages distributed processing via a network such as the Internet. The server executes distributed processing by accessing a plurality of databases according to a user's operation.

[0003]

However, in this prior art, since each database is provided with an interface in which various information corresponding to the contents of the database currently being constructed is defined (implemented), the contents of the database are not provided. When adding / changing, it was necessary to reimplement the information. That is, it was necessary to redevelop an interface, that is, an API (Application Programming Interface). The development of such an API is complicated, requires a lot of time and labor, and has a problem of high cost. That is, once the system was configured, it was not possible to dynamically add / delete the contents of the database.

In addition, EJB (Enterprise Java Beans)
When a standard API such as (registered trademark “Java”) is used, the one connected to the server via the network is specialized for the database, and therefore data (file) analysis and calculation are processed ( Could not connect other applications to run). That is, there is a problem that it is not possible to sufficiently meet the needs of the user.

Therefore, a main object of the present invention is to provide an application cooperation server and an application server and a dynamic cooperation system for distributed applications, which can increase various applications easily and dynamically.

[0006]

According to a first aspect of the present invention, a plurality of application servers providing a predetermined application are connected via a network, and a task execution request is received from an arbitrary user computer connected to the network. In the application cooperation server that links the processing in multiple application servers,
Application cooperation characterized by comprising detection means for detecting the presence or absence of connection of an application engine that controls the operation of an application provided by an application server, and instruction means for instructing the connected application engine to execute a task in response to a request. It is a server.

According to a second aspect of the present invention, in an application server which is connected to an application cooperation server via a network and executes an application in accordance with an instruction from the application cooperation server, at least one application is activated, and the application is supported. Provided with an application adapter and an application engine that controls the operation of the application, the application name of the application, information about whether the application returns data during execution,
The application server is characterized in that only the setting information about the application adapter that receives the application start information and the application status information is installed.

A third aspect of the present invention is a dynamic cooperation system for distributed applications, comprising an application cooperation server connected to an arbitrary user computer and a plurality of application servers via a network, wherein the application cooperation server is the application server. Means for detecting the presence or absence of connection of the application engine that controls the operation of the application provided by
And an instruction means for instructing a connected application engine to execute a task in response to a task execution request from the user computer, and the application server is provided for at least one or more applications The application adapter that controls the operation of the application and the application engine that controls the application are received. The application adapter receives the application name of the application, information whether the application returns data during execution, application start information, and application status information. This is a dynamic linkage system for distributed applications that implements only the setting information for application adapters.

[0009]

The application cooperation server of the first invention is
It is connected to a plurality of application servers that provide a predetermined application via a network such as the Internet or an intranet, and processing is performed by the plurality of application servers in response to a task execution request from any user computer connected to the network. It is to cooperate. The application server is mainly equipped (installed) with an application engine that controls the operation of the application provided by the application server, and the detection means detects whether or not the application engine is connected. Specifically, it detects whether the application server is connected to the network and the application engine is running. That is, it detects whether the application is available.
Therefore, the instructing unit can instruct the connected application engine to execute the task in response to the request from the user computer.

[0010] For example, the application cooperation server has a database inside or outside thereof,
User information about registered users is stored in this database. This user information includes personal information such as user name, address, and contact information, and contract content information such as available service information (first task information). Therefore, when the user operates the user computer and logs in, the database refers to the first task information included in the user information and generates a page (screen) of the tasks available to the user, This is presented to the user computer. Specifically, screens of available tasks are displayed on a monitor connected to the user computer. Therefore, the user can easily select the service to be received, that is, the task to be used, by looking at the screen.

Further, the holding means holds a list (engine list) of currently connected application engines. For example, the detecting means periodically detects whether or not the application engines connected to the engine list are connected, Alternatively, the presence / absence of connection of a new application engine is detected, and the updating means updates the engine list according to the detection result of the detecting means, so that the instructing means can reliably instruct the currently connected application engine to execute the task. .

Further, in the database, the task management means manages the second task information of a plurality of registered tasks. When there is a request from the user computer, the cooperation order determining means determines the execution order of the application engines by referring to the second task information corresponding to the request (first task information). However, when the processing is completed by one application, the execution order is not determined. Therefore, the instruction means instructs the application engine to execute the processing in accordance with the cooperation order determined by the cooperation order determination means. In this way, the processes can be linked.

When executing such processing cooperation,
When the receiving means receives the processing end notification from the application server, the instructing means can instruct the application engine to execute the next processing to execute the processing.

However, if the presence / absence determining means determines that there is no application engine to be processed next, that is, if it is determined that all the processing (execution of tasks) has been completed, the end notifying means is sent to the user computer. Notify the end of the task. Therefore, the user receives this notification, logs in to the application cooperation server, and can confirm or acquire the result of task execution.

The application server of the second invention is
Connected to the application cooperation server via a network such as the Internet or an intranet,
The application (processing) is executed according to the instruction from the application cooperation server. Such an application server is provided with at least one or more applications, and an application adapter corresponding to each application is held as a component in, for example, a database provided inside the application server. In addition, the application server is provided with an application engine that controls operations of various applications.
As described above, the application adapter is provided corresponding to each application, and only the minimum information shown below is implemented (defined). Specifically, only the application name (application name), information about whether the application returns data during execution, application start information, and setting information about the application adapter that receives information about the application state are implemented. . By implementing only the minimum information in this way, it is not necessary to redevelop the adapter even when various applications are added / deleted. In other words, since the restriction on the adapter is reduced, various applications can be easily added / deleted.

For example, the application engine is
It has an adapter list of application adapters and starts an application adapter corresponding to the application instructed by the application cooperation server by referring to the adapter list. Then, the started application adapter starts the application instructed by the application cooperation server according to the instruction of the application engine. In this way, it is possible to dynamically add (start) / delete (stop) an application to the application cooperation server.

Further, in the application adapter, the status judging means judges the processing status of the application, and when the judgment result indicates the processing end, the first notifying means notifies the application engine of the processing end. Then, in the application engine, the second notification means
Notify the application cooperation server of the processing end. That is, the application cooperation server can determine the processing status of an application, can instruct the next application engine to execute processing, and can notify the user computer of processing completion.

The distributed application dynamic cooperation system of the third invention comprises an application cooperation server connected to an arbitrary user computer and a plurality of application servers via a network. For example, in the application server, the detection means
The presence or absence of the connection of the application engine that controls the operation of the application provided by the application server is detected. Therefore, the instruction unit can instruct the connected application engine to execute the task in response to the task execution request from the user computer. Further, the application server is provided with at least one or more applications, and application adapters corresponding to the respective applications are held as components in, for example, a database provided inside the application server.
In addition, the application server is provided with an application engine that controls operations of various applications. As described above, the application adapter is provided corresponding to each application, and only the minimum information shown below is implemented (defined). Specifically, only the application name (application name), information about whether the application returns data during execution, application start information, and setting information about the application adapter that receives information about the application state are implemented. . By implementing only the minimum information in this way, it is not necessary to redevelop the adapter even when various applications are added / deleted. In other words, applications can be easily added / deleted.

For example, the application cooperation server has a database inside or outside thereof,
User information about registered users is stored in this database. This user information includes personal information such as user name, address, and contact information, and contract content information such as available service information (first task information). Therefore, when the user operates the user computer and logs in, the database refers to the first task information included in the user information and generates a page (screen) of the tasks available to the user, This is presented to the user computer. Specifically, screens of available tasks are displayed on a monitor connected to the user computer. Therefore, the user can easily select the service to be received, that is, the task to be used, by looking at the screen.

Further, in the application cooperation server,
The holding unit holds a list of the currently connected application engines (engine list). For example, the detection unit regularly determines whether or not the application engine connected to the engine list is connected, or a new application engine. The presence / absence of the connection is detected and the updating means updates the engine list according to the detection result of the detecting means. Therefore, the instructing means can surely instruct the currently connected application engine to execute the task.

Further, in the database, the task management means manages the second task information of a plurality of registered tasks. When there is a request from the user computer, the cooperation order determining means determines the execution order of the application engines by referring to the second task information corresponding to the request (first task information). However, when the processing is completed by one application, the execution order is not determined. Therefore, the instruction means instructs the application engine to execute the processing in accordance with the cooperation order determined by the cooperation order determination means. In this way, the processes can be linked.

When executing such processing cooperation,
In the application adapter, the status judging means judges the processing status of the application, and when the judgment result indicates that the processing is completed, the first notifying means notifies the application engine of the processing completion. Then, in the application engine, the second notifying unit notifies the application cooperation server of the processing end. Therefore, in the application cooperation server, the receiving unit receives the notification of the processing end. That is, the application cooperation server can determine the processing status of the application and can instruct the next application engine to execute the processing.

However, if the presence / absence determining means determines that there is no application engine to be processed next, that is, if it is determined that all processing (execution of tasks) has been completed, the end notifying means is sent to the user computer. Notify the end of the task. Therefore, the user receives this notification, logs in to the application cooperation server, and can confirm or acquire the result of task execution.

[0024]

As described above, according to these inventions, the restriction on the adapter is reduced, so that various applications can be dynamically added / deleted. In addition, even when adding / deleting an application, it is easy because there is no need to redevelop the adapter.

The above-mentioned objects, other objects, features and advantages of the present invention will become more apparent from the following detailed description of the embodiments with reference to the drawings.

[0026]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring to FIG. 1, a distributed application dynamic cooperation system of this embodiment (hereinafter referred to simply as "system").
Say. ) 10 includes a task server 12 as an application cooperation server. A database (DB) 14 is connected to the task server 12 so that they can communicate with each other. The task server 12 is provided by a user computer 18 such as a personal computer or a workstation, a first application server 20 that provides a predetermined application, and a first application server 20 via a network 16 such as the Internet or an intranet. It is connected to the second application server 22 which provides an application different from the application to be executed.

For simplification, FIG. 1 shows an example in which one user computer and two application servers are connected to the network, but two or more user computers and three or more application servers are shown. Can also be connected.

In this embodiment, the DB 14 is provided outside the task server 12 for easy understanding, but it may be provided inside the task server 12.

Further, in this embodiment, the application is a normal application that analyzes or calculates (processes) various data (files) such as image data, and various data (files) such as image data (files).
Is a concept that includes a database to build.

Further, although not shown, the task server 12, the user computer 18, the first application server 20, and the second application server 22.
A monitor and an input device (keyboard, computer mouse, etc.) are connected to the.

The task server 12 manages tasks, administrator information, user information, etc., which will be described later, in cooperation with the DB 14, and provides services that can be provided by the first application server 20 and the second application server 22 ( Application), or
Services that can be provided by the cooperation of both of them are provided to the user of the user computer 18 or the like.

As shown in FIG. 2, the DB 14 has, for example, memory areas 14a to 14f. An application list is stored in the memory area 14a, and task management information is stored in the memory area 14b. Also,
Administrator information is stored in the memory area 14c, and user information is stored in the memory area 14d. Further, a page template is stored in the memory area 14e, and log (history) information is stored in the memory area 14f.

The application list includes the first application server 20 and the second application server 22.
The table manages application information including the name (application name) of the application and its details (information) provided by, for example. In this embodiment, a plurality of application information items are input (registered) by the administrator of the task server 12 and an application list is created.

The task management information is information relating to (the substance of) the task, and includes a task name, detailed information about the task, an ID (task ID), and the like. For example, in this embodiment, the task ID, the task name and the detailed information thereof are managed in a table.

Although illustration is omitted, the substance of the task is stored in the memory area 14b in association with the task management information.

Further, the administrator information is the task server 12
Information (personal information) about the administrator who manages
Specifically, the administrator's name, ID (administrator ID), password and administrator authority are included. Here, the administrator authority is information that defines whether the application list, task information, administrator information, user information, and the contents of the page template, that is, the contents of the DB 14 can be added, deleted, or changed (edited). Say. For example, the administrator authority may be roughly determined as if it has the authority to edit all the contents, or may finely determine whether the authority to edit each content is present or absent.

Furthermore, the user information is information (personal information) about the user who owns (operates) the user computer 18, and specifically, the user's name, address, contact information (telephone number, fax number or E-mail address or a combination of two or more of these), ID
(User ID), password, available services (tasks), and information about contract contents such as charging method.

The page templates are a plurality of templates for displaying various screens on the monitor of the task server 12 or the user computer 18 according to the operation of the administrator or the user. The template is specifically HTML data.

Further, the history information corresponds to the user name (user ID), the date and time when the user used the service, and the name of the application (or AE) used by the user.
Information), which is managed in a table.

For example, the administrator operates the input device to
When the user logs in to the task server 12, the processing for the service menu can be executed. That is, DB
The contents of 14 can be browsed / searched or edited.
Specifically, the task server 12 executes the processing shown in FIGS. 3 to 11 according to the operation of the administrator.

As shown in FIG. 3, when the administrator operates the input device and requests the task server 12 to log in, the task server 12 starts processing, and in step S1,
A login screen as shown in FIG. 2 (A) is displayed on the monitor. Specifically, the task server 12 reads the template required for displaying the login screen from the memory area 14d of the DB 14 and outputs it to the monitor. Hereinafter, when various screens are displayed on the monitor, similar processing is executed, and therefore detailed description thereof will be omitted each time.

This login screen is provided with ID and password input fields, and the administrator uses the input device to enter both the ID (administrator ID) and password assigned to him / herself, and clicks "OK". Click the "button.

Then, the task server 12 inquires of the DB 14 whether the user is an administrator. That is, step S3
Then, it is determined whether the administrator authentication is OK (correct). Specifically, the DB 14 refers to the administrator information stored in the memory area 14c in response to an inquiry from the task server 12, and determines whether both the administrator ID and the password are correct (match). , And returns the result to the task server 12.

If at least one of the ID and password is not entered and the "OK" button is turned on, the task server 12 displays an error message indicating that both the ID and password should be entered. Display the login screen again.

If "NO" in the step S3, that is, if one or both of the administrator ID and the password are not correct, it is determined that the administrator authentication is NG, and an error message is displayed in a step S5. Display on the monitor and finish the process. On the other hand, in step S3, "YE
If S ", that is, if both the administrator ID and the password are correct, it is determined that the administrator authentication is OK, and the process proceeds to step S7.

In this embodiment, the administrator authentication is N
In the case of G, an error message is displayed in step S7 and then the process is terminated.
You may make it return to 1 and display a login screen again. In this case, the number of retries may be defined and the process may be terminated when the number of retries is exceeded.

In step S7, the task server 12
A service menu screen as shown in FIG. 12B is displayed on the monitor. In this service menu screen, "User Management", "Task Management", "Application Management"
Also, an item of "log / history search / browsing" is displayed, and a "logoff" button is displayed below the item. The administrator can select (click) a desired one from these items and execute editing or the like. Also,
It is also possible to log off from the task server 12 by clicking (turning on) the "logoff" button.

Therefore, in the following step S9, it is determined whether or not the log is off. That is, it is determined whether or not the administrator has turned on the "logoff" button on the service menu screen. If “YES” in the step S9, that is, if the “logoff” button is turned on, the process ends.

On the other hand, if "NO" in the step S9,
That is, if the "logoff" button is not turned on, it is determined in step S11 whether the "user management" item is turned on. If “NO” in the step S11, that is, if the item “user management” is not turned on, the process proceeds to a step S15. On the contrary, if "YES" in the step S11, that is, if the item "user management" is turned on, the user management process is executed in a step S13, and then the process returns to the step S7.

Although description of the user management process is omitted using the drawings, when the administrator designates a specific user, each item of user management information for the designated user is displayed on the screen. On this screen, it is possible to change (correct) and delete the contents of the user management information as described above. In addition, user management information is added / added in response to notification of new user registration or user registration cancellation.
You can also delete it.

As is well known, new registration of a user, deregistration of a user, change / deletion of user information, etc. are notified by a user by telephone, facsimile, mail or e-mail, and such notification is managed. By performing on a web page created by a person, the task server 1
It is performed by the second manager (operator).

The task server 12 also executes step S1.
At 5, it is determined whether or not the item "task management" is turned on in the service menu screen. If "NO" in the step S15, that is, if the item of "task management" is not ON, the process proceeds to a step S19 shown in FIG. On the other hand, if “YES” in the step S15, that is, if the “task management” item is turned on, the step S1
In step 7, a task management process which will be described in detail later is executed, and then the process returns to step S7.

In step S19 shown in FIG. 4, it is determined whether or not the item "application management" is turned on in the service menu screen. If "NO" in the step S19, that is, if the item "application management" is not turned on, the process proceeds to a step S23, but if "YES" in step S19, that is, the item "application management" is turned on. If so, step S21
Then, after executing an application management process which will be described in detail later, the process returns to step S7 shown in FIG.

In step S23, it is determined whether or not the item of "history search / browsing" is turned on in the service menu screen. If “NO” in the step S23, that is, if the item “history search / view” is not turned on, it is determined that the administrator has not selected any service menu (item), and the process directly returns to the step S7. .
On the other hand, if “YES” in the step S23, that is, if the item “history search / browsing” is turned on, the history search / browsing process is ended in a step S25, and then the process returns to the step S7.

Regarding the history search / browsing process, description using the drawings will be omitted. For example, when the item “history search / browsing” is turned on, a button for selecting search or browsing (“ "Search" button, "Browse" button) are displayed on the screen.

Here, when the "search" button is turned on,
An input field for inputting a user name (user ID), date and time, and application name is displayed. When the administrator inputs at least one of these pieces of information and inputs an instruction to start the search, the corresponding history information is searched (so-called AND search) according to the input information (condition), for example, a list is displayed on the monitor. To be done.

On the other hand, when the "view" button is turned on, D
A list of all history information stored in the memory area 14f of B14 is displayed on the monitor. For example, the administrator can browse all the history information displayed in a list by scrolling (rolling up / rolling down) the screen.

Note that such history information can be used not only for searching / browsing, but also as billing information according to the contract contents of the user. For example, with a pay-as-you-go billing system, the billing amount can be easily calculated from the history of the corresponding user.

Referring to FIG. 5, step S17 described above.
When the task management process of is started, the task server 12
Displays the task management screen as shown in FIG. 13A on the monitor in step S31. In this task management screen, items such as "task list", "task added", "task deleted", "task change" and "task search" are displayed, and a "return" button is displayed below them. It The administrator can select any item (menu). However, if the "return" button is turned on, it is possible to return to the service menu screen shown in FIG.

Specifically, in step S33, it is determined whether or not the "return" button is turned on in the task management screen. If “YES” in the step S33,
In other words, if the "return" button is turned on, the task management process is returned and the service menu screen is returned as described above. On the other hand, if “NO” in the step S33,
In other words, if the "return" button is not turned on, step S
At 35, it is determined whether the item of "task list" is turned on.

If "NO" in the step S35, that is, if the item of "task list" is not turned on, the process proceeds to a step S41. On the other hand, if “YES” in the step S35, that is, if the “task list” item is turned on, a task list screen as shown in FIG. 13B is displayed on the monitor in a step S37. On this task list screen, a list of task IDs, task names and their details (information), that is, task information is displayed, and a "return" button is displayed below the task list. Therefore, the administrator can know the task name of the currently registered task and its details by visually checking the task list. Also, by turning on the "Return" button, the task list screen can be terminated and the task management screen can be returned to.

In a succeeding step S39, it is determined whether or not the "return" button is turned on. If "NO" in the step S39, that is, if the "return" button is not turned on, the process directly returns to the step S37. On the other hand, if “YES” in the step S39, that is, if the “return” button is turned on, the process returns to the step S31 to display the task management screen.

In step S41, it is determined whether the "task addition" item is turned on in the task management screen. If "NO" in the step S41, that is, if the item "task addition" is not turned on, the process proceeds to a step S55 shown in FIG. On the other hand, if "YES" in the step S41, that is, if the "task addition" item is turned on, a task addition screen as shown in FIG. 14A is displayed on the monitor in a step S43. On this task addition screen, an input field for the name of the task (task name) and its details is displayed, and below that,
An "OK" button and a "Cancel" button are displayed.

Therefore, the administrator can execute the task registration process described later by inputting the task name and details of the task to be added and turning on the "OK" button. However, if you click the "Cancel" button, the task addition will be canceled and you will be returned to the task management screen.

That is, in step S45, it is determined whether the "OK" button has been turned on. Step S45
If “NO” in S, that is, if the “OK” button is not turned on, the process directly returns to the step S43. On the other hand, if “YES” in the step S45, that is, if the “OK” button is turned on, it is determined that the task name of the task to be added and the details thereof are input, and the management of the operation (work) currently being performed in a step S47. Judge whether the person has the authority to register (add) the task (registration authority).

That is, the task server 12 determines whether or not the administrator currently working has registration authority based on the administrator ID input by the administrator on the login screen.
Contact us. In response to this, the DB 14 refers to the administrator information stored in the memory area 14c, investigates whether there is registration authority, and returns the result to the task server 12.

If "YES" in the step S47, that is, if the user has registration authority, a task addition (registration) process described later is executed in a step S49, and an addition completion message is displayed on the monitor in a step S51. Step S3
Return to 1. On the other hand, if “NO” in the step S47,
That is, if there is no registration authority, a refusal message indicating that there is no authority to add, delete, and change task information is displayed on the monitor in step S49, and the process returns to step S31.

In step S55 shown in FIG. 6, the task server 12 displays "task deletion" on the task management screen.
It is determined whether the item of is turned on. Step S5
If "NO" in 5, that is, if the item of "task deletion" is not turned on, the process proceeds to step S67 shown in FIG.

On the other hand, if "YES" in the step S55, that is, if the item "task deletion" is turned on, a task deletion screen as shown in FIG. 14B is displayed in a step S57. In this task deletion screen, a task list is displayed, and a "delete" button and a "cancel" button are displayed below it. The administrator selects the task information of the task to be deleted from the task list,
When the "Delete" button is turned on, the selected task information and the task (entity) stored in association with it are deleted. However, if you click the "Cancel" button, you can interrupt the task deletion and return to the task management screen.

Note that, in FIG. 14B, the column in which the selected task information is described is provided with diagonal lines, but in reality, the color is inverted or a different color from other columns is added. In this way, the selected task information can be identified.

That is, in step S59, it is determined whether or not the task information to be deleted is selected on the task deletion screen and the "delete" button is turned on. If "NO" in the step S59, that is, if the "delete" button is not turned on, the process directly returns to the step S57. On the other hand, if "YES" in the step S59, that is, if the "delete" button is turned on, it is determined in a step S61 whether or not the administrator currently working has the right to delete the task (delete right). Whether or not the user has the deletion authority is the same as the above-described determination of whether or not the user has the registration authority
It is executed by making an inquiry to the DB 14.

If "NO" in the step S61, that is, if there is no deletion authority, the process returns to the step S53 shown in FIG. On the other hand, if “YES” in the step S61, that is, if the user has deletion authority, the task information selected (corresponding) in the step S63 and the task (entity) stored in association therewith are deleted. The DB 14 is instructed, the deletion completion message is displayed on the monitor in step S65, and then the process returns to step S31 shown in FIG.

In step S67, the task server 12 determines whether the item "task change" is turned on in the task management screen. If “NO” in the step S67, that is, if the “task change” item is not turned on, the process proceeds to a step S79. On the other hand, if “YES” in the step S67, that is, if the item “task change” is turned on, the task list screen shown in FIG. 13B is displayed on the monitor in a step S69.

In a succeeding step S71, it is determined whether or not one task (information) to be changed is selected from the task list. If "NO" in the step S71, the process returns to the same step S71. On the other hand, in step S71, "YE
If "S", that is, if one task information item to be changed is selected, a task edit screen as shown in FIG. 15 is displayed on the monitor in step S73.

This task edit screen is provided with an input (display) field for a task name and details (information) thereof, and the task name and details of the task selected in the task list are displayed. Further, below the task name and details display fields, an input (display) field of an application name and an application pipe (AP) of an application processed as the task is executed is displayed. Here, the application pipe refers to the order of passing data between applications. Therefore, when the applications are not linked, that is, when the processing is executed by one application, the application
The display column of the pipe is blank.

For example, the administrator can delete the application (name) to be changed and select (specify) the application (name) to be replaced with the deleted application from the pull-down menu to add it.

The pull-down menu is DB1
4 is displayed using the application list stored in the memory area 14a.

Application pipe (AP)
When changing the AP, it is possible to delete the currently registered AP and add (input) an AP that replaces the deleted AP. In this way, task changes can be executed, and when the "Back" button is turned on, the contents will be saved in the DB.
14 is registered. That is, the substance of the task is changed.

That is, in step S75, it is determined whether or not the "return" button is turned on. Step S75
If "NO" in S, that is, if the "Return" button is not turned on, the process directly returns to the step S73. On the other hand, if “YES” in the step S75, that is, if the “return” button is turned on, it is determined in a step S77 whether or not the administrator currently working has the authority to change the task (change authority).

As to the registration authority described above, the task server 12 also determines whether or not it has the modification authority.
Contact B14.

If "NO" in the step S77, that is, if there is no change authority, the process returns to the step S53. on the other hand,
If "YES" in the step S77, that is, if the user has the change authority, the task change DB1 is set in a step S79.
4, the change completion message is displayed on the monitor in step S81, and the process returns to step S31.

Although not shown, the task can be changed by selecting any task (information) when the task list screen is displayed. That is,
It is also possible to shift to task change processing from the task list screen.

In step S83, it is determined whether the item "task search" is turned on in the task management screen. If “NO” in the step S83, that is, if the item of “task search” is not turned on, it is determined that the administrator has not turned on the “return” button of any item on the task management screen, and the step is directly performed in the step S31. Return to. On the other hand, if “YES” in the step S83, that is, if the item of “task search” is turned on, a step S8 is performed.
In step 5, the task search screen is displayed.

Although not shown, the task search screen is provided with an input field for inputting the task ID and the task name, and by inputting at least one of them,
A search result screen (search result screen) including the task list of the corresponding task can be displayed. Further, a "return" button is displayed on the search result screen, and by turning this button on, the task search can be terminated (interrupted) and the task management screen can be returned to.

That is, in step S87, it is determined whether the "return" button has been turned on. Step S87
If “NO” in S, that is, if the “Return” button is not turned on, the process returns to step S85 to continue the task search. On the other hand, if “YES” in the step S87, that is, if the “return” button is turned on, the process returns to the step S31 to display the task management screen.

Referring to FIG. 8, when the task registration process shown in step S49 of FIG. 5 is started, task server 12 instructs DB 14 to register the task information of the task to be registered in step S91. . That is, here, only the task ID, the task name, and the details (information) thereof are registered in the memory area 14b of the DB 14, and the substance of the task is not registered. Succeedingly, in a step S93, the task information is read from the DB 14, and in a step S95, a task edit screen for the task information is displayed. That is, the task edit screen as shown in FIG. 15 is displayed with only the task name of the task and its details displayed.

Therefore, the administrator can input (specify) detailed task information. In particular,
The application to be used can be added by selecting the application to be processed along with the execution of the task from the pull-down menu and turning on the "Add" button.

Application pipe (AP)
Can be added. Therefore, the administrator can add (register) an application pipe in order to determine the order of data transfer between the added (registered) applications.

Therefore, in step S97, it is determined whether or not an application has been input. If "NO" in the step S97, that is, if there is no application input, the process directly returns to the step S97. On the other hand, if “YES” in the step S97, that is, if the application is input, the step S99 in FIG.
Application pipe addition screen (A)
P addition screen) is displayed. In this AP addition screen, input fields for the connection source application name, connection source property name, connection destination application name and connection destination property name are displayed, and "OK" button and "Cancel" button are displayed below them. It Therefore, the administrator can input the connection source application name and the connection destination application name by selecting the application name from the pull-down menu. In addition, the property name can be input corresponding to each application name.

The property name is the name of the property set in the application adapter described later.

Succeedingly, in a step S101, it is determined whether or not the application of the delivery source and the application of the delivery destination are input in the input field of the AP addition screen. Specifically, it is determined whether or not the "OK" button is turned on on the AP addition screen. If "NO" in the step S101, that is, if the "OK" button is not turned on, it is determined that the application of the delivery source and the delivery destination is not input, and the process returns to the same step S101.

On the other hand, if "YES" in the step S101, that is, if the "OK" button is turned on, it is determined that the application of the delivery source and the delivery destination is input, and the process proceeds to the step S103 to edit the result (task Display the task edit screen that describes (detailed information). That is, the task edit screen in which the task name, its details, the application to be used, and the AP are described is displayed.
Then, in step S105, the DB 14 is instructed to register the task, and the task registration process is returned. here,
The substance of the task will be registered in the memory area 14b of the DB 14.

Referring to FIG. 9, when the application management process shown in step S21 of FIG. 4 is started, task server 12 displays an application management screen as shown in FIG. 17A in step S111. . On this application management screen, items of “application list”, “application addition”, “application deletion”, application change ”and“ application search ”are displayed, and a“ return ”button is displayed below them. The administrator can perform a desired operation (work) by turning on any item, but can return to the above-mentioned service menu screen by turning on the "return" button.

Specifically, in a succeeding step S113, it is determined whether or not the "return" button is turned on on the application management screen. In step S113, "Y
If it is "ES", that is, if the "return" button is turned on, the application management process is returned, and the service menu screen is displayed again.

On the other hand, if "NO" in the step S113, that is, if the "return" button is not turned on, it is determined in a step S115 whether the item of "application list" is turned on. In step S115, "N
If “O”, that is, if the item of “application list” is not turned on, the process proceeds to step S121.

On the other hand, if "YES" in the step S115, that is, if the item "application list" is turned on, an application list screen as shown in FIG. 17B is displayed in a step S117. On this application list screen, the application (APRI.) Name and ID (APR.
I. ID) and an application list describing the details are displayed. Therefore, the administrator can refer to the application list to know the currently registered application name and the like. Further, a "return" button is displayed below the application list, and by turning on this button, the application management screen can be returned.

That is, in a succeeding step S119, it is determined whether or not the "return" button is turned on. If "NO" in the step S119, that is, if the "return" button is not turned on, the process directly returns to the step S117.
On the other hand, if “YES” in the step S119, that is, if the “return” button is turned on, the process returns to the step S111.

In step S121, it is determined whether or not the "application addition" item is turned on in the application management screen. If "NO" in the step S121, that is, if the "application addition" item is not turned on, the step S13 shown in FIG.
Go to 5. On the other hand, if “YES” in the step S121, that is, if the “application addition” item is turned on, an application addition screen as shown in FIG. 18A is displayed on the monitor in a step S123. On this application addition screen, an input field for inputting the application name and its details is displayed, and "O" is displayed below it.
A "K" button and a "Cancel" button are displayed.
Therefore, the administrator can add an application by inputting the application name and its details and turning on the “OK” button. However, if the "Cancel" button is turned on, it is possible to interrupt the addition of the application and return to the application management screen.

That is, in the subsequent step S125, "O
It is determined whether the "K" button is turned on. If "NO" in the step S125, that is, if the "OK" button is not turned on, the process directly returns to the step S123.
On the other hand, if “YES” in the step S125, that is, if the “OK” button is turned on, it is determined in a step S127 whether or not the administrator currently working has the authority to add the application (additional authority). Specifically, the ID entered by the administrator at login (administrator ID)
Based on the above, it is determined whether or not the user has the additional authority by making an inquiry to the DB 14.

If "YES" in the step S127,
That is, if there is additional authority, the DB 14 is instructed to register the application in step S129, and then step S1
After the registration completion message is displayed on the monitor at 31, the process returns to step S111. That is, in step S129,
The task server 12 gives an instruction to register the application name and its details input on the application addition screen, that is, the application information in the DB 14.

On the other hand, if "NO" in the step S127, that is, if there is no addition authority, there is no authority to register (add), change and delete the application (list) in a step S133, and such work is rejected. Message is displayed on the monitor and the process returns to step S111.

In step S135 shown in FIG. 10, it is determined whether or not the item "application deletion" is turned on in the application management screen. If “NO” in the step S135, that is, if the item “application deletion” is not turned on, the process proceeds to a step S147 shown in FIG. On the other hand, in step S135, "YE
If "S", that is, if the "application deletion" item is turned on, an application deletion screen as shown in FIG. 18B is displayed in step S137.

On this application deletion screen, a list of application information, that is, an application list is displayed, and a "delete" button and a "cancel" button are displayed below it. Therefore,
The administrator can delete the selected (corresponding) application by selecting the application (information) to be deleted from the application list and then turning on the "Delete" button. As can be seen from FIG. 18 (B),
On the application deletion screen, as in the task deletion screen, the selected application (information) column is
It is shown with diagonal lines. Further, the selected application information may be easily visually recognized by performing color reversal display or displaying with a different color from other columns. Also, if the "Cancel" button is turned on, it is possible to return to the application management screen.

That is, in a succeeding step S139, it is determined whether or not the application to be deleted is selected and the "delete" button is turned on. In step S139, “N
If “O”, that is, if the “delete” button is not turned on, the process directly returns to step S137. On the other hand, if “YES” in step S139, that is, if the “delete” button is turned on, it is currently determined in step S141. Determine whether the working administrator has the right to delete the application (delete right).

Whether or not the user has the authority to delete the application is determined by the administrator I input when the administrator logs in.
This is done by making an inquiry to the DB 14 based on D.

If "NO" in the step S141, that is, if there is no deletion authority, the step S13 shown in FIG.
Return to 3. On the other hand, if “YES” in the step S141, that is, if the user has deletion authority, the DB 14 is instructed to delete the application information in a step S143. That is, the application selected on the application deletion screen is deleted from the application list.
Then, in step S145, the deletion completion message is displayed on the monitor, and then the process returns to step S111 shown in FIG.

As shown in FIG. 11, in step S147, it is determined whether or not the "application change" item is turned on in the application management screen.
If “NO” in the step S147, that is, if the “application change” item is not turned on, the process proceeds to a step S163. On the other hand, “YES” in the step S147
If so, that is, if the "change application" item is turned on, the application list screen as shown in FIG. 17B is displayed in step S149.

In a succeeding step S151, it is determined whether or not application information to be changed has been selected from the application list. “NO” in step S151
If so, that is, if the application information to be changed is not selected, the process directly returns to step S149. On the other hand, if “YES” in the step S151, that is, if the application information to be changed is selected, an application changing screen as shown in FIG. 19 is displayed on the monitor in a step S153.

This application change screen is displayed in a state where the application name indicated by the selected application information and its details are input (displayed).
An "OK" button and a "Cancel" button are displayed below the application name and details display fields. Therefore, the administrator can change the application information, that is, the application list by changing the application name and / or the details, and turning on the “OK” button. However, if you click the "Cancel" button, you can return to the application management screen.

That is, in step S155, it is determined whether or not the "OK" button is turned on on the application change screen. If “NO” in the step S155, that is, if the “OK” button is not turned on, the process directly returns to the step S153. On the other hand, step S15
If "YES" in 5, that is, if the "OK" button is turned on, it is determined in step S157 whether or not the administrator currently working has the authority to change the application (change authority).

The presence / absence of change authority can also be determined by the task server 12 making an inquiry to the DB 14.

If "NO" in the step S157, that is, if there is no change authority, the process returns to the step S133. On the other hand, if “YES” in the step S157, that is, if the change authority is given, the application changing process is executed in a step S159, the change completion message is displayed on the monitor in a step S161, and the process returns to the step S111.

In step S163, it is determined whether the item "application search" is turned on in the application management screen. Step S16
If “NO” in 3, that is, if the item of “application search” is not turned on, the step is directly performed in step S1.
Return to 11. On the other hand, if “YES” in the step S163, that is, if the item “application search” is turned on, an application search screen (not shown) is displayed in a step S165.

The application search screen is provided with an input field for inputting an application ID, an application name and detailed information. By inputting at least one of the information, the corresponding application is searched (and search). The search result screen (search result screen) is displayed. Further, a "return" button is displayed on the search result screen, and by turning on this button, it is possible to finish the application search and return to the application management screen.

Therefore, in the following step S167,
Determine if the "Back" button was turned on. That is, it is determined whether the search is completed. If “NO” in the step 167, that is, if the “return” button is not turned on, it is determined that the search is not completed, and the step S is performed as it is.
Return to 165. On the other hand, if “YES” in the step S167, that is, if the “return” button is turned on, the process returns to the step S111.

Returning to FIG. 1, each of the first application server 20 and the second application server 22 has an application engine (AE) incorporated therein, and a plurality of application files (not shown) are stored in an internal DB (internal DB). The adapter (AA) is stored.

AE is the first application server 20
Alternatively, it is a core that executes operations of applications provided by the second application server, data management, and start / stop of AA. The AE is the first application server 20 or the second application server 22.
Holds a list of AA names (hereinafter referred to as "AA list") stored in the internal DB (not shown) of the.
Therefore, the AE can recognize which application can be used based on this AA list.

The AA is started / stopped in accordance with the instruction from the AE, communicates with the AE, and executes the start of the application. In addition, the AA detects the operation status such as the execution of the application or the end of the processing according to the instruction of the AE or by itself, and notifies the AE of the result. Further, the AA is provided corresponding to the application provided by the application server and is stored in the internal DB as a component. Therefore, when the application server provides a plurality of applications, a plurality of AAs are prepared and stored in the internal DB.

Such an AA can usually freely determine how a designer (developer) creates it, what kind of information is needed, and the like. However, in this embodiment, as will be described later, the task server 12 has only the following minimum information in order to easily and dynamically add / remove applications. That is, restrictions are reduced.

For example, the minimum necessary information is the application name, information about whether the application returns data during execution, information about starting the application, and information about the state (event) of the application, that is, processing. It is setting information about a receiver (AE) of information indicating whether it is being executed or processing is completed,
These are implemented (defined) using an API such as JavaBeans.

Further, the AE and AA communicate with each other so that the following necessary information is set in the AE config file. Required information includes registration of one or more adapters (AA) (AA list), application name, adapter class name (in this embodiment, adapter name in JavaBeans),
Load value (information indicating whether AE is BUSY), 1
One or more property (AA property) settings,
A property name and a property value, and these pieces of information are described in a config file in XML (extensible markup language).

Further, the first application server 20 and the second application server 22 are not always connected to the task server 12 via the network 16, and the network 16, that is, the task server 12 does not always follow the time series change. Connected to the task server 1
It is cut from 2. That is, it is necessary to determine whether or not the application can be used (used) at the present time even if it is described in the application list stored in the memory area 14a of the DB 14.

Therefore, the task server 12 is the application server (in this embodiment, the first application server 20 and the second application server 2).
By communicating with 2), the application server (strictly speaking, AE) connected to (connecting to) the network 16 is searched, and a list of connected AEs (hereinafter referred to as “connected AE list”). Is stored in a memory (not shown) provided inside itself. The connecting AE list also includes the AA list as described above.

Specifically, the application server and the task server 12 execute the processes shown in FIGS. 20 and 21, thereby updating (adding / deleting) the connected AE list.

The application server (in this embodiment, the application server 20 or the application server 22) is changed to the one shown in FIG.
AE start / stop notification processing as shown in FIG.

That is, the application server first determines in step S201 whether or not the AE is activated. If “YES” in the step S201, that is, A
If it is the start of E, in step S203, the task server 1
Notify 2 of the connection. However, strictly speaking, when the AE is activated, the AE itself notifies the task server 12 of the connection. On the other hand, if “NO” in the step S201, that is, if the AE is not activated, it is determined in a step S205 whether or not the AE is stopped.

If "NO" in the step S205, that is, if the AE is not stopped, the step is directly performed in the step S201.
Return to. On the other hand, if “YES” in the step S205, the task server 12 is notified of the disconnection in a step S207. However, as in the case of starting, the AE notifies the task server 12 of disconnection before stopping, and then stops.

On the other hand, the task server 12 executes an addition / deletion process of the connected AE list as shown in FIG. 21 by interrupting at regular intervals. First, the task server 12
Determines in step S211 whether there is a notification from the application engine (AE).

If "NO" in the step S211, that is, if there is no notification from the AE, A is set in the step S213.
E It is determined whether or not a fixed time has elapsed since the start of the list addition / deletion process. In step S213, “N
If it is O ”, that is, if a certain time has not passed,
The process directly returns to step S211. On the other hand, step S2
If “YES” in 13, that is, if a predetermined time has passed, the AE list addition / deletion process is returned.

If "YES" in the step S211, that is, if there is a notification from the AE, the step S21
5 receives the notification. Succeedingly, in a step S217, it is determined whether or not the content of the notification is activation of the AE. If “YES” in the step S217, that is, if the AE is activated, the connection of the AE is recognized in a step S219. Then, in step S221, the AE is added to the connected AE list.

On the other hand, if "NO" in the step S217, that is, if the AE is disconnected, the disconnection of the application adapter is recognized in a step S223, and the disconnection of the AE is recognized. Then, in step S225, the AE is deleted from the connected AE list.

In such a system 10, the user
Operate the user computer 18 to execute the task server 12
You can log in to and execute services (applications) according to the contract. Hereinafter, the user logs in to the task server 12 using the user computer 18, and the task server 12 instructs the first application server 20 and the second application server 22 according to the task specified by the user, and the first application server 20 and the first application server 20 2 A case where distributed (cooperative) processing is executed by the application server 22 will be described.

22 to 26 shown below, a partition is provided for each of the processes of the task server 12, the user computer 18 and the application server (20, 22) for easy understanding. Further, in the processing of the application server (20, 22), partitions are provided for these processing so that the processing of each of the application engine (AE), the application adapter (AA) and the application can be understood.

Referring to FIG. 22, when the user operates the user computer 18 to request the task server 12 to log in, the cooperative processing is started and the user computer 1
8 requests the task server 12 to display a login screen in step S301. In response to this, the task server 12 transmits the screen data of the login screen as shown in FIG. 12A to the user computer 18 in step S303.

Therefore, in step S305, the user computer 18 displays the login screen on the monitor. As described above, on the login screen, the input fields for the ID (user ID) and the password are displayed, and the user inputs both of them using the input device and clicks "OK".
When the button is clicked, the user ID and password are sent to the task server 12.

The user ID and password are assigned to the user who has registered as a user, and the user is notified by mail or electronic mail.

In the next step S307, the user computer 18 determines whether or not the "OK" button has been turned on. If "NO" in the step S307, that is, if the "OK" button is not turned on, the process directly returns to the same step S307. On the other hand, in step S307, “YE
If "S", that is, if the "OK" button is turned on,
User authentication is requested in step S309. That is, the user computer 18 transmits the screen data of the password screen in which the user ID and the password are input to the task server 12.

In response to this, the task server 12 inquires of the DB 14 in step S311, and then in step S3.
At 13, it is determined whether the user authentication is OK (correct). Specifically, in response to an inquiry from the task server 12, the DB 14 refers to the user information stored in the memory area 14d and determines whether both the user ID and the password are correct (match).

If at least one of the ID and the password is not input and the "OK" button is turned on, the task server 12 displays an error message indicating that both the ID and the password should be input. Display the login screen again.

If "NO" in the step S313, that is, if the user authentication is NG, an error message indicating that the user authentication, that is, the user ID and the password is incorrect is transmitted to the user computer 18 in a step S315, and the process is ended. To do.

As is well known, after the error message is transmitted, the login screen may be transmitted again to display the login screen on the user computer 18 and log in again. In this case, the number of retries may be set and the process may be terminated when the number of retries is exceeded.

On the other hand, if “YES” in the step S313, that is, if the user authentication is OK, in a step S317 shown in FIG. 23, the task server 12 determines the service (task information) available to the logged-in user. DB1
Get from 4. Specifically, the memory area 1 of the DB 14
The available task information is acquired by referring to the contract content included in the user information stored in 4d.

Subsequently, the task server 12 executes step S
A page corresponding to the task information acquired in 319, that is, a menu screen of usable task information (usable task menu screen) is automatically generated, and the screen data is transmitted to the user computer 18.

When automatically generating a page, the task server 12 uses the page template stored in the memory area 14d of the DB 14.

On the user computer 18, step S
In step 321, the screen data of the page, that is, the available task menu screen is received, and in step S323, the available task menu screen is displayed on the monitor. Although illustration is omitted, for example, on the available task menu screen, available tasks (task names) are displayed as menus (items), and a desired item can be selected by clicking (turning on).

Therefore, in the following step S325,
It is determined whether or not a task is selected on the available task menu screen. That is, it is determined whether or not the item of the desired task is turned on in the available task menu screen. If “NO” in the step S325, that is, if no task is selected, the same step S325 is performed.
Return to 325. On the other hand, if “YES” in the step S325, that is, if the task is selected, the step S32
The task selected in 7 is notified to the task server 12.

In response to this, the task server 12 receives the notification of the selected task in step S329, and enters an input screen (parameter input in step S331) for inputting all parameters necessary for executing the task. Screen), and the screen data is generated by the user computer 1
Send to 8.

Therefore, the user computer 18 is
The screen data of the parameter input screen is received in step S333, and the parameter input screen is displayed on the monitor in step S335. Although illustration is omitted, for example, the parameter input screen is provided with an input field for inputting all parameters required for executing the task, and an “OK” button is provided below the input field. Therefore, the user can send the input parameters to the task server 12 by inputting the parameters and turning on the “OK” button.

Therefore, the user computer 18 is
In step S337, it is determined whether the parameters have been input. In other words, on the parameter input screen,
It is determined whether the "OK" button has been turned on. If “NO” in the step S337, that is, if the “OK” button is not turned on, it is determined that the parameter input is not completed, and the process returns to the same step S337.

On the other hand, if "YES" in the step S337, that is, if the "OK" button is turned on, the user computer 18 sends the parameter and the task execution request input in the step S339 to the task server 1
Send to 2.

Therefore, the task server 12 receives the parameter and the task execution request, and
The process proceeds to step S345 shown in, and thereafter, the process is advanced by the task server 12, the first application server 20, and the second application server 22.

Further, when the user computer 18 transmits the parameter and the task execution request to the task server 12 in step S339, the user computer 18 proceeds to step S343.
Determines whether or not a logoff instruction has been input. If “NO” in the step S343, the same step S3
Return to 43 and wait until there is a logoff instruction. On the other hand, if “YES” in the step S343, that is, if logoff, as shown in FIG. 22, the process is temporarily terminated.

Referring to FIG. 24, in step S345, task server 12 creates a job for the application. That is, the execution (cooperation) order of the applications is determined with reference to the task selected by the user. For example, in this embodiment, first, the processing of the application provided by the first application server 20 is executed, and then the processing of the application provided by the second application server 22 is executed.

When the selected task is completed by the processing by one application, it is not necessary to determine the cooperation order.

In the following step S347, the task server 12 searches the connected AE list for an AE that controls the operation of the application. If the load value is also registered in the connected AE list, it can be recognized whether the AE is BUSY. That is, normally, an application server (A
Since E) is plurally connected to the network 16 (task server 12), the task server 12 can select an AE that is not BUSY from the AE list.

Next, in step S349, the first AE
(1st AE) is specified, and parameters and processing execution requests are transmitted to the first AE, that is, the first application server 20.

In response to this, in step S351, the first AE selects the AA required for executing the task, that is, the AA provided corresponding to the application to be processed from the AA list, and internally selects the AA selected in step SS353. Start from DB. Then, the activated AA (hereinafter,
Corresponding to the first AE, it will be referred to as "first AA". ) To pass parameters and data.

In other words, the AE activates the AA corresponding to the application instructed by the task server 12, and
The activated AA is instructed to activate the application. Therefore, the AA activates the application instructed by the AE. In this way, the application server (20, 22) can start the application according to the instruction from the task server 12. Also, since only the minimum information is implemented in AA,
You can easily add / remove applications. That is, the application can be dynamically added / deleted to / from the task server 12.

In the first AA, the target application (which should execute the process) in step S357 (hereinafter, referred to as the first AA).
Corresponding to E, it will be referred to as “first application”. )
Parameters and data (file) are passed to, and then the first application is started in step S359.

Actually, in step S357 and step S359, the first AA adds parameters and data to the EXE file for starting (executing) the first application and passes it to the first application.

Therefore, in step S361, the first
The application executes a predetermined process using the parameters and data, and passes the process result data (result data) to the first AA in step S363.

The first AA receives the result data in step S365, and finishes the process in the first AE in step S367.
To notify. Then, the first AE notifies the task server 12 of the end of processing.

The task server 12 receives the notification of the processing end in step S371, and the step S37 shown in FIG.
In step 3, it is determined whether there is the next processing. In particular,
Refer to the created job to determine whether there is an application to be processed next.

If "NO" in the step S373, that is, if there is no application to be processed next, the processing end is notified to the user in a step S375, and the process is ended. In other words, an email notifying you
It can be sent to the user computer 18 via a mail server (not shown). Further, if the user computer 18 is not logged off, it is possible to directly send the processing end message to the user computer 18.

On the other hand, if "YES" in the step S373, that is, if there is an application to be processed next, the task server 12 proceeds to the next (2) in the step S377.
An AE (second AE) for executing the (th) process is searched from the connected AE list, and a parameter and a process execution request are transmitted to the second AE specified in step S379. Subsequently, in step S381, the destination of the result data and the transmission of the result data are instructed to the first AE. At this time, the AP is referred to.

In response to this, the first AE determines in step S3.
At 83, the first AA is instructed to send the result data and to send the result data. Therefore, in step S385, the first AA transmits the result data to the designated destination (the second AA described later in this embodiment).

With reference to FIG. 26, the second AE selects the AA required for executing the task (referred to as “second AA” corresponding to the second AE) from the AA list in step S387, and in step S389. The selected second AA is activated from the internal DB. Next, in step S391, parameters and data (excluding result data) are included in the activated second AA.
give.

Further, the second AA receives the result data transmitted from the first AA in step S393,
At 395, the parameters, data, and result data are passed to the target application (which will be referred to as “second AE” corresponding to the second AE). Then, the second AA is step S
At 397, the second application is started.

In step S395 and step S397, the second AA actually executes the same processing as step S357 and step S359 described above.

Subsequently, in step S399, the second application executes a predetermined process (process different from the first application) by using the parameters, data and result data, and in step S401, the second data is processed by the second application.
Give it to A.

The second AA receives the result data in step S403, and terminates the process in step S405.
Notify E. In response to this, the second AE performs step S
In step 407, the task server 12 is notified of the end of processing, and the task server 12 receives the notification of end of processing in step S409, returns to step S373 shown in FIG. 25, and determines whether there is next processing. .

Although illustration is omitted, when all the processes are completed, the result data is transmitted to the task server 12 from the application server (AA) that finally executed the process. Therefore, the user who has been notified of the processing end can log in the task server 12 and check the result of the task execution on the monitor or print it out. Or if you are logged in,
It is possible to check the execution result of the task as it is.

According to this embodiment, the restrictions on the application adapters activated by the application server are reduced as much as possible, so that applications can be added / deleted easily and dynamically. Therefore, it is not necessary to develop an adapter (interface), that is, an API along with the addition / deletion of an application, and a great amount of time and labor required for development can be reduced.
That is, low cost can be realized.

When the task execution is instructed, the task server cooperates with the processing, so that the user can log off and perform another operation.

Further, in most cases, the administrator and the user simply click (turn on) desired items, buttons, etc. on the screen provided by the task server, that is, most operations by GUI (Graphical User Interface). Therefore, it can be easily operated.

For example, by using the system as described above, it is possible to execute a task of analyzing an image and visualizing and displaying the analysis result. For convenience of explanation, the system 10 will be shown as in FIG.

As shown in FIG. 27, in the system 10,
18n and user servers 18a, 18b, ... 18n and application server 20a, application server 20b ,.

The user computers 18a-18m
Is a computer operated (owned) by a user who has a contract with the administrator of the task server 12 (registered as a user).

Also, the application servers 20a-2
0n is a server that provides an application registered in the task server 12, that is, a server that has an application adapter (AA) registered in the AA list.

For example, the user (user name: ABC)
However, when the user computer 18a is operated to log in to the task server 12, a menu screen (available service menu screen) of available tasks (services) as shown in FIG. 28A is displayed (FIG. 22). And correspond to steps S301 to S323 shown in FIG. 23).

In addition, another user (user name: DEF)
However, when the user computer 18b is operated to log in to the task server 12, an available service menu screen as shown in FIG. 28B is displayed (similarly, steps S301 to S323 shown in FIGS. 22 and 23).
Equivalent to. ).

As can be seen from FIGS. 28A and 28B, the contents of the tasks (services) that can be used are different. That is, the user ABC is "analysis model DB.
There are four services available: search, analysis, visualization and confirmation of visualization results.
The user DEF can use three services of “analysis”, “visualization”, and “visualization result / result confirmation”. This is because the contract content with the administrator of the task server 12 differs between users.

When the user clicks (turns on) any item on the available service menu screen, a parameter setting (input) screen for the selected item is displayed. For the sake of simplicity, the case where the user ABC operates the user computer 18a will be described below. For example, when the user ABC turns on the item "analysis", an analysis parameter input screen as shown in FIG. 29A is displayed (corresponding to steps S325 to S335 in FIG. 23).

On this analysis parameter input screen, an analysis name, a description of the analysis contents, and a (calculation) parameter input field are displayed. The user ABC can set a parameter by inputting a numerical value or the like in the calculation parameter input field. (Step S337 and Step S3 in FIG. 23)
Equivalent to 39. ).

Then, the (analysis) parameter confirmation screen as shown in FIG. 29B is displayed. In this analysis parameter confirmation screen, the parameter name and its numerical value (value)
Are displayed in a list. Therefore, the user ABC can confirm the set parameters. Further, below the parameter list, there are provided an “analysis execution” button and a “progress visualization” button.

When the user ABC turns on the "analysis execution" button, the request is sent to the task server 12, and in response to this, the task server 12 creates a job for analysis execution. That is, the task for executing the analysis is read, and the task to be executed is recognized by referring to the task. Next, the connected AE list is referred to and the AE to be used is determined. Then, the parameter and the request for executing the analysis process are transmitted to the application server that executes the analysis application (corresponding to steps S341 to S349 in FIGS. 23 and 24).

When the processing is completed by the application server, the result data is sent to the task server 12. Then, the task server 12 informs the user A that the analysis is completed.
The BC, that is, the user computer 18a is notified.

Therefore, the user ABC can obtain the result data and can also continue to use other services (for example, visualization).

When the "Proceed to visualization" button is turned on in the analysis parameter confirmation screen, the visualization parameter input screen is displayed as shown in FIG. 30A after the analysis parameters are input. . In this visualization parameter input screen, a visualization method selection field and a display method selection field are provided, and "Analysis and visualization execution" is provided below them.
A button and a "run visualization only" button are provided.

When the user selects the visualization method and the display method, the corresponding parameters are set. Next, when the user turns on the “execute analysis and visualization” button, the content is transmitted to the task server 12. In response to this, the task server 12 creates jobs for analysis execution and visualization execution. That is, the task for analysis execution and visualization execution is read and the application to be executed is recognized. Next, referring to the connected AE list, the AE to be used and its order are determined (corresponding to steps S325 to S347 in FIGS. 23 and 24).

When the job is generated, the task server 12
First, a parameter and an analysis process execution request are transmitted to an application server that executes an analysis application. Then, the analysis application executes the analysis process. (Step S34 of FIG.
It corresponds to 9 to step S361. ).

When the analysis process is completed, a process completion notice and result data are sent to the task server 12. Therefore, the task server 12 instructs the application server that has performed the analysis to send the result data to the application server that performs the visualization, and requests the application server that performs the visualization processing to perform the visualization execution request and the parameters and And data (step S363 shown in FIGS. 24 and 5).
~ Corresponds to step S385. ).

In response to this, the visualization process is executed,
When the visualization process ends, the process end notification and the result data are transmitted to the task server 12 (corresponding to steps S387 to S409 in FIG. 26). Therefore, the task server 12 notifies the user ABC, that is, the user computer 18a, of the processing end.

After that, the user ABC can operate the user computer 18a, log in to the task server 18, and obtain the analysis result and the visualization result.

On the other hand, on the input screen of the visualization parameter,
When "Only execute visualization" is turned on, the result data of the analysis process is sent only to the application server that executes the visualization without being given to the task server. In this case, the user can obtain only the visualization result.

For example, the visualization result confirmation screen is shown in FIG.
As shown in (B), the visualization result is displayed in the approximate center of the screen. A "visualization" button is provided below this visualization result, and when this "visualization" button is turned on,
Although illustration is omitted, a display method selection screen is displayed, and the visualization result can be confirmed by another display method.

[Brief description of drawings]

FIG. 1 is an illustrative view showing one embodiment of the present invention.

FIG. 2 is an illustrative view showing contents of a DB shown in FIG. 1 embodiment.

FIG. 3 is a flowchart showing a part of service menu processing of the task server shown in FIG. 1 embodiment.

FIG. 4 is a flowchart showing another part of the service menu process of the task server shown in FIG. 1 embodiment.

FIG. 5 is a flowchart showing a part of task management processing of the task server shown in FIG. 1 embodiment.

FIG. 6 is a flowchart showing another part of the task management processing of the task server shown in FIG. 1 embodiment.

FIG. 7 is a flowchart showing another portion of the task management processing of the task server shown in FIG. 1 embodiment.

FIG. 8 is a flowchart showing task registration processing of the task server shown in FIG. 1 embodiment.

FIG. 9 is a flowchart showing a part of application management processing of the task server shown in FIG. 1 embodiment.

10 is a flowchart showing another part of the application management process of the task server shown in FIG. 1 embodiment.

FIG. 11 is a flowchart showing another portion of the application management processing of the task server shown in FIG. 1 embodiment.

FIG. 12A is an illustrative view showing an example of a login screen, and FIG. 12B is an illustrative view showing an example of a service menu screen.

13A is an illustrative view showing an example of a task management screen, and FIG. 13B is an illustrative view showing an example of a task list screen. FIG.

FIG. 14A is an illustrative view showing an example of a task addition screen, and FIG. 14B is an illustrative view showing an example of a task deletion screen.

FIG. 15 is an illustrative view showing one example of a task edit screen.

FIG. 16 is an illustrative view showing one example of an application pipe addition screen.

FIG. 17A is an illustrative view showing an example of an application management screen, and FIG. 17B is an illustrative view showing an example of a registered application list screen.

FIG. 18 (A) is an illustrative view showing an example of an application addition screen, and FIG. 18 (B) is an illustrative view showing an example of an application deletion screen.

FIG. 19 is an illustrative view showing one example of an application change screen.

FIG. 20 is a flowchart showing an AE start / stop notification process of an application server.

FIG. 21 is a flowchart showing an AE list addition / deletion process of the task server.

FIG. 22 is a flowchart showing a part of the processing of the user computer and the task server for starting the cooperative processing.

FIG. 23 is a flowchart showing another part of the processing by the user computer and task server for starting the cooperative processing.

FIG. 24 is a flowchart showing a part of cooperation processing of a task server, AE, AA, and an application.

FIG. 25 is a flowchart showing another part of the cooperative processing of the task server, AE, AA, and application.

FIG. 26 is a flowchart showing another part of the cooperative processing of the task server, AE, AA, and application.

FIG. 27 is an illustrative view showing one embodiment of the present invention.

FIG. 28 (A) is an illustrative view showing one example of an available service menu screen when a certain user logs in to the task server, and (B) is available when another user logs in to the task server. It is an illustration figure which shows an example of a service menu screen.

FIG. 29A is an illustrative view showing an example of an analysis parameter input screen, and FIG. 29B is an illustrative view showing an example of an analysis parameter confirmation screen.

FIG. 30 (A) is an illustrative view showing one example of a visualization parameter input screen, and (B) is an illustrative view showing one example of a visualization result confirmation screen.

[Explanation of symbols]

10 ... System 12 ... Task server 14 ... DB 16 ... Network 18 ... User computer 20, 22 ... Application server

Continued front page    (72) Inventor Taisuke Sugita             2-8-8 Shinjuku, Shinjuku-ku, Tokyo             Lee G T (72) Inventor Takayuki Tanaka             2-8-8 Shinjuku, Shinjuku-ku, Tokyo             Lee G T (72) Inventor Hiroki Asakura             2-8-8 Shinjuku, Shinjuku-ku, Tokyo             Lee G T (72) Inventor Robin Masson             4-62-5 Minamidai, Nakano-ku, Tokyo (72) Inventor Carlos Viegas             710-50-20-506 Higashiarai, Omiya City, Saitama Prefecture F term (reference) 5B045 BB28 BB42 BB48 BB49 GG01                 5B085 BA06 BC01 BE07 BG02 BG07                 5B098 AA10 GA04 GC14 GC16

Claims (15)

[Claims] 1. A process of connecting to a plurality of application servers that provide a predetermined application via a network, and processing in the plurality of application servers in response to a task execution request from any user computer connected to the network. In an application cooperation server for coordinating with each other, a detection unit that detects whether or not an application engine that controls an application provided by the application server is connected, and instructs the connected application engine to execute the task in response to the request. An application cooperation server comprising an instruction means. 2. A database including at least user information of registered users, the user information including first task information of tasks available to the registered users, and the database being logged in by the user computer. The method according to claim 1, further comprising: a generation unit configured to generate a page of available tasks according to the first task information, and a presentation unit configured to present the page generated by the generation unit to the user computer. Application cooperation server. 3. The application cooperation according to claim 1, further comprising holding means for holding an engine list of an application engine being connected, and updating means for updating the engine list according to a detection result of the detecting means. server. 4. The database includes task management means for managing second task information of a plurality of registered tasks, and cooperation for determining a cooperation order of the application engines according to the second task information according to the request. The application cooperation server according to claim 2, further comprising an order determination unit, wherein the instruction unit instructs the application engine to execute a process according to the cooperation order. 5. The receiving means for receiving a processing end notification from the application server is further provided, and the instructing means executes processing to the next application engine when the processing end notification is received by the receiving means. The application cooperation server according to claim 4, which gives an instruction. 6. A presence / absence determining means for determining whether or not there is the next application engine when the notification of the processing end is received by the receiving means, and a task for the user computer when there is no next application engine. The application cooperation server according to claim 4, further comprising an end notifying unit for notifying the end. 7. An application server which is connected to an application cooperation server via a network and executes an application in accordance with an instruction from the application cooperation server, wherein at least one or more applications, which starts the application and corresponds to the application. Application adapter provided by
And an application engine that controls the operation of the application, the application name of the application, information about whether the application returns data during execution, start information of the application, and information about the state of the application to the application adapter. The application server, wherein only the setting information about the application adapter that receives the application is implemented. 8. The application engine has an adapter list of the application adapter, and starts the application adapter according to an application instructed by the application cooperation server by referring to the adapter list. Application server. 9. The application adapter, a status judging means for judging a processing status of the application, and a first notifying means for notifying the application engine of the processing end when the judgment result of the status judging means indicates processing end. 9. The application server according to claim 7, wherein the application engine includes a second notification unit that receives the notification of the first notification unit and notifies the application cooperation server of the end of the processing. 10. A dynamic collaboration system for distributed applications, comprising an application collaboration server connected to an arbitrary user computer and a plurality of application servers via a network, wherein the application collaboration server is provided by the application server. Detecting means for detecting the presence / absence of connection of an application engine that controls the operation of the application, and instruction means for instructing the connected application engine to execute a task in response to a task execution request from the user computer. The server includes at least one or more applications, an application adapter that launches the application and is provided corresponding to the application, and the application. An application engine that controls the operation of the application, and the application adapter receives the application name of the application, information about whether the application returns data during execution, start information of the application, and information about the state of the application. A dynamic linkage system for distributed applications that implements only the setting information for the application adapter. 11. The application cooperation server includes a database including at least user information of registered users, the user information includes first task information of tasks available to the registered users, and the database is And a presenting means for presenting the page produced by the producing means to the user computer when the user computer logs in, the producing means producing an available task page according to the first task information. The dynamic cooperation system according to claim 1. 12. The application cooperation server further comprises holding means for holding an engine list of an application engine being connected, and updating means for updating the engine list according to a detection result of the detecting means. Alternatively, the dynamic cooperation system described in 11. 13. The database includes task management means for managing second task information of a plurality of registered tasks, and cooperation for determining a cooperation order of the application engines according to the second task information according to the request. The order determining means is further provided, and the instructing means instructs the application engine to execute processing in accordance with the cooperation order.
The dynamic cooperation server described in 2. 14. The status determination means for judging the processing status of the application, the application adapter,
And a first notifying unit for notifying the application engine of the processing end when the judgment result of the situation judging unit indicates that the application cooperation server receives the notification of the first notifying unit. A second notification means for notifying the end of the processing, the application cooperation server further includes a receiving means for receiving a notification of the end of the processing from the application engine, and the instructing means notifies the end of the processing by the receiving means. 14. The dynamic cooperation system according to claim 10, wherein when the notification is received, the next application engine is instructed to execute the processing. 15. The application cooperation server determines whether or not there is the next application engine when the notification of the processing end is received by the receiving means, and when there is no next application engine. The end notification means for notifying the user computer of the end of the task is further provided.
The dynamic cooperation system according to 3 or 14.