How to Prevent Designer from Overwriting Certain Runtime Files

Owned by François-Xavier NICOLAS
Last updated: Mar 21, 2018 by Hilaire Godinot (Deactivated)

The Semarchy Integrator automatically installs the runtime when it starts, and automatically overwrites the files that you have added or modified in the runtime folder.

When installing files (for example, patches) in the runtime folder in the Convergence for DI Designer folder, you can protect them from this mechanism.

Step-by-step guide

To protect files from being overwritten by the Designer:

  1. Edit the protection.rules file stored in the runtime/properties/ folder.
  2. Add one line for each file, folder or group of files that you want to protect.
    • Use a star (* ) character for file/folder names aliases
    • Lines starting with a dash (#) are comments. These are ignored.
  3. Save the file.
  4. Stop and restart the Designer to make sure that the files are correctly protected.

Find below a sample of the protection.rules file.

Protection.rules file sample
/properties/protection.rules
/properties/repository.xml
/properties/engineParameters.xml
/properties/log4j.xml
/properties/userParameters.properties
/properties/engineScheduler.properties
/properties/engines/*
/properties/logs/*
#/lib/*.jar
#/build/xsl/*
/build/xsl/user.xsl
/lib/jdbc/*
/build/xml/userConversion.xml

 Notes

This method can be used to get the designer to use another version of the engine than the one that comes as part of the designer.

You can install a new version of the runtime in any folder / location you want. Though, only the runtime hosted in the DesignerRootFolder/runtime folder can be started from within the design tool using the "Environment" button from the Runtime tab.

To prevent the runtime from beeing replaced by the default version each time you start the designer, create a rule that protects the whole runtime folder as follows

Protection.rules file sample
/*