When it is time to install new software on all hosts in a network, you can use provisioning to speed the process of upgrading
each remote host. This procedure uses the add button.
Prerequisites: The Niagara Network Job Builder (for a one-time job) or the Niagara Network Prototype View (for a prototype job) is already open.
Perform the following steps:
- If you are using a remote PC, connect to the
Supervisor station.
- In the Niagara Network Job Prototype view, click the
(add) button to add the Install Software step to the job.The system opens the Install Software window in which you select the software modules or .dist files to install.
- Click the triangle to expand an artifact to display available module version numbers. Select the version(s) and click OK.
NOTE: In
Niagara 4.8 and later, in the
Install Software window there is added support for filtering the list of available artifacts for installation (by version or module name),
and for making multiple selections of artifacts for installation in a single provisioning step. The Install Software Step
will install all modules selected from the
Install Software window.
- To filter available artifacts, click in the text box next to the
(Filter icon) and start typing the artifact name (as shown) or version. The list of available artifacts will automatically
be filtered to match the search string.
- To make multiple selections, press the
Ctrl key while you click on multiple artifacts.
Once added, the Install Software step appears in the
Job Steps List.
To satisfy dependencies, if the software has dependencies on one or more modules that are not yet installed on a particular
host, and the modules are in the
Supervisor’s software registry, the step automatically includes the modules in the processing for host (station).
NOTE: It is your (provisioning user’s) responsibility to ensure that platform dependencies of the software are met by the hosts
running the target stations. For example, it is permissible to have a job with an Install Software step that includes stations
running on different platform types. However, if a step installs a distribution file specific to one type of controller, note
that the dependency check may fail on a different type of device, with no software being installed on that host.
A slightly different step (InstallStep) is created when you copy/drag a backup .dist file into the Job Steps List. A backup .dist is not a versioned install (nor is it a FileCopyStep).
To run the provisioning job more efficiently, the system combines Install Software steps with other software install steps,
copy file steps, and upgrade out-of-date-software steps.