Overview of app file association

Starting in Sedona TXS-1.2, a Sedona Environment Manager (platform) tool lets you install “Sedona environment files” for Sedona devices networked under a JACE to be located (and maintained) on that JACE platform. Files include kit manifests required for Sox communications, along with kit files and platform archive files needed for Sedona device provisioning. This lets you use the Sedona Tools under each networked Sedona device. See Sedona environment management for details.

Related to this, the JACE also maintains Sedona app files in its station’s file space for each networked Sedona device. Under this Sedona “app store” file space, each device’s “app database” (apps subfolder), can hold one or more app files.

Having all these files on the JACE allows Sedona device provisioning to occur directly from the JACE station, instead of from Workbench. It also allows tasks like Sedona point discovery to be done from the stored Sedona app file, instead of requiring a Sox connection to the device (as for online point discovery). And finally, it allows a station backup to include Sedona device apps as well.

The act of getting a device’s app file onto the JACE, connected with a Sedona device component that represents a specific physical Sedona device is called association. See Association states and Association methods for more details.

For a procedure on “direct” association, see Associating the app file for a Sedona device.