JP2005332151A - Device, method and program for generating web page, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an web page generation device which can generate an web page which automatically displays prescribed information at intended timing, an web page generation method, an web page generation program and a recording medium. <P>SOLUTION: An web page generation device which generates an web page solves the above subject by having a web page generation means by which the required time when generation of the above web page is required is compared with the display time which is set up beforehand to display the prescribed information in the above web page, and when the above required time has passed the above display time, the above web page is generated so that the prescribed information may be displayed. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a Web page generation apparatus, a Web page generation method, a Web page generation program, and a recording medium that generate a Web page.

  With the recent development of Web technology, Internet users can easily browse information provided at various sites around the world using a general-purpose browser. However, in the recent years when the amount of available information has become enormous, it is extremely difficult to find the target information. For this reason, a site as an entrance to the Internet, that is, a portal site, has become widespread, and is now indispensable for Internet users (for example, Patent Document 1).

On the other hand, EIP (Enterprise Information Portal) has been introduced as a means of sharing information in an intranet within a company, so that necessary information can be obtained efficiently. Whether it is a portal site on the Internet or a portal site by EIP, the Web page (portal page) provided by the site is divided into a plurality of areas, and information with high utilization is displayed in each divided area. It is common. Therefore, the user can view useful information on one screen at a time, and such convenience is considered to be a factor of popularity of the portal site.
JP 2002-222271 A

  However, there is a problem that the visibility of individual information on the portal page is relatively deteriorated when the amount of information posted on one screen increases. Some are not required. For example, when there is a divided area for displaying status information of a network device such as a printer, it is only necessary to check the information once a day, and there is a need to hide it in other cases.

  In addition, it is effective to display items to be communicated to the user immediately before an event to be contacted occurs. In order to realize such a function, conventionally, an administrator has to manually perform maintenance work in accordance with the time when a message or the like is displayed.

  The present invention has been made in view of the above points, and is a Web page generation device, a Web page generation method, and a Web page that can generate a Web page that automatically displays predetermined information at an intended timing. An object is to provide a generation program and a recording medium.

  Accordingly, in order to solve the above-described problem, the present invention provides a Web page generation device that generates a Web page, as described in claim 1, wherein the request time when the generation of the Web page is requested and the Web page Compare the predetermined information to be displayed with a preset display time, and when the request time has passed the display time, the Web page is displayed so that the predetermined information is displayed. Web page generating means for generating is provided.

  In such a Web page generation device, by setting a display time in advance for information to be displayed on the Web page, the information can be automatically displayed in accordance with the display time.

  In order to solve the above problems, the present invention provides a Web page generation method in the Web page generation apparatus, a Web page generation program for causing the Web page generation apparatus to execute the Web page generation method, or the Web page generation A recording medium on which the program is recorded may be used.

  According to the present invention, it is possible to provide a Web page generation device, a Web page generation method, a Web page generation program, and a recording medium that can generate a Web page that can clearly indicate the occurrence of a predetermined event.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of a Web system according to an embodiment of the present invention. In the Web system 1 of FIG. 1, a Web server 10, a Web client 20, a printer server 30a, a document management server 30b, and a mail server 30c are connected via a network 40 such as a LAN (Local Area Network) or the Internet. Has been.

  The Web client 20 is a terminal in which a Web browser is installed, and corresponds to, for example, a PC (Personal Computer), a PDA (Personal Digital Assistants), a mobile phone, and the like.

  The printer server 30a is a computer that provides a print service related to the connected printer 50 on the network 40 as a Web service. That is, the function of the printer server 30a can be called by SOAP RPC. For example, the printer server 30 a has a “print request method” for printing specified document data and the like, a “status information acquisition method” for providing status information of the printer 50, and the like, which are disclosed on the network 40. doing.

  The document management server 30b is a computer that provides a document management service related to document data stored in a document DB (Data Base) 60 on the network 40 as a Web service. That is, the function of the document management server 30b can be called by SOAP RPC. For example, the document management server 30 b has a “document list acquisition method” for acquiring list information of document data stored in the document DB 60, and is disclosed on the network 40.

  The mail server 30c is a computer that provides a mail service on the network 40 as a Web service. The function of the mail server 30c can be called by the SOAP RPC as in the printer server 30a described above. The mail server 30c publishes, for example, a “mail list acquisition method” for acquiring a list of received mails. In the following description, a server that can call up its function by SOAP RPC, such as the printer server 30a, the document management server 30b, and the mail server 30c, is described as a “SOAP server”.

  Based on the Web page acquisition request from the Web client 20, the Web server 10 calls the functions of the printer server 30a and other SOAP servers (not shown) by SOAP RPC, thereby obtaining information necessary for generating the Web page. collect. Further, the web server 10 generates a web page based on the collected information, and transmits the web page to the web client 20. Therefore, the Web server 10 does not need to have any content in advance, and the main role is to generate a Web page based on information collected via the network 40. However, the Web server 10 may be provided with a function for executing some service.

  Next, details of the Web server 10 will be described. FIG. 2 is a diagram illustrating a hardware configuration example of the Web server according to the embodiment of the present invention. The Web server 10 includes a CPU 11, a ROM 12, a RAM 13, an auxiliary storage device 14, a network interface (I / F) 15, a drive device 16, and the like.

  The CPU 11 is a control unit that controls the entire Web server 10 and executes various control programs and application programs stored in the ROM 12 and the auxiliary storage device 14 to control the device, control communication, acquire and edit data, and the like. Perform the action. The ROM 12 is a storage unit that mainly stores a control program for the apparatus, and the RAM 13 is a storage unit that is used to store the work memory of the CPU 11 and temporary data. The auxiliary storage device 14 is a storage unit that stores various application programs and data. The network I / F 15 is an interface for connecting the Web server 10 to the network 40. The drive device 16 is a device for reading a recording medium 17 such as a CD-ROM in which a program for executing the functions of the present invention is recorded.

  2 does not show an operation unit or a display unit, but an operation unit using a keyboard or a mouse or a display unit using a liquid crystal or a cathode ray tube (CRT) is provided to accept input from the user and display an operation result. You may be able to do that.

  Next, the functional configuration of the Web system 1 will be described. FIG. 3 is a schematic diagram of a functional configuration example of the Web system according to the embodiment of the present invention. As shown in FIG. 3, the Web server 10 includes a Web server program 101, a Web application 110, a service proxy 120, and the like.

  The Web server program 101 is generally equivalent to a program called HTTPd (HTTP daemon), and is for causing the Web server 10 to function as a Web server. That is, the Web server program 101 receives an HTTP request from the Web browser 21 of the Web client 20 and calls the Web application 110. In addition, the Web server program 101 transmits a Web page generated by the called Web application 110 to the Web browser 21 as an HTTP response.

  The web application 110 is a so-called web application that generates a web page for displaying such information based on information collected from various SOAP servers 30, information stored locally in the web server 10, and the like.

  The service proxy 120 is a module that transparently provides a method interface for a function (service 31) in the SOAP server 30. That is, the Web application 110 can call the function of the SOAP server 30 without being aware of the network boundary by calling the method of the service proxy 120.

  The Web application 110 will be described in more detail. FIG. 4 is a class diagram for explaining the functional configuration of the Web application.

  4, the Web application 110 includes a servlet 111, a page generation class 112, a profile operation class 113, a profile XML 114, a unit data acquisition class A 115a, a unit data acquisition class B 115b, and a unit data acquisition class C 115c. Etc.

  The servlet 111 determines the web page requested by the web browser 21 based on the URL specified in the HTTP request from the web browser 21 received by the web server program 110, and generates a page corresponding to the web page. This is a module in which a function for generating an instance of a class 112 to generate a Web page is implemented.

  The page generation class 112 is a class for realizing a Web page generation function. The page generation class 112 acquires information defined in the profile XML 114 via the profile operation class 113, and generates a Web page based on the information. The page generation class 112 is defined according to the type of Web page.

  In the present embodiment, there is a class for generating a portal page as the page generation class 112. Here, the portal page refers to a Web page that displays various information in a single display area, and is used as an entrance of the Internet or an intranet.

  FIG. 5 is a diagram showing an example of a portal page in the embodiment of the present invention. As shown in FIG. 5, the portal page 210 includes a service list unit 211, a printer information unit 212, a notification unit 213, a document list unit 214, an inbox unit 215, and the like. In the present embodiment, each area divided on the portal page 210 is referred to as a “unit”.

  The service list unit 211 is a unit that displays a list (hyperlink) of various services. When each link in the service list unit 211 is clicked, a Web page for providing the corresponding service is newly displayed. The printer information unit 212 is a unit for displaying status information of the printer 50 acquired from the printer server 30a. However, the status information is not always displayed, but is displayed when the portal page 210 is displayed after a predetermined time. FIG. 5 shows a state in which status information is not displayed.

  The notification unit 213 is a unit that displays the contents when there is a message for the user (employee). Examples of the communication items include prompting the user to perform some work. The notification item is also displayed when the portal page 210 is displayed after a predetermined time, similarly to the status information of the printer 50.

  The document list unit 214 is a unit for displaying list information of document data in a predetermined folder of the document DB 60 acquired from the document management server 30b. The inbox unit 215 is an area in which a list of received mails of the current user managed by the mail server 30c is displayed.

  Returning to FIG. The profile operation class 113 is a class that provides an access means to the profile XML 114. The profile XML 114 is an XML format file in which an operation environment on the portal page 210 is defined for each user. Specifically, information relating to how to divide the portal page 210 and information relating to allocation of display information indicating what information is to be displayed in each unit (hereinafter collectively referred to as “page "Configuration information").

  The unit data acquisition class A 115a, unit data acquisition class B 115b, unit data acquisition class C 115c, etc. (hereinafter collectively referred to as “unit data acquisition class 115”) are information to be displayed on each unit of the portal page 210 (hereinafter referred to as “unit data acquisition class 115”). It is defined for each type of “unit data”), and is a class in which a function for acquiring the unit data is implemented. For example, the unit data acquisition class A 115a is a class for acquiring status information of the printer 50 from the printer server 30a, the unit data acquisition class B 115b is a class for acquiring list information of document data from the document management server 30b, and so on. It is. Accordingly, the three unit data acquisition classes 115 displayed in the drawing are merely examples, and many more unit data acquisition classes 115 can be defined.

  The service proxy 120a and the service proxy 121b correspond to the service proxy 120 in FIG. 3 (therefore, the service proxy 120a and the service proxy 121b are collectively referred to as “service proxy 120”). That is, the service proxy 120 exists for each service 31 of each SOAP server 30, and the service proxy 120a is displayed as one example, and the service proxy 121b is displayed as another example. Therefore, each unit data acquisition class 115 acquires unit data from each service 31 by calling a method of the service proxy 120 corresponding to the display information to be acquired.

  The service 31a and the service 31b are illustrated by distinguishing each of the services 31 of each SOAP server 30. For example, the service 31a is a service 31 (printer service) in the printer server 30a, and the service 31b is a service 31 (document management service) in the document management server 30b. The local module 121c is an example of a library that the unit data acquisition class C115c for a unit whose unit data is acquired from a local environment, such as the notification unit 213, uses to acquire the unit data.

  Hereinafter, a processing procedure when the Web server 10 of FIGS. 3 and 4 generates the portal page 210 will be described. FIG. 6 is a sequence diagram for explaining the portal page generation processing in the first embodiment. When the transmission request (HTTP request) of the portal page 210 from the Web browser 21 of the Web client 20 is received by the Web server program 101 and the servlet 111 is called by the Web server program 101, the processing of FIG.

  In step S101, the servlet 111 determines that the portal page 210 is requested from the URL specified in the HTTP request, and generates the portal page 210 in the page generation class 112 (an instance thereof) corresponding to the portal page 210. Request. In the following, when referring to an instance of each class, it is described simply with the class name of the class.

  Progressing to step S102 following step S101, when the page generation class 112 requests the profile operation class 113 to provide page configuration information, the profile operation class 113 reads the page configuration information from the profile XML 114 of the current user, The contents are output to the page generation class 112 (S103).

  FIG. 7 is a diagram illustrating a definition example of the profile XML in the first embodiment. In FIG. 7, the definition enclosed by the <page> tag is page configuration information for one portal page 210.

  The presence of the left element 1141 surrounded by the <left> tag and the right element 1142 surrounded by the <right> tag stipulates that the portal page 210 is divided into two in the horizontal direction. In this embodiment, the portal page 210 is divided into two in the horizontal direction, but the number of divisions can be arbitrarily defined. For example, when dividing into three, a new definition (for example, a center element) may be added at the same level as the left element 1141 and the right element 1142.

  Each of the left element 1141 and the right element 1142 has one or more unit elements as child elements. The unit element is for defining each unit on the portal page 210. Therefore, the number of units in the left area and the right area in the portal page 210 is defined by the number of unit elements, and the arrangement position of each unit is defined in the order of definition of the unit elements.

  The left element 1141 includes two unit elements 1141a and 1141b. Therefore, it can be seen that two units are arranged in the left region. This corresponds to the service list unit 211 and the printer information unit 212, respectively. The right element 1142 includes three unit elements 1142a, 1142b, and 1142c. Therefore, it can be seen that three units are arranged in the right region. This corresponds to the notification unit 213, the document list unit 214, and the inbox unit 215, respectively.

  Each unit element defines an id attribute, a title attribute, a type attribute, a notify attribute, an expand attribute, and the like. The id attribute is an attribute for identifying each unit element, and information uniquely assigned to each unit element (hereinafter referred to as “unit ID”) is designated as the value of the id attribute. The title attribute is an attribute that takes a title character string to be displayed on the title bar of the unit as a value.

  The type attribute is an attribute for identifying the type (unit type) of each unit. Here, the unit type is information that depends on the type of information displayed on the unit. That is, the type of information displayed on the unit is specified by the type attribute. For example, the value of the type attribute (type attribute 1141a-1, type attribute 1142a-1) of the unit element 1141a and the unit element 1142a is “bookmark”, but such a unit is a child element of the unit element. The character element ("XXX" in the item element 1141a-2) designated by the value of the item element (in the unit element 1141a, the item element 1141a-2 and the item element 1141a-3) is displayed. , A link is made to the URL specified in the url attribute of the item element.

  The value of the type attribute 1141b-1 of the unit element 1141b is “print status”, and such a unit is acquired from the service 31 specified by the service URI attribute of the item element that is a child element of the unit element. Printer status information is displayed. The value of the type attribute 1142b-1 of the unit element 1142b is “doclist”, but such a unit is acquired from the service 31 specified by the serviceURI attribute of the item element that is a child element of the unit element. List information of document data to be displayed. The value of the type attribute 1142c-1 of the unit element 1142c is “maillist”, but such a unit is acquired from the service 31 specified by the serviceURI attribute of the item element that is a child element of the unit element. List of received mails to be displayed.

  The notify attribute is an attribute that takes a true / false value. If the value is “true”, the unit sends predetermined information to the user at a predetermined time (hereinafter referred to as “notification time”). This indicates that the unit is designated as the one to be notified (hereinafter referred to as “notification unit”). As can be seen from FIG. 7, in this embodiment, units corresponding to the unit element 1141b and the unit element 1142a, that is, the printer information unit 212 and the notification unit 213 are notification units. The expand attribute is an attribute that takes a true / false value. If the value is “true”, the unit is maximized. If the value is “false”, it indicates that the unit is minimized. Show.

  A timing attribute and a lastNotified attribute are further defined in the unit element for which the value of the notify attribute is “true”, that is, the unit element for the notification unit. The timing attribute is an attribute for managing the notification time. For example, the value of the timing attribute 1141b-2 of the unit element 1141b is “12:00”, so that the notification of the printer status information in the printer information unit 212 is requested to be displayed every day after 12:00. It can be seen that this is done on page 210. In addition, the value of the timing attribute 1142a-2 of the unit element 1142a is “30 Apr 2004”, so that the display of the notification item in the notification unit 213 was requested after April 30, 2004. It can be seen that this is done on the portal page 210.

  The lastNotified attribute is an element for managing the time at which notification was last performed (hereinafter referred to as “final notification time”). For example, the value of the lastNotified attribute 1141b-3 of the unit element 1141b is “10 Apr 2004 14:12:07”. From this, the status information of the printer 50 in the unit element 1141b (hereinafter simply referred to as “status information”). It can be seen that the last time when this notification was made (that is, the time when the user finally checked the status information on the portal page 210) was 14:12:07 on April 10, 2004.

  In step S103, the profile operation class 113 may output the content of the profile XML 114 as it is to the page generation class 112. However, in this embodiment, the value of the id attribute of each unit element (unit ID) ), A list of title attribute values (title character string) and type attribute values (unit type) are output.

  Subsequent to step S103, the processing from step S104 to step S117 is executed for each unit element in the page configuration information. Hereinafter, a unit element to be processed is referred to as a “current unit element”, and a unit related to the current unit element (a unit on the portal page 210) is referred to as a “current unit”.

  In step S104, when the page generation class 112 inquires to the profile operation class 113 based on the unit ID whether the current unit is a notification unit, the profile operation class 113 sets the value of the notify attribute in the current unit element to true. It is confirmed whether or not there is, and the result is returned to the page generation class 112 (S105). For example, when the current unit element is the unit element 1141b, since the value of the notify attribute is true, it is returned that the current unit is a notification unit. If it is returned that the current unit is not a notification unit, the process proceeds to step S110 described later.

  If it is returned that the current unit is a notification unit, the process proceeds to step S106 following step S105, and whether or not the notification time defined by the page generation class 112 for the current unit element has already passed. Is inquired of the profile operation class 113, the profile operation class 113 compares the timing attribute value (notification time) of the current unit element with the current time, that is, the time when the portal page 210 is requested, and the result is obtained. Returned to the page generation class 112 (S107). For example, when the current unit element is the unit element 1141b, only the time (12:00) is specified as the value of the timing attribute, and thus the current date is adopted in the time comparison. Then, if the current time is 13:00 on April 11, 2004, the notification time is 12:00 on April 11, 2004. In this case, the fact that the notification time has passed is returned. Is done. If it is returned that the notification time has not been reached, there is no need to notify the current unit, so the unit data is not acquired for the current unit, and the processing after step S104 is performed for the next unit element. Is done.

  Even when the notification time has passed, the portal page 210 may already be displayed after the notification time. Therefore, the process proceeds to step S108 following step S107, and the page generation class 112 inquires the profile operation class 113 whether the notification time of the current unit is after the final notification time. In response to the inquiry, the profile operation class 113 compares the timing attribute value of the current unit with the value of the lastNotified attribute, and returns information indicating the context of the comparison to the page generation class 112 (S109). For example, if the current unit element is the unit element 1141b and the current time is 13:00 on April 11, 2004, the notification time is 14:00 on April 11, 2004, as described above. Since the last notification time is 14:12 on the previous day, the fact that the notification time is later than the last notification time is returned. If it is returned that the notification time is before the final time, today's notification has already been made, so the unit data is not acquired for the current unit, and the next unit element is targeted. The process after S104 is performed.

  If it is returned that the notification time is later than the final notification time, today's notification has not yet been made. Accordingly, the process proceeds to step S110 following step S109, and the page generation class 112 specifies the unit data acquisition class 115 corresponding to the current unit element based on the unit type of the current unit element, and the unit data acquisition class 115 Requesting unit data acquisition. Progressing to step S111 following step S110, the unit data acquisition class 115 requests transmission of information used as unit data to the corresponding service 31 by SOAP RPC by calling a method of the service proxy 121. (S112). In step S113 following step S112, when the service 31 transmits unit data to the service proxy 121, the service proxy 121 outputs unit data to the unit data acquisition class 115 (S114). The unit data acquisition class 115 outputs the acquired unit data to the page generation class 112 (S115).

  For example, when the current unit element is the unit element 1141b, the status information of the printer 50 is acquired from the printer server 30a by the processing from step S110 to step S115. The information acquired here may be status information of the printer 50 at that time (acquisition time). For example, when the status information of the printer 50 is periodically collected every day by the printer server 30a, the information is periodically acquired. It may be the status information acquired. In the latter case, even if the time for displaying the portal page 210 is different, status information at the same time is displayed every day. In the present embodiment, it is assumed that status information of the printer 50 is collected by the printer server 30a every day at 12:00 and the status information is acquired by the unit data acquisition class 115.

  Subsequent to step S115, if the current unit is not a notification unit, the process proceeds to step S119. On the other hand, if the current unit is a notification unit, the process proceeds to step S116 following step S115. When the page generation class 112 requests the profile operation class 113 to update the last notification time, the profile operation class 113 The value of the lastNotified attribute of the current unit element is updated to the current time, and the result is reflected in the profile XML 114 (S117).

  Progressing to step S118 following step S115 or step S117, the above-described processing from step S104 to step S117 is also executed for other units. Therefore, unit data to be displayed on each unit is collected under the page generation unit 112.

  When the unit data acquisition processing for all the units is completed, the process proceeds to step S119, and the page generation class 112 generates the portal page 210 based on the page configuration information and the unit data. At this time, each unit data is arranged on the portal page 210 in the order defined in the page configuration information. Progressing to step S 120 following step S 119, the page generation class 112 outputs the generated portal page 210 to the servlet 111. Thereafter, the portal page 210 is transmitted to the web browser 21 by the web server program 101 and displayed by the web browser 21.

  FIG. 8 is a diagram illustrating a display example of a portal page for notifying printer status information. The printer information unit 212 of the portal page 210 in FIG. 8 displays status information of the printer 50 at 12:00 on April 11, 2004. Even if the portal page 210 is displayed again immediately after this, since the notification time is before the final notification time, nothing is displayed on the printer information unit 212. The next time the status information is displayed when the portal page 210 is displayed after 12:00 on the next day, the status information indicating the status of the printer 50 on the next day is displayed. Information.

  In the above description of the sequence diagram, the printer information unit 212 (unit element 1141g) has been mainly described. However, the notification page 213 (unit element 1142a) also displays the portal page first after the notification time has elapsed. If this happens, a message will be displayed.

  As described above, according to the Web server 10 in the first embodiment, after a predetermined time has elapsed, when the portal page 210 is displayed for the first time, it is automatically assigned to a predetermined unit and periodically. Information can be displayed. Therefore, it is not necessary to perform maintenance work on the Web page every time the administrator needs to display information, and the work burden on the administrator can be reduced.

  By the way, in 1st Embodiment, the example which sets notification time etc. for every unit was demonstrated. However, the number of communication items displayed on the notification unit 213 is not necessarily one, and there are cases where the timing at which each of the plurality of communication items is desired to be displayed is different. Therefore, as a second embodiment, an example in which notification time and the like can be set for each item to be displayed on the notification unit 213 will be described.

  FIG. 9 is a sequence diagram for explaining a portal page generation process according to the second embodiment. In FIG. 9, similarly to FIG. 6, processing is started based on a transmission request (HTTP request) of the portal page 210 from the Web browser 21 of the Web client 20.

  Steps S201 to S203 are the same as the processes from steps S101 to S103 in FIG. That is, when the servlet 111 called based on the HTTP request from the Web browser 21 requests the page generation class 112 to generate the portal page 210 (S201), the page generation class 112 passes through the profile operation class 113. The page configuration information in the profile XML 114 is acquired (S202, S203).

  FIG. 10 is a diagram illustrating a definition example of the profile XML in the second embodiment. In FIG. 10, the same parts as those in FIG. Comparing FIG. 10 and FIG. 7, it can be seen that the unit element 1142a in FIG. 10 does not define the notify attribute, timing attribute, and lastNotified attribute, which are necessary for determining whether notification is necessary. Instead, it is a child element of the unit element 1142a, and a notify attribute or the like is defined for each item element corresponding to one communication item to be displayed. In other words, the page configuration information in the second embodiment is configured so that the necessity of notification, the notification time, and the final notification time can be managed for each communication item displayed on the notification unit 213. In FIG. 10, the description of the left element 1141 is omitted, but this is because there is no difference from the description of the left element 1141 of FIG.

  Subsequent to step S203, the processing from step S204 to step S216 is executed for each unit element in the page configuration information. Here, a case where the unit element 1142a is processed will be described.

  In step S204, the page generation class 112 specifies the unit data acquisition class 115 corresponding to the unit element 1142a based on the unit type (bookmark) of the unit element 1142a, and acquires unit data for the unit data acquisition class 115. Request.

  Subsequent to step S204, the processing from step S205 to step S214 is executed for each item element that is a child element of the unit element 1142a. First, the unit data acquisition class 115 is the item element (hereinafter referred to as “notification item”) that requires the first item element (item element 1142a-4) of the unit element 1142a to be notified to the profile operation class 113. (S205). Here, since the value of the notify attribute of the item element 1142a-4 is “true”, the profile operation class 113 returns that the item element 1142a-4 is a notification item (S206).

  Proceeding to step S207 following step S206, when the unit data acquisition class 115 inquires of the profile operation class 113 whether or not the notification time has already passed for the item element 1142a-4, the profile operation class 113 receives the item element. The value (notification time) of the timing attribute of 1142a-4 is compared with the current time, and the result is returned to the unit data acquisition class 115 (S208). Since the value of the timing attribute 1142a-2 of the item element 1142a-4 is “30 Apr 2004”, the notification time is midnight on 30th of 2004. Therefore, for example, when the current time is 13:00 on April 30, 2004, a notification that the notification time has passed is returned.

  Progressing to step S209 following step S208, the unit data acquisition class 115 inquires of the profile operation class 113 whether the notification time of the item element 1142a-4 is later than the final notification time. In response to the inquiry, the profile operation class 113 receives the value of the lastNotified attribute of the item element 1142a-4 (March 30, 2004 13:28:12) and the notification time (April 30, 2004 midnight) As a result, that is, the fact that the notification time is later than the final notification time is returned to the unit data acquisition class 115 (S210).

  Proceeding to step S211 following step S210, when the unit data acquisition class 115 requests a message to the profile operation class 113, the profile operation class 113 is set as the value of the item element 1142a-4 from the page configuration information. ([Important / End-of-month notice] Please submit the work management table) and output it to the unit data acquisition class 115 (S212).

  Proceeding to step S213 following step S212, when the unit data acquisition class 115 requests the profile operation class 113 to update the last notification time of the item element 1142a-4, the profile operation class 113 receives the last unit element of the current unit element. The attribute value is updated to the current time, and the result is reflected in the profile XML 114 (S214).

  When the processing from step S205 to step S214 is completed for all other item elements (S215), the unit data acquisition class 115 outputs the unit data including the acquired communication items to the page generation class 112.

  Subsequent to step S216, the process proceeds to step S217, and unit data acquisition processing is also executed for other unit elements. Therefore, unit data to be displayed on each unit is collected under the page generation unit 112.

  When the processing for all the units is completed, the page generation class 112 generates the portal page 210 based on the page configuration information (S218), and the servlet page 111 is then generated as in the first embodiment. (S219). Thereafter, the portal page 210 is transmitted to the web browser 21 by the web server program 101 and displayed by the web browser 21.

  FIG. 11 is a diagram illustrating a display example of a portal page that notifies a communication item. As shown in FIG. 11, a notification item at the end of the month such as “Please submit a work management table” is displayed in the notification unit 213 of the portal page 210. However, the communication items corresponding to all the item elements in the unit element 1142a-4 are not always displayed at the same time. This is because the notification time may be different for each communication item.

  As described above, according to the Web server 10 in the second embodiment, notification can be performed at different timings for each item to be displayed in one unit, and the convenience of the Web page can be improved.

  Incidentally, it is necessary for the administrator to set in advance the items to be displayed on the notification unit 213. Therefore, by using the mechanism described above, it is possible to notify the administrator that it is necessary to set a notification item, and based on the notification, the administrator can easily notify the notification item. An example in which settings can be made will be described as a third embodiment.

  FIG. 12 is a sequence diagram for explaining a portal page generation process according to the third embodiment. The sequence diagram shown in FIG. 12 is almost the same as that of FIG. In the third embodiment, it is assumed that the user of the Web client 20 is not an ordinary user but an administrator.

  When the servlet 111 called based on the HTTP request from the Web browser 21 requests the page generation class 112 to generate the portal page 210 (S301), the page generation class 112 passes through the profile operation class 113. The page configuration information in the profile XML 114 for the administrator is acquired (S302, S303).

  FIG. 13 is a diagram illustrating a definition example of the administrator profile XML according to the third embodiment. In FIG. 13, the same parts as those in FIG. The configuration of the page configuration information in FIG. 13 is the same as that in FIG. However, the values set in the item element 1142a-4 are different. That is, the value of the item element 1142a-4 in FIG. 13 is “[Important / Notice at the end of month] Work management table submission request notification is approaching.”, And it is necessary to submit a work management table submission request. A message indicating that there is a message is set as a message. Further, the notification time of the relevant notification item is found to be midnight on April 25, 2004 from the value of the timing attribute 1142a-2 (“25 Apr 2004”).

  Subsequent to step S303, step S304 and subsequent steps are substantially the same as step S204 and subsequent steps in FIG. Therefore, when the processing from step S304 to step S318 is executed for the unit element 1142a, whether the notification time has passed and the notification time is later than the final notification time for each item element belonging to the unit element 1142a. Is determined (S305 to S310). The item element (hereinafter referred to as “notification target item element”) that has been notified since the notification time has passed the current time and is later than the final notification time is the value of the item element. A communication item is acquired from the profile operation class 113 by the unit data acquisition class 115, and the last notification time (lastNotified attribute value) of the item element is updated (S311 to S314).

  Subsequent to step S314, steps S315 and S316 are processes newly added in FIG. That is, when the unit data acquisition class 115 requests the profile operation class 113 for the value of the url attribute of the notification target item element (S315), the profile operation class 113 sets the value of the url attribute of the notification target item element as the profile. Obtained from the XML 114 and output to the unit data obtaining class 115 (S316).

  For example, when looking at the item element 1142a-4 (FIG. 13), if the current time is after midnight on April 25, it is treated as the notification target item element and is the value of the item element 1142a-4. The unit data acquisition class 115 acquires the message (“[Important / End of month notification] work management table submission request notification is approaching”) and the value of the url attribute 1142a-6 (./BookmarkList). . Here, the value of the url attribute 1142a-6 is the URL of the link destination attached to the contact item, and in the present embodiment, a Web page (hereinafter, “setting”) for setting the notification item to be notified to each user. URL ”).

  When the processing from step S305 to step S316 is executed for all item elements, the unit data acquisition class 115 uses the value (communication matter) of each item element and the value of the url attribute as unit data to generate the page generation class 112. (S318).

  For other unit elements, the unit data acquisition process corresponding to each unit element is executed (S319), and when the unit data for all units is collected in the page generation class 112, the page generation class 112 Based on the configuration information and unit data, the portal page 210 is generated (S320). Here, the page generation class 112 has the portal page 210 so that a link to the URL specified in the value of the url attribute of the item element corresponding to each message is displayed for the message to be displayed on the notification unit 213. Is generated. Therefore, for example, a link to the setting page is provided in the notification item of the item element 1142a-4, “[Notification of important / end of month] work management table submission request notification is approaching.”.

  Progressing to step S321 following step S320, when the page generation class 112 outputs the generated portal page 210 to the servlet 111 (S219), the portal page 210 is transmitted to the web browser 21 by the web server program 101. And displayed by the Web browser 21.

  FIG. 14 is a diagram illustrating a display example of a portal page for an administrator. In the notification unit 213 of the portal page 210 shown in FIG. 14, a contact item 2131 for the administrator is displayed. The administrator can recognize that it is necessary to request the employee to submit the work management table by checking the communication item 2131. Here, since the contact item 2131 has a link to the setting page, when the administrator clicks the notification item 2131, the setting page is displayed on the Web browser 21.

  FIG. 15 is a diagram illustrating a display example of the setting page. The setting page 220 shown in FIG. 15 includes a title input area 221, a contact item setting area 222, an operation button 223, and the like. The title input area 221 is an area for inputting a title character string to be displayed on the title bar 213 of the portal page 210. The contact item setting area 222 is an area for setting a character string to be displayed as a contact item, a URL of a link destination added to the contact item, and a notification time of the contact item. The addition, deletion, change, etc. of the communication items can be performed by using the operation buttons 223.

  When the administrator clicks an OK button 224 after inputting a title character string or setting a contact item on the setting page 220, an HTTP request for setting the contact item is transmitted to the Web server 10. The Web server 10 reflects the contents set in the setting page 220 in the page configuration information of the profile XML 114 of each user. That is, the character string input in the title input area 221 is set as the value of the title attribute of the unit element 1142a, and the contact item, URL, and update time set in the contact item setting area 222 are respectively set in the unit element 1142a. It is set as the value of the item element, the value of the url attribute, and the value of the timing attribute. Therefore, when the user tries to display the portal page 210 after the administrator's work on the setting page 220 is performed, the processing described in the second embodiment is executed, and the setting is performed on the setting page 220. The notification unit 213 on the portal page 210 is displayed according to the content that has been made.

  As described above, according to the Web server 10 in the third embodiment, a notification item indicating that setting of a notification item is necessary is required for the administrator and a link to the setting page is provided. A portal page 210 that can be displayed can be provided. Therefore, the administrator can display the setting page 220 based on the communication item, and can easily set the communication item as it is.

  By the way, in recent years, an embedded device specialized for a specific function has been provided that can execute information processing equivalent to a computer, such as a device that functions as a Web server. For example, an image forming apparatus having a plurality of applications that performs processing unique to a composite service such as a printer, a copy machine, or a facsimile machine, which is called a multi-function machine or a multi-function machine, also corresponds to this apparatus. Some recent image forming apparatuses have a function as a Web server, and further have a document management function for storing copied information or information received by FAX as document data.

  Therefore, even if the Web system 1 in the present embodiment is configured using such an image forming apparatus, the effects of the present invention can be obtained in the same manner. For example, FIG. 16 is a diagram illustrating a configuration example of a Web system configured using an image forming apparatus as a Web server. In FIG. 16, the same parts as those in FIG. 16 is compared with FIG. 1, in FIG. 16, the image forming apparatus 410 is a component of the Web system 1 instead of the Web server 10. In the image forming apparatus 410, functions implemented in the Web server 10, that is, the Web server program 101, the Web application 110, the service proxy 120, and the like are incorporated. Therefore, the image forming apparatus 410 can function as the Web server 10.

  The image forming apparatus 410 will be described in more detail. FIG. 17 is a diagram illustrating a functional configuration example of the image forming apparatus according to the embodiment of the present invention. In FIG. 17, an image forming apparatus 410 includes hardware resources for performing individual image processing such as a plotter engine 1203 and a scanner engine 1204, an engine control board 1202, an OS 1201, a system management service 1106, and a network service 1107. A memory management service 1108, an operation panel management service 1109, an engine management service 1200, and various applications such as a copy application 1101, a fax application 1102, a printer application 1103, and a web application 1104.

  The engine control board 1202 controls individual functions of the image forming apparatus 410 such as the plotter engine 1203 and the scanner engine 1204, and provides the functions of the engine control board 1202 to the OS 1201 and the like through an engine I / F (interface).

  The OS 1201 is an operating system such as UNIX (registered trademark), and executes various software implemented as applications such as a copy application 1101 and a fax application 1102 in parallel as processes.

  A system management service 1106, a network service 1107, a memory management service 1108, an operation panel management service 1109, and an engine management service 1200 provide functions to upper applications such as the copy application 1101 through an API (Application Programming Interface). is there. That is, the system management service 1106 provides a function related to system management, and the network service 1107 provides a function related to network communication. For example, the network service 1107 has a function equivalent to the Web server program 101 (FIG. 3). The memory management service 1108 provides functions related to memory management, and the operation panel management service 1109 provides functions related to an operation panel (operation panel) installed in the image forming apparatus 410. Further, the engine management service 1200 provides a function for controlling the plotter engine 1203 and the scanner engine 1204 via the engine control board 1202.

  The copy application 1101 is a copy application, and the fax application 1102 is a facsimile application. The printer application 1103 is a printer application having a page description language (PDL), PCL, and postscript (PS). The web application 1104 is an application in which a function corresponding to the web application 110 of the web server 10 in the present embodiment is implemented. Therefore, the image forming apparatus 410 realizes the same function as the Web server 10 by executing the processing described in FIG. 6, FIG. 9, FIG.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

