JPH11338808A - Home page confirming method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily set the condition of a home page which is dynamically generated and also to shorten the confirming time of the home page by attaining the easy confirmation of contents of the home page without changing its environment. SOLUTION: A confirming client computer 1 includes a transfer data generation part 15 which converts the condition data 11 and the end notification data 13 into the forms to be transferred to a server computer 3 and a confirming data acquisition part 16 which acquires the confirming home page display data 46 generated by the computer 3. The data 11 are inputted for the computer 1 to dynamically generate a home page. Then the data 11 are converted into the transfer data and notified to the computer 3 where the dynamic home page data are generated from the data 11. The computer 1 can instantaneously display and confirm the dynamic home page data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention
The present invention relates to a method for confirming a dynamically generated homepage in an intranet environment.

[0002]

2. Description of the Related Art When creating a homepage, it is necessary to confirm the display result of the created homepage definition file. In this confirmation step, the displayed contents can be confirmed by using software called a browser for displaying a homepage actually used in the actual stage.

[0003]

At present, it is possible to dynamically generate a home page and change the display content according to the date and time, the access user, and the like.

[0004] In the above-mentioned conventional technology, since only confirmation after homepage generation can be performed, conditions such as date and time and access user must be set each time and confirmed one by one. There was a problem that it took time. Further, there is another problem that the condition that the environment setting needs to be changed in the server computer, such as the date and time data, affects all the clients, so that the server computer must be occupied in order to confirm the display contents.

An object of the present invention is to make it possible to easily confirm the display contents of a dynamically generated homepage.

Another object of the present invention is to make it possible to confirm the condition setting of a dynamically generated home page without changing the environment setting of an actual server computer and without affecting other client computers. The purpose is to make the contents of the confirmed homepage immediately usable as a production homepage.

[0007]

In order to achieve the above object, a condition for dynamically generating a homepage by a client computer is input as condition data. The condition data is converted into transfer data and notified to the server computer. The server computer generates the dynamic homepage data by giving the condition data to the software for generating the dynamic homepage from the notified condition data. In the client computer, the generated dynamic homepage data can be immediately displayed and confirmed.

In order to achieve the above object, it is determined whether or not condition data and end notification data are attached to data transferred from a client computer. If it is not attached, the homepage generation conditions of the dynamic homepage generation software are obtained from the date and time data obtained from the operating system or the access user data obtained from the access user data database to generate the dynamic homepage data. In the case where there is attached data and condition data, a homepage generation condition is acquired from the attached data to generate dynamic homepage data. If the attached data is end notification data, the confirmed homepage definition file is expanded into a production homepage definition file.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of the present invention.

The client computer 1 for confirmation is
Confirmation homepage generation request unit 10 for requesting generation of a homepage with condition data 11, end notification data 13
A confirmation end requesting unit 12 for requesting termination of confirmation and deployment to the production environment, a confirmation homepage display unit 14 for displaying confirmation contents, and conversion of condition data 11 and termination notification data 13 to a format for transfer to the server computer 3. And a confirmation data acquisition unit 16 for acquiring confirmation home page display data 46 generated by the server computer 3.

The production client computer 2 includes a production home page generation request unit 21, a production home page display unit 22, and browser software 23 for realizing each request.

The server computer 3 includes a WWW server 30 that receives request data from the confirmation client computer 1 and the production client computer 2, presence / absence of condition data 11 and end notification data 13, and ancillary data for determining the type of data. An analysis unit 33, a data setting unit 34 for setting a condition for the dynamic homepage generation unit 38 when the attached data type is the condition data 11, and an input / output file for switching the input / output file of the dynamic homepage generation unit 38 depending on the presence or absence of the attached data. The output switching unit 37, the date and time data 36 acquired from the operating system 32 to be input to the dynamic homepage generation unit 38 at the time of the request from the production homepage generation requesting unit 21,
B41, access user data DB 35, production homepage file 42, production homepage display data 43 to be output, and confirmation homepage definition to be input to the dynamic website generation unit 38 when requested from the confirmation homepage generation request unit 10. File 44, confirmation homepage display temporary data 45 to be output, confirmation end request unit 1
The production definition file replacement unit 40 that switches the production homepage definition file 42, which is the production environment data, to the confirmation homepage definition file 44, which is the confirmed data, can be displayed as a list from the confirmation homepage display temporary data group 45 in response to a request from the server 2. Confirmation homepage generation unit 39 that generates confirmation homepage data 46 in a format.
Is provided.

FIG. 2 shows an example of condition data whose display contents are changed when a home page is dynamically generated.

A home page having a different display content is dynamically generated depending on the date and time and data for each access user.

FIG. 3 shows an example of data for transferring the condition data 11 and the end notification data 13 from the confirmation client computer 1 to the server computer 3. By executing the data of FIG. 3, the condition data 11 and the end notification data 13 are transferred to the server computer 3 as files.

FIG. 4 shows an example of the file contents of the condition data 11.

FIG. 5 shows an example of the file contents of the end notification data 13.

