This procedure defines how to transfer XML configuration between environments or companies. It is done by creating a configuration data file (ZIP file that contains an XML file) and then import it into the receiving environment/company. This allows you to transfer your work without having to recreate it in the receiving environment/company.
Start 'List and Printer programs. Configure' (CMS005).
In the field 'Select', select Printer files.
Select the printer file and use option 27='Export configuration'.
In the pop-up window, specify file name and version, click OK.
To check the export XML file, start 'Configuration Data Jobs. Open' (MNS200) select the start date and job number and use option 20='Display XML file'.
The actual name of the ZIP file will be 'ConfigData_<File name>.xml.xip'.
Import is done in M3 BE Administration Tools.
Select 'Business Engine Configuration Data'.
Select tab 'Exported' to see a list of all export XML file (same list as in (MNS200)).
Select the XML file and click 'Import'. The import tool then reads the XML file and runs the needed API programs to write the data to the M3 BE database. The API program and transaction to be run are specified in the XML file. During import, you can decide if the existing data should be replaced or not. If data should be replaced, a Delete transaction is run before the Add transaction.
The Content part of the configuration data file always includes these sections: Check, Delete, and Add. It is processed from beginning to end.
This specifies if API transactions need to be checked for related data before starting the processing of delete and add transactions. If any error message is received from the API transactions, the process ends, and the add and delete sections are not processed.
This specifies the API transactions needed to delete existing data. The delete section is only processed if check box ’Replace existing data’ is selected in the tool wizard. There is usually one API transaction specified but if needed, several API transactions can be listed. Error or warning messages from API transactions are logged, but XML continues to process the next API transaction.
This specifies the API transactions needed to add data. The add section is always processed (if no errors are found during the Check section). One API transaction is usually specified, but if needed, several API transactions can be listed. Error or warning messages from API transactions are logged, but XML continues to process the next API transaction.