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.

Import vs. copy into modules

Related Links