JP2011221682A - Information processor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily analyze an error factor by recording data whose failure has been generated or error information or the like according to various uploaded data formats when the equipment type of each terminal equipment or an loaded OS or the like is different.SOLUTION: This information processor is provided with: a reception part 21 for receiving XML format data; a determination part 22 for determining whether or not the XML format data are proper, and for determining whether or not the XML format data are transmittable; and a table storage part 23 for, when it is determined that the XML format data are not proper, or not transmittable, storing records specifying the XML format data in a log table 31a, and for storing records based on a master element in a record table 31b for every master element, and for storing records based on a slave element in an element table 31c for every slave element in association with the master element.

Description

  The present invention relates to an information processing apparatus that receives data and transmits it via a predetermined interface.

  2. Description of the Related Art Conventionally, there is an information processing apparatus that receives information uploaded from a plurality of clients at a server and transfers each received information to another server. In this information processing apparatus, when the transfer to another server cannot be executed due to a malfunction or the like, the error information is recorded. Then, after grasping and dealing with the cause of the error, the transfer is executed again to another server. For example, the gateway server described in Patent Document 1 receives a data file uploaded from an arbitrary terminal device, converts the format of the data file, and registers it in another server. At this time, if registration to another server cannot be executed, an error log is generated.

JP 2006-277586 A

  However, as described in Patent Document 1, when information uploaded from a plurality of terminal devices is received by a server, the information is uploaded if the device type of each terminal device or the installed OS is different. The data format to be used is different for each terminal device. For this reason, if transfer to another server could not be executed due to a problem, etc., it would be necessary to record the data in which the problem occurred, error information, etc. according to various data formats. Problems arise in terms of quality.

  SUMMARY An advantage of some aspects of the invention is to solve at least a part of the problems described above, and the invention can be implemented as the following forms or application examples.

  Application Example 1 A receiving unit that receives data in XML format, and determines whether the received XML format data is appropriate, and transmits transmission data based on the XML format data via a predetermined interface. A determination unit that determines whether or not the received XML format data can be transmitted, and when the received XML format data is determined to be inappropriate or when it is determined that the transmission data cannot be transmitted, the received XML format data In the first table, a record based on the parent element is stored in the second table for each parent element with respect to the elements in the parent-child relationship included in the received XML format data. A table storage unit that stores a record based on a child element in a third table in association with the parent element for each child element; The information processing apparatus according to claim.

According to the information processing apparatus described above, the determination unit determines whether or not the received XML format data is appropriate, and determines whether or not transmission is possible. When it is determined that the XML format data is not appropriate or cannot be transmitted and an error occurs, the table storage unit stores a record specifying the XML format data in the first table, and records based on the parent element. Each parent element is stored in the second table, and a record based on the child element is associated with the parent element and stored in the third table for each child element.
When an error occurs, a record based on the parent element of the XML format data is stored for each parent element, and a record based on the child element is stored in association with the parent element for each child element. As a result, even when the device type of the terminal device that transmits data and the installed OS, etc. are different, the common program is used to perform data processing on the failed data, error information, etc. Data can be referenced and used efficiently. Moreover, by using a common program, the cost of program development can be suppressed and quality can be improved.

  Application Example 2 The information processing apparatus, wherein the table storage unit stores information on a determination result in the determination unit in the first table.

  According to the information processing apparatus described above, by storing the determination result information in the first table, the cause of the error can be grasped and dealt with based on the determination result information.

  Application Example 3 The table storage unit identifies the received XML format data even when the received XML format data is determined to be appropriate and the transmission data is determined to be transmitted. The information processing apparatus is characterized in that a record to be stored is stored in the first table.

  According to the information processing apparatus described above, when it is determined that the data in the XML format is appropriate and can be transmitted, the record specifying the data in the XML format is stored in the first table. As a result, a history of XML format data that can be normally transmitted can be left.

  Application Example 4 In the information processing, the table storage unit stores a record specifying the received data in the XML format in the first table for each piece of determination result information in the determination unit. apparatus.

  According to the information processing apparatus described above, by storing a record specifying XML format data in the first table for each piece of determination result information, it is possible to easily analyze a factor when there are a plurality of error factors. it can.

