If you do not wish to use the default Console application, but would instead prefer to integrate the generated code into you own code, simply call the “run” method of the object representing the mapping from your own code. The execution of the Console application can be automated by writing a batch file. For convenience, compiling the generated code “as is” results in a Console application which when run, executes the mapping. The generated code files contain the mapping logic used to transform the source data into the desired output format(s). Selecting “Java”, “C#” or “C++” as the target language allows you to generate Java, C#, or C++ code from a mapping. By accessing the RaptorXML API programmatically, writing a batch file to call RaptorXML via the command line interface, or by setting up a FlowForce “job” which calls RaptorXML Server, you can automate the execution of XSLT or XQuery transformations. RaptorXML Server can be accessed programmatically via the API, via the command line interface, or via FlowForce Server. To transform XML source data, the generated XSLT or XQuery file must be passed along with the source data to an XSLT or XQuery engine (such as RaptorXML Server) for processing. The generated XSLT and XQuery files generated from a mapping contain the mapping logic used to transform the source xml data into the desired output format. Selecting “XSLT”, “XSLT2”, “XSLT3” or “XQuery” as the target language allows you to generate XSLT 1.0, XSLT 2.0, XSLT 3.0 or XQuery 1.0 files from a mapping. Which of these target languages are available for a particular mapping will depend on which data formats, functions and components are used in that mapping. The following target languages are supported by MapForce Enterprise Edition: To understand how the execution of mapping logic can be automated, it is necessary to understand which languages mapping logic can be generated in, and how mapping-logic in a particular language can be executed outside of MapForce. to ensure that the mapping is producing the correct result, however in a production environment most workflows will require some form of automation without any user interaction. This is fine for development purposes i.e. When developing a mapping in MapForce the user can switch to the “Output” tab to execute the mapping (using the source data provided at design time).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |