JP2004157676A - Business integration device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a business integration device capable of executing another application having linkage relation from a certain application, and allowing easy grasp of a linkage key or transition of the application from an initial state to the present. <P>SOLUTION: Every time an application linkage part 25 executes the linking application, the application linkage part 25 collects information about the applications of a linkage source and a linkage destination, and displays a linkage history between the applications. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a business integration device that displays a plurality of executable applications.
[0002]
[Prior art]
A conventional business integration device integrates different applications for each business and receives access to the various applications in order to improve the efficiency of various businesses in the manufacturing and finance industries. Which is displaying multiple possible applications).
Therefore, if the user operates his / her own terminal to access the business portal server and display the portal screen, various applications can be appropriately executed.
[0003]
[Patent Document 1]
JP 2001-338125 A (FIGS. 2 and 4)
[0004]
[Problems to be solved by the invention]
Since the conventional business integration apparatus is configured as described above, various applications can be appropriately executed by accessing the business portal server and displaying the portal screen. However, since cooperation between a plurality of applications is not achieved, it is not possible to execute another application directly from one application, and it is necessary to return to the portal screen and execute another application once. was there.
Even if one application can execute another application directly, the cooperation history indicating the cooperation source and the cooperation destination of the application is not specified. There has been a problem that the transition of the application from the state to the present and the cooperation key may not be understood.
[0005]
SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. In addition to being able to execute another application that has a cooperative relationship from one application, it is also possible to execute transition of an application from an initial state to the present and a cooperative key. It is an object of the present invention to obtain a business integration device capable of easily grasping the information.
[0006]
[Means for Solving the Problems]
The business integration apparatus according to the present invention includes a cooperation history display unit that collects information on a cooperation source and a cooperation destination application and displays a cooperation history between applications each time the cooperation unit executes an application that cooperates. Things.
[0007]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of the present invention will be described.
Embodiment 1 FIG.
FIG. 1 is a system configuration diagram showing a business system to which a business integration device according to a first embodiment of the present invention is applied. In the figure, application servers 1 to 3 hold applications related to various business, and are used by the business integration device. A certain business portal server 4 receives an execution of an application held by the application servers 1 to 3, and executes the application. In addition, the business portal client 5 receives an application execution request under user operation, and transmits the execution request to the business portal server 4.
[0008]
FIG. 2 is a configuration diagram showing the internal configuration of the business portal server 4 which is a business integration device. In the figure, the script processing engine 11 has a built-in cooperation key management unit 12, and the cooperation key management unit 12 has a cooperation history between applications. The application cooperation script master 13 stores information on the cooperation history between applications.
The portal GUI 14 has a built-in cooperation key monitoring unit 15, and the cooperation key monitoring unit 15 displays the execution result of the application and the cooperation history between the applications.
[0009]
FIG. 3 is a configuration diagram showing a detailed configuration of the cooperation key management unit 12 and the cooperation key monitoring unit 15. In the figure, an application menu display unit 21 constituting an application menu display unit is held by the application servers 1 to 3. It has a function of generating an application menu indicating an application and displaying the application menu on the display of the business portal client 5.
The application selecting unit 22 has a function of receiving a selection of an application to be executed from an application menu, the application executing unit 23 has a function of executing the selected application, and the application displaying unit 24 has an application executing unit 23 or an application executing unit. It has a function of displaying the execution result of the coordination unit 25 on the display of the business portal client 5. Note that the application selecting unit 22 and the application executing unit 23 constitute an application executing unit.
[0010]
The application linking unit 25 constituting the linking unit has a function of receiving an execution request of an application linked with the application executed by the application executing unit 23 and having a function of executing the application. Each time the cooperative application is executed, the cooperative application has a function of collecting information on the cooperating source and cooperating destination applications. The cooperative history display unit 27 refers to the information collected by the log information collecting unit 26, and performs coordination between the applications. It has a function to display the history. The history information collecting unit 26 and the cooperation history display unit 27 constitute a cooperation history display unit.
FIG. 4 is a flowchart showing the processing contents of the cooperation key management unit 12 and the cooperation key monitoring unit 15.
[0011]
Next, the operation will be described.
First, when the user operates the business portal client 5 to access the business portal server 4, the script processing engine 11 of the business portal server 4 transmits information for prompting the user to input a user ID to the business portal client 5.
[0012]
When the user operates the business portal client 5 and inputs a user ID, the cooperation key monitor unit 15 of the script processing engine 11 performs an authentication process using the user ID as a key, and executes an application prepared for the user. Identify.
Here, for convenience of explanation, it is assumed that the applications A to F held in any of the application servers 1 to 3 are applications prepared for the user.
The application menu display unit 21 of the link key monitor unit 15 generates an application menu indicating that the applications A to F are executable applications, and displays the application menu on the display of the business portal client 5 (step ST1). .
[0013]
When the user who has viewed the application menu operates the business portal client 5 and selects an application desired to be executed, the application selecting unit 22 of the cooperative key management unit 12 performs a selection accepting process (step ST2).
When the application selecting unit 22 performs the selection accepting process, the application execution unit 23 of the cooperation key management unit 12 executes the application selected by the user, and the application display unit 24 of the cooperation key monitoring unit 15 The execution result is displayed on the display of the business portal client 5 (step ST3).
For example, if the application selected by the user is the application A, the application A is executed. For example, if the application A is related to an application for creating a “process guide work flow”, a database (not shown) The data of the “process guide business flow” created by the user in the past is read out, and the “process guide business flow” created by the user is displayed (see FIG. 5). However, if there is no data of the “process guide business flow” created in the past, a business flow creation screen is displayed.
[0014]
The application linking unit 25 of the linking key management unit 12 requests the user who has viewed the “process guide business flow” that is the execution result of the application A to operate the business portal client 5 and execute the application linked to the application A. Then, a process of receiving an execution request of the cooperating application is performed (step ST4).
Then, the application linking unit 25 executes the linked application by using a link key defined in advance (for example, a process number assigned when a “process guide work flow” is created in the past). Then, the application display unit 24 of the cooperation key monitor unit 15 displays the execution result of the application on the display of the business portal client 5 (step ST5).
[0015]
For example, when the user operates the business portal client 5 and clicks “Approval application calculation” in the “Process guide business flow”, an application indicating “Approval application calculation work guide” (here, for convenience of explanation, , Application B) to display an “approval application calculation work guide” (see FIG. 6).
Here, the coordination key is a unique number or the like indicating an individual concrete task common to the application A and the application B, and corresponds to, for example, an order number, a process number, a part number, or the like. It should be noted that the link key is composed of a link key name and a link key value.
[0016]
When the application coordinating unit 25 executes the cooperating application, the history information collecting unit 26 of the coordinating key managing unit 12 collects information on the cooperating source and cooperating destination applications (step ST6).
That is, in the above example, in addition to the FROM-TO information indicating that the cooperation source application is the application A and the cooperation destination application is the application B, the application cooperation unit 25 uses the application B to execute the cooperation application B. The collected cooperation key (for example, the process number assigned when the “process guide work flow” was created in the past) is also collected.
[0017]
The link history display unit 27 of the link key monitor unit 15 generates a link history screen indicating the link history between the applications with reference to the information collected by the log information collecting unit 26, and as shown in FIG. The cooperation history screen is displayed on the display of the business portal client 5 (step ST7).
Note that the cooperation history screen is updated every time the application cooperation unit 25 executes the cooperating application, and is resident and displayed on a part of the display.
[0018]
Here, FIG. 8 shows a transition image of the cooperation history screen. In the header part of the table, “Process No.” is a number that sequentially numbers the application to be executed, and “Cooperation script No.” is the number of the application to be executed. It is a unique number.
The “cooperation script name” is the name of the application to be executed, “application name: FROM” is the application of the cooperation source, and “application name: TO” is the application of the cooperation destination.
Further, “cooperation key 1” is a coordination key that appears first, and “cooperation key 2” is a coordination key that appears next. When three or more cooperation keys appear, the cooperation key 3, the cooperation key 4,... The cooperation key N are displayed. When a plurality of cooperation keys appear, the narrowing of the cooperation is performed based on the AND condition of each cooperation key. Done.
[0019]
Numbers <1> to <6> at the upper left of the cooperation history screen in FIG. 8 represent screen transitions, and in each screen transition, the row with the largest “Process No” (top row) indicates the latest cooperation processing. And the second and subsequent lines indicate the past cooperative processing.
For example, “Process No = 2” in the numbers <2> to <6> indicates that the application A is linked to the application B, and the link key at that time is “XX01” and the link key value is “ 123456 ".
"Process No. 1" in the numbers <1> to <6> is a special script, and the user ID at the time of login is displayed as a cooperation key.
[0020]
As is clear from the above, according to the first embodiment, every time the application cooperation unit 25 executes the cooperating application, information on the application of the cooperation source and the cooperation destination is collected, and the cooperation history between the applications is stored. Because it is configured to display, even if the cooperation of the application is complicated, it is possible to easily grasp the transition of the application from the initial state to the present and the cooperation key, and as a result, various tasks This has the effect of increasing efficiency.
[0021]
Further, according to the first embodiment, when the application cooperation unit 25 executes an application to cooperate, the application is executed using a pre-defined cooperation key. Each time execution of an application is requested, the application can be executed without defining a link key.
Further, according to the first embodiment, the configuration is such that the cooperation key used when the application cooperation unit 25 executes the cooperating application is displayed, so that the effect that the application cooperation condition can be grasped is obtained. Play.
Furthermore, according to the first embodiment, the cooperation history screen indicating the cooperation history between the applications is configured to be resident and displayed on a part of the display, so that the user does not need to request the display of the cooperation history screen. This has the effect of being able to grasp the transition and the cooperation key.
[0022]
Embodiment 2 FIG.
In the first embodiment, the case where the application cooperation unit 25 executes the application using the cooperation key defined in advance when executing the application to cooperate is described, but the user operates the business portal client 5 by operating the business portal client 5. Then, when a request for resetting the cooperation key is output, as shown in FIG. 9, the application cooperation unit 25 blanks the column of the process No. next to the latest process, and sets a predefined cooperation key as the default cooperation key. It may be returned.
As a result, there is an effect that the coordination key can be deleted according to the user's request.
[0023]
Embodiment 3 FIG.
In the first embodiment, the case where the application cooperation unit 25 executes the application using the cooperation key defined in advance when executing the application to cooperate is described, but the user operates the business portal client 5 by operating the business portal client 5. Then, when the cooperation key setting request is output, as shown in FIG. 10, the application cooperation unit 25 displays a pop-up menu for setting the cooperation key on the display of the business portal client 5, accepts the setting of the cooperation key, and The application may be executed using a link key.
As a result, there is an effect that a cooperative key can be set according to a user's request and a cooperative application can be narrowed down.
[0024]
Embodiment 4 FIG.
In the first embodiment described above, each time the application cooperation unit 25 executes the cooperating application, the information about the cooperation source and the cooperation destination application is collected and the cooperation history between the applications is displayed. Operates the business portal client 5 and specifies, for example, “Process No.” on the cooperation history screen, and displays the execution result of the cooperation source application and the execution result of the cooperation destination application at the “Process No.” in the business portal. It may be displayed on the client 5.
As a result, the execution result of the application executed in the past can be displayed, so that, for example, when a certain operation is being performed, the effect of being able to check the contents of the past operation is provided.
[0025]
【The invention's effect】
As described above, according to the present invention, every time the coordinating unit executes the cooperating application, information on the cooperating source and cooperating destination applications is collected and the cooperative history between the applications is displayed. However, even if the cooperation relationship between the applications is complicated, there is an effect that the transition of the application from the initial state to the present and the cooperation key can be easily grasped.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing a business system to which a business integration device according to a first embodiment of the present invention is applied.
FIG. 2 is a configuration diagram illustrating an internal configuration of a business portal server that is a business integration device.
FIG. 3 is a configuration diagram illustrating a detailed configuration of a cooperation key management unit and a cooperation key monitoring unit;
FIG. 4 is a flowchart illustrating processing contents of a coordination key management unit and a coordination key monitoring unit.
FIG. 5 is an explanatory diagram showing a display example of a business flow of a process guide.
FIG. 6 is an explanatory diagram showing a display example of a work guide for calculating an approval application.
FIG. 7 is an explanatory diagram showing a screen display example of a business portal client.
FIG. 8 is an explanatory diagram showing screen transition of a cooperation history screen.
FIG. 9 is an explanatory diagram showing screen transition of a cooperation history screen.
FIG. 10 is an explanatory diagram showing screen transition of a cooperation history screen.
[Explanation of symbols]
1-3 Application Server, 4 Business Portal Server (Business Integration Device), 5 Business Portal Client, 11 Script Processing Engine, 12 Cooperation Key Management Unit, 13 Application Cooperation Script Master, 14 Portal GUI, 15 Cooperation Key Monitor Unit, 21 Applications Menu display unit (application menu display unit), 22 application selection unit (application execution unit), 23 application execution unit (application execution unit), 24 application display unit, 25 application cooperation unit (cooperation unit), 26 history information collection unit, 27 Cooperation history display unit (cooperation history display means).

Claims (7)

Application menu display means for displaying an application menu indicating a plurality of executable applications; and accepting selection of an application desired to be executed from the application menu displayed on the application menu display means, and executing the application An application execution unit, a coordination unit that receives an execution request of an application that cooperates with the application executed by the application execution unit, and executes the application. A business integration device comprising: a cooperation history display unit that collects information about a cooperation destination application and displays a cooperation history between applications. 2. The business integration device according to claim 1, wherein the coordination unit executes the cooperative application by using a pre-defined coordination key when executing the cooperative application. 3. The business integration apparatus according to claim 2, wherein the coordinating means returns a predefined coordination key to a default coordination key when receiving a coordination key reset request. 2. The business integration apparatus according to claim 1, wherein the coordinating unit accepts a setting of a coordination key when executing the cooperating application, and executes the application using the coordination key. The business integration device according to any one of claims 1 to 4, wherein the cooperation history display means displays a cooperation key used when executing an application cooperating with the cooperation means. The business integration device according to claim 1, wherein the cooperation history display unit displays a cooperation history screen indicating a cooperation history between the applications on a part of a display. The business integration apparatus according to claim 1, wherein the cooperation history display unit receives a display request of an application executed in the past and displays the application.

Images