JP5691683B2 - Portal system and method for arranging portlets having dependencies - Google Patents

Description

  The present invention relates to a portal system and a method for arranging portlets having dependency relationships.

  Among the portal systems, there is a system that prevents portlet placement omissions or placement mistakes when portlet placement is changed by managing the dependencies between portlets set by the portal administrator or portlet developer. It has been.

  For example, the system outputs a warning to the user so that a dependent portlet is also placed when placing a portlet that depends on another portlet on the portal screen, or a plurality of dependent portlets By setting so that only a part of these cannot be removed from the portal screen, portlet placement omissions or placement mistakes are prevented.

  In addition, using the relationship information regarding the relationship between two portlets, between two portal screens, or between a portlet and a portal screen, appropriate information corresponding to the relationship between the portlet and the portal screen can be easily displayed. Is known (for example, see Patent Document 1).

JP 2007-264928

  However, in the portal system described above, since it is necessary to manually register the portlet dependency in the system, there is a possibility of omission of registration or registration error.

  Moreover, since the portal administrator must grasp the dependency relationship between the portlets one by one based on the information obtained from the portlet developer and the portlet design document, the burden on the portal administrator is large.

  Furthermore, since it was necessary for the portlet developer to develop a case in which no portlet having a dependency relationship exists on the same portal screen, the burden on the portlet developer was also great.

  On the other hand, the technique described in Patent Document 1 does not display all relevant portlets appropriately.

  The present invention has been made in view of the above circumstances, and its purpose is to automatically arrange all portlets having a dependency relationship with the portlet on the portal screen when the portlet is arranged on the portal screen. It is an object of the present invention to provide a portal system that can be used and a method for arranging portlets having dependencies.

  The present invention is a portal system that is communicably connected to an administrator terminal that manages a portal screen on which a portlet is arranged, and a detection code that detects a program that communicates with other portlets in the portlet execution program Detection code embedding means for embedding, receiving means for receiving an instruction to place a portlet on the portal screen from the administrator terminal, and detection code embedded in the execution program of the received portlet when generating the portal screen Dependency information acquisition means for acquiring dependency information with other portlets based on the above, and determining whether all other portlets having a dependency relationship with the portlet are arranged on the portal screen based on the dependency information, If it is determined that all are not placed, all the other portlets are displayed. If the portal screen is regenerated as described above, and it is determined that the determination is performed again by the determination means and the determination means based on the dependency information on the portlet rearranged on the regenerated portal screen, Providing means for providing the portal screen to the operation terminal.

  According to the present invention, when a portlet is arranged on a portal screen, a portal system capable of automatically arranging all portlets having a dependency relationship with the portlet on the portal screen and a method for arranging the portlet having a dependency relationship are provided. it can.

