JP2002108926A - Web suite system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a Web Suite system capable of freely setting contents and a layout thereof especially while using an XML document or the like and capable of dealing with even a portable telephone or PDA. SOLUTION: In this Web Suite system, a site can be flexibly constructed while freely selecting the layout or contents of a Web site by constructing a database while using a computer language such as XML.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to Java, XML
Web site that can freely select the layout and contents of a website (Web site) based on the content and configuration information constructed in the database using a computer language such as System.

[0002]

2. Description of the Related Art Conventionally, HTML (Hyper Text Marku
Web sites are being constructed using p Language). The construction of the Web site using this HTML is HT
ML tags are used to set the position, size, color, and the like of page data, and to insert content.

However, when using HTML,
The definition of each tag is defined uniformly and cannot be set freely. In addition, it takes time to perform a content search and a narrow search. Therefore, the page designer can freely set the tag function using XML and use the DTD (Document Type Defi
nition) and a method of constructing a site for defining a document using an XML schema.

[0004]

However, the above X
Even when the ML is used, the page configuration information and the contents constituting the page data cannot be freely incorporated in the database. Further, with respect to PDAs such as mobile phones and mobile devices, it has not been possible to freely use programs described in XML description and page configuration information and contents constructed in a database.

According to the present invention, content and its layout can be freely set by using page description information and content in an XML description and a database.
It is to provide a web suite system that can cope with the problem.

[0006]

According to the first aspect of the present invention, there is provided a storage process for storing content and page configuration information in a database, and the content and page configuration information stored in the database by the process. And a web suite system that performs page data creation processing for creating page data and display processing for displaying the page data created by the page data creation processing on a user terminal device.

Here, various applications can be used as the database, and various contents such as characters, images, sounds, and binary codes can be used as the contents.

Also, the layout can be freely set for the page configuration information as well. With such a configuration, the content and its layout can be dynamically set. Therefore, forms that support data input can be freely combined with the Web browser, and interactive contents can be provided.

According to a second aspect, in the first aspect, the content is a character, an image, a sound, a binary code, or the like. With this configuration, the web suite system of the present invention can use more contents.

According to a third aspect of the present invention, in the first aspect, the creation of the page data is based on XML. By using XML in this way, various applications can be used, so-called user-friendly page screens and screen transitions can be designed, and the designed pages can be used immediately.

Furthermore, since the definition and access method for the database storing the information collected by the application can be described in the XML, the data to be stored can be freely extended.

According to a fourth aspect of the present invention, in the first aspect of the invention, the page data can be created by acquiring data from a database connected to a network.
With this configuration, another database connected to a network such as the Internet can be used, and a wider range of information can be used to create a page.

According to a fifth aspect of the present invention, in the first aspect, the terminal device is a PDA. Where PD
A (Parsonal Digital Assistants) is an information terminal device, such as Windows CE or WAP (Wi-Fi).
It supports a reless application protocol, cHTML protocol, etc., and can build a content distribution site for PDAs, and can also build a content distribution site for mobile phones.

According to the present invention, there is provided a storage means for storing content and page configuration information in a database, and using the content and page configuration information stored in the storage means to store page data. This can be achieved by providing a web suite server that has a page data creation unit that creates the page data and supplies the page data created by the page data creation unit to a user terminal device.

This embodiment is an invention of a web sweet server. The server makes it possible to use databases of various applications and dynamically set contents and layout thereof. In addition, forms supporting data input can be freely combined from a Web browser, and interactive contents can be provided.

According to a seventh aspect of the present invention, for example, the content is a character, an image, a sound, a binary code or the like. According to an eighth aspect of the present invention, in the invention according to the sixth aspect, the page data is created based on XML.

According to a ninth aspect of the present invention, in the sixth aspect of the invention, the page data is created by acquiring data from a database connected to a network.

According to a tenth aspect, in the invention according to the sixth aspect, the terminal device is a PDA. Claims 6 to 10 describe claims 2 to 5 above.
And has corresponding functions and functions.

According to the present invention, a storage function for storing content and page configuration information in a database, and the content and page configuration information stored in the database by the function are used to create page data. Providing a recording medium for recording a computer-executable program, the program having a function of transmitting page data generated by the page data generating function and a function of transmitting the page data generated by the page data generating function to a user terminal device. Can be achieved by doing