The figure which shows schematic structure of the information processing system which concerns on this embodiment. The figure which shows the function structure in an application server. The figure which shows the example of the data of the XML format uploaded from client PC. A table showing a log table constituting log information. A table showing a record table constituting log information. A table showing an element table constituting log information. The flowchart which shows the operation | movement which concerns on an application server. The figure which shows the example of the data of the XML format in a modification.

  Hereinafter, an example of the information processing apparatus according to the present embodiment will be described with reference to the drawings.

<Schematic configuration of information processing system>
FIG. 1 is a diagram illustrating a schematic configuration of an information processing system according to the present embodiment. As shown in FIG. 1, the information processing system 10 includes a firewall (FW) 11, an application server 13 as an information processing apparatus, a management database server 16, a product database server 18, and the like.

  A plurality of client PCs 50 are connected to the information processing system 10 via a network 80 such as the Internet and an intranet, and various devices 51 are connected to each client PC 50. In the example of FIG. 1, client PCs 50A, 50B, and 50C for product A, B, and C are connected, and a printer 51A, a printer 51B, and a scanner 51C are connected to these client PCs 50A, 50B, and 50C, respectively. It is connected. Each client PC 50 can convert information on the devices 51 connected thereto, for example, information on consumables and troubles, into XML format data and upload it to the information processing system 10 via the network 80.

  Each application server 13 in the information processing system 10 is arranged in a DMZ (demilitarized zone) 12 through a firewall 11. The management database server 16 includes a management database 17 and is disposed in a secure (secure zone) 15 via the firewall 11. The product database server 18 includes a product database 19 and is connected to an information bus B10 as a predetermined interface. In the example of FIG. 1, database servers 18A, 18B, and 18C for product A, B, and C are connected, and these database servers 18A, 18B, and 18C respectively connect product databases 19A, 19B, and 19C. I have. As described above, the information processing system 10 is secured by the firewall 11, DMZ 12, and Secure 15.

  The application server 13 receives XML format data uploaded from each client PC 50 via the network 80. Then, it is determined whether the uploaded data is appropriate and whether it can be transmitted to the product database server 18 via the information bus B10, and information on the determination result is transmitted to the management database server 16. To do. If it is determined that the uploaded XML data is appropriate and can be transmitted to the product database server 18, transmission data based on the uploaded data is transmitted to the corresponding product database server 19. .

The management database server 16 receives the determination result information and the like transmitted from the application server 13 and stores them in the management database 17. In addition, various data stored in the management database 17 are read and searched.
The product database server 18 receives the transmission data transmitted from the application server 13 and stores it in the product database 19. Further, the data stored in the product database 19 is read and searched. Here, as the management database 17 and the product database 19, for example, a relational database can be used. Each product database 19 has a database structure constructed in accordance with the requirements of various products.

<Functional configuration of application server>
Next, a functional configuration in the application server 13 will be described. FIG. 2 is a diagram illustrating a functional configuration in the application server 13. As shown in the figure, the application server 13 includes a reception unit 21, a determination unit 22, a table storage unit 23, a product data storage unit 24, and the like. The application server 13 can access the management database 17 via the management database server 16 and can access each product database 19 via each product database server 18.

  The receiving unit 21 receives XML format data uploaded from each client PC 50 via the network 80. FIG. 3 shows an example of XML format data uploaded from the client PC 50. The XML format data shown in the figure is divided into two parts, a “Header” element h110 and a “Body” element b110. The first “Header” element h110 is an identification of data uploaded from the client PC 50, and the next “Body” element b110 is a data body uploaded from the client PC 50.

A “ServiceCode” element h111 included in the “Header” element h110 indicates the product identification of the uploaded client PC 50. The “AgentCode” element h112 indicates the identification of the client PC 50. The “DeviceCode” element h113 indicates the identification of the device 51 connected to the client PC 50. A “Date” element h <b> 114 and a “LocalDate” element h <b> 115 indicate times uploaded from the client PC 50.
On the other hand, the “Body” element b110 is composed of elements that are in a parent-child relationship between the “Record” elements b120, b130, b140, and b150 that are parent elements and the child element groups b121, b131, b141, and b151. The
As shown in the element name in the lower position of the “LocalDate” element h115 included in the “Header” element h110, the client PC 50 accepts input of a user ID and password and option selection, and these input values are converted into XML. The update may be included in the format data.