It is a figure which shows the structure of the portal system which concerns on embodiment of this invention. It is a figure for demonstrating the position which embeds the detection code which concerns on the embodiment. It is a figure which shows an example of the screen layout information which concerns on the embodiment. It is a figure which shows an example of the dependency relationship information which concerns on the embodiment. It is a figure which shows an example of the reference relationship information which concerns on the embodiment. It is a figure for demonstrating the other portlet reference detection which concerns on the embodiment. It is a flowchart which shows a part of dependence relationship resolution process which concerns on the same embodiment. It is a flowchart which shows the other part of the dependence relationship resolution process which concerns on the embodiment. It is a flowchart which shows the deployment process which concerns on the same embodiment. It is a figure which shows the operation | movement which solves the dependency which concerns on the embodiment. It is a figure which shows the operation | movement which solves the dependency which concerns on the embodiment. It is a figure which shows the operation | movement which solves the dependency which concerns on the embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating a configuration of a portal system. As shown in the figure, the portal system 100 includes an operation terminal 20 that deploys portlets and a portal server 30 that operates under program control. The portal server 30 is connected to the administrator terminal 10 equipped with the web browser 10a and the user terminal 11 equipped with the web browser 11a so as to be able to communicate with each other.

  The operation terminal 20 includes an inter-portlet communication detection code embedding unit 21 that operates by program control, a deployment unit 22 that operates by program control, a portlet 23 that operates by program control on a portlet container 32 to be described later, and a detection code embedding. The detection code 24 embedded in the execution program of the portlet 23 by the means 21 and the portlet 25 after the detection code 24 is inserted are included.

  The portal server 30 is operated by program control, and is stored in a portal screen generation means 31, a portlet container 32, a portlet addition means 33, a portal screen generation / analysis means 34, a dependency relationship resolution means 35, and an auxiliary storage device or storage medium. Screen layout information 36 and dependency relationship information 37. Further, the portal screen generating / analyzing unit 34 includes a content analyzing unit 38 and a portal screen generating unit 39, and the portlet container 32 is inserted with the portlet deployed by the deployment unit 22 of the operation terminal 20 and the detection code 24. Have a customized portlet.

  1 includes portlet A, portlet A including detection code 24 (hereinafter referred to as portlet A ′), portlet B and portlet B including detection code 24 (hereinafter referred to as portlet B ′). ing.

  As shown in FIG. 2, the detection code embedding unit 21 analyzes the execution program of the portlet 23, mechanically embeds the detection code 24 immediately after the list of inter-portlet communication instructions, and the portlet 25 into which the detection code 24 is inserted. Is generated. The detection code 24 is a program code that operates at the time of message communication between portlets and notifies the portal server 30 of information for specifying a message transmission source portlet and a reception destination portlet. Note that the technology related to the above-described code embedding is the same as the conventional technology, and thus detailed description thereof is omitted.

  The deployment unit 22 deploys the portlet 23 and the portlet 25 into which the detection code 24 is inserted into the portlet container 32 of the portal server 30.

  When displaying a portal screen on the web browser 11 a of the user terminal 11, the user transmits a predetermined request to the portal screen generation unit 31 of the portal server 30 via the web browser 11 a of the user terminal 11.

  Upon receiving a request from the user terminal 11, the portal screen generation unit 31 acquires information on a portlet to be arranged on the portal screen and its layout information from the screen layout information 36 (see: FIG. 3). Then, the portal screen generation unit 31 makes an execution request for the portlet to be arranged to the portlet container 32. As shown in FIG. 3, the screen layout information 36 is information indicating the relationship between the portlet name displayed on the portal screen and the portlet placement position.

  The portlet container 32 executes the target portlet in response to the execution request from the portal screen generation unit 31, and returns html information of the execution result to the portal screen generation unit 31.

  Thereafter, the portal screen generation unit 31 refers to the acquired html information and layout information of each portlet, determines which portlet is to be placed on the portal screen, and displays the determined portal screen on the user terminal 11. Send.

  The user terminal 11 displays the portal screen transmitted from the portal screen generation means 31 using the web browser 11a. In this way, the portal system 100 is configured so that the user can display a desired portal screen.

  When the administrator of the portal system 100 adds a portlet to the portal screen, a predetermined request is transmitted to the portlet adding means 33 of the portal server 30 via the web browser 10a of the administrator terminal 10.

  Upon receiving a request from the administrator terminal 10, the portlet addition unit 33 updates the screen layout information 36 and adds the target portlet to an arbitrary position on the portal screen. In synchronization with this, the portlet adding means 33 transmits a request to the portal screen generating / analyzing means 34.

  When the portal screen generating / analyzing unit 34 receives a request from the portlet adding unit 33, the portal screen generating / analyzing unit 34 acquires, from the screen layout information 36, information on the portlet to be arranged on the portal screen. Then, the portal screen generating / analyzing unit 34 requests the portlet container 32 to execute the portlet to be arranged. However, the execution request here is made not to the portlet 23 but to the portlet 25 in which the detection code 24 is inserted.

  The portlet 25 is executed in the portlet container 32 and returns the html information of the execution result to the portal screen generation unit 39 of the portal screen generation / analysis unit 34. Further, when message communication is performed with other portlets during the execution of the portlet 25, the detection code 24 operates and information for identifying the message transmission source portlet and the reception destination portlet is generated on the portal screen generation / analysis means 34. Notify Upon receiving this notification, the portal screen generating / analyzing unit 34 records the dependency relationship information between the portlets in the dependency relationship information 37 (refer to FIG. 4). As shown in FIG. 4, the dependency relationship information 37 is information indicating the relationship between the portlet name and the dependency destination portlet name.

  The portal screen generation / analysis means 34 aggregates the acquired html information of each portlet as one portal screen.

  Next, the portal screen generation / analysis unit 34 checks whether or not a reference relationship exists between the portlet contents in the content analysis unit 38 included therein (see: FIG. 5). This confirmation is performed, for example, by determining whether or not an instruction for referring to another portlet is included in the script program in the portlet content as shown in FIG. 5 (refer to FIG. 6). FIG. 5 shows a case where there is a relationship for referring to another portlet between portlet contents (acquisition of work address from portlet D). FIG. 6 shows how the content analysis means 38 detects a code referring to another portlet from the other portlet reference instruction list.

  When the reference relationship exists, the portal screen generation / analysis unit 34 determines that the dependency relationship exists between the portlets, and records the reference relationship in the dependency relationship information 37 as the dependency relationship information. In synchronization with this, the portal screen generating / analyzing unit 34 transmits a request to the dependency relationship solving unit 35.

  When receiving the request from the portal screen generating / analyzing unit 34, the dependency relationship solving unit 35 acquires information on the portlet to be arranged on the portal screen from the screen layout information 36. Further, the dependency relationship solving means 35 acquires dependency relationship information between portlets from the dependency relationship information 37. Then, by collating these two pieces of information, the dependency relationship solving means 35 confirms whether or not all the portlets on which the portlets depend are arranged on the same portal screen. When the dependency destination portlet is not arranged, the portlet addition means 33 is requested to add the portlet.

  Next, with reference to the flowcharts of FIGS. 7 and 8, when a portlet is added to the portal screen, a process for arranging all other portlets having a dependency relationship with the added portlet on the portal screen will be described in detail.

  First, a request is transmitted from the administrator terminal 10 to the portlet adding means 33 of the portal server 30 using the web browser 10a (S101).

  When receiving a request from the administrator terminal 10 (receiving means), the portlet adding means 33 updates the screen layout information 36 and adds the target portlet to an arbitrary position on the portal screen (S102).

  Next, the portal screen generating / analyzing unit 34 acquires information on the portlet to be arranged on the portal screen from the screen layout information 36, and issues an execution request for the target portlet to the portlet container 32 (S103). The request in step S103 is made to the portlet 25 in which the detection code 24 is inserted instead of a normal portlet.

  The portlet 25 is executed on the portlet container 32, and the html information of the execution result is returned to the portal screen generation / analysis means 34 (S105).

  When message communication is performed with another portlet during the execution of the portlet 25 (S106: YES), the detection code 24 operates to generate and analyze the information for identifying the message transmission source portlet and the reception destination portlet. The means 34 is notified (S107).

  Upon receiving this notification, the portal screen generating / analyzing unit 34 records the dependency relationship between the portlets in the dependency relationship information 37 (S108). Thereby, the dependency information with other portlets can be acquired based on the detection code embedded in the execution program of the portlet that has received an instruction from the administrator terminal 10 (dependency information acquiring means).

  When the dependency relationship is recorded (S108), or when message communication is not performed with another portlet during the execution of the portlet 25 (S106: NO), the portal screen generation / analysis unit 34 performs steps S104 to S108. It is determined whether the process has been repeated for the number of portlets (S109).

  If the number of portlets has not been repeated (S109: NO), the above-described processing of steps S104 to S108 is repeated.

  When the number of portlets is repeated (S109: YES), the portal screen generation / analysis unit 34 aggregates the acquired html information of each portlet as one portal screen (S110).

  Next, the content analysis unit 38 confirms whether there is a reference relationship between the portlet contents (S111).

  If there is a reference relationship (S112: YES), the content analysis means 38 determines that there is a dependency relationship between the portlets, and records the dependency relationship in the dependency relationship information 37 (S113). Thereby, it is possible to acquire reference information indicating other portlets having other contents referred to by the contents generated by the portlet (reference information acquiring means). In synchronization with this processing or when there is no reference relationship (S112: NO), the portal screen generation / analysis unit 34 transmits a request to the dependency relationship resolution unit 35.

  When receiving the request from the portal screen generating / analyzing unit 34, the dependency relationship solving unit 35 acquires a list of portlets to be arranged on the portal screen from the screen layout information 36 (S114).

  Further, the dependency relationship solving unit 35 acquires the dependency relationship between the portlets from the dependency relationship information 37 (S115).

  Next, the dependency relationship solving means 35 checks these two pieces of information to confirm whether or not all the portlets on which each portlet depends are arranged on the same portal screen (S116).

  When all the portlets having the dependency relationship are not arranged (S117: NO), the dependency relationship solving unit 35 requests the portlet adding unit 33 to add a missing portlet (S118). Then, the process returns to step S102, and the above-described steps S102 to S118 are repeated until it is determined that all the portlets having the dependency relationship are arranged on the same portal screen. That is, based on the dependency relationship information 37, it is determined whether or not all other portlets having a dependency relationship with the portlet are arranged on the same portal screen. The portal screen is regenerated so as to display all, and the above-described determination can be performed again based on the dependency relationship information 37 regarding the portlet rearranged on the regenerated portal screen (determination means).

  If all the portlets having the dependency relationship are arranged on the same portal screen (S117: YES), the portal server 30 provides the portal screen to the administrator terminal 10 (providing means), and this process ends. .

  Next, processing for deploying the portlet 25 into which the portlet 23 and the detection code 24 are inserted in the portlet container 32 will be described with reference to FIG.

  The detection code embedding means 21 analyzes the execution program of the portlet 23 and inserts the detection code 24 for detecting communication between portlets immediately after the list of communication instructions between portlets without correcting the source, and after inserting the detection code The portlet 25 is generated (S201).

  Next, the deployment unit 22 deploys the portlet 23 and the portlet 25 into which the detection code 24 is inserted into the portlet container 32 on the portal server 30 (S202).

  In this way, the portlet 23 and the portlet 25 are deployed in the portlet container 32.

  Next, a specific operation executed by the portal system 100 when the administrator arranges a portlet on the portal screen will be described with reference to FIGS.

  More specifically, in the situation where portlet A receives a message from portlet B and references the content of portlet C from the content of portlet B, that is, there is a dependency relationship of portlet A → portlet B → portlet C. A case where portlet A is added to the portal screen A by the adding means 33 will be described.

  At this time, the portal screen generating / analyzing unit 34 acquires information about the portlet A as a portlet to be arranged on the portal screen from the screen layout information 36. Subsequently, the portal screen generation / analysis unit 34 makes an execution request to the portlet container 32 for the portlet A ′ in which the detection code 24 is inserted into the portlet A.

  The portlet A ′ is executed on the portlet container 32, and html information of the execution result is returned to the portal screen generation / analysis means 34.

  When the message communication is performed with the portlet B ′ during the execution of the portlet A ′ (FIG. 10: S11), the detection code 24 operates and the information “Portlet A depends on the portlet B” is displayed. The portal screen generation / analysis means 34 is notified (FIG. 10: S12). Upon receiving this notification, the portal screen generating / analyzing unit 34 records the dependency relationship between the portlet A and the portlet B in the dependency relationship information 37 (FIG. 10: S13).

  Subsequently, the dependency relationship solving means 35 acquires information on the portlets arranged on the portal screen and the dependency relationship between the portlets from the screen layout information 36 and the dependency relationship information 37. Each information at this point is as shown in FIG. Since the portlet B which is the dependency destination of the portlet A is not yet arranged on the portal screen A, the dependency relationship resolving unit 35 requests the portlet adding unit 33 to add the portlet B (FIG. 10: S14).

  As shown in FIG. 11, portlet B is added to portal screen A by portlet adding means 33, and information about portlet B is recorded in screen layout information 36.

  Then, the portal screen generating / analyzing unit 34 acquires information on portlet A and portlet B as portlets to be arranged on the portal screen from the screen layout information 36. Subsequently, the portal screen generating / analyzing unit 34 requests the portlet container 32 to execute the portlet A ′ and the portlet B ′. The portlet A ′ is executed in the same manner as described above. The portlet B ′ is executed on the portlet container 32, and the html information of the execution result is returned to the portal screen generation / analysis means 34 (FIG. 11: S21).

  The content analysis unit 38 detects that the content of the portlet C is referred to from the content of the portlet B ′, and notifies the portal screen generation / analysis unit 34 of the information “Portlet B depends on the portlet C”. (FIG. 11: S22).

  In response to this notification, the portal screen generation / analysis unit 34 records the dependency relationship between the portlet B and the portlet C in the dependency relationship information 37 (FIG. 11: S23).

  Subsequently, the dependency relationship solving means 35 acquires information on portlets arranged on the portal screen and dependency relationship information between portlets from the screen layout information 36 and the dependency relationship information 37. Each information at this time is as shown in FIG. Since portlet C which is the dependency destination of portlet B is not yet arranged on portal screen A, a request to add portlet C is made to portlet adding means 33 (FIG. 11: S24).

  As shown in FIG. 12, portlet C is added to the portal screen A by the portlet adding means 33, and information on the portlet C is recorded in the screen layout information 36.

  Then, the portal screen generating / analyzing unit 34 acquires information on portlet A, portlet B, and portlet C as portlets to be arranged on the portal screen from the screen layout information 36. Subsequently, the portal screen generating / analyzing unit 34 requests the portlet container 32 to execute portlet A ′, portlet B ′, and portlet C ′. The portlets A ′ and B ′ are executed in the same manner as described above. The portlet C ′ is executed on the portlet container 32, and the html information of the execution result is returned to the portal screen generation / analysis means 34.

  Subsequently, the dependency relationship solving means 35 acquires information on the portlets to be arranged on the portal screen and the dependency relationship between the portlets from the screen layout information 36 and the dependency relationship information 37, respectively. Each information at this point is as shown in FIG. Since all the portlets A, B, and C including the portlets B and C on which the respective portlets A and B depend are arranged on the portal screen A, the processing is ended.

  According to the portal system 100 configured as described above, only a portlet is arranged on the portal screen, and all portlets having a dependency relationship with the portlet are automatically arranged on the portal screen.

  Therefore, even if the administrator of the portal system 100 does not grasp the dependency relationship between portlets in advance, it is possible to prevent omission of registration or registration error of other portlets having dependency relationship with the arranged portlet. In addition, it is not necessary to assume a case where a portlet having a dependency relationship does not exist on the same portal screen, and the burden on the portlet developer is reduced.

  In the above embodiment, the operation terminal 20 and the portal server 30 are described as separate devices. However, these devices may be included in one device.

  In addition, this invention is not limited to the above-mentioned embodiment, A various deformation | transformation is possible in the case of the implementation.

  A part or all of the above embodiment can be described as in the following supplementary notes, but is not limited thereto.

