WARNING: This server provides a static reference view of the NetKernel documentation. Links to dynamic content do not work. For the best experience we recommend you install NetKernel and view the documentation in the live system .

A module is a physical container of code and resources. NetKernel and applications are managed at the level of modules; modules can be added, updated and removed from a running instance of NetKernel through the Apposite client. NetKernel uses the physical file modules.xml located in the directory [install]/etc to keep track of deployed modules.

Standard Module

The Standard Module is new with NetKernel 4. It replaces the NetKernel 3 "classic" module, providing more power and flexibility.

A Standard Module must contain the file module.xml which defines the logical structure of one or more spaces. As a physical container, the standard module may contain physical files containing code, compiled code, images, documents, etc.

Each standard module has a globally unique identifier and a version number. NetKernel uses the combination of the identifier and version number to manage the deployment and commissioning of modules on a single NetKernel instance or across multiple instances in an enterprise.