How integrations work
Systems, groups, identities and data properties, what happens when a group runs, and how each curve or timeseries is judged
Systems, groups, identities and data properties, what happens when a group runs, and how each curve or timeseries is judged
The downstream systems that have a ready-made Integration plug-in, what each one sends, and where to find its guide
Where integrations are kept, the formats of the group settings, secrets, processes, report configuration and report data, writing a plug-in extension, and troubleshooting
Writes curves, timeseries and options as CSV or JSON files to a container in Azure Blob Storage
Writes curves, timeseries and options as CSV or JSON files to a file system in Azure Data Lake Storage Gen2
Publishes an event to an Azure Event Grid topic for each curve and timeseries sent
Writes curves, timeseries and options as CSV or JSON files to an Azure Files share, for systems that read files from a network folder
Sends curves, timeseries and options as JSON messages to one of your company's platform queues (Azure Service Bus), for any system that reads the queue
Sends curves and timeseries to the Molecule ETRM marks API as marks, one per contract or per quarter hour, including clock changes
Pushes the values of curves, timeseries and options as rows to a Power BI streaming or push dataset
Posts curves, timeseries and options as JSON to a webhook or HTTP endpoint
An introduction to the Integration extension, which sends groups of curves and timeseries to downstream systems such as ETRMs, risk engines and data lakes on a schedule, with a daily report of what was sent
The item messages, group messages, Event Grid events, CSV rows and file names of the generic Integration plug-ins