The determination unit 22 analyzes the XML format data uploaded from the client PC 50 and received by the reception unit 21, and determines whether or not the XML format data is appropriate. Then, when the data in the XML format is appropriate, it is determined whether the data in the XML format or the data converted from the data can be transmitted as transmission data to the product database server 18 via the information bus B10.
Here, as a case where it is determined that the data in the XML format is not appropriate, for example, when the contents of the “ServiceCode” element h111, the “AgentCode” element h112, and the “DeviceCode” element h113 do not correspond, that is, in the XML format There is a case where the identification of the product indicated by the data, the identification of the client PC 50 and the identification of the device 51 are not registered as data in the information processing system 10. Also, if there is an error in the XML data description, it is determined that the data in the XML format is not appropriate.
Next, as a case where XML format data or the like cannot be transmitted via the information bus B10, for example, when an abnormality occurs in the information bus B10, or when the destination product database server 18 determines that the data cannot be stored. Can be given.

The table storage unit 23 stores the log information 31 for each product in the management database 17 via the management database server 16 based on the determination result in the determination unit 22. Note that the table types and data contents constituting the log information 31 differ depending on the determination result in the determination unit 22.
If the determination unit 22 determines that the XML format data is not appropriate or cannot be transmitted via the information bus B10 even when determined to be appropriate, as shown in the management database 17 of FIG. The log information 31 includes a log table 31a as a first table, a record table 31b as a second table, and an element table 31c as a third table.
On the other hand, when the determination unit 22 determines that the data in the XML format is appropriate and can be transmitted via the information bus B10, the log information 31 includes only the log table 31a.

  4 to 6 are tables showing each table constituting the log information 31 at the time of error. 4 shows the log table 31a, FIG. 5 shows the record table 31b, and FIG. 6 shows the element table 31c. Each table is generated and stored for each upload unit based on the XML format data shown in FIG.

As shown in FIG. 4, the log table 31a includes items of upload_id, log_message, service_code, agent_code, device_code, and upload_date, and one record is generated and stored. In the item of upload_id, the ID of the log information 31 numbered in units of upload is set. In the log_message item, information of a determination result in the determination unit 22 is set. In the example of FIG. 4, the message “Service code TEST_SERVICE is not found” is set, which indicates an error because the content of the uploaded “ServiceCode” element h111 does not correspond. In the items of service_code, agent_code, device_code, and upload_date, the contents of the “ServiceCode” element h111, “AgentCode” element h112, “DeviceCode” element h113, and “Date” element h114 of the XML format data in FIG. 3 are set, respectively.
On the other hand, if the determination unit 22 determines that the data in the XML format is appropriate and can be transmitted via the information bus B10, it indicates that the data is normally stored in the log_message of the log table 31a shown in FIG. A message is set and only the log table 31a is stored. That is, neither the record table 31b nor the element table 31c is stored.

  Next, as shown in FIG. 5, the record table 31b is composed of items of upload_id, record_id, and table_name, and a record is generated and stored for each parent element. In the item of upload_id, the upload_id of the log table 31a is set, and the record table 31b and the log table 31a are associated with each other. In the record_id item, a number assigned to each parent element is set. In the table_name item, the contents of “Record” elements b120, b130, b140, and b150 which are the parent elements in FIG. 3 are set.

  Next, as shown in FIG. 6, the element table 31c is composed of items of upload_id, record_id, element_id, column_name, and value, and a record is generated and stored for each child element. The upload_id and record_id are set with the upload_id of the log table 31a and the record_id of the record table 31b, and the parent-child relationship between the child element in the element table 31c and the parent element in the record table 31b is associated. In the element_id item, a number assigned to each child element belonging to each parent element is set. In the column_name and value items, the element names and contents of the child elements in the child element groups b121, b131, b141, and b151 in FIG. 3 are set.

  When the determination unit 22 determines that the XML format data is appropriate and can be transmitted via the information bus B10, the product data storage unit 24 stores the XML format data uploaded from the client PC 50 or the data. The transmission data to be converted data is transmitted to the corresponding product database server 18 and stored as product data 41 in the product database 19 shown in FIG.

