Run the Manifest Manager to ensure kit manifests are loaded

NoteStarting in Sedona TXS-1.2, the importance of a Sedona network’s Manifest Manager has diminished in favor of installing the complete set of “Sedona environment files” required by networked Sedona devices on the NiagaraAX platform hosting the station. This includes not only kit manifests, but also kits and platform files. This permits Sedona device provisioning “through the station”, in addition to support for proxy points. Therefore, you can safely skip this section—and instead install Sedona environment files. For procedures, see sections JACE workflow and Installing Sedona environment files in a JACE in the Sedona Framework Network Driver Installation section.

To support Sedona proxy points, the NiagaraAX host (typically JACE) running the station with any Sedona Framework network requires all the Sedona “manifest” files for all the kits in each type of networked Sedona Framework device. These are the same manifest files required on your NiagaraAX Workbench host to support a Sox connection (or a tunneled Sox connection) to these devices.

NoteThe following quick start procedure assumes you already have all the necessary kit manifest files on your Sedona-enabled NiagaraAX Workbench host, located in the “manifests” subfolder of your working “sedona.home” (starting in AX-3.7, sedona.home is invariably !sedona). For the purposes of this procedure, consider this collection of manifest files your “Local Database”. Complete details on Sedona manifests and using the Manifest Manager are in the Sedona Framework Manifest Manager - Engineering Notes document.

To run the Sedona Manifest Manager for the Sedona Framework network

This procedure applies to either Sedona Framework network type (SedonaNetwork or SedonaJen6lpNetwork), and results in the identical view and selections.

  1. With the station opened, right-click the SedonaNetwork or SedonaJen6lpNetwork and select: Views->Manifest Manager. This brings up the Manifest Manager.

    The left side of the view is your “Local Database”; the right side is the “Station Database”.

  2. Right-click in the (far left) Manifests column of your Local Database and choose Select All.



    All kits in the Manifests column become highlighted, as shown above.

  3. Right-click in the Checksums column of your Local Database, and choose Select Missing.



    This typically results in one or more Local Database “Checksums” entries becoming highlighted, which you can see by scrolling down that column, as shown below. In some cases it may result in all entries selected (usually this is OK, as these files are small and do not use much space).

    Figure 8. Manifests in the Local Database but missing in the Station Database are highlighted


    Manifests in the Local Database but missing in the Station Database are highlighted

    The “Local Database” to “Station Database” manifest copy button also becomes enabled.

  4. Click this copy button to copy the manifests to the station’s host.

    This produces a confirmation dialog listing the manifest files to be copied, as shown below.



  5. Click OK to copy the manifest files to the station’s host.

    The manifests are transferred and are now immediately available in the hosting station to support Sedona proxy point operations, such as online point discovery (no station restart required).