The following is a list of terms and abbreviations used in this document when describing the Sedona Device Simulator. Complete Sedona Framework documentation is available at the Sedona Framework website (http://www.sedonadev.org). For general NiagaraAX terms, see the Glossary in the Niagara AX User Guide.
For application. The app in a Sedona Framework device is its collection of Sedona Framework components, including links between them, plus configuration properties.
The act of matching a Sedona device’s app file to one of the Sedona devices residing under a SedonaNetwork in the station database on the JACE is referred to as association. App files reside in the JACE file system.
A common software development term, it refers to loading an application using a much smaller initial app to initiate and load more complex processes. As used in this document, “bootstrapping” describes the process of loading the simulator SVM with a default scode image and default app file for the platform. Once the SVM is bootstrapped with the default app, the standard Sedona Framework TXS provisioning tools are used to connect to the SVM and re-provision it with the app you have selected to run in the simulator.
Sedona Framework kits are the basic unit of modularity of Sedona Framework software, encapsulating code, types, and metadata. A kit is analogous to a module on a NiagaraAX platform. The app in a device instantiates components and services contained in its installed kits. You must have the appropriate kits available on your Workbench to change a device’s “core” software. Sedona Framework Sox Tools in Workbench include a “Kit Manager” view to manage kits on a Sedona Framework device.
Each kit has a corresponding manifest, that contains all the metadata needed by tools like Workbench to connect via Sox to a Sedona Framework device, and for a station to support Sedona Framework proxy points in that device. Manifest files are compact XML files, named using a kitName-checksum convention similar to kit files, but with an .xml extension. Use the Manifest Manager view of either Sedona Framework network type to manage kit manifests on the NiagaraAX host (JACE or Supervisor). Use the Sedona Manifest Manager view in Workbench tools to manage manifests on your Workbench host. For more details see the Sedona Manifest Manager document.
For Platform Archive, or PAR file. This is a zip file with a .par extension that provides a way of organizing various files and metadata about a platform into a single entity. The contents of the platform archive includes an XML file that describes the platform.
The Simulator runs in a “sandbox” folder called “sedonaDeviceSim
” which is created under your user folder: <niagara-release>/users/<username>/SedonaDeviceSim
). The SVM, scode, and app files are copied to this folder and run from this location. Also, the provisioning process writes
files to this location.
For Sedona App Binary. This is a compact binary representation of a Sedona Framework app suitable for storage and execution on a Sedona Framework device. One of two file formats (.sab) for a Sedona Framework app.
For Sedona App XML. This is a simple XML representation of a Sedona Framework app that is easily generated and consumed by Sedona Framework software tools. One of two file formats (.sax) for a Sedona Framework app.
A compiled set of kits in a Sedona Framework code image file with an .scode extension. The scode image is executed by the SVM in the device. The Kit Manager tool is used to modify kits.scode on a Sedona Framework device.
The term SEDONA HOME is a system “variable” for the installation-specific directory of your Workbench computer's “root” folder for Sedona Framework files used in Sox connections from Workbench. Beginning with Sedona TXS-1.2, the default location for SEDONA HOME is !/sedona.
The app file that is loaded and successfully running in the Sedona Device Simulator is the simulator app.
Sox is the standard protocol used to communicate with Sedona Framework devices. It runs over UDP via the lower-level DASP protocol. Workbench always uses Sox to open a connection to a Sedona Framework device. A Niagara station also uses Sox to discover as well as read and write to Sedona Framework proxy points.
The SVM (Sedona Virtual Machine or VM) executes the Sedona app on a device using the kits installed on that device.
Copyright © 2000-2014 Tridium Inc. All rights reserved.