Backing up runtime and workspace files

The runtime files are as a result of compiling mainly binary encrypted. These cannot be compared directly with the editor-component data. As detailed below, we therefore recommend that you create a separate runtime component for the targeted comparison.

Creating a customize component type for the runtime

1. Create a runtime component type in the Component type editor, located in the AdminClient.
2. In the section Compare these files, enter all the files that you want to be used in the comparison.

Examples of file endings often included in the runtime files. SpecificationComparatorSubdirectory*.txtASCIIInclude*.ini ASCIIInclude*.xml ASCIIInclude*.pdfPDFInclude*.wsp6ASCIIOptional

In the section Ignore these files during the comparison, you have the option that files and folders can be sorted according to which ones disrupt the comparison and which ones can be classed as unimportant. – Examples of files that change by simply compiling them once again: Specification**Subdirectory**Project.cmpIncludeVBR_Para.emsInclude Examples of files that change by simply activating the runtime: Specification**Subdirectory**project_m.vbaIncludeVSTAorig.zipInclude In the section Save these files and Do not save these files, you can decide which files from the working directory you want to save.

Filling runtime components

1. In the UserClient, copy the workspace file (WSP6) into the component file Root (only the first time).
2. Open the workspace file in the zenon editor.

1. Copy all of the projects that you want to save in this project in the workspace.

1. Check whether all projects in the zenon editor have entered the same correct component path. Follow the path: Project -> project configuration -> General -> runtime file (for example, D:VDClientArchivezenonRT component “).

If the path in front of the project file is identical to the WSP6 file storage place, the zenon editor will automatically go to the path that corresponds to the project path.

1. In the zenon editor, create all the runtime files that you want to save.

The global project must be not complied and the global project that was created through compiling needs to be removed from the component.

(Global project files data are automatically taken over into other projects. A separate compile is therefore not necessary. The global project file that was created during compiling can cause problems during the comparison. For example, comparing a version with a backup).

1. Close the workspace.
2. Create the base version of your component.

Advantages of a separate runtime component

• Runtime data is saved and compared for binary changes. For example, a backup of the delivery status for SCADA/HMI serves as a basis for a binary comparison of a version and backup of the runtime.
• The workspace file for the zenon component is also saved and can be accessed by all users.

Related Topics

• AdminClient -> Component type editor