This embodiment is an invention of a recording medium for recording an execution program of a web suite system, and the recording medium may be a floppy (registered trademark) disk or a CD-RO.
M, MO, etc. correspond. By using a recording medium that records such a program, it is also possible to dynamically set the content and its layout, and it is possible to freely combine forms that support data input from a Web browser, thereby enabling interactive content. Can be provided.

[0021]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a system configuration diagram of a web suite system illustrating an embodiment of the present invention. The terminal device 1 of the user is a web suite (We
A website (Web site) 3 can be connected via the bSuite 2, and various information is distributed from the commerce company 4 to the website (Web site) 3. Here, the user's terminal device 1 is a personal computer,
It is composed of a mobile phone and various mobile devices, and is represented by, for example, a personal computer 1-1, a mobile phone 1-2, a mobile device 1-3,.

The web site (Web site) 3 has a server, and FIG. 2 is a schematic diagram of the server. The server is
It comprises a CPU 3a, a ROM 3b, a RAM 3c, etc.
The PU 3a performs processing in accordance with the system program registered in the ROM 3b, and accesses the database 3 'connected to the server as necessary to exchange data.
Further, necessary information is displayed on the display 3d, and information is exchanged via a communication line. The system control of this embodiment is executed in accordance with a program stored in the ROM 3b. As shown in the figure, a media driver 3e provided in the server stores a floppy disk or CD-RO in the media driver 3e.
A configuration is also possible in which a recording medium such as M is mounted, and the program is read from these recording media and used.

FIG. 3 shows the above-mentioned web suite (WebSu).
FIG. 3 is a diagram illustrating the configuration of item 2). Web Suite (Web Suite) 2 is an XML loader (XML Load).
er) 5, WSSchena pool 6,
Action part 7, WSDATA9, DATA BASE Handler 1
0, Statement / Transfer 11, and a service program interface (Service Program Interface) 15. The action unit 7 performs a process according to a request (Request Dispatcher) 16 by the user 1.

An XML loader (XML Loader) 5 analyzes the supplied XML document and generates an integrated XML program. The supplied XML document is Action
XML31, ViewXML32, GatherXML33, Page
There is an XML 34 and a Contents XML 35, which include a logic format, a schema, a character string, and the like.

WS Schema pool
Reference numeral 6 has a function of storing the above-mentioned XML information generated by the XML loader (XML Loader) 5. When the system of this example is started, a required XML document is created and read out to the WS schema pool (WSSchena pool) 6.

The action section 7 has an action (Action).
8, the Session Control process 8a, User G
roup Authorization processing 8b, Data Base Updating processing 8c, Access Logging processing 8d, Cache Read processing 8e,
Perform Cache Write processing 8f. Further, a page for the user is created by the above-described processes. For example, Data Base
The Updating process 8c is a process for updating a database described later. The Access Logging process 8d counts, for example, the number of accesses. The Cache Write process 8f caches information read from the database, for example.
The Cache Read process 8e reads cache data when necessary and creates a page.

Also, User Group Authorization processing 8b
Is used for controlling the user group environment and setting the group. And the page created by the above process,
PageCreation generated in 8g, action
8 is sent to the terminal device 1 of the user.

On the other hand, WSDATA 9 is a format for enabling data processing by the action unit 7, and
TA BASE Handler 10, Statement / Transfer 11, DATA
Data is exchanged with a database (DATA BASE) 13 via a BASE Driver (JDBC) 12. The database (DATA BASE) 13 has many applications, and a program for accessing each application and reading necessary data is a DATA BASE Driver (J).
DBC) 12.

WSDATA 9 has layout information. For example, when creating an application, it has information (layout information) that cannot be handled by existing pages and contents. The Statement / Transfer 11 searches, changes, and deletes the database (DATA BASE) 13 by SQ.
SQL is changed by the database (DATA BASE) 13 having L.

Plug-in via a service program interface (Service Program Interface) 15
Software 14 can also be used. FIG. 4 shows WSDATA 9, DATA BASE Handler 10, and Statement / Tran of the above configuration.
FIG. 3 is a diagram specifically illustrating functions of a sfer 11 and the like.

WSDATA9 is WSView17, WSGather1
8, WSPage19, WSContents20, Page / Contents
It has the functions of the Loader 21. The WS Gather 18 has a function of collecting frame information and content information from the database (DATA BASE) 13, and the collected page information and content information are displayed by the WSView 17. The collection of page information is performed by WSPage19, and the collection of content information is performed by WSContents20. Also, Page / C
The ontents Loader 21 actually collects page information and content information via the DATA BASE Handler 10.

The collection of the page information and the content information is performed by using GatherXML 33, PageXML34, ContentsX.
It is executed according to each description of ML35. On the other hand, the database (DATA BASE) 13 contains stored procedures 23, Pa
ge Schema 24, Contents 25, Cache 26, User / Gro
Data construction such as up / Roll / Acl 27 can be performed.

FIG. 5 is a diagram for explaining each of the above functions in more detail. In FIG. 5, ActionXML 31 describes the contents of the user's instruction. For example, "Press a predetermined button to display a map" or " Press to display a specific person's schedule ". Also, ViewX
The ML 32 is an XM that describes, for example, “where to display the map” or “where to display the schedule”.
L document. GatherXML 33 (however, not shown in FIG. 5) is an XML document that describes an instruction such as “what range of maps to collect” or “what range of schedules to collect”. In addition, PageXM
L34 is, for example, XML describing a page layout.
ContentsXML 35 is a document that describes an instruction to collect content information.

Each of the XMLs 31 to 35 is supplied to the WS schema pool (WSSchena pool) 6 as described above, drives the corresponding loader, and performs processing for a user request. For example, Request Dispat
cher) 16, the Action Loaders 47 are activated according to the description of the ActionXML 31, and give an action instruction such as a map display by a user's button operation.

Further, the Action Classes 48 are activated, and the above-mentioned WSAction is activated. Hereinafter, the View Loaders 49 and the like are also driven according to the description of the corresponding XML 32 and XML 34, and the above-described WSView 17, WS Gather 18, W
Necessary page information and content information are collected using SPage 19, WSContents Gather 20, and the like. Where W
SDOM (WS Document Object Model) 52 is a program for bridging an XML document and application data, classifying each content for each object,
Data that can be processed by the application. Also, W
SView Element 53 is an element constituting a page,
In the case of the above-mentioned schedule, it is an element such as “date and time”, “meeting”, “day of the week”, and in the case of map information, it is an element such as “place”, “hotel”, “restaurant”.

The WSContents Data 54 is specific content (data). For example, in the case of the above schedule, "September 30", "Saturday", "meeting with Mr. XX", and "October 3" , "Tuesday", "Mr. XX and meeting", and the like.

FIG. 6 shows a database (DATA BASE).
13 is a system configuration at the time of accessing, and is similar to FIG. 5 in that PageXML61, ContentsXML62, SQLStatem
ent63, DATA BASE SchemaXML64, DATA BASE Acc
Processing is performed based on the information described in the ess Rules XML 65, and the database (DATA BASE) 13 is accessed. Note that WSView Element 53 and WSContents Dat
About a54, it is the same as that of said FIG.

In the web suite system having the above-described configuration, first, a registration process to the web suite system of the present embodiment will be described. FIG. 7 is a flowchart for explaining the registration process.

First, the user operates his / her personal computer, starts a web browser (Web browser), and sets the URL of the web site (Web site) 3 in this example.
(Step (hereinafter, referred to as S) 1). This UR
With the input of L, the display data of the initial screen is sent from the website (Web site) 3 to the user and displayed on the display of the terminal device of the user (S2).

FIG. 8 shows a display example of the initial screen, in which a login frame, a frame of service information, a sign-up transition button, and the like are displayed. Here, if the user has not registered in this system yet, "Sign up"
Click the button (S3 is Y (yes)). That is, the position of the cursor is moved to the position a shown in FIG. 8 by operating the mouse or the like, and clicked.

According to the user's instruction, a sign-up item input screen is sent from the web site (Web site) 3 and displayed on the display of the terminal device (S4).
FIG. 9 is a display example of this sign-up item input screen.
First, the terms of use are displayed. If the user agrees with the terms of use, the user clicks the "I agree"button; otherwise, the user clicks the "I do not agree" button.

Here, when the user clicks the "I do not agree" button (Y in S5), the process returns to the above-mentioned processing (S2), and the initial screen is displayed on the display (S6). On the other hand, if the user agrees with the above terms and conditions, the user clicks the "I agree" button to display the sign-up item input screen shown in FIG. 10 on the display. On the sign-up item input screen, various items such as an e-mail address, a password, a nickname, and a model name of a mobile phone are displayed, and the user inputs necessary information.

