Skip to content
Contact us

Data Management 

Release 25.04

Ability to write User Mart Execution Meta Data to Azure Service Bus for Integration ETL STP

As of version 25.04, clients now have the option to write User Mart Trigger messages to an Azure Service Bus Queue or Topic in order to enable the initiation of ETL processes downstream of SimCorp Dimension.  

When User Mart data files are written to an Azure Blob Storage Container, a trigger message can also be generated at the time of execution. This message contains various meta data elements related to the execution of the User Mart and corresponding data file.  Information in the file includes, but is not limited to, the location of the data file on the Blob Storage Container, the time it was generated, the number of records.  For user marts executed as part of a Portfolio or Fund STP-initiated Data Warehouse load, the corresponding Fund and/or Portfolio Identifiers are also included.

Prior to 25.04, clients only had the ability to write this trigger data into a file on the same Blob Storage Container as the Result File.However, as of 25.04, this information can now be written to an Azure Service Bus Queue or Topic. This allows clients to read the trigger file information and begin loading the data from the Results File as part of an automated flow.
The User Mart Trigger Messages can be included in any execution user marts within a Data Warehouse Load Plan where the resulting data is being written to an Azure Blob Storage Container:

This includes:

  • Via Portfolio/Fund STP where loads are restricted to data related to a specific Fund and/or Portfolio
  • Manually executed from within the Data Warehouse Manager on all SimCorp Dimension (Not Fund/Portfolio-specific)
  • Execution via batch job

Benefits 

  1. Enhanced automation with Azure Service Bus: Utilizing Azure Service Bus Queue or Topic for User Mart Trigger messages enables the automated initiation of ETL processes, significantly reducing manual intervention and boosting operational efficiency.
  2. Reliable and scalable messaging: Azure Service Bus provides a robust and scalable messaging platform, ensuring that trigger messages are reliably delivered and processed, enhancing overall data integration and processing workflow.
  3. Flexible and decoupled architecture: Writing trigger data to Azure Service Bus allows for a more flexible and decoupled architecture, enabling clients to manage and initiate downstream processes independently of the storage solution, thus enhancing overall system flexibility and maintainability.
Overall Flow

User Mart Trigger messages can be optionally included as part of the User Mart Execution in Data Warehouse

User Mart Trigger Message

Example of user mart trigger message in JSON format which is written to Azure Service Bus Queue or Topic

User Mart Trigger Messages

Users have the option to write either to a Queue or Topic in Azure Service Bus

View Messages on Queue or Topic in Azure

The contents of the message can be viewed directly in Azure Service Bus from the Queue/Topic

Subscription based licensing

Data Warehouse Manager

Sales module dependency

Snowflake Extension for Data Warehouse

Browse the Release Portal

IBOR

Learn more

Front Office

Learn More

Portfolio Analytics & Reporting

Learn More

ABOR

Learn More

Alternative Investments

Learn More

Data Management

Learn More

ESG

Learn More

  • Privacy policy
  • Cookie Policy
  • Terms of Use
  • Trademark guidelines

Copyright © 2025 SimCorp A/S