Automated migration of translation maps for use in exchanging documents between entities
View Patent ↗A method for migrating a legacy translation map to an evolved translation map includes determining an input file structure from input file structure information in the legacy translation map, determining an output file structure from output file structure information in the legacy translation map, and creating an XML binding object representation of source code for the input and output file structure. The method may further include creating an evolved language object representation of translation instructions in the legacy translation map, adding temporary segments to the XML binding object representation for the input file structure, and generating evolved language object representation of instructions to write input data into the temporary segments. The evolved language object representation of translation instructions is then merged into the XML binding object representation. The evolved translation map is then generated as an XML file based on the XML binding object representation resulting from the merging.
1. A method for migrating a legacy translation map suitable for a legacy application to an evolved translation map suitable for an evolved application, comprising:
determining an input file structure from input file structure information in the legacy translation map;
determining an output file structure from output file structure information in the legacy translation map;
creating an extensible markup language (XML) binding object representation of:
source code for the input file structure; and
source code for the output file structure;
creating an evolved language object representation of translation instructions in the legacy translation map;
adding temporary segments to the XML binding object representation of source code for the input file structure;
generating evolved language object representation of instructions to write input data into the temporary segments;
merging the evolved language object representation of translation instructions into the XML binding object representation; and
generating the evolved translation map as an XML file based on the XML binding object representation resulting from said merging.
2. The method of claim 1 , wherein the evolved language object representation comprises a Java® object representation and the XML binding object representation comprises an XMLBeans object representation.
3. The method of claim 1 , further comprising, prior to said adding, removing from the Java® object representation of translation instructions, instructions not relevant to the evolved platform.
4. The method of claim 1 , further comprising, prior to said adding, sorting said Java® object representation of said instructions for proper execution sequence in the evolved platform.
5. The method of claim 1 , wherein creating the evolved language object representation of translation instructions includes reading translation instructions in the legacy translation map using an Another Tool for Language Recognition (ANTLR) compliant language engine.
6. The method of claim 1 , wherein at least one of the input file structure and the output file structure is compliant with an electronic data interchange (EDI) standard.
7. The computer readable medium of claim 6 , further comprising invoking the evolved translation map to convert the input file into an EDI compliant electronic document.
8. A map translation server comprising a processor, computer readable storage accessible to the processor method and instructions for migrating a legacy translation map suitable for a legacy application to an evolved translation map suitable for an evolved application, the instructions comprising instructions for:
determining an input file structure from input file structure information in the legacy translation map;
determining an output file structure from output file structure information in the legacy translation map;
creating an extensible markup language (XML) binding object representation of:
source code for the input file structure; and
source code for the output file structure;
creating an evolved language object representation of translation instructions in the legacy translation map;
adding temporary segments to the XML binding object representation of source code for the input file structure;
generating evolved language object representation of instructions to write input data into the temporary segments;
merging the evolved language object representation of translation instructions into the XML binding object representation; and
generating the evolved translation map as an XML file based on the XML binding object representation resulting from said merging.
9. The server of claim 8 , wherein the evolved language object representation comprises a Java® object representation and the XML binding object representation comprises an XMLBeans object representation.
10. The server of claim 8 , further comprising, prior to said adding, removing from the Java® object representation of translation instructions, instructions not relevant to the evolved platform.
11. The server of claim 8 , further comprising, prior to said adding, sorting said Java® object representation of said instructions for proper execution sequence in the evolved platform.
12. The server of claim 8 , wherein creating the evolved language object representation of translation instructions includes reading translation instructions in the legacy translation map using an Another Tool for Language Recognition (ANTLR) compliant language engine.
13. The server of claim 8 , wherein at least one of the input file structure and the output file structure is compliant with an electronic data interchange (EDI) standard.
14. The computer readable medium of claim 13 , further comprising invoking the evolved translation map to convert the input file into an EDI compliant electronic document.
15. A computer readable medium including instructions, embedded in the computer readable medium, for migrating a legacy translation map suitable for a legacy application to an evolved translation map suitable for an evolved application, comprising:
determining an input file structure from input file structure information in the legacy translation map;
determining an output file structure from output file structure information in the legacy translation map;
creating an extensible markup language (XML) binding object representation of:
source code for the input file structure; and
source code for the output file structure;
creating an evolved language object representation of translation instructions in the legacy translation map;
adding temporary segments to the XML binding object representation of source code for the input file structure;
generating evolved language object representation of instructions to write input data into the temporary segments;
merging the evolved language object representation of translation instructions into the XML binding object representation; and
generating the evolved translation map as an XML file based on the XML binding object representation resulting from said merging.
16. The computer readable medium of claim 15 , wherein the evolved language object representation comprises a Java® object representation and the XML binding object representation comprises an XMLBeans object representation.
17. The computer readable medium of claim 15 , further comprising, prior to said adding, removing from the Java® object representation of translation instructions, instructions not relevant to the evolved platform.
18. The computer readable medium of claim 15 , further comprising, prior to said adding, sorting said Java® object representation of said instructions for proper execution sequence in the evolved platform.
19. The computer readable medium of claim 15 , wherein creating the evolved language object representation of translation instructions includes reading translation instructions in the legacy translation map using an Another Tool for Language Recognition (ANTLR) compliant language engine.
20. The computer readable medium of claim 15 , wherein at least one of the input file structure and the output file structure is compliant with an electronic data interchange (EDI) standard.