Application control buttons

For the selected station in the Application Director, application control buttons apply as follows:
 
NOTE: Be careful about using station controls, and understand the difference between them before using them.
 
  • Start

    Enabled if the selected station has an “Idle” or “Failed” status in the “installed applications” area. When pressed, that host’s platform daemon immediately starts that station. Text in the “station output” area is cleared, and output messages begin with the new startup of that station.

     
    NOTE: If you manually stop a station on a AX JACE (using Stop button), it has a status of "Halted." In this case, the Start button will not be available. You must Reboot the platform to restart the station. This differs from a manually stopped station on a Windows-based host or Linux-based Supervisor, which then shows a status "Idle."
     
  • Stop

    Enabled if the selected station has a “Running” status in the “installed applications” area. When pressed, a popup confirmation appears. If you confirm, the host’s platform daemon shuts the station down gracefully (saving configuration to its config.bog file, and potentially saving history data).

  • Restart

    Enabled if the selected station has a “Running” status in the “installed applications” area. When pressed, a popup confirmation dialog appears. If you confirm, the host’s platform daemon shuts the station down gracefully, then restarts it.

  • Reboot

    Always enabled. When pressed, a popup confirmation dialog appears. If you confirm, the selected host is rebooted. This is considered a drastic action. For details, see “Reboot”.

  • Kill

    Enabled only if the selected station has a status of “Starting”, “Stopping”, or “Running” the “installed applications” area. When pressed, a popup confirmation dialog appears. If you confirm, the host’s platform daemon terminates the station process immediately.

    Always use Stop instead of Kill, unless unavailable (stuck for a long time as either “Starting” or “Stopping”). Unlike a station stop, a station kill does not cause the station to save its database (config.bog), histories or alarms, nor does it update the “station output” area.

  • Dump Threads

    Enabled only if the station has a “Running” status in the “installed applications” area. When pressed, the host’s platform daemon has the station send a VM thread dump to its station output.

  • Save Bog

    Enabled only if the station has a “Running” status in the “installed applications” area. When pressed, the host’s platform daemon has the station locally save its configuration to config.bog.

  • Verify Software

    Enabled regardless of station status. When pressed, Workbench parses the station’s config.bog file and the host’s platform.bog file, looking for module references. Workbench then checks to see if those modules (and any other software upon which they depend) are installed. Any missing software is listed in a popup dialog, and if available in your Workbench installation, the dialog offers to install the missing software into the remote host.

    Only modules (or versions of modules) needed by the station are installed that do not require commissioning. If the station needs modules that require commissioning, meaning an upgrade of core Niagara software, those modules are not copied.