Scope

Starting from release 1.11 YADE requires XML configuration files.
SOS provides migration tools that convert existing .ini configuration files to YADE - XML Configuration files.
The migrations tools are shipped with the XML Editor and can be used for previous YADE releases:
- The XML Editor can be used to convert .ini files to .xml configuration files.
- The XML Editor can be configured to create XML configuration files and compatible .ini configuration files in parallel for use with YADE releases 1.8 up to 1.10.

Migration Tools

The conversion is provided by a number of Java classes that are available with the XML Editor and are located in the plugins folder.

The converter tries to identify existing profiles and fragments from your YADE settings file (.ini format):
- A fragment is a section in the settings file that is included by other sections, mainly profiles.
- The remaining sections of a settings file are identfied as profiles if they
  - do not represent global sections (section header: [globals]) and
  - include an operation setting (having resolved any include statements from the profile section).
The converter provides limited accuracy when identifying profiles:
- If a profile from a settings file is included by any other profile then it will be considered a fragment and not a profile.
- Settings file sections that are not used, incomplete or invalid are subject to conversion and might result in conversion errors. We recommend to clean-up existing settings files before conversion.
- For some profiles no operation setting might have been specified as this can be added by direct parameterization of the YADE Client. Such profiles will not be identified as candidates for conversion and will be skipped.
The XML result file of a conversion might not be valid if
- empty settings have been used, i.e. settings without assignment, e.g. a missing recipient for a mail_to= setting. Such empty settings are valid for the settings file format but not for the XML configuration file format.

Profiles from settings files that use send/receive operation settings are converted to the respective XML operations Copy and Move (should the setting remove_files=true have been used).
Die generierte XML-Konfigurationsdatei ist nicht zwangsweise valide. In diesem Fall hilft der XML-Editor beim Beheben der Fehler.
Der Konverter protokolliert die vermissten erforderlichen Parameter.
Fehlt nach Auflösen aller etwaigen Includes das Protokoll an der Source oder am Target, dann wird das Profile nicht konvertiert. Hier muss das entsprechende Profile in der INI-Datei korrigiert werden.
Der Konverter protokolliert den fehlenden Protokoll-Parameter.

x

tbd: Usage & Screenshots