JP4191926B2 - Data processing program, data processing apparatus, and data processing method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a data processing program, a data processing apparatus, and a data processing method for performing predetermined processing on data collected from an information source.
[0002]
[Prior art]
In performing specific processing in a certain business, data is often collected from a plurality of information sources and data processing is performed based on the collected data. As a form of collecting data from the information source, there are data retrieval from a database, data input from a client terminal, and taking in data transmitted by e-mail. Further, in recent years, there are various forms such as data transmitted by data exchange between systems / businesses between electronic commerce systems between businesses such as BtoB.
[0003]
FIG. 19 shows a conventional general data processing apparatus. This apparatus includes a database 2, a client terminal 4, and a mail server 6 as information sources. The processing unit 16 for processing data is connected to the database 2 via the access unit 10, connected to the terminal 4 via the display unit 12 and the application (AP) server 8, and connected to the mail server 6. Are connected via the messenger unit 14.
[0004]
In such a conventional apparatus, which data is collected from which information source, that is, the form of the information source is determined in advance, and an application program for the processing unit 16 is developed accordingly. For example, in order to retrieve data from the database 2, the processing unit 16 causes the access unit 10 to issue a structured query language (SQL) to the database 2. In order for the user to input data from the terminal 4, the processing unit 16 displays a data input screen on the terminal 4 via the display unit 12 and the application server 8 and captures the input data. For data exchange between the systems, the processing unit 16 takes in data from the mail server 6 via the messenger unit 14.
[0005]
However, when a data processing system is reconstructed due to business expansion or the like, the data acquisition form may change significantly. For example, data that has been sequentially input from the terminal 4 by the user until now can be centrally managed in the database 2, or conversely, data that has been searched from the database 2 until now can be stored in the terminal 4 for a specific customer. You may be asked to input from. Further, there is a case where data exchange between companies that has been input from the terminal 4 so far is attempted to be automated. When the information source form is changed in this way, the method for accessing the information source is changed, which causes a significant rewriting of the application program. This is because the method for acquiring data in the application program is designed depending on the form of the information source.
[0006]
[Problems to be solved by the invention]
As described above, the conventional data processing program, data processing apparatus, and data processing method have a drawback that the entire application program must be rewritten when the information source is changed.
[0007]
An object of the present invention is to provide a data processing program, a data processing device, and a data processing method that can flexibly cope with a change in the form of an information source when processing data collected from the information source.
[0008]
[Means for Solving the Problems]
In order to solve the above problems and achieve the object, the present invention uses the following means.
[0009]
(1) A data processing program of the present invention is a data processing program in a computer that collects data from a plurality of information sources through a common presentation unit.
The presentation unit is connected to the mediation unit that receives a skeleton describing the structure of data to be collected in a markup language, and the plurality of information sources. , Based on the access method according to the type of information source A plurality of connection modules,
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing program includes a computer,
Means for supplying a skeleton corresponding to data to be collected to the mediation unit;
Means for selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Means for supplying said skeleton to a selected connection module and collecting information from an information source;
It is a data processing program for making it function.
[0010]
(2) A data processing apparatus according to the present invention is a data processing apparatus that collects data from a plurality of information sources through a common presentation unit.
The presentation unit is connected to the mediation unit that receives a skeleton describing the structure of data to be collected in a markup language, and the plurality of information sources. , Based on the access method according to the type of information source A plurality of connection modules,
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing device includes:
Means for supplying a skeleton corresponding to data to be collected to the mediation unit;
Means for selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Means for supplying said skeleton to a selected connection module and collecting information from an information source;
It comprises.
[0011]
(3) A data processing method of the present invention is a data processing method for collecting data from a plurality of information sources via a common presentation unit.
The presentation unit is connected to the mediation unit that receives a skeleton describing the structure of data to be collected in a markup language, and the plurality of information sources. , Based on the access method according to the type of information source A plurality of connection modules,
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing method includes:
Supplying a skeleton corresponding to data to be collected to the mediation unit;
Selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Supplying the skeleton to a selected connection module and collecting information from an information source;
It comprises.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of a data processing program, a data processing apparatus, and a data processing method according to the present invention will be described with reference to the drawings.
[0013]
First embodiment
FIG. 1 is a diagram showing a configuration of a data processing apparatus according to the first embodiment. This apparatus includes a database 22, a client terminal 24, and a mail server 26 as information sources. The processing unit 32 that processes data is connected to the database 2, the application (AP) server 28, and the mail server 26 via the presentation unit 30. The application server 28 is connected to the terminal 24. This embodiment differs from the conventional example shown in FIG. 19 in that the access unit 10 to the database 2, the display unit 12 that displays a data input screen on the terminal 24 via the application server 28, and the messenger to the mail server 26 The functions of the unit 14 are summarized as a presentation unit 30.
[0014]
In such a configuration, the processing unit 32 can request data from the presentation unit 30 by a common access method regardless of the information source. When the information source is changed, only the inside of the presentation unit 30 needs to be changed, and it is not necessary to rewrite the entire application program of the processing unit 32. Furthermore, in order to minimize changes in the entire interior of the presentation unit 30, a number of connection modules corresponding to information sources are prepared, and the presentation function is realized by appropriately combining these modules.
[0015]
FIG. 2 shows details of the inside of the presentation unit 30. When collecting data from an information source, the processing unit 32 describes the structure of data to be collected as XML data in a skeleton 34 and passes it to the mediation unit 36. The actually collected data is stored in the structure of the skeleton 34. The mediation unit 36 has a role of a queue, and stores the skeleton 34 passed from the processing unit 32 in the XML database 38. The mediation unit 36 is connected to a plurality of connection modules (here, connection modules 42 and 44). The connection module 42 is connected to the database 22, and the connection module 44 is connected to the mail server 26 and to the terminal 24 through the application server 28. Further, the connection modules 42 and 44 are connected to the access method description file storage 48, and a specific access method description file corresponding to the module (information source to which the module is connected) can be read. The mediation unit 36 has a correspondence between a specific tag in the skeleton 34 and a connection module as a module correspondence table 40. That is, the mediation unit 36 selects an appropriate connection module corresponding to the tag described in the skeleton 34.
[0016]
Each connection module 42, 44 is activated by a trigger from the processing unit 32, reads a skeleton from the XML database 38, executes the process, and returns the skeleton to the XML database 38 again when the process is completed. The intermediary unit 36 periodically checks the skeleton and checks whether or not the processing of all related connection modules has been completed. When the processing is completed, the mediation unit 36 notifies the processing unit 32, and the processing unit 32 takes out the processed skeleton from the mediation unit 36, and the data collection is completed.
[0017]
The data collection operation will be specifically described below. FIG. 3 shows an example of the skeleton 34. Here, an example is given of a system that checks the amount of harmful substances contained in a product manufactured by a certain manufacturer. Such a survey requires a survey of individual parts used in the product and a survey of harmful substances mixed in the manufacturing process of the product. It is assumed that hazardous substances mixed in the product manufacturing process are managed in the company's own database, and the hazardous substances contained in parts are inquired of the parts manufacturer. Hazardous substances include lead, mercury, dioxin, and chlorofluorocarbons, and we will examine the content of some of these items. It is also assumed that the mass of a product (part) is also examined.
[0018]
The skeleton shown in Fig. 3 is an example of examining the product code 'XX', product code '□□□', and part code 'XXX' for mass and lead. Represents a component tag, mass represents a mass tag, and lead represents an item to be investigated by a lead tag. The skeleton has a status tag, which describes the survey status of the entire skeleton. States can be outstanding, in progress, or complete.
[0019]
FIG. 4 shows an example of the module correspondence table 40, where the product tag is connected to the connection module 42 and the component tag is connected to the connection module 44. The form of the information source can be changed by rewriting this correspondence table. For example, in order to retrieve mass and lead data related to parts from the database 22, the part tag may be rewritten to the connection module 42. When the processing unit 32 passes the skeleton 34 to the mediation unit 36, the processing unit 32 issues an investigation start command to the mediation unit 36. Upon receiving the investigation start command, the mediation unit 36 sequentially connects to the module corresponding to the tag of the skeleton 34 and executes the process. In the example of the skeleton of FIG. 3, the tag <product code = 'XXX'> is read, and the XML data 34a below the tag is passed to the connection module 42 corresponding to the tag. The XML data 34a passed to the connection module 42 has the following semantic structure.
[0020]
<Product code = '○○○'>
<Mass />
<Lead />
</ Product>
The connection module 42 reads the access method description file 48 a from the access method description file storage 48. The access method description file read by the connection module 42 is defined in advance for each module.
[0021]
FIG. 5 shows an example of the table configuration of the database 22. FIG. 6 shows an access method description file 48 a of the connection module 42. The description file 48a includes a path and column table, and the column indicates the column of the table in FIG. The path represents an element of XML data. For example, the product / @ code row indicates that the value of the code attribute of the product tag corresponds to the value of the code column of the database, and the product / mass / text () row indicates the child tag of the product tag. The value of the text element indicates that it corresponds to the value of the weight column of the database. The description file also has a search condition column indicating whether or not the row is a search condition. In the example of FIG. 6, it is shown that “weight”, “Pb”, “Hg”, and the like are set as search results using “code” as a search condition.
[0022]
FIG. 7 shows a mechanism in which the connection module 42 generates a query language (SQL) 52 for the database 22 from the given XML data 34a and the access method description file 48a. The inquiry language 52 is defined in advance as a template, and only the search condition 52a and the item 52b to be searched are blank. The connection module 42 reads the XML data 34a and checks whether the tag is in the description file 48a. If the tag exists in the description file 48a, it is checked whether or not it is a search condition. In the case of a search condition (when the tag is a product code), the column name (code) is inserted into the search condition portion 52 a of the query language 52. If it is not the search condition (when the tag is mass or lead), the column name (weight, Pb) is inserted into the search item portion 52b. By executing the above operation for all tags, the query language is finally completed.
[0023]
When the query language 52 is created, the database 22 is queried and the search result is acquired. The connection module 42 compares the search result with the access method description file 48a, and inserts a value into the corresponding part of the XML data 34a. FIG. 8 shows a mechanism for inserting the search result into the XML data 34a. For the column names weight and Pb of the search result 22a, the path corresponding to the column name is checked from the description file 48a, and the path of the XML data 34a, here product / mass / text (), product / lead / text () Write the values 100 and 5. When the connection module 42 completes the writing of the data to the XML data 34a, the connection module 42 returns the XML data 34a to the mediation unit 36. When the XML data is returned from the connection module 42, the mediation unit 36 checks the grammatical structure, and if there is no problem, the mediation unit 36 overwrites a part of the skeleton stored in the XML database 38 with the XML data 34a. Thereby, the data search / collection from the database 22 by the connection module 42 ends.
[0024]
When the processing by the connection module 42 ends, the mediation unit 36 checks the next tag of the skeleton 34. If the next tag is also a product tag, the same processing is repeated. In the case of a component tag, XML data below the component tag is passed to the corresponding connection module 44 based on the module correspondence table 40. The XML data passed to the connection module 44 has the following semantic structure.
[0025]
<Part code = '×××'>
<Mass />
<Lead />
</ Parts>
FIG. 9 shows the details inside the connection module 44. In the module 44, a data input screen is displayed on the terminal 24, and a value input by the user is reflected on the skeleton 34 as data. In the example described above, the user is a person in charge of the company that delivered the parts used in the product. For this reason, it is necessary to instruct the user to input data when the mediation unit 36 requests the connection module 44 to collect data. The connection module 44 uses the mail distribution unit 60 to notify the user of an input instruction by distributing mail to the user through the mail server 26. A mail URL address for inputting data is described in the mail, and the user accesses the address from the terminal to display an input screen.
[0026]
Specifically, the mediation unit 36 sends XML data to the control unit 72 and issues a data collection request. In response to the data collection request, the control unit 72 issues a request code and stores it in the input request code database 70. The request code indicates which tag portion of which skeleton is input when the user inputs data. As shown in FIG. 10, the input request code database 70 has a request code, a skeleton file name, and a path to a tag as a column. The control unit 72 sends XML data and a request code to the mail distribution unit 60.
[0027]
The mail delivery unit 60 has an address table 62 as one of the access method description files, and acquires the address of the contact corresponding to the XML data. FIG. 11 shows details of the address table 62.
[0028]
The mail distribution unit 60 distributes an email requesting to input data by accessing a predetermined Web address to the acquired address. Here, the person-in-charge ID, password, and request code are described in the mail. When receiving the mail, the user accesses an address on the Web from the terminal.
[0029]
FIG. 12 shows an example of a login screen on the Web. The person-in-charge ID, password, and request code are entered on the screen. When the terminal 24 accesses the application server 28 indicated by the address, the application server 28 activates the input screen generation unit 64 to generate an input screen. At this time, the ID, password, and request code entered on the login screen are passed to the input screen generator 64. The input screen generation unit 64 requests the control unit 72 for a skeleton corresponding to the request code. The control unit 72 searches the input request code database 70 (FIG. 10), and acquires a skeleton and a path corresponding to the request code. The control unit 72 requests the intermediary unit 36 for XML data having a predetermined structure or less of the corresponding skeleton. The mediation unit 36 reads the skeleton from the XML database 38, returns XML data below the corresponding component tag, and finally returns it to the input screen generation unit 64 via the control unit 72.
[0030]
The input screen generation unit 64 reads the input item table 66 which is one of the XML data and the access method description file, and generates an input screen. FIG. 13 shows details of the input item table 66. The table consists of four columns: path, parameter, comment, and display. FIG. 14 shows a mechanism for generating an input screen from the XML data 34 b and the input item table 66. The HTML file 64a is generated and displayed on the terminal as a screen.
[0031]
The input screen generation unit 64 reads the XML data 34 b and checks whether the tag is in the input item table 66. If the tag exists in the input item table 66, it is checked whether or not it is a display item. In the case of a display item, using the value of the comment and tag,
<TR><TD> Comment </ TD><TD> The tag value </ TD></TR> is described in the HTML file. If it is not a display item, use the comment and parameter values,
<TR><TD> Comment </ TD><TD><INPUT NAME = 'parameter'/></TD></TR>
Is described in the HTML file. By executing the above operation for all the tags, the HTML file is finally completed.
[0032]
FIG. 15 shows a screen displayed on the terminal 24 by the HTML file 64a.
[0033]
FIG. 16 shows a mechanism for reflecting data input by the user in response to the input screen in the XML data 34b. Data input from the terminal 24 is sent to the parameter analysis unit 68 via the application server 28 as a parameter list 24a. A request code is also described in the parameter list 24a. The parameter analysis unit 68 requests the XML data 34b below the structure indicated by the part code of the skeleton indicated by the request code to the mediation unit 36 through the control unit 72. The analysis unit 68 reads the XML data 34 b and checks whether the tag is in the input item table 66. If the tag exists in the input item table 66 and is not a display item, the parameter name weight and Pb are acquired, the corresponding parameter name values 13579011 and 40 are acquired from the parameter list 24a, and the XML data is used as the tag value. Write to 34b.
[0034]
When the connection module 44 completes the writing of the data to the XML data 34b, the connection module 44 returns the XML data 34b to the mediation unit 36. The following is the same as the case of the product tag. When the XML data is returned from the connection module 44, the mediation unit 36 checks the grammatical structure, and if there is no problem, the mediation unit 36 overwrites a part of the skeleton stored in the XML database 38 with the XML data 34b. Thereby, the data input / collection from the terminal 24 by the connection module 44 is completed.
[0035]
The mediation unit 36 checks whether or not all predetermined data (values) are written in the skeleton. When each connection module collects necessary data and the writing to the skeleton is completed, the skeleton status tag (see FIG. 3) is completed, and the processing unit 32 is notified of the completion of data collection. Upon receiving the notification, the processing unit 32 issues a skeleton read command to the mediation unit 36, and data collection is completed. Note that the processing unit 32 can inquire of the mediation unit 36 about the skeleton state at an arbitrary timing. The mediation unit 36 returns the value of the skeleton status tag. Further, the processing unit 32 can issue a skeleton read command at an arbitrary timing to interrupt the data collection process.
[0036]
FIG. 17 shows a flowchart of the first embodiment.
[0037]
In step S <b> 12, the processing unit 32 passes the skeleton 34 for data collection to the mediation unit 36 and issues an investigation start command to the mediation unit 36.
[0038]
In step S14, the mediation unit 36 sequentially checks the tags of the skeleton 34 and activates the connection module corresponding to the tag.
[0039]
If the tag is a product, the XML data 34a below the tag is passed to the connection module 42 in step S16.
[0040]
In step S 18, the connection module 42 reads the access method description file 48 a from the access method description file storage 48.
[0041]
In step S20, the connection module 42 generates a query language 52 for the database 22 from the XML data 34a and the access method description file 48a.
[0042]
In step S22, an inquiry is made to the database 22, and a value is inserted into a corresponding portion of the XML data 34a based on the obtained search result. When the connection module 42 completes the writing of the data to the XML data 34a, the connection module 42 returns the XML data 34a to the mediation unit 36.
[0043]
In step S24, the mediation unit 36 overwrites part of the skeleton stored in the XML database 38 with the XML data 34a.
[0044]
In step S26, it is determined whether or not there is a next tag. If there is a next tag, the process returns to step S14, the next tag is checked, and a connection module corresponding to the tag is activated.
[0045]
If the tag is a component, the XML data 34b below the tag is passed to the connection module 44 in step S30.
[0046]
In step S <b> 32, the connection module 44 issues a request code and stores it in the input request code database 70.
[0047]
In step S34, the connection module 44 refers to the address table 62 and distributes an email requesting that the person in charge of the company that has delivered the parts to access a predetermined Web address and input data.
[0048]
When the user accesses this Web address, an input screen is generated in step S36.
[0049]
When the user inputs data to this input screen, after the input data is reflected in the XML data 34b in step S38, the XML data 34b is returned to the mediation unit 36. Thereafter, the process proceeds to step S24.
[0050]
If it is determined in step S26 that all tag values have been collected, the intermediary unit 36 completes the skeleton status tag in step S28 and notifies the processing unit 32 of the completion of data collection.
[0051]
As described above, according to the first embodiment, a data processing program for processing data collected from an information source has a semantic structure of data to be collected and a method for accessing the information source of the data to be collected. It is described separately, and data is collected from the information source according to the description of the semantic structure and the description of the access method.
[0052]
For this reason, even when the information source form is changed, only the description of the access method and the connection module corresponding thereto need be changed. Alternatively, only the description of the access method needs to be changed. Application programs for data processing need only be designed depending on the semantic structure of the data, and are not affected by changes in the information source.
[0053]
The data processing device generates a description for acquiring necessary data from the information source according to the description of the semantic structure and the description of the access method.
[0054]
For this reason, the connection module can be divided into a function for converting a description of a semantic structure and a description of an access method into a description of data acquisition and a function of acquiring data according to the description of data acquisition. If the description of data acquisition after conversion is a standard structured query language (SQL or the like), the function of acquiring data can use the existing search function as it is, and only the conversion function of the description needs to be developed.
[0055]
When collecting a plurality of data, the data processing apparatus describes the semantic structure description of the data to be collected as one structured document, and reads the semantic structure description of one data of the structured document. The necessary data is acquired based on the description of the access method to the information source corresponding to the structure, and the structured document is updated based on the acquired data.
[0056]
The information source is a database, the description of the access method indicates mapping data between individual elements of the data and the database table, and the description for obtaining necessary data from the information source is a structured query language.
[0057]
Therefore, the application program can be designed without being aware of the table structure of the database. When changing the information source to another database, it is only necessary to change the mapping data. For information sources that access the database, only mapping data need be defined, and the conversion function can be used in common.
[0058]
The information source is the data entered by the user from the terminal, and the access method description defines the comments, parameter names, and input restrictions for creating the input text box for each element of the data. The description for acquiring data is an HTML document for displaying an input screen by combining predetermined comments, parameter names, and input restrictions based on the description of the semantic structure of the data.
[0059]
For this reason, the application program does not have to separately implement an input screen or a function for analyzing a value input in a form. An input FORM can be created flexibly by combining appropriate required comments, parameter names, and input screens according to the required data items, and a description of the access method for changing comment text and input conditions. Just change the
The description of the access method includes the user ID, password, and e-mail address of the person who enters the data, reads the structured document, issues an identification code for the input request, and gives the user ID, password, and input to the user corresponding to the data When the user accesses the homepage and inputs the user ID, password, and identification code, the structured document corresponding to the identification code is read, Check ID and password.
[0060]
For this reason, when there are a plurality of skeletons that request data input to different users, the correspondence between the user and the skeleton and access control can be performed.
[0061]
Second embodiment
FIG. 18 is a block diagram of a data processing apparatus according to the second embodiment. In the first embodiment, all the information sources are directly connected to the data processing apparatus. However, in the second embodiment, the module 44 to which the terminal 24 is connected and the access method description file 48 are provided for security safety. Configured in separate presentation units and provided a firewall between them. That is, the connection module 44 is arranged in the presentation unit 72 outside the company. The external presentation unit 72 also includes a mediation unit 74 and an XML database 76, and the mediation unit 74 is connected to the mediation unit 74 and the XML database 76. The in-house presentation unit 30 includes a connection module 78 instead of the connection module 44 of the first embodiment, and the connection module 78 is connected to the mediation unit 74 and the XML database 76 in the external presentation unit 72 via a firewall 80. The
[0062]
When the tag is a product, the mediation unit 36 activates the connection module 42 as in the first embodiment, and activates the connection module 78 if the tag is a component. When the connection module 78 receives the XML data (34b in FIG. 3) for instructing data collection regarding the part from the mediation unit 36, the connection module 78 stores it in the XML database 76 outside the company. At the same time, the external mediation unit 74 is notified of the path to the XML data stored in the XML database 76.
[0063]
Upon receiving the notification from the connection module 78, the mediation unit 74 reads XML data corresponding to the path from the XML database 76 and passes it to the connection module 44. The subsequent operation of the connection module 44 is the same as that of the first embodiment.
[0064]
The connection module 44 finally passes the XML data in which the data has been written to the mediation unit 74, and the mediation unit 74 stores the XML data in the XML database 76. The connection module 78 periodically checks the XML data in the XML database 76 to check whether all data is written in the XML data. When all the data has been written, the XML data is read and passed to the mediation unit 36. Subsequent operations of the mediation unit 36 are the same as those in the first embodiment.
[0065]
In FIG. 18, a firewall 80 exists between the connection module 78 and the XML database 76, and it is possible to access the database 76 from the module 78, but it is impossible to access the connection module 78 from the database 76. It is set. Similarly, there is a firewall 80 between the connection module 78 and the mediation unit 74, and only access from the connection module 78 is possible. As a result, the connection module 78 can go through the firewall 80 and instruct the mediation unit 74 to collect data and read the collected data. I can't do it.
[0066]
As described above, according to the second embodiment, in addition to the operation of the first embodiment, a function of separating a specific description of one structured document as another structured document is further provided. Here, it is possible to refer to one structured document from one structured document, but it is impossible to refer to one structured document from another structured document.
[0067]
For this reason, the structure of the skeleton which can be accessed by a specific connection module can be restricted. For example, in the case of a skeleton that collects data from an internal information source and an external information source, prepare an external information source sub-skeleton, and place the sub-skeleton and the connection module outside the firewall, so that the external module Can be prevented from accessing the corporate network.
[0068]
Modified example
The present invention is not limited to the embodiment described above, and can be implemented with various modifications. For example, in the above description, the connection module to the mail server 2626 and the connection module to the terminal 24 via the application server 28 are integrated, but they may be separated.
[0069]
The present invention can also be implemented as a computer-readable recording medium that records a program for causing a computer to execute predetermined means.
[0070]
【The invention's effect】
As described above, according to the present invention, when processing data collected from an information source, it is possible to provide a data processing program, a data processing device, and a data processing method that can flexibly cope with a change in the form of the information source. .
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a first embodiment of a data processing apparatus according to the present invention.
FIG. 2 is a block diagram showing a configuration of a presentation unit in FIG.
FIG. 3 is a diagram showing an example of a skeleton used in the first embodiment.
4 is a diagram showing a module correspondence table of FIG. 2;
5 is a diagram showing the configuration of the database in FIG.
6 is a diagram showing an example of an access method description file in FIG. 2. FIG.
FIG. 7 is a diagram showing a mechanism for generating a query language for a database from a skeleton and an access method description file.
FIG. 8 is a diagram showing a mechanism for reflecting a database search result in a skeleton.
9 is a diagram showing a configuration of the connection module 44 in FIG. 2;
10 is a diagram showing a configuration of a request code database in FIG. 9;
11 is a diagram showing the configuration of the address table in FIG. 9;
FIG. 12 is a diagram showing a login screen when a user inputs data.
13 is a diagram showing a configuration of an input item table in FIG. 9;
FIG. 14 is a diagram showing a mechanism for generating an input screen from a skeleton and an input item table.
FIG. 15 is a diagram showing an example of an input screen displayed on the terminal.
FIG. 16 is a diagram showing a mechanism for reflecting data input by a user on a skeleton.
FIG. 17 is a flowchart showing the operation of the first embodiment.
FIG. 18 is a block diagram showing the configuration of a second embodiment of the data processing apparatus according to the present invention;
FIG. 19 is a block diagram showing a configuration of a conventional example of a data processing apparatus.
[Explanation of symbols]
22 ... Database
24 ... terminal
28 ... AP server
30 ... presentation section
32. Processing unit
34 ... Skeleton
36 ... Intermediary Department
38 ... XML database
40 ... Module correspondence table
42, 44 ... connection module
48 ... Access method description file storage

Claims (7)

In a data processing program in a computer that collects data from a plurality of information sources through a common presentation unit,
Said presentation unit arbitration unit 420 receives a skeleton that describes the structure of the data to be collected in a markup language, which is connected to a plurality of information sources, the information source types to a plurality of that runs on the basis of the access method according A connection module;
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing program includes a computer,
Means for supplying a skeleton corresponding to data to be collected to the mediation unit;
Means for selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Means for supplying said skeleton to a selected connection module and collecting information from an information source;
Data processing program to make it function. The computer,
The data processing program according to claim 1, further functioning as means for storing the collected data in the skeleton. The presentation unit further comprises a storage for storing an access method description file,
Supplying the skeleton to a selected connection module and causing the computer to function as a means of collecting information from an information source;
The data processing program according to claim 1, further comprising: supplying the skeleton together with an access method description file corresponding to the selected connection module and collecting information from an information source. The information source is a database;
The access method description file corresponding to the database includes a search condition,
If the computer supplies the skeleton to a selected connection module and functions as means for collecting information from an information source, if the tag in the skeleton is the search condition, a structured query including the search condition is provided. 4. The data processing program according to claim 3, comprising supplying a language to a database. The information source is a mail server,
The access method description file corresponding to the mail server includes an address table;
Supplying the skeleton to a selected connection module and causing the computer to function as means for collecting information from an information source includes transmitting a data input request mail with reference to the address table. A data processing program according to claim 3. In a data processing apparatus that collects data from a plurality of information sources through a common presentation unit,
Said presentation unit arbitration unit 420 receives a skeleton that describes the structure of the data to be collected in a markup language, which is connected to a plurality of information sources, the information source types to a plurality of that runs on the basis of the access method according A connection module;
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing device includes:
Means for supplying a skeleton corresponding to data to be collected to the mediation unit;
Means for selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Means for supplying said skeleton to a selected connection module and collecting information from an information source;
A data processing apparatus comprising: In a data processing method for collecting data from a plurality of information sources through a common presentation unit,
Said presentation unit arbitration unit 420 receives a skeleton that describes the structure of the data to be collected in a markup language, which is connected to a plurality of information sources, the information source types to a plurality of that runs on the basis of the access method according A connection module;
A module correspondence table describing the correspondence between tags in the skeleton and connection modules;
The data processing method includes:
Supplying a skeleton corresponding to data to be collected to the mediation unit;
Selecting a connection module corresponding to a tag in the skeleton with reference to the module correspondence table;
Supplying the skeleton to a selected connection module and collecting information from an information source;
A data processing method comprising:

Images