Scheduled Engine Invocation
IXM Engine Config from earlier in the document spoke about the config as a way of setting up the configuration for when the engine is run.
But it’s also capable of control when engines are executed. This is actually not stored in the IXM engine config table, but instead, it's part of the DVC Schedule Entry (similar to workflows).
A key technique is to schedule a chain engine (next section) and have the chain specify the order all the engines that do real work in the order they need to be executed.
<ScheduleName>SampleSchedule</ScheduleName>
<ScheduleDef> <![CDATA[ <ScheduleDef
xmlns=
"http://www.onenetwork.com/Platform"
> <RepeatingSchedule>
<IntervalInMinutes>
100
</IntervalInMinutes>
<OffsetFromHourInMinutes>
0
</OffsetFromHourInMinutes>
</RepeatingSchedule> </ScheduleDef> ]]>
</ScheduleDef>
Changes to this configuration are sent to the server when you execute the load data and target on the dataset or when you click the Submit to ONE Network button in the studio.