IEG scripts and resources are stored in the database and may be discarded or overwritten by files from the file system during a database build. This build process uses a data manager configuration to tell what files should be included in the build. Customer specific data such as IEG scripts and resources should be stored on the file system as DMX files, CLOBs (large character objects) and BLOBs (large binary objects).
An IEG script definition is stored in the IEGSCRIPTINFO database table as a CLOB. Application resources are stored in the APPRESOURCE database table as BLOBs.
It is important therefore that any custom IEG scripts, custom application resources, the IEGSCRIPTINFO.dmx file and the APPRESOURCE.dmx file are on the file system and placed under source control. Cúram recommend the following steps to ensure the custom artifacts are picked up by the build database process: