JP2007265197A - Data conversion apparatus, data conversion method, and data conversion program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To cooperate legacy systems where used data formats are different. <P>SOLUTION: A data conversion apparatus 1 comprises an XML (extensible markup language) conversion section 20 that refers to format definition XML data 14s obtained by defining the data format of legacy data 26 used in a legacy system 2 of a transmission origin with the XML and converts the legacy data 26 of the transmission origin into XML data 29. The data conversion apparatus 1 also comprises a legacy data conversion section 23 that refers to format definition XML data 14r obtained by defining the data format of legacy data 30 used in a legacy system 3 of a receiving destination with the XML and converts the XML data 29 converted from the legacy data 26 of the transmission origin into the data format used in the legacy system 3 of the receiving destination. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  A data conversion apparatus, a data conversion method, and a data conversion program according to the present invention include a data conversion apparatus, a data conversion method, and a data conversion that mutually transmit data between data processing apparatuses having different data formats or conversion protocols. In particular, the present invention relates to a data conversion apparatus, a data conversion method, and a data conversion program that link legacy systems.

For example, in a data conversion apparatus, a data conversion method, and a data conversion program for cooperating with a legacy system (hereinafter referred to as a legacy system) such as a host-centralized architecture system, generally, data ( hereinafter, the format of data transmitted from the legacy data) is defined as meta data into open data format, such as XML (E x tensible M arkup L anguage) based thereon.

  Here, the legacy data is data in which metadata such as format definition is not included in the data. A legacy system is a system that communicates with legacy data.

  When the legacy system uses legacy data, it is used by referring to data related to the format definition stored separately from the legacy data in addition to the legacy data.

As an example of such a data conversion processing program, for example, in Patent Document 1, metadata of a data format definition of a legacy system is set as a format definition XML, converted into XML data based on the format definition XML, and used in an open system. Techniques to do this are disclosed.
JP 2004-318420 A

  Since the above-described data conversion device, data conversion method, and data conversion program are programs for cooperation between legacy systems and open systems, they may not be used as data format conversion programs for cooperation between legacy systems. It was a challenge.

  In addition, since the format definition must be created in XML, there is a problem that it takes time to create the format definition.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and a data conversion apparatus, a data conversion method, and a data conversion program capable of easily linking legacy systems with different data formats to be used than before. The purpose is to provide.

  In order to solve the above-described problem, the data conversion apparatus according to the present invention refers to the format definition XML data in which the data format of the legacy data used in the legacy system of the transmission source is defined in XML as described in claim 1. XML data conversion means for converting the legacy data of the transmission source into XML data, and a format definition XML data in which the data format of the legacy data used in the legacy system of the reception destination is defined in XML. And a legacy data conversion means for converting the XML data converted from the legacy data into a data format used in the legacy system of the receiving source.

  In order to solve the above-described problem, the data conversion method according to the present invention converts data in a format corresponding to the system received from the legacy system of the transmission source into XML data as described in claim 10. Legacy / XML conversion processing step, XML / legacy conversion processing step for converting data converted into XML data in the legacy / XML conversion processing step into data of a format corresponding to the legacy system of the receiving destination, and the XML / legacy A reception destination legacy data transmission step of transmitting the data converted in the conversion processing step to a legacy system as a reception destination.

  Furthermore, in order to solve the above-described problem, the data conversion program according to the present invention converts data in a format corresponding to the system received from the transmission source legacy system into XML data as described in claim 15. Legacy / XML conversion processing step, XML / legacy conversion processing step for converting data converted into XML data in the legacy / XML conversion processing step into data of a format corresponding to the legacy system of the receiving destination, and the XML / legacy A computer is caused to execute a data conversion processing procedure including a reception destination legacy data transmission step of transmitting the data converted in the conversion processing step to a legacy system as a reception destination.

  According to the data conversion device, the data conversion method, and the data conversion program according to the present invention, legacy systems that use different data formats can be linked more easily than before.

  The best mode for carrying out a data conversion device, a data conversion method, and a data conversion program according to the present invention will be described below with reference to the drawings.

  FIG. 1 is a schematic diagram showing a configuration of a data conversion apparatus 1 which is an embodiment of a data conversion apparatus according to the present invention.

  The data conversion apparatus 1 can mutually use data having different data formats used in the existing systems (hereinafter referred to as legacy systems) 2 and 3 such as a host-centralized architecture system, for example. Data conversion is performed. That is, data conversion is performed so that data used in the legacy system 2 can be used in the legacy system 3 or data used in the legacy system 3 can be used in the legacy system 2.

  In the data conversion apparatus 1, the data conversion function is realized by the electronic computer 4 reading and executing a data conversion program (hereinafter abbreviated as PG) 5. As a result, the data conversion apparatus 1 receives the data used in the legacy system 2 of the transmission source and converts the data into a data format that can be used in the legacy system 3 of the reception destination, or the legacy system of the transmission source 3 can be received and converted into a data format that can be used by the legacy system 2 of the receiving destination.

  The electronic computer 4 includes an input unit 7 through which a user inputs an operation, a display unit 8 that displays information, and a communication interface unit (hereinafter referred to as communication) that transmits and receives data to and from a plurality of legacy systems such as two. 9), a CPU (Central Processing Unit) 10 for executing arithmetic processing, a memory 11 for storing and storing electronic data during the arithmetic processing, and a recording means 12 for recording and saving electronic data. It comprises.

