Editorial_UpdateConfig.xml
Contents
You can use a custom Editorial_UpdateConfig.xml file to update your GN4 system. Have in mind that it is a custom file so you might have to update it manually all the times before performing an upgrade.
The Editorial_UpdateConfig.xml file derives from the Editorial_InstallConfig.xml from which are stripped off initial data loading (<DataFile>) and some config loading (<ConfigFile>) - where it is presumed that your configuration files might be customized (e.g. ServerConfig.xml, EditorialConfig, GlobalConfig etc.)
A possible way to generate an Editorial_UpdateConfig.xml is to copy in it the content of the Editorial_InstalConfig.xml and then remove the lines that load data or config you don't want to overwrite in your customized system.
All (?) lines with <DataFile> prefix Generally speaking, none of <DataFile> is supposed to remain in the Editorial_UpdateConfig.xml. An exception is when you are warned in upgrade notes that some new initial data for the newly added features is to be loaded to an existing database. Therefore, when updating your custom Editorial_UpdateConfig.xml, if there's no any warning about new initial data, just make sure that all lines starting with <DataFile> were deleted from the Editorial_UpdateConfig.xml: <!-- Data file to import in the database --> <DataFile>Data\dataSrcTemplate_ImportDocuments.xml</DataFile> <DataFile>Data\dataSrc_ImportDocuments.xml</DataFile> .... Specific lines with <ConfigFile> prefix It's very likely that your customized system will have a modified EditorialConfig.xml, possibly also the GlobalConfig.xml file. If so, you may want to comment out the loading of these two files, in order not to overwrite your custom settings. <ConfigFile>Global\EditorialConfig.xml</ConfigFile> <ConfigFile>Global\GlobalConfig.xml</ConfigFile> Another file you may care not to overwrite with the default values is the serverconfig.xml: <ConfigFile>Global\ServerConfig.xml</ConfigFile>
|
Some general rules
•The file Editorial_installconfig.xml must be used ONLY for installing from scratch and never on an already customized GN4 database.
•Create editorial_updateConfig.xml based on the latest editorial_installconfig.xml removing <DataFile> e ServerConfig.xml da <ConfigFile>. You have to redo it on every upgrade.
•When updating, compare the previous editorial_installconfig.xml (that you made a copy of) with the latest one. In that way you can see what has been added. If <DataFile> lines were added, this means that the new initial data was required, and you have to import those, while removing all others - that were present also in the previous version of the editorial_installconfig.xml.
•It is highly recommended that you keep trace of all customized configuration files (we recommended the use of SVN) so that you can compare old and new and merge the differences.
•Keep a copy also of the modified schemas, and on every upgrade merge the new default modifications into custom schemas.