SJAR files are the mechanism for distributing synthetic modules. SJAR stands for “Synthetic Java ARchive.” An SJAR file (.sjar) is a compressed package whose components can be viewed with WinZip or other archive viewing tool. With synthetic modules and types, there is no source code, and no compiling. Rather than being loaded from precompiled module files, the Java byte code for these modules is generated in memory at run-time. This means that you no longer need to know Java or be an experienced software developer to create modules and types.

Synthetic modules can be created and edited from anywhere in the file system, however they must reside in the modules folder of the Niagara installation to be used by the station or Workbench. Also, Workbench uses the synthetic module icon () to distinguish synthetic modules from non-synthetic ones.

After creating a synthetic module, you have a new .sjar file at the designated location under the SysHome node that is loaded in memory but it is basically empty. You must edit the module to customize it and make it usable. As with standard (.jar) modules, whenever a synthetic module is modified the station or Workbench must be restarted in order for those changes to take effect.

All synthetic (.sjar) modules: