Setting up Failover - Design Phase
eMagiz flows, or more specifically, the flows' inbound components, can be grouped. The benefit from this is that you can later in Deploy, control them as one entity. This is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model.
Building on this functionality, you can even configure the group to run in an active/passive failover mode when you activate the multiple runtimes option on your runtime, and each separate runtime is deployed on another machine. The failover functionality is not only relevant in cases of server maintenance. It can also assist you when you want to exchange data with a system that allows only one active connection. Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).
Setting up this failover functionality in your model requires you to first execute some steps in your Design, Create, and lastly Deploy phase. In this microlearning, we will focus on configuring your setup in the Design phase if you want to activate the active/passive failover configuration.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Prerequisites
- Intermediate knowledge of the eMagiz platform.
2. Key concepts
This microlearning describes how to configure (parts of) of your Design phase to enable failover for your model. The grouping and failover functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists in that case and allows you to have a fallback option on an active connection.
3. Design Phase Configuration
3.1 Solution Design
To configure grouping, we need to open the flow designer of the flow in Create. We want to edit and enter "Start Editing" mode. On the inbound component(s) in the flow, we now have an "Advanced" tab that allows you to configure the grouping information.
3.2 Design Architecture
4. Key takeaways
- Grouping is beneficial when external systems go through maintenance or downtime.
- Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time.
- The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work.
- For the infra configuration of the failover setup, we have a store item that you can use.
5. Suggested Additional Readings
If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: