The Software container under the ProvisioningNwExt provides a “window” into the Supervisor’s software registry (installable software files stored under its !sw directory), and is populated by components that represent these files. When the service starts (station startup), it starts a thread that scans the software registry and populates this container. The Software container also lists software files added to the registry after the initial scan.

Direct children of the Software container are summary objects (InstallableSummary components) for named, typed software files (for example, file type module named “baja”). For each summary object, there is a specification object (InstallableSpec components) for each version in the registry.

Apart from these summary children, the Software container has but a single frozen property: “loaded”, a boolean slot indicating if the startup thread has finished scanning the registry (by default, it is hidden). Your key interface to the Software container is its default view: the Supervisor Software Manager.