(Appendix 1)
A portal system that is communicably connected to an administrator terminal that manages a portal screen on which a portlet is placed,
A detection code embedding means for embedding a detection code for detecting a program that communicates with other portlets in the portlet execution program;
Receiving means for receiving an instruction to place a portlet on the portal screen from the administrator terminal;
When generating the portal screen, dependency information acquisition means for acquiring dependency information with other portlets based on a detection code embedded in the execution program of the portlet that has received the instruction;
Based on the dependency information, it is determined whether all other portlets having a dependency relationship with the portlet are arranged on the portal screen. If it is determined that all other portlets are not arranged, all the other portlets are displayed. A determination unit that regenerates the portal screen and re-performs the previous determination based on the dependency information regarding the portlet rearranged on the regenerated portal screen,
If it is determined by the determination means that all are arranged, providing means for providing the portal screen to the operation terminal;
A portal system characterized by comprising:

(Appendix 2)
When generating the portal screen, comprising a reference information acquisition means for acquiring reference information indicating other portlets having other content referred to by the content generated by the portlet,
The portal system according to appendix 1, wherein the dependency information includes reference information acquired by the reference information acquisition unit.

(Appendix 3)
The portal system according to appendix 1 or 2, wherein the detection code embedding unit embeds the detection code immediately after a program for communicating with the other portlet.