The recording means 12, the data conversion PG5, format definition XML (E x tensible M arkup L anguage) file 14, the code conversion definition XSL (E x tensible S tylesheet L anguage) files 15 and the format conversion definition XSL file 16 is saved The CPU 10 executes the data conversion PG 5 and can refer to the format definition XML file 14, the code conversion definition XSL file 15, and the format conversion definition XSL file 16 as necessary.

  Further, in the recording unit 12, for example, electronic data for code conversion (code conversion data) such as the code conversion table 17 referred to by the CPU 10 at the time of code conversion is appropriately stored as necessary.

  The format definition XML file 14, the code conversion definition XSL file 15, and the format conversion definition XSL file 16 are created in advance based on the data of the legacy systems 2 and 3 (hereinafter referred to as legacy data) that exchange data. The

  Here, the format definition XML is positioned as the metadata of the legacy data of the legacy systems 2 and 3 not including the meta information, and the format definition XML file 14 is the data included in the legacy data to be converted. The XML file defines the size, format, name, and the like as XML tags.

  The code conversion definition XSL file 15 is an XSL file that defines data code conversion rules. The format conversion definition XSL file 16 is an XSL file that defines format conversion rules.

  The CPU 10 refers to the format definition XML file 14 to convert the data format of the legacy data of the legacy systems 2 and 3 defined in the format definition XML file 14 into the XML format.

  Further, the CPU 10 refers to the code conversion definition XSL file 15 to convert the code system of the XML file.

  Furthermore, the CPU 10 refers to the format conversion definition XSL file 16 to convert a format related to a structure such as a repetitive structure or an arrangement order.

  FIG. 2 is a functional block diagram of the data conversion apparatus 1 which is an embodiment of the data conversion apparatus according to the present invention.

  FIG. 2 shows a case where the legacy system 2 is the data transmission side and the legacy system 3 is the data reception side.

  Each function of the data conversion device 1 is realized by the cooperation of the electronic computer 4 and the data conversion PG 5 which are hardware resources. In other words, the electronic computer 4 functions as the data conversion device 1 by executing the data conversion PG5.

  According to FIG. 2, the data conversion apparatus 1 receives data in a data format used in the transmission-side legacy system 2 (hereinafter referred to as transmission-side legacy data), and converts the data into XML data. A code conversion unit 21 that converts the code of the XML data converted by the XML conversion unit 20 as necessary, and a format conversion unit 22 that converts the format of the XML data converted by the XML conversion unit 20 as necessary. A legacy data conversion unit 23 that converts XML data into data in a data format used in the legacy system 3 on the receiving side, and definition data (format definition XML file 14, code conversion definition XSL file based on a user input operation) 15 and / or format conversion definition XSL file 16), New, storage, and includes a definition data editing unit 24 for editing or deletion.

  The XML conversion unit 20 serving as the XML data conversion means refers to a format definition XML file (hereinafter referred to as a transmission side format definition XML file) 14s that defines a legacy data format of the legacy system 2 on the transmission side. The transmission side legacy data 26 received from the legacy system 2 is converted into XML data.

  When receiving the transmission-side legacy data 26 from the legacy system 2, the XML conversion unit 20 converts the received transmission-side legacy data 26 into XML data (hereinafter referred to as 0th-order XML data) 27. The zero-order XML data 27 is transmitted from the XML conversion unit 20 to the code conversion unit 21.

  The code conversion unit 21 as a code conversion unit has a function (code system conversion function) for converting a code system of XML data. The code conversion unit 21 generates an XML file (hereinafter referred to as a primary XML file) 28 obtained by converting the code system of the 0th-order XML data 27 input with reference to the code conversion definition XSL file 15. The primary XML file 28 is transmitted from the code conversion unit 21 to the format conversion unit 22.

  The format conversion unit 22 as a format conversion unit has a function (format conversion function) for converting a format related to a repetitive structure or arrangement order of XML data. The format conversion unit 22 generates an XML file (hereinafter referred to as a secondary XML file) 29 obtained by converting the format related to the structure of the primary XML file 28 input with reference to the format conversion definition XSL file 16. The secondary XML file 29 is transmitted from the format conversion unit 22 to the legacy data conversion unit 23.

  The legacy data conversion unit 23 as a legacy data conversion unit refers to a format definition XML file (hereinafter referred to as a reception side format definition XML file) 14r that defines a legacy data format of the legacy system 3 on the reception side, and generates XML data. Is converted into legacy data (hereinafter referred to as reception side legacy data) 30 used in the legacy system 3.

  When receiving the secondary XML data 29, the legacy data conversion unit 23 refers to the reception-side format definition file 14r, extracts data elements one by one from the received secondary XML data 29, and converts them into the secondary XML data 29. The included metadata is removed and converted to the legacy data 30 on the receiving side. The reception-side legacy data 30 is transmitted from the legacy data conversion unit 23 to the reception-side legacy system 3.

  The definition data editing unit 24 as definition data data editing means provides a user with a GUI (Graphical User Interface) and has a function of editing definition data based on an input operation from the user. The definition data to be edited by the definition data editing unit 24 can be created by using general-purpose software such as a text editor, for example, but the data conversion apparatus 1 provides the user with a GUI so that the user can It simplifies the work of editing definition data and reduces the burden of editing work.

  FIG. 3 is an explanatory diagram for explaining an example of the contents of the format definition XML file 14 visualized by the GUI provided by the definition data editing unit 24 of the data conversion apparatus 1.

  The format definition XML file 14 is created when the definition data editing unit 24 defines the legacy data input to the data conversion apparatus 1 as XML format data based on an input operation from the user.

  More specifically, the format definition XML file 14 defines the data format of legacy data in XML by providing a name column 31, a format column 32, a data length column 33, and an extended attribute column 34 for each data item.

  Here, Bin described in the format column 32 indicates data in binary format, and Str indicates data in string format. Further, JIS in the extended attribute column 34 indicates that the type of character code is JIS code.

  On the other hand, if there is a portion having a loop structure in the data to be defined, a loop column 35 is further provided in the format definition XML file 14 to add a label. A loop label is described in the extended attribute column 34 of an item representing the number of loop repetitions.

  For example, in the case of the format definition XML file 14 shown in FIG. 3, the Cond and Cond2 items defined in the name field 31 have one loop structure, and the loop field 35 is labeled L1. An item representing the number of loop iterations of L1 is the name LoopLen defined in the name field 31, and L1 is described in the extended attribute field 34 of the name LoopLen.

  FIG. 4 is a diagram for explaining an example of a screen for setting the definition of data conversion from the transmission side legacy data 26 visualized by the GUI provided by the definition data editing unit 24 of the data conversion device 1 to the reception side legacy data 30. FIG.

  When the user requests to set the definition of data conversion, the format definition XML data 14s and 14r of the data conversion source (transmission side) and the data conversion destination (reception side) are read, and the definition data editing unit 24, for example, As shown in FIG. 4, the format definition 38 of the transmission side legacy system 2 corresponding to the transmission side format definition XML data 14s is displayed on the left side of the screen, and the reception side corresponding to the reception format definition XML data 14r is displayed on the right side of the screen. The format definition 39 of the legacy system 3 is displayed.

  The definition of data conversion can be performed, for example, by dragging a pointing device such as a mouse, which is an example of the input means 7 included in the electronic computer 4. More specifically, the data conversion definition is set by dragging the data item of the format definition 38 of the data conversion source and the corresponding data item of the format definition 39 of the conversion destination.

  Further, when code or format conversion is required, for example, icons 40 (40a to 40h) for executing necessary code or format conversion are arranged in the central portion displayed as both format definitions 38 and 39. To do. The user can associate the format definition 38 of the conversion source with the format definition 39 of the conversion destination by using the arranged icon 40.

  The icon 40 can be pulled out from a tool box (not shown in FIG. 4) that can be called on the screen shown in FIG. Conversely, unnecessary icons 40 can be stored in the toolbox.

  Here, it supplements about the processing content which each icon 40a-40h shown by FIG. 4 performs.

  The icon “FIX: 7” to which reference numeral 40 a is attached is an icon for executing processing contents for embedding the fixed value 7 in the reception destination legacy data 30.

  The icon “SIZE: OrderNo: #END” to which 40b is attached is an icon for executing processing contents for embedding the data length from the item of OrderNo to the last in the receiving destination legacy data 30.

  The icon “Bin: Str” to which 40c is attached is an icon for executing processing contents for converting binary format data into string format data.

  The icon “DataConv3” to which 40d is attached is an icon for executing processing contents for converting three items in the transmission source legacy data 26 into one item in the reception destination legacy data 30.

  The icon “VarFixConv” to which 40e is attached is an icon for executing processing contents for converting variable-length data into fixed-length data.

  The icon “FixVarConv” to which 40f is attached is an icon for executing processing contents for converting fixed-length data into variable-length data.

  The icon “AddressDiv” to which 40 g is attached is an example for executing processing contents for converting one item in the transmission source legacy data 26 into a plurality of items in the reception destination legacy data 30. This is an icon for executing processing contents for converting one item of an address (Address) into three items of a prefecture (Pref), a municipality (City), and an address (Address) in the destination legacy data 30.

  The icon “CodeConv (Pat)” to which 40h is attached executes the processing content that converts the data code for the PatCode item in the transmission source legacy data 26 to become the data for the PCode item in the reception destination legacy data 30. It is an icon for.

  In code conversion, electronic data such as the code conversion table 17 shown in FIG. 1 is referred to. In the example of the icon 40h, the code conversion unit 21 can read out electronic data necessary for code conversion using Pat as an argument.

  As described above, in the data conversion apparatus 1 configured so that the icons 40a to 40h can be used by the user, data linkage between legacy systems having different data formats of legacy data to be used is more easily realized than before. be able to.

  For example, by selecting the icon 40d and causing the format conversion unit 22 to execute a predetermined process, one item in the transmission source legacy data 26 can be converted into a plurality of items in the reception legacy data 30. A plurality of items in the transmission source legacy data 26 can be converted into one item in the reception destination legacy data 30 by selecting and causing the format conversion unit 22 to execute a predetermined process. Therefore, the data conversion apparatus 1 can be applied even to legacy systems where the correspondence of data items is not 1: 1.

  As another example, by selecting the icon 40h and causing the code conversion unit 21 to execute a predetermined process, the code conversion unit 21 uses electronic data necessary for code conversion using Pat as an argument (for example, the code conversion table 17). ) Can be read for code conversion.

  5-7 is explanatory drawing showing an example of the code conversion table 17 as electronic data required for code conversion.

  More specifically, FIG. 5 is an example of the code conversion table 17 when one-to-one code conversion is performed between the transmission source and the reception destination, and FIG. 6 is a case where a certain numerical range is converted into corresponding data. 7 is an example of the code conversion table 17 in the case where data matching the pattern represented by the regular expression is converted into a corresponding value.

  As in the above example, the code conversion table 17 referred to by the code conversion unit 21 when performing code conversion can take various forms. That is, even between the legacy systems 2 and 3 having different code systems of the transmission source and the reception source, the code conversion unit 21 can perform code conversion according to the code conversion table 17 illustrated in FIGS. it can.

  On the other hand, since the transmission format of the legacy system often gives meaning to the storage position, it is necessary to cope with the legacy system having the transmission format that makes the storage position meaningful.

  FIGS. 8 and 9 show an example of the code conversion table 17 that can be used for a legacy system having a transmission format in which the storage location is meaningful.

  More specifically, FIG. 8 is an example of the code conversion table 17 that defines the order in the loop corresponding to the code when, for example, the loop repeat position has a meaning, and FIG. It is an example of a code conversion table 17 that defines a code and a data item name corresponding to a storage position in a loop.

  A legacy system having a transmission format in which the transmission source legacy system 2 and the reception destination legacy system 3 give meaning to storage locations by referring to an example of the code conversion table 17 shown in FIG. 8 or FIG. Even in the case of 2, 3, the code conversion unit 21 can perform code conversion.

  Furthermore, as another example, by selecting the icon 40b and causing the format conversion unit 22 to execute predetermined processing, data that does not exist in the transmission source legacy data 26 that is the conversion source is included in the range specified by the reception destination legacy data 30. Can be inserted with the specified data length.

  Furthermore, as another example, by selecting the icons 40e and 40f and causing the format conversion unit 22 to execute a predetermined process, it supports legacy systems 2 and 3 that use a transmission format including variable-length data items. can do.

  Next, a data conversion method according to the present invention will be described.

  The data conversion method according to the present invention is executed, for example, when the data conversion apparatus 1 executes a data conversion processing procedure.

  FIG. 10 is an explanatory diagram for explaining the processing contents of the data conversion processing procedure executed by the data conversion apparatus 1 according to the present invention in order.

  As shown in FIG. 10, the data conversion processing procedure (steps S1 to S7) receives data from the transmission source legacy system 2 (in the case of YES in step S1), and a format corresponding to the received transmission source legacy system 2 If the legacy / XML conversion processing step (step S2) for converting the data in step S2 into the XML data and the code conversion definition XSL file 15 exist (YES in step S3), the code conversion definition XSL file 15 is referred to as the legacy. A code conversion processing step (step S4) for converting the code of the data converted into XML data in the / XML conversion processing step, and a format conversion definition XSL file 16 (if YES in step S5), a format conversion definition Referring to XSL file 16, Legacy / XM The format conversion processing step (step S6) for converting the format of the data converted into XML data in the conversion processing step, and the data converted into the XML data in the legacy / XML conversion processing step correspond to the legacy system 3 of the reception destination. XML / legacy conversion processing step (step S7) for converting the data into the format data, and a reception destination legacy data transmission step (step S8) for transmitting the data converted in the XML / legacy conversion processing step to the legacy system 3 as the reception destination; Is provided.

  In executing the data conversion processing procedure, format definition XML files 14s and 14r that define the legacy data formats of the transmission source legacy system 2 and the reception destination legacy system 3 in advance, and the transmission source legacy system 2 and the reception destination legacy system 3 The code conversion definition XSL file 15 and the format conversion definition XSL file 16 are created in accordance with the legacy data format.

  In the data conversion processing procedure, when the processing procedure is started, it is in a state of waiting for reception of data transmitted from the transmission source legacy system 2 in step S1. When the transmission side legacy data 26 is received from the transmission source legacy system 2 (YES in step S1), the process proceeds to step S2, and the XML conversion unit 20 converts the data in the format corresponding to the received transmission source legacy system 2 into XML. Conversion into data (step S2).

  Subsequently, the process proceeds to step S3, and if the code conversion definition XSL file 15 exists (YES in step S3), the process proceeds to step S4, and the code conversion unit 21 refers to the code conversion definition XSL file 15 to read the legacy / The code of the data converted into the XML data in the XML conversion processing step is converted (step S4).

  Subsequently, the process proceeds to step S5, and if the format conversion definition XSL file 16 exists (YES in step S5), the process proceeds to step S6, where the format conversion unit 22 refers to the format conversion definition XSL file 16 and The format of the data converted into the XML data in the XML conversion processing step is converted (step S6).

  In step S7, the legacy data conversion unit 23 converts the data converted into XML data in the legacy / XML conversion processing step (in the case of NO in step S3 and step S5, the 0th-order XML file 27, in step S3). If YES and NO in step S5, the primary XML file 28 is received. If YES in steps S3 and S5, the secondary XML file 29 is received in the format corresponding to the legacy system 3 of the reception destination (reception). Side legacy data) 30 (step S7).

  When the legacy data conversion unit 23 performs the XML / legacy conversion processing step in step S7, the process proceeds to step S8, and the reception-side legacy data 30 is transmitted to the legacy system 3 that is the reception destination (step S8). When the reception-side legacy data 30 is transmitted to the legacy system 3 that is the reception destination, the data conversion processing procedure ends (END).

  On the other hand, when the transmission side legacy data 26 is not received from the transmission source legacy system 2 in step S1 (NO in step S1), the process returns to step S1 and the processing step of step S1 is continued. That is, the reception standby state is continued until the transmission side legacy data 26 is received from the transmission source legacy system 2.

  If the code conversion definition XSL file 15 does not exist in step S3 (NO in step S3), the process proceeds to step S5, and the processing steps after step S5 are performed.

  Further, the process proceeds to step S5, and if the format conversion definition XSL file 16 does not exist (NO in step S5), the process proceeds to step S7, and the processing steps after step S7 are performed.

  By executing such a data conversion processing procedure, it is possible to more easily realize data cooperation between legacy systems that use different data formats of legacy data.

  In the data conversion processing procedure shown in FIG. 10, the processing steps from Step S3 to Step S4 and the processing steps from Step S5 to Step S6 may be interchanged. That is, following step S2, the existence of the format conversion definition XSL file 16 is confirmed, and if it exists, the format conversion processing step is executed, and then the existence of the code conversion definition XSL file 15 is confirmed. In addition, the code conversion processing step may be executed.

  Next, a data conversion program according to the present invention will be described.

  An example of the data conversion program according to the present invention is the data conversion PG5. That is, by cooperating with the electronic computer 4 which is a hardware resource, the electronic computer 4 can execute the data conversion processing procedure shown in FIG.

  As described above, according to the present invention, the data conversion rule can be visually defined by the GUI, so that legacy systems having different data formats to be used can be linked more easily than before.

  More specifically, in the data conversion apparatus 1 configured so that the icons 40 a to 40 h can be used by the user, one item in the source legacy data 26 is converted into a plurality of items in the destination legacy data 30. In addition, since a plurality of items in the transmission source legacy data 26 can be converted into one item in the reception destination legacy data 30, the data even in the legacy systems when the correspondence between the data items is not one-to-one. The conversion apparatus 1 can be applied.

  Further, since the code conversion unit 21 can read out the electronic data (for example, the code conversion table 17) necessary for the code conversion and perform the code conversion, the legacy systems 2 and 3 having different code systems of the transmission source and the reception source. Even during this time, code conversion can be performed according to the code conversion table 17.

  Furthermore, as another example, by selecting the icon 40b and causing the format conversion unit 22 to execute predetermined processing, data that does not exist in the transmission source legacy data 26 that is the conversion source is included in the range specified by the reception destination legacy data 30. Can be inserted with the specified data length.

  Furthermore, as another example, by selecting the icons 40e and 40f and causing the format conversion unit 22 to execute a predetermined process, it supports legacy systems 2 and 3 that use a transmission format including variable-length data items. can do.

  On the other hand, in the legacy system, the storage position is often given meaning, but since the code conversion table 17 can take various forms, the transmission source legacy system 2 and the reception destination legacy system 3 have meaning in the storage position. Even in the legacy systems 2 and 3 having the transmission format with the code, the code conversion unit 21 can perform the code conversion.

  In the data conversion apparatus 1, the user inputs an operation using the input unit 7 of the electronic computer 4, but a plurality of input units 7 may be provided. Further, a dedicated input terminal specialized for the data conversion device 1 may be provided instead of the input means 7.

  Further, the CPU 10 refers to the definition XSL file 15 or the format conversion definition XSL file 16 at the time of code system or format conversion. However, since the code system and format may not require conversion, they are used in the legacy systems 2 and 3. It is not always necessary to refer to it depending on the data format. That is, the definition XSL file 15 and the format conversion definition XSL file 16 may not be stored in the recording unit 12.

  Furthermore, when at least one of the code system and the format conversion is not required, the 0th-order XML data 27 shown in FIG. 2 may be the primary XML file 28 or the secondary XML file 29, and the primary XML file 29 may be used. The file 28 may be a secondary XML file 29.

  On the other hand, the data forms of the format definition XML file 14, the code conversion definition XSL file 15, and the format conversion definition XSL file 16 are not limited to various files, and may take other data forms such as a database.

  Further, the data conversion PG 5, the format definition XML file 14, the code conversion definition XSL file 15 and the format conversion definition XSL file 16 stored in the recording unit 12 do not necessarily have to be stored in the recording unit 12. May be stored in other recording means as long as it is accessible.

  Further, in the data conversion apparatus 1, the transmission source and the reception destination are not necessarily one system, and at least one of the transmission source and the reception destination may be a plurality of systems.

