Software Import

As shown in Figure 73, an Import button at the bottom of the Software Manager provides two menu choices for you to add new (or earlier) installable software files (module .jars, .dists) in your software database.

Also see the next section, Import vs. copy into modules.

Figure 73. Import choices to bring in file(s) or entire folders

The two import options are:

Import software from files

This produces the standard File Chooser dialog, in which you navigate to the proper location and select one or more software files for import.
Import software from directory

This produces the standard Directory Chooser dialog, in which you navigate to the proper location and select a directory, for inclusion of any contained software files. For example, you might do this for an earlier installed build of Niagara, selecting its “sw” folder, or a portion thereof.

Upon import, the software list is again rebuilt by the Software Manager (popup dialogs appear while software files are copied). Afterwards, any modules that are newer-versioned, or that did not previously exist, will now be represented by default in the software table.

If imported modules are earlier versions, they are also available for installation in the Software Manager. See Right-click option to install earlier version.

Import vs. copy into modules

When receiving updated or new module jar files (say sent from Systems Engineering or downloaded from Niagara Central), you have two basic options when copying them to your Workbench PC, as follows:

Copy directly into your !/modules directory. This makes the module(s) available in your Workbench environment, and also available to install in other remote platforms (when the installer runs, the module(s) are also copied into your software database, available for installation). This is the typical choice.
Copy into your !/sw/inbox directory (or, use the equivalent Software Import feature in the Software Manager). In this case, the module(s) are not used in your Workbench environment, but are available in your 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.