Atomia Billing Server

Plug-in configuration

42 views 0

Overview

The configuration settings of plug-ins are placed into two tables of the Atomia Billing database:

  • plugin – contains all registered plug-ins, and
  • plugin_configuration – contains additional plug-in data.

Structure of plugin table:

COLUMN NAME DESCRIPTION
id Unique identifier of the record.
name Unique name of the plug-in (used to reference this record).
full_class_name Class that implements the IPlugin interface, in format <class name>, <dll file that contains class>.
enabled Enables and disables the plug-in, when set to 0 plug-in is disabled.

Here is an example of a plug-in configuration:

COLUMN NAME EXAMPLE
name CampaignPlugin
full_class_name Atomia.Billing.Plugins.CampaignPlugin, Atomia.Billing.Plugins.CampaignPlugin
enabled 1

Additional plug-in configuration data is stored in the plugin_configuration table which has following structure:

COLUMN NAME DESCRIPTION
id Unique identifier of the record
fk_reseller_id Unique identifier of the reseller
key Parameter name
value Parameter value
fk_plugin_id Unique identifier of the plugin

Configuration example

The following table shows an example of the PaymentRule plug-in configuration which has two parameters (HighBound and LowBound):

ID FK_RESELLER_ID KEY VALUE FK_PLUGIN_ID
9D3AFAB0… B77B8B91… HighBound 20;1000SEK F7D5B3D8…
DFCAD78C… B77B8B91… LowBound 1;4SEK F7D5B3D8…

Was this helpful?