Some functions of AggreGate Server are implemented using plugins. AggreGate Server supports several types of plugins for communicating with different Devices, adding new contexts to a server context tree, building custom reports, localizing and customizing textual and graphical resources etc.
|
NEW TERM: A Plugin is a computer program that interacts with a main application (a web browser or an email program, for example) to provide a certain, usually very specific, function on-demand. |
All plugins are loaded by the server at startup. They are located in the /plugins subfolder of the AggreGate Server installation folder. To install new plugin, simply copy plugin archive into the corresponding subfolder of /plugins and restart AggreGate Server. When installing new version of existing plugin received from Tibbo, overwrite the old plugin archive with a new one.
Every plugin has up to two levels of settings:
| • | Global Settings. These affect the default behaviour of plugins. Global settings may be edited only by users with sufficient permissions. |
| • | User-level Settings. These affect the behaviour of a plugin only when its actions are related to a certain user account. |
Many plugins have global settings only or no settings at all.
Administering Plugins
Two contexts are used to administer plugins: One is the general Drivers/Plugins Configuration context, which serves as a container. The other is the Driver/Plugin Configuration context, which holds the configuration for one plugin. There are two types of plugin configuration containers: global container for global settings and user's personal container for storing plugins settings related to a certain user account. |
|
Enabling/Disabling Plugins
Individual plugins may be enabled or disabled using Active Plugins server global configuration option.