This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
nebolintegration_builtin_integrations [2021/09/27 01:38] – created nebol | nebolintegration_builtin_integrations [2021/09/27 02:04] (current) – nebol | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ==== NebolIntegration: | ||
+ | === Updating === | ||
- | The Updating integration periodically checks | + | Let's say that you manually edit the Integration table and set the Status on one of the integrations |
- | for any changed parameters | + | |
- | of the integrations, healthchecks and triggers accordingly | + | |
+ | The Updating integration periodically checks the database for any changed parameters and updates the in-memory instances of the integrations, | ||
+ | |||
+ | This is how to use it: | ||
+ | |||
+ | < | ||
+ | // now let's add the Updating integration + trigger | ||
+ | engine.Integrations.Add(new UpdatingIntegration(sharpConfig, | ||
+ | engine.Triggers.Add(new UpdatingTrigger(sharpConfig)); | ||
+ | </ | ||
+ | |||
+ | Note that you're supplying the engine instance to the integration. This is so that the integration can communicate with the engine. | ||
+ | |||
+ | Also note that if you're running multiple engines on the same database you will need to run multiple Updating integrations aswell! You can do this by modifying the TechnicalName of the Updating integrations like so: | ||
+ | |||
+ | < | ||
+ | // now let's add the Updating integration + trigger | ||
+ | engine.Integrations.Add(new UpdatingIntegration(sharpConfig, | ||
+ | engine.Triggers.Add(new UpdatingTrigger(sharpConfig)); | ||
+ | </ | ||
+ | |||
+ | on your other service/ | ||
+ | |||
+ | < | ||
+ | // now let's add the Updating integration + trigger | ||
+ | engine.Integrations.Add(new UpdatingIntegration(sharpConfig, | ||
+ | engine.Triggers.Add(new UpdatingTrigger(sharpConfig)); | ||
+ | </ | ||
+ | |||
+ | The " |