Custom Files

If a Plant SCADA project relies on externally-created files that you need to incorporate into a runtime deployment (such as DBF files, HTML files, or ActiveX objects), you will need to identify these files as Custom Files in the Setup activity.

When a project is compiled, any files you have identified in this way will be compressed into one of the following zip files:

• custActiveX.zip - includes the associated ActiveX files

• custFiles.zip - includes other associated files.

These zip files are then incorporated into a project. Each time an operator starts Plant SCADA Runtime, the client process checks the project and its included projects directories. If custFiles.zip or custActiveX.zip is found locally, the compressed archive is unzipped. (If [CtEdit]Copy is specified, then the zip files may be copied from the copy path first.)

Files in CustFiles.zip are unpacked to the project directory and its sub directories, depending on the value specified in the Destination Location field.

ActiveX control files in CustActiveX.zip are unpacked to the project directory and its sub directories first, then moved to "%PROGRAMFILES(X86)%\Common Files\AVEVA Plant SCADA" and, if the file is a valid ActiveX control, it is registered.

Note: Custom files can be transferred to remote computers via a deployment server using Plant SCADA's Deployment feature.

See Also

Include Custom Files