Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

How TOP Server loads .opf project files during Runtime

How does TOP Server handle loading project files (.opf) and determining which is utilized during Runtime?

  • The Runtime service always loads the default.opf => active project
    • By default during installation the default project location is set to:
      C:\ProgramData\Software Toolbox\TOP Server\V6
    • When loading a different project into runtime service, the default.opf file is overwritten and stores a backup of the original project to the default path:
      C:\ProgramData\Software Toolbox\TOP Server\V6\Project Backups
  • The Configuration utility is the user interface for editing a project configuration
  • The content of the default.opf is being re-written depending on the project the user decides to load when the Runtime is connected
  • When the Configuration utility is connected to the Runtime it always displays the default.opf file
  • Any changes made within the Configuration while it is connected is a real-time change to that default.opf file
  • When the Configuration disconnects, the default.opf project is still loaded in the Runtime while the Configuration can make off-line changes or open another project file
  • You can edit another project configuration while it is disconnected from the Runtime and save it under different names and paths
  • When opening a saved project and/or connecting to the Runtime the user is prompted with the option to 'update the runtime with the loaded project'
    • Yes - overwrites the content of the default.opf with the project currently opened in the Configuration and loads it into the Runtime
    • No - just opens/keeps the project in the Configuration in offline mode, while the Runtime continues running with the default.opf currently available