JP5648971B2 - Portal server and portal page display method - Google Patents

Description

  The present invention relates to a portal server for displaying a portal page and a portal page display method.

  The portal system arranges a plurality of small screens called portlets on a portal page screen, and the portal page is configured to display portlets related to a business system or a web page. In this portal system, the user can move the display position of the portlet in the portal page within the scope of authority. Therefore, the user can move the portlet so that the user can easily perform business processing or web page browsing by an operation such as drag and drop.

  In general portal systems, a portal page tab function is provided. Multiple portals can be placed on each portal page using this portal page tab function, and the user can switch to the desired portal page by pressing the portal page tab and display the portlet to be used. ing.

  Furthermore, a technique is known in which a user can customize the arrangement of portlets displayed on a portal page by using a customization screen (see, for example, Patent Document 1).

JP 2004-78276 A

  In a portal system having a portal page tab function, when the number of portal pages to be used increases, it may not be possible to grasp which portlet is displayed on which portal page. For this reason, it takes much time and effort when the user performs management such as changing the display position of the portlet.

  For example, considering the case where a portlet displayed at a predetermined position on a portal page is changed to a specific position on another portal page in order to improve business efficiency, it is necessary to take the following procedure.

  First, the user switches between portal pages using the portal page tab function, and checks which portlet is configured to be displayed on which portal page. Next, the user considers the processing efficiency at the time of performing business, and examines the portal page that displays the portlet to be moved and the configuration of the portlet in the portal page, and selects the optimal portal page. Subsequently, the user drags and drops the portlet to be moved onto the selected portal page. After the portlet to be moved is moved to the selected portal page in this way, the user switches the portal page to the selected portal page, and moves the portlet to be moved to a specific position. It was necessary to follow the procedure of changing the display position of.

  Therefore, particularly when there are a large number of portal pages and a large number of portlets, the time required for the user to manage the change of the display position of the portlet is a time that cannot be ignored. For this reason, even if the portlet customization function of the portal system is used, it takes time to customize the display position of the portlet, and the customization function cannot shorten the time required for managing the portlet.

  Some portal systems provide a site map function. The site map function is a function for displaying a portal page in a portal site and a list of portlets displayed on the portal page in a tree shape.

  However, since the site map function cannot visually recognize the display position of the portlet in the portal page, in order to manage the change of the display position of the portlet, etc., the user eventually switches the portal page and displays it on each portal page. It is necessary to confirm the portlet to be used. Therefore, even if the site map function is used, the inconvenience in customizing the display position of the portlet described above cannot be solved.

  Furthermore, the technique described in Patent Document 1 cannot grasp the display position of a portlet displayed on each portal page.

  The present invention has been made in view of the above circumstances, and its purpose is to easily visually recognize the display positions of portlets displayed on a plurality of portal pages when the user uses a plurality of portal pages. It is to provide a portal server and a portal page display method capable of performing the above.

  The present invention is a portal server configured to be able to provide a plurality of portal pages, a holding means for holding first portlet configuration information relating to a root portal page that displays each of the plurality of portal pages in a portlet format, and a client Receiving means for receiving a display request for the root portal page from the receiving means, and when receiving the display request by the receiving means, an acquiring means for acquiring the first portlet configuration information held in the holding means, and a first acquired by the acquiring means Based on the portlet configuration information of the above, the root portal page screen is generated by using the object generation unit that generates the portlet-format portal page object to be displayed on the root portal page and the object generated by the object generation unit. root Characterized in that it comprises a providing means for providing over barrel page screen to the client, the.

  Another aspect of the present invention is a portal page display method of a portal server configured to be capable of providing a plurality of portal pages, the portal page relating to a root portal page that displays each of the plurality of portal pages in a portlet format. A step of receiving a portlet portal configuration information and receiving a root portal page display request from a client; and a step of acquiring first portlet configuration information held in a holding unit when a display request is received; , Based on the first portlet configuration information acquired by the acquisition means, generating a portlet-format portal page object to be displayed on the root portal page, generating a root portal page screen using the generated object, and Generate And having the steps of: providing a route portal page screen to the client.

  ADVANTAGE OF THE INVENTION According to this invention, when a user uses a some portal page, the portal server and portal page display method which can visually recognize the display position of the portlet displayed on these some portal pages easily can be provided.

