Nebol's Wiki

Let's say that you manually edit the Integration table and set the Status on one of the integrations to 2 (Paused). Nothing will change unless that field is read by the application or service that is currently running your integrations.

The Updating integration periodically checks the database for any changed parameters and updates the in-memory instances of the integrations, healthchecks, triggers and schedules accordingly

This is how to use it:

// now let's add the Updating integration + trigger
engine.Integrations.Add(new UpdatingIntegration(sharpConfig, engine));
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, "_ALPHA"));
engine.Triggers.Add(new UpdatingTrigger(sharpConfig));

on your other service/server:

// now let's add the Updating integration + trigger
engine.Integrations.Add(new UpdatingIntegration(sharpConfig, engine, "_BETA"));
engine.Triggers.Add(new UpdatingTrigger(sharpConfig));

The “_ALPHA” and “_BETA” suffixes will be added to the technical name of the integration and thus make them unique.