It is a figure which shows the structural example of the Web system in embodiment of this invention. It is a figure which shows the hardware structural example of the Web server in embodiment of this invention. It is the schematic of the example of a function structure of the Web system in embodiment of this invention. It is a class diagram for demonstrating the function structure of a Web application. It is a figure which shows the example of the portal page in embodiment of this invention. It is a sequence diagram for demonstrating the production | generation process of the portal page in 1st embodiment. It is a figure which shows the example of a definition of the profile XML in 1st embodiment. FIG. 6 is a diagram illustrating a display example of a portal page that notifies printer status information. It is a sequence diagram for demonstrating the production | generation process of the portal page in 2nd embodiment. It is a figure which shows the example of a definition of the profile XML in 2nd embodiment. It is a figure which shows the example of a display of the portal page which notifies a notification matter. It is a sequence diagram for demonstrating the production | generation process of the portal page in 3rd embodiment. It is a figure which shows the example of a definition of the profile XML for managers in 3rd embodiment. It is a figure which shows the example of a display of the portal page for administrators. It is a figure which shows the example of a display of a setting page. 1 is a diagram illustrating a configuration example of a Web system configured using an image forming apparatus in a Web server. 1 is a diagram illustrating a functional configuration example of an image forming apparatus according to an embodiment of the present invention.

