This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
nebolintegration_builtin_integrations [2021/09/27 01:48] – nebol | nebolintegration_builtin_integrations [2021/09/27 02:04] (current) – nebol | ||
---|---|---|---|
Line 10: | Line 10: | ||
< | < | ||
- | WIP | + | // 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. | ||
- | Note that if you're running multiple engines on the same database you will need to run multiple Updating integrations! You can do this by modifying the TechnicalName of the Updating integrations like so: | + | Also note that if you're running multiple engines on the same database you will need to run multiple Updating integrations |
< | < | ||
- | WIP | + | // 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 " |