The S4MXMLMC mini connector is used to create the tables and data in MSSQL from a XML file or to recreate the file from a database.
It keeps the relations between the XML tags by creating GUIDs that reference to the parent XML tag.
The use of this tool is at users own risk. The user understands that Scope4mation is not responsible nor liable for any damages, unexpected results, costs or any other effect that might occur as a result of using this tool.
1. Configure the config file
2. Open an command prompt window
3. Enter the full path to Exe file
3.1 To convert an XML to tables enter for example: -XMLToDB “C:\InputFile.XML” as arguments
3.2 To convert tables back to an XML file enter for example: -DBToXML “C:\OutputFile.xml” as arguments
The tool can only recreate files from databases where the tables are created by this tool.
If there are comments in you're XML File it will create an #comment Column in the table. Than the text that is inside the comment will be written in the #comment row.
How to comment in XML:
Tags can be included in comments!
<add key="Username" value="sa" />
<add key="Password" value=" ****" />
<add key="Server" value="s4mtest-s4mxml-1" />
<add key="DB" value="S4MXML" />
<add key"EmptyTableBeforeInserting" value="True" />
<add key="ClientSettingsProvider.ServiceUri" value="" />
<add key="UseLogServer" value="" />
|Username||Fill in the Username of the MSSQL Database User.||sa|
|Password||Fill in the password of the user you named above.||****|
|Server||Fill in the Hostname of the server where the Database is running on.||s4mtest-s4mxml-1|
|DB||Fill in the Database you want to use for the tool.||S4MXML|
|EmptyTableBeforeInserting||Will empty the output table before inserting the new data||True|
|UseLogServer||True or False; When True, it will use the logging server. More info can be found here.||False|
3. Logging (Optional)
The most common error message is the following:
1. No valid License found: The License should be located in the directory where the .exe of the MC is located.
If this did not fix the problem: Contact support.
You can read more about the logging settings here.