Skip to content

Integrating projects

Info

  • Use the same project structure of the zenon editor in the Project tree of the UserClient.
  • As a rule, manage only one project and consequently only one DB.INI per component.
  • Create a separate runtime component with a customize component type so that the job can back up and execute a binary comparison of these files.

  • By creating a separate component for the runtime files, the workspace file for the zenon component is also backed up and can be used by all users.

Integrating project data

  1. Create a new component in the UserClient. SelectZenon as component type in the directory COPA-DATA/HMI SCADA software.
  2. Select the DB.ini file of the zenon project.

    Info

    The DB.ini file provides the system with the information required to backup the project data (e.g. the project path).

    In the standard installation of the zenon editor, the DB.ini is stored under the path C:\ProgramData\COPA-DATA\SQL\{Project-GUID}. To find the DB.ini file of your zenon project:

    • Option with editor key combination:

      1. Open the zenon project in the editor.
      2. Select the project in the project tree of the editor.
      3. Press CTRL + ALT + E to open the file manager in the SQL folder of the project (e.g. path: {Drive}:\\SQL\{GUID}\{FILES directory}).
      4. Navigate one directory level back to {GUID}{Drive}:\\SQL\{GUIDdirectory}.
    • Option via the project GUID:

      1. Start the zenon editor.
      2. Select the File > Insert existing project menu. The Project selection dialog opens. The projects available for selection are displayed with their project names.
      3. In the dialog for project selection, click on the plus sign (+) in front of the desired project. Detailed information about the project is displayed - including the Project ID.
      4. Open the file manager.
      5. Search for a folder on the computer whose name corresponds to the GUID.
  3. Copy the DB.ini of the project into the working directory of your component.

  4. Close the file manager and click on the arrow (>) in front of the zenon component in the Project tree. The DB.ini inserted locally is displayed.
  5. Right-click on the DB.ini and select Open with editor in the context menu. Alternatively: Press the F4 key. The Data adapter for zenon projects dialog opens:

    Figure: Data adapter dialog for zenon projects, Open in editor

  6. Make the following settings in the data adapter:

    • Under zenon editor to use, select the zenon editor version with which the zenon
      project was last edited. If you do not know which zenon editor version was last used to work on the project, determine this e.g. via the project.ini file.
      Procedure 1. Open Windows Explorer. 1. Select Computer in the navigation area of the explorer. 1. Enter the Project ID of the zenon project in the search field of the explorer and start the search. If the search is successful, a folder is displayed whose name corresponds to the Project ID you are looking for. 1. Open the folder and search for the project.ini file. 1. Open the project.ini file with a text editor.

      Info

      If the zenon editor version with which the project was last edited is not available on the computer, select the highest zenon editor version that is available. Please note that the project may be converted when opening in the editor.

    • Define a workspace file under zenon Workspace file (*.wsp6). You can select an existing workspace file or create a new workspace file:

      A. Create a new Workspace file by directly entering an absolute path in the field zenon Workspace file (*.wsp6).

      Info

      As a new workspace does not yet contain any project data, you must then load the project of this component into the workspace in the editor.

      B. Select an existing workspace file via the file selection. If the project selected in the data adapter is not contained in the existing Workspace file, it is inserted. If the workspace file selected in the data adapter contains several projects, all projects are displayed in the Additional projects in workspace of the data adapter. Make your selection here.

    Info

    You will find the option Update zenon project database in the data adapter. If this option is selected, the central zenon project database is updated with the content of the component, otherwise no update takes place. This option is not relevant for the integration of an existing zenon project.

  7. Once you have made all the settings, click OK in the data adapter. The project is then automatically opened in the editor. This is necessary for technical reasons after copying the DB.ini file.

  8. Now close the editor again. If you have made changes to the project, save your data before closing.
  9. Switch to the UserClient. Select the zenon component and click on
    Create base version and Check-In.
    The zenon project is now integrated and can be managed.

Integrating runtime files

  1. In the UserClient, create a new component and choose the customized component type for runtime files.
  2. Copy the workspace file (*.WSP6) to the Root component folder (only for first filling).
  3. Open the workspace file in the zenon Editor.

    Info

    Make sure you have the correct editor version for your zenon project.

  4. Copy all projects that are to be saved in this component to the workspace.

    Info

    You should only save a reasonable number of projects in the runtime component (e.g. a project structure with Global project + main umbrella project + all sub-projects).

  5. Check whether all projects in the zenon editor have exactly the same, correct component path entered. To do this follow the path: Project > Project properties > General > Runtime folder (e.g.: D:\VDClientArchive\zenon\RT-Component\{Project name}). If the path before the project folder matches with the letter of the storage location of the WSP6 file, the automatic mechanism of the zenon Editor takes effect and adjusts the project's path.

  6. Create all runtime files to be saved in the zenon editor. The global project does not have to be compiled or the global project folder created by compiling must be removed from the component. (The data of the global project is automatically transferred to other projects, so separate compilation is not necessary. The global project folder created during compilation can interfere with comparison, e.g. comparison of version with backup.)
  7. Close the zenon editor.
  8. Create the base version of your component.
    You can now manage the runtime in octoplant.