It is a figure which shows the structure of the portal system which concerns on embodiment of this invention. It is a figure which shows the example of a screen of the root portal page concerning the embodiment. It is a figure which shows the example of a screen of the portal page which concerns on the embodiment. It is a table which shows the example of the portlet structure information which concerns on the embodiment. It is a flowchart which shows the portal screen display process which concerns on the same embodiment. It is a flowchart which shows the portlet content acquisition process which concerns on the same embodiment. It is a flowchart which shows the title bar production | generation process which concerns on the embodiment. It is a figure which shows the example of a screen of the root portal page after the portlet movement based on the embodiment.

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

  FIG. 1 shows the configuration of the portal system 10. The portal system 10 includes a client 100 and a portal server 200. In the figure, only one client 100 is shown for simplicity of explanation.

  The client 100 is an information processing apparatus such as a personal computer and has a browser 101. The user of the client 100 displays a portal page provided from the portal server 200 via the browser 101 by performing a predetermined operation, and can perform a predetermined operation based on the display.

  The portal server 200 provides a portal page to the client 100 in response to a request from the client 100. Further, the portal server 200 includes a portal operation reception unit 201, a portal screen generation reception unit 202 as reception means, a portlet content acquisition unit 203 as acquisition means, a portal screen generation unit 204 as provision means, a portal page management unit 205, It includes a portlet configuration information holding unit 206 that is a holding unit, a general portlet management unit 207, a portal page portlet management unit 208, a portlet object generation unit 209 that is an object generation unit, and a portlet configuration screen combining unit 210.

  The portal operation reception unit 201 receives a user operation on the portal server 200 from the browser 101. As an operation to accept, for example, there is a drag & drop of a portlet object. Further, the portal operation reception unit 201 requests the portal page management unit 205 to process the received operation. When the processing for the received operation is completed, the portal operation reception unit 201 requests the portal screen generation reception unit 202 to display the target portal page.

  The portal screen generation accepting unit 202 accepts a portal page display request from the browser 101 or the portal operation accepting unit 201 and, based on the portal page name included in the display request, the portal configuration information of the portal page to the portal page management unit 205. Inquire. Further, when the portlet configuration information is acquired from the portal page management unit 205, the portal screen generation reception unit 202 transmits the acquired portlet configuration information to the portlet content acquisition unit 203.

  The portlet content acquisition unit 203 acquires the contents of the portal page portlet and the general portlet. Here, the portal page portlet is a portal page displayed in a portlet format, and the general portlet is a portlet displayed on a conventional portal page.

  When the portlet content acquisition unit 203 receives the portlet configuration information from the portal screen generation reception unit 202, the portlet content acquisition unit 203 uses the received portlet configuration information to sort the portlets in the portal page into general portlets or portal page portlets. For a general portlet, the portlet content acquisition unit 203 transmits the name of the portlet to the general portlet management unit 207 and receives the content of the portlet. In addition, for the portal page portlet, the portlet content acquisition unit 203 transmits the name of the portlet to the portal page portlet management unit 208 and receives the content of the portlet.

  Furthermore, the portlet content acquisition unit 203 transmits the portlet configuration information received from the portal screen generation reception unit 202 and the portlet content received from the general portlet management unit 207 and the portal page portlet management unit 208 to the portal screen generation unit 204.

  The portal screen generation unit 204 generates a portal screen based on the portlet configuration information and portlet content received from the portlet content acquisition unit 203 and transmits the portal screen to the browser 101 of the client 100.

  The portal screen generation unit 204 first receives portlet configuration information and portlet content from the portlet content acquisition unit 203. Next, the portal screen generating unit 204 generates a portal page title bar and a portlet window by attaching a title bar to the portal page name and each portlet content obtained based on the received portlet configuration information.

The portal screen generation unit 204 passes the portlet configuration information and the generated portlet window to the portlet configuration screen combination unit 210 and receives the combined portlet configuration screen from the portlet configuration screen combination unit 210.

  Further, the portal screen generation unit 204 combines the portal page title bar and the received portlet configuration screen, and transmits the combined portal screen to the browser 101. The portal screen to be generated is, for example, FIGS. 2 is a portal screen displaying a root portal page, and FIG. 3 is a portal screen displaying a portal page x (details will be described later).

  Further, a link for calling the portal page s having the same name is assigned to the maximize button (FIG. 2: 313, 323 and 333) of the portal page portlet s. Further, for the button for returning the portal page s (FIG. 3: 403), the portal page portlet s having the same name is searched from the portlet name of the portlet configuration information, and the portal page name of the hit line is used. Assign a link that calls the portal page. Here, “s” represents an arbitrary portal page name (= portal page portlet name).

  The portal page management unit 205 performs management such as acquiring and changing portlet configuration information held in the portlet configuration information holding unit 206 in accordance with the requests received from the portal operation receiving unit 201 and the portal screen generation receiving unit 202.

  When the portal page management unit 205 receives the portal page name from the portal screen generation reception unit 202 or the portal page portlet management unit 208, the portal page management unit 205 uses the received portal page name to store the portal page information in the portlet configuration information holding unit 206. Queries the portlet configuration information.

  Further, when the portal page management unit 205 acquires the portlet configuration information from the portlet configuration information holding unit 206, the portal page management unit 205 transmits the acquired portlet configuration information to the portal screen generation reception unit 202 or the portal page portlet management unit 208.

  Further, when the portal page management unit 205 receives a portal operation request (for example, a request for moving a portlet between portal page portlets) from the portal operation reception unit 201, the portal page management unit 205 performs the following operation according to the request and holds the portlet configuration information. A portlet configuration information update request is transmitted to the unit 206. Here, in the following, “s” and “t” indicate arbitrary portal page names (= portal page portlet names), and “u” indicates arbitrary general portlet names (= portlet object names of general portlets). .

  When creating a portal page portlet t in the portal page s, a portal page named t is created, and configuration information of the portal page portlet t is added to the portal page s.

  When deleting the portal page portlet t in the portal page s, the portal page named t is deleted, and the configuration information of the portal page portlet t is deleted from the portal page s.

  Furthermore, when creating the portlet object u in the portal page portlet s, the configuration information of the portlet u is added to the portal page s.

  Furthermore, when deleting the portlet object u in the portal page portlet s, the configuration information of the portlet u is deleted from the portal page s.

  When the above operation is completed, the portal page management unit 205 transmits a message to that effect to the portal operation reception unit 201.

  The portlet configuration information holding unit 206 holds portlet configuration information used for providing a plurality of portal pages provided to the client 100. The portlet configuration information includes first portlet configuration information related to a root portal page that displays a plurality of portal pages in a portlet format and second portlet configuration information related to a portlet displayed on the portal page.

  FIG. 4 shows an example of portlet configuration information. The portlet configuration information 500 is configured by associating a portal page name 510, a portlet name 520, a portlet position 530, a portlet size 540, and a portlet type 550. Here, the information on the root portal page constitutes the first portlet configuration information described above, and the information on the portal pages x, y, z constitutes the second portlet configuration information described above.

  The portal page name 510 defines a root portal page and a portal page provided to the client 100. The portlet name 520 defines a portlet name displayed on the portal page. The portlet position 530 defines a row position and a column position for displaying the portlet on the portal page. The portlet size 540 defines the width (px) and height (px) displayed on the portal page. The portlet type 550 defines whether it is a portal page portlet or a general portlet.

  In FIG. 4, when the portal page name and the portlet name are the same (for example, the portal page name “x” and the portlet name “x”), it indicates that there is a correspondence relationship.

  When the portlet configuration information holding unit 206 receives a request for acquisition or change of the portlet configuration information from the portal page management unit 205, the portlet configuration information holding unit 206 returns the portlet configuration information or changes the content of the portlet configuration information according to the request.

  The general portlet management unit 207 acquires content of general portlets. More specifically, when the portlet name is received from the portlet content acquisition unit 203, the general portlet management unit 207 acquires the content of the corresponding portlet using the received portlet name, and uses the acquired portlet content as the portlet content. The data is transmitted to the acquisition unit 203.

  The portal page portlet management unit 208 acquires the content of the portal page portlet. More specifically, when the portal page portlet management unit 208 receives a portlet name from the portlet content acquisition unit 2033, the portal page portlet management unit 208 uses the received portlet name to inquire the portal page management unit 205 for a portal page with the same name, and The portlet configuration information of the portal page is acquired from the management unit 205.

  Further, the portal page portlet management unit 208 transmits the portlet configuration information acquired from the portal page management unit 205 to the portlet object generation unit 209, and receives the generated portlet object from the portlet object generation unit 209.

  Further, the portal page portlet management unit 208 transmits the portlet configuration information acquired from the portal page management unit 205 and the portlet object received from the portlet object generation unit 209 to the portlet configuration screen combining unit 210, and displays the combined portlet configuration screen as a portlet. The received portlet configuration screen is received from the configuration screen combining unit 210 and transmitted to the portlet content acquisition unit 203.

  The portlet object generation unit 209 generates a portlet object that represents a reduced image of the portlet.

  When the portlet object generation unit 209 receives the portlet configuration information from the portal page portlet management unit 208, the portlet object generation unit 209 reduces the portlet height and width by a certain ratio for each portlet in the portlet configuration information, and sets the content to the portlet name. Generate a portlet object, such as a portlet icon or a portlet snapshot.

  The reduction ratio takes a value such as 50%, for example, and the width and height of the portlet object are the width of the portlet object = portlet width * reduction ratio and the height of the portlet object = portlet height * reduction ratio. Obtain by calculation. Further, in order to enable the drag and drop movement of the portlet object, the portlet object generation unit 209 generates the portlet object by configuring the portlet object to be draggable.

  Further, the portlet object generation unit 209 transmits the generated portlet object to the portal page portlet management unit 208.

  The portlet configuration screen combining unit 210 generates a portlet configuration screen using a portlet window or a portlet object according to the portlet configuration information acquired from the portal page portlet management unit 208.

  When generating the portlet configuration screen, the portlet configuration screen combining unit 210 is configured so that the portlet object can be dropped on the portlet configuration screen in order to enable the drag and drop movement of the portlet object. Therefore, the generated portlet configuration screen corresponds to the drop of the portlet window or portlet object.

  Further, the portlet configuration screen combining unit 210 receives the portlet configuration information and the portlet window from the portal screen generation unit 204, receives the portlet configuration information and the portlet object from the portal page portlet management unit 208, and receives the received portlet configuration information and the portlet window or Portlet configuration screen is generated using portlet object.

  Further, the portlet configuration screen combining unit 210 transmits the generated portlet configuration screen to the portal screen generation unit 204 or the portal page portlet management unit 208.

  Next, processing in which the portal server 200 displays the root portal page on the browser 101 of the client 100 in accordance with a request from the client 100 will be described with reference to FIGS.

  As illustrated in FIG. 5, the user performs an operation such as inputting a link of the root portal page on the browser 101 of the client 100, and requests the portal screen generation reception unit 202 of the portal server 200 to display the root portal page. In the case of transmission, this process is started.

  When the portal screen generation accepting unit 202 accepts a request to display the root portal page (S101), it queries the portal page management 205 for the name of the root portal page, and acquires the portlet configuration information of the root portal page from the portal page management unit 205 ( S102).

  Next, the portlet content acquisition unit 203 receives the portlet configuration information of the root portal page acquired in step S102 from the portal screen generation reception unit 202, and acquires the portlet content acquisition process for acquiring the portlet content in the root portal page. Execute (S103). Details of the portlet content acquisition process will be described with reference to FIG.

  When the portlet content acquisition unit 203 acquires the portlet configuration information of the root portal page (S201), the portlet content acquisition unit 203 determines whether the portlet is a portal page portlet based on the portlet name and the portlet type included in the portlet configuration information (S201). S202).

  When it is determined that it is not a portal page portlet, that is, a general portlet (S202: NO), the portlet content acquisition unit 203 makes an inquiry to the general portlet management unit 207 to acquire the content of the corresponding portlet (S203). Note that the processing for acquiring the contents of a general portlet is the same as that conventionally performed, and thus detailed description thereof is omitted.

  On the other hand, when it is determined that it is a portal page portlet (S202: YES), the portlet content acquisition unit 203 acquires the portlet configuration information of the corresponding portal page portlet (S204).

  Here, the portlet “x” in the portlet configuration information 500 of FIG. 4 will be described in detail as an example. This portlet x has a portal page portlet type. For this reason, the portlet content acquisition unit 203 transmits the name of the portlet x to the portal page portlet management unit 208. When the portal page portlet management unit 208 receives the name of the portlet x from the portlet content acquisition unit 203, the portal page portlet management unit 208 makes an inquiry to the portal page management unit 205 using “x” of the portlet x as the name of the portal page. The portal page management unit 205 makes an inquiry about the portlet x to the portlet configuration information holding unit 206 using the portal page x, and acquires the portlet configuration information of the portal page x.

  Next, the portal page management unit 205 transmits the acquired portlet configuration information of the portal page to the portal page portlet management unit 208. The portal page portlet management unit 208 transmits the acquired portlet page configuration information of the portal page to the portlet object generation unit 209. Based on the portlet configuration information on the portal page, the portlet object generation unit 209 performs a calculation for multiplying the width and height of the portlet included in the portlet configuration information by the reduction ratio (S205).