(Appendix 4)
A portlet placement method having a dependency relationship with a portal system that is communicably connected to an administrator terminal that manages a portal screen on which a portlet is placed,
Receiving an instruction to place a portlet on a portal screen from the administrator terminal;
When generating the portal screen, obtaining dependency information with other portlets based on a detection code for detecting a program that communicates with other portlets embedded in the portlet execution program that has received the instruction; ,
Based on the dependency information, it is determined whether all other portlets having a dependency relationship with the portlet are arranged on the portal screen. If it is determined that all other portlets are not arranged, all the other portlets are displayed. Regenerating the portal screen as described above, and performing the determination again based on the dependency information regarding the portlet rearranged on the regenerated portal screen;
If it is determined that all are arranged in the step, providing the portal screen to the operation terminal;
A method for arranging portlets having dependency relations, characterized by comprising:

  The present invention can be widely applied to a portal system having a dependency relationship between portlets and a method for solving the dependency relationship.

10: administrator terminals 10a, 11a ... web browser 11 ... user terminal 20 ... operation terminal 21 ... detection code embedding means 22 ... deployment means 23 ... portlet 24 ... Detection code 25: Portlet 30 in which detection code is embedded ... Portal server 31 ... Portal screen generation means 32 ... Portlet container 33 ... Portlet addition means 34 ... Portal screen generation / analysis means 35 ... dependency relationship solving means 36 ... screen layout information 37 ... dependency relationship information 100 ... portal system