Schematic which showed an example of the structure of the data converter which concerns on this invention. The functional block diagram which showed an example of the function structure which the data converter which concerns on this invention has. Explanatory drawing explaining an example of the content of the format definition XML file visualized by GUI provided by the definition data editing part of the data converter concerning the present invention. Explanatory drawing explaining an example of the screen which sets the definition of the data conversion from the transmission side legacy data visualized by GUI provided by the definition data editing part of the data conversion apparatus which concerns on this invention to the reception side legacy data. It is a figure showing the code conversion table which the code conversion part of the data converter which concerns on this invention refers, and explanatory drawing which showed the example in the case of performing one-to-one code conversion with a transmission source and a receiving destination. It is a figure showing the code conversion table which the code conversion part of the data converter which concerns on this invention refers, and is explanatory drawing which showed the example in the case of converting a certain numerical range into corresponding data. It is a figure showing the code conversion table which the code conversion part of the data converter which concerns on this invention refers, and explanatory drawing which showed the example in the case of converting the data which match the pattern shown by the regular expression into a corresponding value . It is a figure explaining the code conversion table which the code conversion part of the data converter which concerns on this invention refers, Comprising: The example which defines the order in a loop corresponding to a code, when the repetition position of a loop has a meaning Explanatory drawing which showed. It is a figure explaining the code conversion table which the code conversion part of the data converter which concerns on this invention refers, Comprising: When the repetition position of a loop has a meaning, the code | cord | chord and data item name corresponding to the storage position in a loop Explanatory drawing which showed the example which defines. Explanatory drawing explaining order for the process step of the data conversion method which concerns on this invention later on.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Data converter 2 Source legacy system 3 Receiver legacy system 4 Electronic computer 5 Data conversion PG
7 Input means 8 Display means 9 Communication I / F means 10 CPU
11 Memory 12 Recording means 14 Format definition XML file 14s Transmission side format definition XML file 14r Reception side format definition XML file 15 Code conversion definition XSL file 16 Format conversion definition XSL file 17 Conversion table 20 XML conversion unit 21 Code conversion unit 22 Format conversion Unit 23 legacy data conversion unit 24 definition data editing unit 26 transmission side legacy data 27 primary XML data 28 primary XML file 29 secondary XML file 30 reception side legacy data 31 name column 32 format column 33 data length column 34 extended attribute column 35 Loop field 38 Format definition corresponding to transmission side format definition XML data 39 Format definition corresponding to reception side format definition XML data 40 Icon

