Starting in AX-3.7 with Sedona Framework TXS-1.2, many Sedona TXS features can be “pushed down” from Workbench to the JACE controller level, allowing the JACE to be the central location for connecting to and provisioning Sedona devices. Included are Sedona device app saves (gets) and backups stored in the JACE station’s file space, allowing a station backup or save to capture the entire system. Also, all necessary Sedona kits, manifests, and platform files can reside on the JACE, independent of Workbench.
As shown in Figure B.1, each networked Sedona device has Sedona Tools that work in this manner. In addition, each Sedona device also has a “Sox Gateway” for access of the device’s Sedona app.
This differs from Sedona device provisioning or app access when using a “direct Sox connection” from Workbench, or if using
a “Tunneled Sox” connection through a JACE. Such connections are shown below.
Direct Sox connection | Tunneled Sox connection |
---|---|
![]() |
![]() |
To support provisioning “through the JACE” (as in Figure B.1), the JACE requires “Sedona environment files” installed, using a !sedona
folder with subfolders for Sedona kit manifests, kits, and platforms.
To install and manage this environment, you use a new platform view on the JACE: the Sedona Environment Manager (Figure B.2).
In this platform view, the left-side shows folders in your local (Workbench) Sedona environment. The equivalent Sedona environment folders on the remote (typically JACE) host are on the right side.
Copyright © 2000-2014 Tridium Inc. All rights reserved.