While software modules are usually part of a Niagara installation .zip file, you may receive additional modules
separately.
You are working in Workbench and are connected to your Supervisor PC or workstation.
The modules to import are available in another location on the PC.
When receiving updated or new module .jar files, you have
two basic options when copying them to your Workbench PC:
You may copy the modules directly into your !/modules folder. This makes the module(s) available to your Workbench environment, and also available to install in
other remote platforms (when the installer runs, it copies the module(s)
into your software database, making them available for remote platform
installation). This is the typical choice.
You may update the software database by copying the modules
or .dist files into your computer’s !/sw/inbox folder. In this case, your Workbench environment does not use the module(s) themselves,
but makes them available in the software database for installation
in remote platforms. This would be the choice where you want to keep
using a newer (or older) version of the received module(s) in your Workbench environment. A scenario that fits here is if
you received older versions of modules, perhaps needed to restore
an older backup .dist file in a certain remote platform.
Copying the modules to the computer’s !/sw/inbox is equivalent to using the Import button
in the Software Manager, which this procedure
documents.
- Expand the Platform node in the
Nav tree or double-click Platform.
The contents of the Nav Container View opens in the tree
or in the main view.
- Double-click Software Manager.
The
Software Manager view opens.

- Expand the drop-down list of the Import button.
The list provides three options.

Import software from files opens the
standard File Chooser from which you can navigate
to the module location and select one or more software files for import.
Import software from directory the standard Directory Chooser with which to navigate to and select
a directory for inclusion of any contained software files. For example,
you might do this for an earlier installed software build, selecting
its sw folder or a portion thereof.
Import software from remote host opens
the standard Import from Platform window in which
you can navigate to the location and select one or more software files
for import.
- Select one of the options.
Upon import, the
Software Manager builds or re-builds the software list. Popup windows open while
software files are being copied. Afterwards, any modules that are
newer-versioned, or that did not previously exist, are represented
in the software table.
If imported modules are earlier versions,
they are also available for installation.
When you add different-versioned
installable files, the number of different subdirectories under your sw directory increase. By default, the Software
Manager displays only the most recent version of any module
as the Avail. Version.
Older software
files (modules, .dists) are also useful in your software database
when restoring a backup .dist for the controller, if the backup was
made using a previous software release. You use the platform Distribution File Installer to restore a backup.