Next, operations related to the application server 13 will be described.
FIG. 7 is a flowchart showing an operation related to the application server 13.

  First, the client PC 50 uploads XML format data to the information processing system 10 via the network 80 (step S110). Then, in the information processing system 10, the application server 13 receives the XML format data uploaded from the client PC 50 by the receiving unit 21 (step S120).

  Next, the application server 13 uses the determination unit 22 to analyze the XML format data received in step S120 to determine whether the XML format data is appropriate, and further, for the product via the information bus B10. It is determined whether or not transmission to the database server 18 is possible (step S130).

  When it is determined that the XML format data is appropriate and can be transmitted to the product database server 18 (step S130: Yes), the table storage unit 23 manages the log table 31a indicating that the data has been stored normally. (Step S140). Then, the product data storage unit 24 stores the data in the XML format received in step S120 or the transmission data that is converted from the data in the product database 19 (step S150), and the operation of the flowchart of FIG. .

  On the other hand, when it is determined in step S130 that the data in the XML format is not appropriate or cannot be transmitted to the product database server 18 (step S130: No), the application server 13 is in error by the table storage unit 23. Is stored in the management database 17 (step S160). Then, a record table 31b composed of parent elements is stored in the management database 17 (step S170), and subsequently an element table 31c composed of child elements is stored (step S180), and the operation of the flowchart of FIG. Exit.

  In the above-described embodiment, XML format data uploaded from each client PC 50 is received and an error is determined, and in the event of an error, the log database 31a, the record table 31b, and the element table 31c are stored in the management database 17. The log information 31 to be configured is stored. At this time, the record table 31b stores a record for each parent element, and the element table 31c stores a record for each child element, and the parent-child relationship is associated with each other. As a result, even if the device type of each client PC 50, the installed OS, etc. are different, the log information 31 can be generated and stored by a program common to each client PC 50 in the event of an error. Moreover, even if the received XML format data has various hierarchical structures and the number of elements, it can be stored in a unified format using the record table 31b and the element table 31c in which the parent-child relationship is associated. Thus, it is possible to efficiently cope with error factor analysis and error data recovery.

(Modification 1)
In the above-described embodiment, XML format data as shown in FIG. 3 is received from each client PC 50. However, in each client PC 50, the XML format data may be dealt with by encryption or digital signature as shown in FIG. In this case, if the signature content of the XML format data is not authenticated by the determination unit 22, it is determined that the XML format data is not appropriate.

(Modification 2)
In the above-described embodiment, one record is generated and stored for each upload unit of the log table 31a constituting the log information 31. However, when a plurality of error factors occur in the determination unit 22, a record may be generated for each of these error factors and stored in the log table 31a. By generating a record for each error factor, for example, each error factor can be dealt with, or each error factor can be sorted and analyzed.

  DESCRIPTION OF SYMBOLS 10 ... Information processing system, 11 ... Firewall, 12 ... DMZ, 13 ... Application server, 15 ... Secure, 16 ... Management database server, 17 ... Management database, 18 ... Product database server, 19 ... Product database, 21 ... Receiving unit, 22 ... Determining unit, 23 ... Table storage unit, 24 ... Product data storage unit, 31 ... Log information, 31a ... Log table, 31b ... Record table, 31c ... Element table, 41 ... Product data, 50 ... Client PC, 51 ... device, 80 ... network, B10 ... information bus.

Claims (4)

A receiving unit for receiving data in XML format;
A determination unit that determines whether or not the received XML format data is appropriate and determines whether or not transmission data based on the XML format data can be transmitted via a predetermined interface;
When it is determined that the received XML format data is not appropriate, or when it is determined that the transmission data cannot be transmitted,
A record for specifying the received XML format data is stored in the first table, and a record based on a parent element is stored for each parent element in the parent-child relationship included in the received XML format data. And a table storage unit that stores a record based on a child element in a third table in association with the parent element and stores the child element in a third table.   The information processing apparatus according to claim 1, wherein the table storage unit stores information on a determination result in the determination unit in the first table.   The table storage unit also stores a record that specifies the received XML format data even when it is determined that the received XML format data is appropriate and the transmission data can be transmitted. The information processing apparatus according to claim 2, wherein the information processing apparatus is stored in one table.   The said table storage part stores the record which specifies the said data of the received XML format in a said 1st table for every information of the determination result in the said determination part, The Claim 2 or 3 characterized by the above-mentioned. Information processing device.

Images