Applies To:
  • CitectSCADA 5.xx, 6.xx, 7.0

I have a project that I want to setup with only the minimum runtime files and no configuration databases. What files can I copy to a new run directory?

NOTE: As projects vary greatly in the files they use, this is a general guide only. Citect strongly advises fully testing all features in a project before putting a minimum runtime project online.

After fully compiling, the project files with the following extensions can be copied to the new run directory (if using include projects then only copy the files from the master project directory) -


The following files may also be needed:

- CTM and CTL libraries are needed for Genies with symbols
- Users.DBF is required if users can be modified at runtime
- Any language DBF files (eg. German.dbf, Korean.dbf)
- Variable.dbf and Variable.ndx may also be needed in some projects. If there are include projects then all records will need to be manually added into the one file.
- UNITS.DBF is needed for some I/O Device drvers

See also KB Q1952 for information on previous versions of Citect.


Solution for v 6.xx and 7.0

With componentisation we do not support using minimum set of files. The exact project files used by the runtime will vary depending on the features used, and also the way the customer has configured their system. There is a fast and reliable way to determine which project files are accessed by the runtime system.
A. You could use something like filemon
B. More simply you can use the DIR command in the windows command line to list the files by the time they were last accessed.
  * Just before starting the runtime make a note of the system time.
  * START -> RUN cmd
  * change into the project directory
  * DIR /O:-D /T:A
  * the top of the list represents the most recently accessed files or directories. Anything newer than the noted time was accessed / required by the runtime.
  * It may be wise to leave the system running for an extended time before running the command to ensure that less often accessed files are listed.
  * Virus scanners will sometimes access files on a periodic scan "just because they exist". Not just "on access".
  * A more practical way may be to redirect the output to a file for permanent reference. Eg DIR /O:-D /T:A > c:\file_list.txt