Configuration data, which can by changed by users, include stations, templates, registry, logs, and other data. Runtime data include core software modules, the JRE, and binary executables. Maintaining separate file locations enhances security by denying general access to runtime files (runtime folders are read-only) and allowing each user access to only their personal configuration files.

Multiple home directories serve to separate configuration and runtime data. Each platform has a User Home for configuration data and a System Home (Sys Home) for runtime data. Several other folders under these homes serve specific functions.

The platform’s System Home (Sys Home) is sometimes identified by its alias, niagara_home. It has a security subfolder that contains license files and license certificates. Except when it is time to upgrade, the System Home’s runtime files are read-only.

The platform’s User Homes contain all configurable data. Referred to by the alias niagara_user_home, the separation of these files from the runtime files stored in the System Home folder is new in Niagara 4. The impact of this change is mostly felt when manipulating stations. When Workbench creates a new station, it puts the station in the platform’s User Home directory. To start Niagara, the station must be copied from the station User Home to the platform’s daemon User Home.

Due to application differences, there are some minor differences between the complete list of files in a user’s User Home and the daemon’s User Home. For instance, daemon.properties only exists in the daemon’s User Home and navTree.xml only exists in the logged in user’s User Home.