IEG script definitions are stored in the database. When editing an IEG script using the IEG Editor, the script is edited in place and updated directly in the database. IEG script definitions are development artifacts and from a software configuration management point of view it is important that these artifacts are placed under source control as you would with any other artifacts.
It is possible to download a script definition from the IEG script administration screens. When the option to download a script is chosen, the script is first retrieved from the database, then the properties files associated with the script definition are retrieved from the Resource Store and the textual properties are "injected" into the script definition before it is made available. However downloading a script in this way does not provide all the resources that may be associated with a script definition. For example, it does not provide properties files in multiple locales and it does not provide images and icons. Please see the Compliancy appendix of the Authoring Scripts using Intelligent Evidence Gathering (IEG) developer's guide for more information on the database representation of an IEG script.
When populating the database with script definitions, it is important to be aware of the differences in functionality between importing a script through the IEG script administration screens and loading a script definitions via DMX files.