<aside> 🧭

Navigation:

• Architecture & AI & Documents Indexers
• Architecture & Monitoring : Measuring Performance issues of Dynamics 365 with Dynatrace and StresStimulus
• Architecture & Integration : Power Platform & SAP
• Resiliency & Architecture for integration service between Power Platform and SAP
• Resiliency for Autonomous Service (Power BI & Power Platform)
• Microsoft 365 Copilot Early Access Program
• Migration/Synchronization Plan from SQL Server On-Premise to Microsoft Fabric

</aside>

The architecture of resiliency is based on the solution which has been selected regarding the technical constraints inside our Business Unit : Integration from SAP to Power Platform.

1. The schedule will trigger the listener.
2. The listener will ping the sever A (main server in which the app has been deployed).
3. The listener will after that, ping the file server in which the API Manager deploys the files (SAP data).
4. Regarding the following use case (Server A is offline), the listener will trigger the app deployed in the Server B (same server than the listener).
5. The second app will insert, update or delete data in the power platform environment.
6. Meanwhile, the listener will log information regarding the process.

Monitoring of the process using Power Automate

The log generated in the dataverse will trigger an automated process (Power Automate) in order to send an email to the main addresse or the owner of the process (STEP 7).

Starting the process of the resilient app in server

The instanciation of the [Process] class will allow to start the process associated with the app deployed in the same server. The process will use the data with which th start the process.