TOP Server JSON Configuration File Format

Flexibility for Sophisticated Users

The TOP Server configuration file can be saved in a JSON format which allows experienced users to perform edits as required to the entire channel+device set, such as a mass IP address update.  The use of this feature expects that a user is able to read/understand JSON structure formatting, understands TOP Server configuration, and that the user will follow best practices regarding backups of their work and working with care. Users comfortable with development, such as integrators or users with in house staff skilled in web services and .NET, can also use the TOP configuration API's instead of exporting to JSON and re-opening the project.  

We strongly recommend that users only use this format for editing, and then save the configuration file in the native *.OPF file format as that format provides encryption and password security capabilities. We also suggest that you not leave JSON format text files that could contain sensitive information in unsecured locations if you have concerns about the risks of someone accessing the files.  

The native *.OPF secure binary format also will perform better than a text JSON configuration on startup and updating of projects from the configuration UI. Users with small to mid-sized configurations will not notice a difference but if you have configurations in the tens of thousands or hundreds of thousands of tags, you may notice the difference.

Here's some more details about how to use this feature.