This selection from the Platform Administration view lets you globally change the “module content level” of the connected platform. This affects how much file space is consumed by installed Niagara modules.
-
For any Windows-based host (providing it has hard drive for file storage), you typically want the fullest possible content level, meaning including all documentation (doc+ui+runtime).
-
For a QNX-based JACE, with more limited flash-based file storage, you may wish to change module content level. Selection produces the Update Module Content Filter dialog (Figure 60).
Typically, you specify the module content level once during initial JACE commissioning, then never change it.
Module content level is one of the following, from largest to smallest:
-
doc+ui+runtime— Typically appropriate only for Windows-based platforms. -
ui+runtime— Appropriate for any JACE that is to run the Web Service. This is typical for any “standalone” JACE, as well as any JACEs that serve PxPages directly to browser clients. -
runtime— Typically only for a QNX-based JACE not running Web Service (all PxPages served instead by a Supervisor).
Operations from a change in module content level differ according to the “direction” of the change.
Depending on how you change the module content filter level, operations on the platform vary:
-
If you restrict the content level (say, go from “
ui+runtime” to “runtime”), modules already installed are not automatically re-installed (to reduce storage). You simply click the button to close the dialog, and platform/station operation is otherwise unaffected. However, if you later re-install existing modules, or install new modules, the new content filter level is applied—typically with resulting savings in storage space.Therefore, if “freeing” storage space is the goal when restricting module content, after changing the content level, you should re-install existing modules. Do this using the Software Manager.
-
If you increase the content level (say, from “
runtime” to “ui+runtime”), this typically requires modules to be re-installed in that platform. In this case, the dialog provides a button and explains that this automatically occurs, with the station first stopped as a result, as shown in Figure 61. Note that if a QNX-based platform, this also automatically results in a reboot of that host platform.
