Modules are the primary method for extending the core Partner Platform. They are a pluggable component that can contain subcomponents to extend many aspects of the Partner Platform.

These include:

  • Java libraries
  • native libraries and applications
  • app scripts
  • mapset definitions
  • Cog schema datatypes
  • system event listeners
  • workbench actions
  • templates
  • script libraries
  • general resources

Like the containing Partner Platform, modules have a well-defined filesystem for storing these subcomponents and files. Modules also have a lifecycle that governs how they are loaded, initialized, and used within the Partner Platform.

As the Partner Platform has matured, many components that were formerly part of the core Platform have migrated to modules, leaving the core Platform leaner and more flexible.

Modules may be developed and distributed by Partner Software itself, or by certified third-party developers or even Partner customers. They are the only mechanism for extending and customizing the Partner Platform that Partner will support - modifying the core Platform or Partner-developed modules is highly frowned upon, for what are good and hopefully obvious reasons.

Previous topic


Next topic

Module Filesystem And Structure

This Page