Next, the input check of the sign-up item is checked (S7), and if there is no problem, the display shifts to the display of the next sign-up item confirmation screen (Y in S7, S8). If an error is detected by the input check (N in S7), a sign-up item input screen is displayed (S9), and the input is corrected.

On the other hand, if there is no problem in the input check, a sign-up item confirmation screen shown in FIG. 11 is displayed (S8). This confirmation screen displays the above input information. If there is an error in the e-mail address, nickname, model name of the mobile phone, etc., click the "change input contents" button (not shown) and re-enter the sign-up item input screen. It is displayed (S10 is Y, S11). On the other hand, if there is no error in the input information, a “Sign-up execution” button (not shown) is clicked, and a sign-up execution instruction is output (S12).

When the sign-up process is completed on the website (Web site) 3, a sign-up completion notice is displayed on the display (S13). On this screen, when the user clicks "Next", a top screen exclusively for members is displayed (S14, S15).

On the other hand, the user who has already registered in the present system is N (No) in the above-mentioned determination (S3), and the "registration ID number" and "Registration ID number" already held from the initial screen shown in FIG. Enter "Password" and "Login"
The button (position b in FIG. 8) is checked (Y in S16). By this processing, the “registration ID number” and “password” are sent to the website (Web site) 3, and the “registration ID number” and “password” are checked (S17). If the input is not a check of the "login" button (N in S16), other corresponding processing is executed.

Here, if there is no problem with the "registration ID number" and the "password", a top screen exclusively for the member is displayed (S17 is OK, S18). On the other hand, if there is an error in either or both the “registration ID number” and the “password” (NG in S17), the “registration ID number” and the “password”
Is displayed, and an error message is displayed (S19).

When the "password" is forgotten, the display of "forgot password" (not shown) is clicked to display a reminder input screen (Y in S20, S21). In this case, the "password" can be confirmed by inputting the predetermined information.

On the other hand, after the error message is displayed, the web site (Web site) 3 inputs the "password"
And the "registration ID number" are checked, and if OK, a top screen exclusively for the member is displayed (OK in S22, S2
3). If the above check is also NG, the "Registration ID
The input screen for the “number” and the “password” is displayed (S22
Is NG, S24).

FIG. 12 is a flowchart for explaining the above-mentioned reminder processing. First, a reminder input screen is displayed (S21-1). FIG. 13 shows a reminder input screen, in which data is input in a form to answer a question, the data is checked, and if there is no problem, the screen shifts to a member-only top screen (S21-4, S21-6). On the other hand, if there is an error in the answered data, the reminder input screen is redisplayed and input again (S21-4, S21-5). During this time, when the “return” button displayed on the screen is clicked, the above-described initial screen is displayed (S21-2, S21-
3).

On the other hand, FIG. 14 shows a top screen exclusively for members, in which menus such as “schedule”, “task”, and “album” are displayed. FIG. 15 is a flowchart for explaining the subsequent processing. After the top screen for the member is displayed, "sign out" is determined (S26), and if it is signed out, the corresponding sign out processing is performed (S2).
7 to S29).

On the other hand, when the setting is clicked, the designated menu screen is displayed (S26 is N, S30 is Y, S
31). This time is 60 seconds. Here, for example, FIG.
When the "schedule" shown in FIG. 4 is clicked (Y in S32), an initial screen of the "schedule" is displayed (S3).
3). This display continues for 60 seconds, and thereafter returns to the above-described member-only top screen.

Similarly, when "task" shown in FIG. 14 is clicked (Y in S34), an initial screen of "task" is displayed (S35), and after this display is continued for 60 seconds, the above-mentioned member-only top page is displayed. Return to the screen. Hereinafter, similarly, when "Album" is clicked, an initial screen of "Album" is displayed (Y in S36, S37), and when "Messenger" is clicked, an initial screen of "Messenger" is displayed (Y in S38, Y). S39.

Hereinafter, similarly, as shown in FIG. 15, “address book”, “bookmark”, “message list”,
Regarding the “schedule list”, the respective initial screens can be displayed by checking the corresponding buttons (S40 to S47).

Next, FIG. 16 is a view for explaining a case where the above-mentioned "address book" is selected. First, the initial screen of the "address book" is displayed in the address in the past display order. Before the change according to this example, the display order is the registration order and the user ID order in addition to the display order. For example, by clicking the “registration order” button shown in FIG. 16, the registration order is displayed next. By clicking a button of "not shown""user ID order" which appears in the registration order display, the user ID order is displayed.

As described above, the display shown in FIG. 16 is in the display order, and indicates that the past display history is in the order of "Taro Yamada", "Ichiro Takahashi", and "Yumiko Sato". In the database having the above configuration, in many cases, kanji is input in the name field in Japan, and even if the name is displayed in the name order, the order is in the order of the kanji code, so that it is difficult to search. Therefore, in this example, a nickname column is added, a pseudonym or a Roman character is input in the nickname column, and the nickname column can be displayed in the order of the nickname. Hereinafter, a specific description will be given.

FIG. 17 is a diagram showing a change image of the "address book" in this case. FIG. 11A is an example of the address list screen before the change shown in FIG.
Is an example of the address registration update screen before the change. From this state, the XML document is changed, "nickname" is added to the database, updated, and the database is regenerated.

FIG. 18 is a flowchart for explaining this processing. For example, the function is changed without changing the coating of the Java program. First, a schema definition XML of the address management database (3 shown in FIG. 3)
4, a "nickname" is added to step 71 shown in FIG. 4 and step 64 shown in FIG. 6 (step (hereinafter referred to as ST) 1).

Next, a "nickname" item is provided in the address management database, and the database is reorganized (ST2). That is, next, a "nickname" column is added to the page definition database of the address list screen (ST3).

Next, an address list screen information acquisition statement XML (33 shown in FIG. 3, 72 shown in FIG. 4,
Is changed so as to acquire the "nickname" information (ST4). At this time,
It changes so that "nickname" information may be acquired in "user ID order" and "name order".

Next, an address list screen information acquisition statement XML "nickname field" is added (ST
5). Next, the address list screen page view XML (32 shown in FIG. 3, 37 shown in FIG. 4, and 42 shown in FIG. 5) is changed so that the “nickname” field can be set as a view (ST6).

Next, a button of “order of nickname” is added to the display order select button form database (ST).
7) Add an action definition when "Nick order" is selected in the display order select button form database (ST8).

Next, an input / output column of "nickname" is added to the page definition database of the address registration update screen (ST9), and an address information acquisition statement XML is added.
(33 shown in FIG. 3, 72 shown in FIG. 4, 63 shown in FIG. 6)
Is changed to obtain "nickname" information (ST10).

Next, the address registration update screen page view XML (32 shown in FIG. 3, 37 shown in FIG. 4, and 42 shown in FIG. 5) is changed so that the “nickname” field is also set to the view (ST11). The "nickname" information is changed to be updated by the address information registration update statement XML (33 shown in FIG. 3, 72 shown in FIG. 4, and 63 shown in FIG. 6) (ST12).

Next, address information registration update action X
ML (31 shown in FIG. 3, 73 shown in FIG. 4, 4 shown in FIG. 5)
In step 1), the content of the “nickname” field is changed to be registered in the address management database (ST1).
3).

By the above processing, the address list screen shown in FIG. 17C is created. By, for example, checking the "nickname" button, the display can be changed from the display order to the nickname order. Therefore, an address search can be performed by a nickname, and a site that can be more easily searched can be constructed. FIG. 17D shows an example of the address registration update screen after the change.

In the above embodiment, the example of the "address information" shown in FIG. 17 has been described. However, the present invention is not limited to the "address information" but includes "map information", "schedule", "mail information" and the like. It can be applied to the construction of various databases, and can also be applied to portable devices such as PDAs and mobile phones.

In this example, since the XML document is used, the text contents can be individually stored in the database, and processing such as a character string search over a plurality of applications can be easily performed.

Further, by using the database (DB) editor, the settings of the page layout DB and the content DB can be corrected, and the corrected page information can be immediately displayed in the sub-window. Therefore, the page information DB can be maintained while confirming the change result.

Further, by using the logic editor, the XML document can be corrected in real time, and the logic can be confirmed in the WS maintenance mode according to the corrected XML document.

Further, according to this example, the connection of a necessary connection is performed at the time of starting the server by the pooling process described above, so that the response can be substantially reduced to zero.

[0072]

As described above, according to the web suite system of the present invention, processing such as database construction and data change is easy, and content and its layout can be easily changed.

Further, the form of the page to be constructed can be freely changed, and interactive contents can be provided.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of a web suite system illustrating an embodiment of the present invention.

