Altova has conducted an internal investigation regarding the Log4j vulnerabilities (CVE-2021-44228 & CVE-2021-45046) and we can confirm that none of our software products are affected by these vulnerabilities, because they neither require nor directly use the Log4j library.
Altova Developer Tool software is only available for Windows. To run our Developer Tool software on macOS it would be necessary to use software such as those described on our Support OS Platforms page.
Previous versions of each product are available from the “Previous Releases” section of that product’s Download page, as well as from our Software Archive.
This problem can occur when library folders (i.e. “My Documents", “My Pictures", etc.) are stored on a network drive. In order to resolve this issue please temporarily move such folders to your local hard disk, install the software, start the application, and then quit. After you have done so you can move the aforementioned folders back to the network share.
This error occurs if there is a problem with the VBScript support on your system. The solution can be found in the Microsoft Forum.
You need to install the integration package for the appropriate Developer Tool software that you wish to embed into your application (i.e., XMLSpy, MapForce, StyleVision, or UModel). When you install the integration package a control will be added to the Toolbox in Visual Studio. This control can then be used in your application.
Visual Studio is a 32-bit application and therefore requires a 32-bit plug-in. If you want your Developer Tool software (i.e. XMLSpy, MapForce, StyleVision, or UModel) to integrate into Visual Studio, you will have to install both the 32-bit version of the software as well as the 32-bit integration package for that software.
This error most likely has to do with an architecture mismatch i.e. you are trying to connect to the database from a 64-bit version of our Developer Tool software using a 32-bit database driver, or vice versa. If you are using a 32-bit version of our Developer Tool software then you must use a 32-bit database driver to connect to a database, likewise if you are using a 64-bit version of our Developer Tool software it will be necessary to use a 64-bit database driver to connect to the database.
The advantages as well as possible implications of using the 64-bit versions of our software are covered here.
Graphical editing of WSDL files is only supported in the Enterprise Edition of XMLSpy. If you have the Professional Edition of XMLSpy and wish to upgrade, please contact our Sales department.
To get the XPath for a particular node in an XML file, right click on the node in the Grid or Text views of XMLSpy and then select “Copy XPath” from the context menu.
To get the XPaths for all nodes it would be necessary to generate Schema documentation from the XSD schema associated with your instance XML file:
Use XML Schema annotations instead of comments. Annotations will not be moved, and using the annotation mechanism provided by XML Schema is the preferred method of “commenting” an XML Schema file.
You can use the XMLSpy API to validate or transform an XML file, however some user interaction will be required. If you wish to completely automate validation or transformation you must use RaptorXML Server and its API / command line interface instead.
You can parse / generate fixed-length or delimited text files which have multiple record types (Header / Detail type structure) by designing a FlexText template and inserting this into your mapping. FlexText templates can be designed using the FlexText utility which is included in the Enterprise Edition of MapForce.
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). This is fine for development purposes i.e. 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.
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.
The following target languages are supported by MapForce Enterprise Edition:
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.
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. 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. 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. RaptorXML Server can be accessed programmatically via the API, via the command line interface, or via FlowForce Server. 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.
Selecting “Java”, “C#” or “C++” as the target language allows you to generate Java, C#, or C++ code from a mapping. The generated code files contain the mapping logic used to transform the source data into the desired output format(s). For convenience, compiling the generated code “as is” results in a Console application which when run, executes the mapping. The execution of the Console application can be automated by writing a batch file. 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.
Selecting “BUILT-IN” as the target language allows you to compile your mapping to an “.mfx” file. An “.mfx” file must be run using MapForce Server. MapForce Server can be accessed programmatically via the API, via the command line interface, or by setting up a FlowForce “job” which calls MapForce Server. By accessing the MapForce Server API programmatically, writing a batch file to call the command line interface of MapForce Server, or by setting up a FlowForce “job”, you can automate the execution of the mapping.
Of the aforementioned target language options “BUILT-IN” is the least restrictive and most performant. Unless you are otherwise restricted to a particular target language, it is advisable to use the “BUILT-IN” option. To automate the execution of mappings which have the target language set to “BUILT-IN” MapForce Server is required. If your automation requirements are complex it would be advisable to also use FlowForce Server (in addition to MapForce Server). FlowForce allows for the orchestration of complex automation worflows.
If you have the requirement to process EDI transactions which are non standard compliant you can customize the EDI configuration files to provide support for such transactions.
Try the following:
Mappings developed in MapForce targeting the “BUILT-IN” engine must be executed using MapForce Server. By using the MapForce Server command line interface or the MapForce Server API to execute “.mfx” files, it is possible to develop BASIC automation scenarios with minimal effort. Many situations however, will require more complex automation workflows - for such scenarios we recommend using FlowForce Server in addition to MapForce Server.
FlowForce Server supports the following features allowing for the creation of complex automation workflows:
It is important to note that FlowForce Server is not an alternative to MapForce Server but rather an addition to Mapforce Server i.e. internally FlowForce Server relies on MapForce Server to perform the actual execution of the mapping.
Using StyleVision Enterprise Edition you can generate stylesheets which allow for the transformation of XML into PDF. Altova does not have a tool which can convert from PDF to XML.
It is possible to import existing XSLT stylesheets into Stylevision to use as a basis for a StyleVision design, however it is possible that not all XSLT constructs will be imported. Otherwise, use XMLSpy to edit your existing XSLT files.