Explanation of symbols

1 Web system 10 Web server 11 CPU
12 ROM
13 RAM
14 Auxiliary storage 15 Network I / F
16 Drive device 17 Recording medium 20 Web client 21 Web browser 30a Printer server 30b Document management server 30c Mail server 31, 31a, 31b Service 40 Network 50 Printer 60 Document DB
101 Web Server Program 110 Web Application 111 Servlet 112 Page Generation Class 113 Profile Operation Class 114 Profile XML
115a Unit data acquisition class A
115b Unit data acquisition class B
115c Unit data acquisition class C
120, 120a, 120b Service proxy 121c Local module 410 Image forming apparatus 1101 Copy application 1102 Fax application 1103 Printer application 1104 Web application 1106 System management service 1107 Network service 1108 Memory management service 1109 Operation panel management service 1200 Engine management service 1201 OS
1202 Engine control board 1203 Plotter engine 1204 Scanner engine

Claims (12)

A web page generation device that generates a web page,
When the request time at which the generation of the Web page is requested is compared with a display time set in advance for predetermined information to be displayed on the Web page, and the request time has passed the display time. A Web page generation apparatus comprising Web page generation means for generating the Web page so that the predetermined information is displayed. The Web page generation unit according to claim 1, wherein the Web page generation unit generates the Web page so that the predetermined information is displayed when the request time first passes the display time. apparatus. 3. The Web page generation unit generates the Web page so that the predetermined information is displayed every time the request time first passes the display time within a predetermined time. Web page generation device. The web page generation unit records a generation time when the web page is generated so that the predetermined information is displayed,
The predetermined information is displayed when the request time has passed the display time and the display time is later than the generation time recorded within the certain period. The web page generation apparatus according to claim 3, wherein the web page is generated. 5. The web page according to claim 1, wherein the web page generation unit generates the web page so that the predetermined information is displayed in a partial area of the web page. 6. Generator. The web page is a web page in which a plurality of display areas each having display information are integrated,
6. The Web page generation apparatus according to claim 5, wherein the Web page generation unit generates the Web page so that the predetermined information is displayed in one display area of the plurality of display areas. . The web page generation apparatus according to claim 6, further comprising a display time management unit that manages the display time for each display information of the plurality of display areas. The Web page according to claim 6 or 7, wherein the display time management means is capable of managing the display time for each item constituting display information displayed in one display area. Generator. 9. The Web page generation unit, when generating the Web page, incorporates a link to a Web page related to the predetermined information with respect to the predetermined information. The web page generation device described. A web page generation method using a computer,
A determination procedure for determining whether a request time at which the generation request is made has passed a display time preset for predetermined information to be displayed on the Web page in response to a Web page generation request;
And a Web page generation procedure for generating the Web page so that the predetermined information is displayed when it is determined in the determination procedure that the request time has passed the display time. A Web page generation method. On the computer,
A determination procedure for determining whether a request time at which the generation request is made has passed a display time preset for predetermined information to be displayed on the Web page in response to a Web page generation request;
A Web page generation procedure for generating the Web page so that the predetermined information is displayed when it is determined in the determination procedure that the request time has passed the display time. Web page generation program. The computer-readable recording medium which recorded the web page generation program of Claim 11.

Images