Claims (18)

XML data conversion means for converting the legacy data of the transmission source into XML data with reference to the format definition XML data in which the data format of the legacy data used in the legacy system of the transmission source is defined in XML,
The data format of the legacy data used in the legacy system of the receiving destination is referred to the format definition XML data defined in XML, and the XML data converted from the legacy data of the sending source is changed to a data format used in the legacy system of the receiving source. A data conversion apparatus comprising: legacy data conversion means for conversion. Code conversion means for converting the code system of the XML data obtained by conversion by the XML data conversion means based on the code conversion definition XSL data defining the conversion rule of the data code;
2. The apparatus according to claim 1, further comprising at least one of format conversion means for converting a format of XML data obtained by the XML data conversion means based on format conversion definition XSL data defining a format conversion rule. The data converter described. A graphical user interface is provided, and the format definition XML data of the transmission source, the format definition XML data of the reception destination, the code conversion definition XSL data, and the format conversion based on the operation content input through the graphical user interface 3. The data conversion apparatus according to claim 1, further comprising definition data editing means for editing at least one of the definition XSL data. A definition that provides a graphical user interface and relates legacy data used in the legacy system of the transmission source to legacy data used in the legacy system of the reception destination based on the operation contents input through the graphical user interface The data conversion apparatus according to claim 1, further comprising data editing means. The association includes integrating a plurality of items of the XML data into one item, dividing one item of the XML data into a plurality of items, and making the variable-length data item of the XML data a fixed-length data item, 5. The data conversion apparatus according to claim 4, wherein at least one of the fixed-length data item of the XML data is a variable-length data item. A graphical user interface is provided, and data that does not exist in the legacy data used in the legacy system of the transmission source is converted into legacy data used in the legacy system of the reception destination based on the operation content input through the graphical user interface. The data conversion apparatus according to claim 1, further comprising definition data editing means to be inserted. 3. The data conversion apparatus according to claim 2, wherein the code conversion means has a code system conversion function for converting a code system of the XML data based on referenceable code conversion data. The code system conversion function includes a function for converting a source and a receiver into a one-to-one code, a function for converting a group of a plurality of numerical ranges and a code corresponding to each group of the numerical ranges, The function that converts the expression and the content when matched with this regular expression to the corresponding code, the function that converts the code to the code corresponding to the loop repeat position when the repeat position in the loop is meaningful, and 8. The data conversion apparatus according to claim 7, further comprising at least one of functions for inserting data at a repetition position of a loop corresponding to a code when the repetition position has a meaning. The format conversion means has a format conversion function for converting a format related to the structure of the XML data. The format conversion function is a function for integrating a plurality of items of the XML data into one item, and one item of the XML data. A function of dividing into a plurality of items, a function of making the variable length data item of the XML data a fixed length data item, a function of making the fixed length data item of the XML data a variable length data item, and the legacy system of the transmission source 3. The data conversion apparatus according to claim 2, further comprising at least one of functions for inserting data that does not exist in the legacy data to be used into the legacy data used in the legacy system of the receiving destination. Legacy / XML conversion processing step for converting data in a format corresponding to the system received from the legacy system of the transmission source into XML data;
An XML / legacy conversion processing step for converting the data converted into the XML data in the legacy / XML conversion processing step into data of a format corresponding to the legacy system of the reception destination;
A data conversion method comprising: a reception destination legacy data transmission step of transmitting the data converted in the XML / legacy conversion processing step to a legacy system as a reception destination. A code conversion processing step of converting a code of data converted into XML data in the legacy / XML conversion processing step with reference to the code conversion definition XSL file when a code conversion definition XSL file exists;
At least one process of converting the format of data converted into XML data in the legacy / XML conversion processing step with reference to the format conversion definition XSL file when the format conversion definition XSL file exists The data conversion method according to claim 10, further comprising a step. 12. The data conversion method according to claim 11, wherein the code conversion processing step converts a code system of the XML data based on code conversion data that can be referred to. The code conversion processing step includes a processing step of converting a code corresponding to a transmission source and a reception destination on a one-to-one basis based on code conversion data that can be referred to, a group of a plurality of numerical value ranges, A processing step for converting to a code corresponding to a group, a processing step for converting a regular expression and contents when matched with this regular expression, a loop repetition position when the repetition position in the loop is meaningful And at least one of the processing steps of inserting data at the loop repetition position corresponding to the code when the repetition position in the loop is meaningful. The data conversion method according to claim 11, wherein the data conversion method is a data conversion method. The format conversion processing step includes a processing step of integrating a plurality of items of the XML data into one item, a processing step of dividing one item of the XML data into a plurality of items, and a variable length data item of the XML data as a fixed length data item. A processing step in which the fixed-length data item of the XML data is a variable-length data item, and data that does not exist in the legacy data used in the legacy system of the transmission source is used in the legacy system of the reception destination 12. The data conversion method according to claim 11, further comprising at least one of processing steps to be inserted into legacy data. Legacy / XML conversion processing step for converting data in a format corresponding to the system received from the legacy system of the transmission source into XML data;
An XML / legacy conversion processing step for converting the data converted into the XML data in the legacy / XML conversion processing step into data of a format corresponding to the legacy system of the reception destination;
A data conversion program for causing a computer to execute a data conversion processing procedure including a reception destination legacy data transmission step of transmitting the data converted in the XML / legacy conversion processing step to a legacy system as a reception destination. A code conversion processing step for converting a code of data converted into XML data in the legacy / XML conversion processing step with reference to the code conversion definition XSL file when a code conversion definition XSL file exists; and a format conversion definition At least one processing step of converting a format of data converted into XML data in the legacy / XML conversion processing step with reference to the format conversion definition XSL file when the XSL file exists Prepared,
16. The data conversion program according to claim 15, wherein the reception destination legacy data transmission step is a processing step of transmitting data after at least one of the code conversion processing step and the format conversion processing step. The code conversion processing step includes a processing step of converting a code corresponding to a transmission source and a reception destination on a one-to-one basis based on code conversion data that can be referred to, a group of a plurality of numerical value ranges, and individual values of the numerical value ranges. A processing step for converting to a code corresponding to a group, a processing step for converting a regular expression and contents when matched with this regular expression, a loop repetition position when the repetition position in the loop is meaningful And at least one of the processing steps of inserting data at the loop repetition position corresponding to the code when the repetition position in the loop is meaningful. 17. The data conversion program according to claim 16, wherein The format conversion processing step includes a processing step of integrating a plurality of items of the XML data into one item, a processing step of dividing one item of the XML data into a plurality of items, and a variable length data item of the XML data as a fixed length data item. A processing step in which the fixed-length data item of the XML data is a variable-length data item, and data that does not exist in the legacy data used in the legacy system of the transmission source is used in the legacy system of the reception destination 17. The data conversion program according to claim 16, further comprising at least one of processing steps to be inserted into legacy data.

Images