Here, the process of multiplying the reduction ratio will be described in the case of the portal page x described above. The portlet configuration information of the portal page x includes portlets a, b, and c. Taking portlet a as an example, the portlet size of portlet a is 200 px (pixels) wide and 400 px wide, as shown in FIG. When the reduction ratio is 50%, the width and height of the portlet object a are calculated as follows.
Portlet object a width = portlet width * reduction ratio = 200 * 50% = 100 (px)
Portlet object a height = portlet height * reduction ratio = 400 * 50% = 200 (px)

  Next, the portlet object generation unit 209 generates a portlet object using the portlet width and height obtained in step S206 (S206). In the present embodiment, the contents of the portlet object are only displayed for the name of the portlet object, and a frame is added.

  Next, the portlet object generation unit 209 determines whether or not the above-described steps S205 and S206 have been performed on all portlets included in the portlet configuration information (S207).

  When it is determined that the processing in steps S205 and S206 described above has not been performed for all portlets (S207: NO), the portlet object generation unit 209 determines the step S205 described above for the portlets that have not yet been processed. And the process of S206 is performed. As a result, portlet objects can be generated for the portlets b and c included in the portal page x described above, as in the case of the portlet a.

  On the other hand, when it is determined that the processing of steps S205 and S206 described above has been performed for all portlets (S207: YES), the portlet configuration screen combining unit 210 performs the processing of portlet configuration information and the above-described steps S205 to S207. Each portlet object calculated in the above is received from the portal page portlet management unit 208, and each portlet object is arranged according to the portlet position information on the portal page to generate a portlet configuration screen (S208).

  Upon receiving the portlet configuration screen from the portlet configuration screen combining unit 210, the portal page portlet management unit 208 acquires the portlet arranged on the portlet configuration screen from the portlet content acquisition unit 203 as the portal page portlet content (S209).

  Next, the portlet content acquisition unit 203 determines whether or not content has been acquired for all portlets (S210). If it is determined that content has not been acquired for all portlets (S210: NO), the above-described steps S201 to S209 are repeated for content for other portal page portlets. Thereby, content can be acquired for all portlets displayed on the root portal page. On the other hand, if it is determined that content has been acquired for all portlets (S210: YES), this portlet content acquisition process is terminated.

  Returning to FIG. 5 and continuing the explanation, the portal screen generation unit 204 acquires the portlet configuration information and the content of the portal page portlet (or general portlet) from the portlet content acquisition unit 203, and then generates the title bar of each portal page. Processing is executed (S204). Processing for generating the title bar will be described with reference to FIG.

  First, the portal screen generation unit 204 determines whether the portlet acquired in step S203 is a portal page portlet (S301).

  When it is determined that it is not a portal page portlet (S301: NO), that is, when it is a general portlet, the portal screen generation unit 204 generates a title bar of the general portlet with the maximize button (S302).

  On the other hand, when it is determined that the page is a portal page portlet (S301: YES), the portal screen generation unit 204, when the maximizing button (FIG. 4: 313, 323, 333) is clicked, the portal page portlet corresponds to. A title bar defined to call a page link is generated (S303).

  For example, taking the portal page portlet 310 (portal page portlet x) described with reference to FIG. 4 as an example, since it is a portal page portlet (S301: YES), a title bar for the portal page portlet is generated. Note that the maximize button 313 attached to the title bar of the portal page portrait x allocates a link with the portal page x so that the portal page x can be displayed on the browser 101 when pressed (S303).

  Next, the portal screen generation unit 204 determines whether title bars have been generated for all portlets (S304). When it is determined that the title bar has not been generated for all portlets (S304: NO), the portal screen generation unit 204 executes the processes of steps S301 to S303 described above for the portlet for which no title bar has been generated. . Thereby, title bars are generated for all portlets.

  On the other hand, when it is determined that the title bar has been generated for all portlets (S304: YES), the portal screen generation unit 204 generates the title bar of the portal page (S305). The title bar is given the title of the root portal page or portal page portlets. Here, “s” is the name of the portal page portlet.

  Next, the portal screen generation unit 204 determines whether the portal page is a root portal page (S306). If it is determined that the page is the root portal page (S306: YES), the portal screen generation unit 204 ends the title bar generation process. In this case, since it is the root portal page, no button is added to the title bar.

  On the other hand, when it is determined that the page is not the root portal page (S306: YES), the portal screen generation unit 204 adds a button (FIG. 3: 403) for returning the portal page to the upper portal page of the portal page in the title bar. (S307). That is, the button is defined so as to call the link of the upper portal page at the time of the click operation.

  Upon completion of the process in step S306 or S307, the title bar generation process of the portal screen generation unit 204 ends, and the process proceeds to step S105. The portal screen generation unit 204 transmits a portal page portlet with a title bar attached thereto to the portlet configuration screen combining unit 210.

  Returning to FIG. 5 again and continuing the description, the portlet configuration screen combining unit 210 arranges each portal page portlet according to the portlet position information of the root portal page, similarly to the process of step S208 (S105).

  Next, the portal screen generation unit 204 adds the title bar of the root portal page to the portlet configuration screen of the root portal page, generates a portal screen, and transmits it to the client 100 side (S106).

  As a result, the browser 101 of the client 100 displays the root portal page screen. For example, the root portal page based on the portlet configuration information 500 described with reference to FIG. 4 is displayed on the browser 101 as shown in FIG.

  As shown in FIG. 2, the root portal page 300 includes a title bar 301 and a portlet window 302. The title bar 31 displays a title “root portal page”, and the portlet window 302 includes a portal page. Portlets 310, 320, and 330 are displayed. In the portal page portlets 310, 320, and 330, title bars 311, 321, and 331 and portlet windows 312, 322, and 332 are displayed, respectively. Furthermore, maximize buttons 313, 323, and 333 are attached to the title bars 311, 321 and 331, respectively.

  Therefore, the user can view the plurality of portlets displayed on the plurality of portal pages from a bird's-eye view through the root portal page 300.

  The user can maximize and display the portal page linked to the portal page portlet by clicking the maximize buttons 313, 323, and 333. For example, when the maximize button 313 of the portal page portlet 310 is clicked, the portal page x linked to the portal page portlet x is displayed on the browser 101 as shown in FIG.

  As shown in FIG. 3, the portal page 400 (portal page x) has a title bar 401 and a portlet window 402. The title bar displays the portal page x as a title and is provided with a button 403. In the portlet window 402, portlets 410, 420, and 430 are displayed. In addition, when the button 403 is clicked, it returns to the root portal page as described above.

  Each portlet 410, 420, and 430 is provided with a title bar 411, 421, and 431 and a content window 412, 422, and 432, respectively. Since the content displayed on the portal page is the same as that of the conventional one, detailed description thereof is omitted.

  Next, an operation for moving a portlet displayed in the portal page portlet of the root portal page to another portal page portlet will be described. More specifically, a case will be described in which the user performs a drag-and-drop operation on the portlet e in the portal page portlet 320 shown in FIG.

  The user drags the portlet e in the portal page portlet 320 on the browser 101 of the client 100 and drops it on the portal page portlet 310. As a result, the browser 101 transmits a portlet movement request to the portal operation reception unit 201 of the portal server 200. The information of this request includes information such as the name (y) of the portal page portlet 320, the name (x) of the portal page portlet 310, the name of the portlet e, and the location information of the location where the portlet e is dropped.

  When receiving a portlet movement request from the browser 101, the portal operation reception unit 201 requests the portal page management unit 205 to execute the following processing.

  When the portal page management unit 205 receives a request to move a portlet, the portal page management unit 205 updates the contents of the portlet configuration information 500 held in the portlet configuration information holding unit 206. That is, information regarding the movement of the portlet e is added to the portlet configuration information regarding the portal page x. Specifically, information is added to the portlet configuration information 500 so that the position of the portlet e on the portal page x is the second row and the second column, which are the position information of the location where the portlet e is dropped.

  Next, the portal page management unit 205 deletes information regarding the portlet e from the portlet configuration information for the portal page y held in the portlet configuration information holding unit 206.

  When the above processing is completed, the portal page management unit 205 transmits processing completion to the portal operation reception unit 201. When receiving the processing completion, the portal operation reception unit 201 transmits a portal screen display request to the portal screen generation unit reception unit 202. Thereafter, the process of regenerating the root portal page is the same as the process described above, and thus the description thereof is omitted.

  The portal screen generation unit 204 transmits the root portal page screen generated based on the portal screen display request to the client 100 side.

  In the browser 101 of the client 100, the root portal page after the portlet e of the portal page portlet 320 is moved to the portal page portlet 310 is displayed as shown in FIG.

  According to the portal system 10 of this embodiment, since a plurality of portal pages can be displayed as one portal page portlet 310, 320 and 330 on one root portal page 300, the user views the plurality of portlets from a bird's-eye view. The display position of each portlet can be easily grasped.

  Further, according to the portal system 10, the user can easily move the portlet from a predetermined position to a desired position between the portal page portlets 310, 320 and 330 displayed on the root portal page 300. For this reason, for example, when performing a process of moving a plurality of portlets so that the user can efficiently perform his / her business, the processing load can be reduced.

  In the above embodiment, a case has been described in which a plurality of portal pages x, y, and z portal page portlets 310, 320, and 330 are displayed on the root portal page 300. However, the present invention is not limited to this. Since the portal page portlet is also a portlet, it is possible to display the portal page in a hierarchy by configuring the portal page portlet to be hierarchical.

  In such a hierarchical portal page configuration, general portlets can be dragged and dropped onto portal page portlets, and portlet objects can be dragged and dropped onto the portal page that is being displayed. It becomes possible to move up and down.

  In the above embodiment, the description has been given of the case where the portlet object creation and deletion processing is performed inside the portal server 200. However, the present invention is not limited to this. It is also possible to provide a user interface for creating and deleting a portlet object. With this configuration, the user can perform processing such as moving a portlet while viewing the portal page from a bird's-eye view, and management of the portlet becomes easier.

  Further, the portal system 10 manages the state of whether or not the portlet object displayed on the root portal page 300 described in the above embodiment is selected by the user, and the user selects a plurality of portlet objects. By configuring so that a plurality of portlets can be moved or deleted, a single operation can be performed across portal pages. In addition, the user can move the selected portlet object across a plurality of portal pages to an arbitrary portal page.

  Further, the portal system 10 displays portlet objects (in accordance with the state of the general portlet and the portal page portlet displayed on the root portal page 300 (for example, the state in which the portlets are linked), the importance level, and the usage frequency ( By configuring to change the color, transparency, and size), the user can visually recognize the state of the portlet.

  For example, it is configured to classify portlets according to importance, and portlets having the same importance are automatically grouped into one portal page and displayed as portal page portlets. Thereby, the user can manage the portlet while visually confirming the result of displaying the confirmation and change of the grouping result in a bird's-eye view.

  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 server configured to provide a plurality of portal pages,
Holding means for holding first portlet configuration information relating to a root portal page for displaying the plurality of portal pages in a portlet format;
Receiving means for receiving a request to display the root portal page from a client;
An acquisition unit that acquires the first portlet configuration information held in the holding unit when the display unit receives the display request;
Based on the first portlet configuration information acquired by the acquisition unit, an object generation unit that generates an object of a portal page in a portlet format to be displayed on the root portal page;
Providing means for generating a root portal page screen using the object generated by the object generating means, and providing the generated root portal page screen to the client;
A portal server characterized by comprising:

(Appendix 2)
The portal server according to appendix 1, wherein the portal page portlet displayed on the root portal page is linked to the portal page.

(Appendix 3)
The holding unit holds second portlet configuration information related to a portlet displayed on the portal page,
The acquisition means acquires the first portlet configuration information and the second portlet configuration information,
The object generation means generates an object of a portal page portlet having a reduced size of the portal page based on the first portlet configuration information and the second portlet configuration information acquired by the acquisition means; The portal server according to Supplementary Note 1 or 2, which is a feature.

(Appendix 4)
When an operation for moving a portlet displayed in a portal page portlet into another portal page portlet is received from a client, the management unit, based on the received operation, the first portlet configuration information and the second portlet configuration information Update the portlet configuration information of
Based on the updated first portlet configuration information and second portlet configuration information, the object generation means generates an object,
The portal server according to appendix 3, wherein the screen providing means provides the client with a root portal page after the portlet movement.

(Appendix 5)
A portal page display method of a portal server configured to be able to provide a plurality of portal pages,
The portal page holds first portlet configuration information related to a root portal page that displays the plurality of portal pages in a portlet format.
Receiving a display request for the root portal page from a client;
When receiving the display request, obtaining the first portlet configuration information held in the holding unit;
Generating a portlet-format portal page object to be displayed on the root portal page based on the first portlet configuration information acquired by the acquisition means;
Generating a root portal page screen using the generated object, and providing the generated root portal page screen to the client;
A portal page display method for a portal server, comprising:

  The present invention is widely applicable to portal servers, portal systems, and the like that provide portal pages to clients.

DESCRIPTION OF SYMBOLS 10 ... Portal system 100 ... Client 101 ... Browser 200 ... Portal server 201 ... Portal operation reception part 202 ... Portal screen generation reception part 203 ... Portlet content acquisition part 204 ··· Portal screen generation unit 205 ··· Portal page management unit 206 ··· Portlet configuration information holding unit 207 ··· General portlet management unit 208 ··· Portal page portlet management unit 209 ··· Portlet object generation unit 210 ..Portlet configuration screen combining unit 300 ... Root portal page 400 ... Portal page 500 ... Example of portlet configuration information

Claims (4)

A portal server configured to provide a plurality of portal pages,
Each pre Symbol portal page was portlet format, the first portlet configuration information about the route portal page screen displaying side by side without overlapping on one PortletWindow, and a second related portlets to be displayed on each of the portal pages Holding means for holding portlet configuration information ;
Receiving means for receiving a request to display the root portal page screen from a client;
When receiving the display request by the receiving unit, an obtaining unit configured to obtain the first portlet configuration information and the second portlet configuration information held in said holding means,
Based on the acquired first portlet configuration information by the acquisition unit, the route to generate object portlets form of a portal page to be displayed on a portal page screen, the first portlet configuration information acquired by the acquisition means and Object generating means for generating an object of a portal page portlet in which the size of the portal page is reduced based on the second portlet configuration information ;
And providing means for using each object generated by said object generating means generates the route portal page screen, providing the root portal page screen thus generated to the client,
A portal server characterized by comprising: 2. The portal server according to claim 1, wherein the portal page portlet displayed on the root portal page screen is linked to the portal page from which the portal page portlet is generated . A management unit for updating the first portlet configuration information and the second portlet configuration information;
When an operation of said moving portlets to be displayed on the portal page portlets to another of said portal page portlet received from the client in the reception unit,
The management unit updates the first portlet configuration information and the second portlet configuration information based on the operation received by the reception unit ,
It said object generating means on the basis of the first portlet configuration information and the second portlet configuration information updated by the management unit, and generates object,
Said screen providing means provides said route portal page screen after the portlet moved to the client,
The portal server according to claim 1 or 2 , characterized in that A portal page display method of a portal server configured to be able to provide a plurality of portal pages,
The portal server includes first portlet configuration information related to a root portal page screen that displays the portal pages in a portlet format side by side without overlapping each other on a portlet window, and portlets that are displayed on the portal pages. Holding means for holding the second portlet configuration information regarding,
The portal server is
Receiving a request to display the root portal page screen from a client;
When receiving the display request, a step of acquiring the first portlet configuration information and the second portlet configuration information held in said holding means,
Based on the prior Quito obtained by said first portlet configuration information, the route portal page screen to create an object of the portal page for the portlet format for displaying the acquired first portlet configuration information and the second portlet Generating a portal page portlet object in which the size of the portal page is reduced based on configuration information ;
A step of said generating a root portal page screen, providing the root portal page screen thus generated to the client with each object the generated,
A portal page display method for a portal server, comprising:

Images