FIG. 6 shows an example of the confirmation homepage display data 46 regenerated by the confirmation homepage display temporary data group 45 in the confirmation homepage generation section 39 of the server computer 3 so that the list can be displayed. It is composed of a set of a homepage dividing unit 100, a list display unit 101, and a homepage 102 for confirmation.

FIG. 7 shows a confirmation homepage generation request unit 1.
0, processing completion for each request from the confirmation end requesting unit 12 and the production homepage generation requesting unit 21 and an example of each processing.

The transfer data is acquired from the WWW server 30 (201), and it is determined whether or not the attached data such as the condition data 11 and the end notification data 13 exist as the transfer data (202). If the attached data does not exist, the production homepage definition file 42 is set in the input definition file as a request from the production homepage generation request section 21 (203), and the dynamic homepage generation section 38 is called (216). If the attached data exists, the homepage definition file for confirmation 44 is set as an input definition file of the dynamic homepage generation unit 38 (204), and it is determined whether the type is the condition data 11 (210).

If it is not the condition data 11, it is determined whether the type is the end notification data 13 (220). In the case of the end notification data 13, after saving the current production homepage definition file 42 as a request from the confirmation end request unit 12 (221), the storage location of the production homepage definition file 42 is acquired from the end notification data 13. (22
2), the confirmed homepage definition file 44 is switched to the production homepage definition file 42 (223).
If it is not the end notification data 13, an error notification is made (2
18) End.

If the type of the attached data is the condition data 11, it is determined whether the content of the data is date and time data (21).
1). If it is date and time data, a date and time condition is set from the condition data 11 (212), and if it is not date data, it is determined whether it is access user data (213). If it is not the access user data, an error notification is performed (21
8) End.

If it is access user data, the setting of user conditions from the condition data 11 (214) is repeated by the number of user data (215). Calling of the dynamic homepage generation unit 38 according to the conditions set in the above processing (2
16) is repeated by the number of condition data (217). With the above processing, the dynamic homepage generator 3 for each request type
8, the input data is switched, the conditions are set, and the confirmation environment is switched to the production environment.

FIG. 8 shows an example of processing of the dynamic homepage generation unit.

In the processing example shown in FIG. 7, the input (301) of the homepage definition file determined by the setting of the production definition file (203) or the setting of the confirmation definition file (204) as the input file and the dynamically generated data DB41
Is input (302). Next, it is determined whether or not the condition data 11 has been set (303).
6 (303) and access user data from the access user DB 35 (305) to generate the production home page display data 43 (306).

If the condition data 11 has been set, the confirmation homepage display temporary data 45 is deleted (30).
7), date data and access user data are obtained from the conditions set by the date and time condition setting (212) and the access user condition setting (214) in FIG.
08), the generation of the confirmation homepage display temporary data 45 (309) is repeated by the number of conditions (310).

According to the above processing example, at the time of a request from the confirmation homepage generation request unit 10, the confirmation homepage display temporary data 45 is generated from the condition data 11, and at the time of the request from the production homepage generation request unit 21, the server Access user data DB 38 in which date and time data 35 of the computer 3 itself and production user data are stored.
Production homepage display data 4 from user data in
3 is generated.

[0029]

According to the above-described embodiment, the condition setting of a dynamically generated home page can be easily set, and confirmation can be performed immediately, which is effective in shortening the confirmation work. In addition, you can also perform confirmation work at the same time as the operation of the production environment, and after confirmation, you can easily deploy it to the production environment,
It is also effective for effective use of server computers.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a homepage checking method according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of a homepage generation condition of the present invention.

FIG. 3 is a diagram showing an example of data for transfer processing of the present invention.

FIG. 4 is a diagram showing an example of condition data according to the present invention.

FIG. 5 is a diagram showing an example of end notification data according to the present invention.

FIG. 6 is a diagram showing an example of homepage data for confirmation according to the present invention.

FIG. 7 is a flowchart illustrating an example of a client request separation process according to the present invention.

FIG. 8 is a flowchart illustrating a processing example of a dynamic homepage generation unit of the present invention.

[Explanation of symbols]

10: confirmation homepage generation request unit, 11: condition data, 12: confirmation end request unit, 21: production homepage generation request unit, 33: attached data analysis unit
34: Data setting unit, 37: Input / output data switching unit, 40: Production definition file replacement unit

Claims (2)

[Claims] 1. Condition data for dynamic homepage generation such as date and time data and access user data on a client computer, a homepage generation request section for confirmation, a data generation section for transfer, a data acquisition section for confirmation, and display of a homepage for confirmation. It consists of a data analysis part, a data setting part, an input / output data switching part, a dynamic homepage generation part, a homepage definition file for verification, a homepage generation part for verification, and homepage display data for verification on the server computer. A method for confirming the contents of a homepage, wherein the contents of the generated homepage can be easily checked without changing the environment. 2. Condition data for generating a dynamic home page such as date and time data and access user data, end notification data, an attached data analysis section, a production home page definition file, a confirmation home page definition file, and an input / output data switching section. A homepage confirmation method comprising a production definition file replacement unit, wherein the confirmation work can be performed simultaneously with the production environment, and the confirmed homepage can be developed for the production environment immediately after the confirmation work is completed.