FIG. 2 is a diagram illustrating a configuration of a server.

FIG. 3 is a diagram for explaining a basic configuration of Web Suite.

FIG. 4 is a diagram for more specifically explaining the configuration of WSDATA.

FIG. 5 is a diagram illustrating processing of the web suite system.

FIG. 6 is a diagram illustrating processing of the web suite system.

FIG. 7 is a flowchart illustrating a processing operation of the web suite system of the present example.

FIG. 8 is a display example of an initial screen, which is a display example of a login frame, a frame of service information, a sign-up shift button, and the like.

FIG. 9 is a display example of a sign-up item input screen, showing an actual mail format.

FIG. 10 is an example of a sign-up item input screen.

FIG. 11 is a view showing a sign-up item confirmation screen.

FIG. 12 is a flowchart illustrating a reminder process.

FIG. 13 is a diagram showing a reminder input screen.

FIG. 14 is a diagram showing a top screen exclusively for members.

FIG. 15 is a flowchart illustrating processing after the top screen exclusively for members.

FIG. 16 is a diagram illustrating a case where “address book” is selected.

FIG. 17 is a diagram illustrating an example of a process of changing the contents of “address book”.

FIG. 18 is a flowchart illustrating a content change processing operation of the “address book”.

FIG. 19 is a flowchart illustrating a content change processing operation of the “address book”.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 Terminal device 1-1 Personal computer 1-2 Mobile phone 1-3 Mobile device 2 Web suite 3 Website (Web site) 4 Commerce company 5 XML loader (XML Loader) 6 WS schema pool (WSSchena pool) 7 Action Part 8 Action 8a Session Control processing 8b User Group Authorization processing 8c Date Base Updating processing 8d Access Logging processing 8e Cache Read processing 8f Cache Write processing 8g Page Creation 9 WSDATA 10 DATA BASE Handler 11 Statement / Transfer 12 DATA BASE Driver ( JDBC) 13 Database (DATA BASE) 14 Plug-in software 15 Service program interface (Service
Program Interface) 16 Request (Request Dispatcher) 17 WSView 18 WSGather 19 WSPage 20 WSContents 21 Page / Contents Loader 23 Stored Produre 24 Page Schema 25 Contents 26 Cache 27 User / Group-Roll / Acl 31 GatherXML 32 ViewXML 33 ContentsXMLXML Contents 37 PageXMLViewXML32 47 Action Loaders 48 Action Classes 49 View Loaders 52 WSDOM (WS Document Object Model) 53 WSView Element 54 WSContents Data 61 PageXML 62 ContentsXML 63 SQLStatement 64 DATA BASE SchemaXML 65 DATA BASE Access RulesXML

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/21 501 G06F 17/21 501T 590 590E 17/60 302 17/60 302E 504 504 F Term (Reference) 5B009 NA12 NC06 5B049 AA02 CC02 DD01 FF03 FF09 GG02 GG04 GG07 5B075 ND03 NK02 NK54 PP02 PP12 PP22 PQ02 PQ46 PR08 QM01 UU08 5B082 GA07 5B085 BG03 BG06

Claims (11)

[Claims] 1. A storage process for storing content and page configuration information in a database; a page data creation process for creating page data using the content and page configuration information stored in the database by the process; And a display process for displaying the page data created by the creation process on the user's terminal device. 2. The web suite system according to claim 1, wherein the content is a character, an image, a sound, or a binary code. 3. The web suite system according to claim 1, wherein the page data is created based on an XML document. 4. The web suite system according to claim 1, wherein the creation of the page data is performed by acquiring data from a database connected to a network. 5. The web suite system according to claim 1, wherein the terminal device is a PDA. 6. A storage means for storing content and page configuration information in a database; and page data creation means for creating page data using the content and page configuration information stored in the storage means. A web suite server wherein the page data created by the page data creating means is supplied by a user terminal device. 7. The web suite server according to claim 6, wherein the content is a character, an image, a sound, or a binary code. 8. The web suite server according to claim 6, wherein the page data is created based on an XML description. 9. The web suite server according to claim 6, wherein the page data is created by acquiring data from a database connected to a network. 10. The web suite server according to claim 6, wherein the terminal device is a PDA. 11. A storage function for storing content and page configuration information in a database, a page data creation function for creating page data using the content and page configuration information stored in the database by the function, A function of transmitting the page data created by the creating function to the user's terminal device; and a computer readable recording medium.