Claims (4)

A portal system that is communicably connected to an administrator terminal that manages a portal screen on which a portlet is placed,
A detection code embedding means for embedding a detection code for detecting a program that communicates with other portlets in the portlet execution program;
Receiving means for receiving an instruction to place a portlet on the portal screen from the administrator terminal;
When generating the portal screen, dependency information acquisition means for acquiring dependency information with other portlets based on a detection code embedded in the execution program of the portlet that has received the instruction;
Based on the dependency information, it is determined whether all other portlets having a dependency relationship with the portlet are arranged on the portal screen. If it is determined that all other portlets are not arranged, all the other portlets are displayed. A determination unit for regenerating the portal screen as described above, and performing the determination again based on the dependency information regarding the portlet rearranged on the regenerated portal screen,
Providing means for providing the portal screen to the administrator terminal when it is determined that the determination means is all arranged;
A portal system characterized by comprising: When generating the portal screen, comprising a reference information acquisition means for acquiring reference information indicating other portlets having other content referred to by the content generated by the portlet,
The portal system according to claim 1, wherein the dependency information includes reference information acquired by the reference information acquisition unit.   The portal system according to claim 1, wherein the detection code embedding unit embeds the detection code immediately after a program for communicating with the other portlet. A portlet placement method having a dependency relationship with a portal system that is communicably connected to an administrator terminal that manages a portal screen on which a portlet is placed,
Receiving an instruction to place a portlet on a portal screen from the administrator terminal;
When generating the portal screen, obtaining dependency information with other portlets based on a detection code for detecting a program that communicates with other portlets embedded in the portlet execution program that has received the instruction; ,
Based on the dependency information, it is determined whether all other portlets having a dependency relationship with the portlet are arranged on the portal screen. If it is determined that all other portlets are not arranged, all the other portlets are displayed. Regenerating the portal screen as described above, and performing the determination again based on the dependency information regarding the portlet rearranged on the regenerated portal screen;
If it is determined that all are arranged in the step, providing the portal screen to the administrator terminal ;
A method for arranging portlets having dependency relations, characterized by comprising:

Images