Search: "Failover"
Last modified by Rico Kieboom on 2022/04/11 14:18
Refine your search
Select a category and activate filters on the current results
Last modification date
Failover - Configuration
Located in
- Title
Failover - Configuration
- Location
-
…
Grouping and Failover
…intermediate-grouping-and-failover-setting-up-failover-design-phase
- Raw document content
Failover Configuration == === 3.1 Solution Design === To configure failover for systems that are connecting with your model, we first need to go to the Design phase.
…Afterward, you will see the "Number of runtimes" and "Run in failover" fields. To enable failover, make sure that you fill in 2 as the "Number of runtimes", before selecting the "Run in failover" checkbox.
…[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-solution-design.png]] {{info}}Systems with the failover option enabled must have "Number of runtimes" exactly two and must be placed on an external machine in the Architecture panel.
212 - Failover Fiesta
Located in
- Rendered document content
Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done.
…Create - Flow Designer: New components have been created to support a failover setup. More information can be found here. Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found here.
- Title
212 - Failover Fiesta
- Location
-
…
212 - Failover Fiesta
- Raw document content
Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done. Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. ====New features==== * Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. * Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. * Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment.
Failover - Deploy Possibilities
Located in
- Title
Failover - Deploy Possibilities
- Location
-
…
Grouping and Failover
…intermediate-grouping-and-failover-setting-up-failover-deploy-phase
- Raw document content
{{/warning}} [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]] Notice that here you can find the "Internal IP address" and "Failover port" fields, which have been pre-filled in with property placeholders.
…[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-deployment-plan.png]] === 3.4 Deploy Release === Once you have configured your Deployment Plan, then it is time to create a new release for your updated flows in the Deploy>Release page.
…[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-properties.png]] When you are done, then you can save your changes, and proceed with creating a new release.
Active/Passive Failover
Located in
- Title
Active/Passive Failover
- Location
-
…
Active-Passive Failover
- Raw document content
{{container}} {{container layoutStyle="columns"}} ((( == About == This store item can easily add the required configuration to your infra flow to make the active/passive failover functionality possible within the runtime context. == Documentation == ==== 1. How to use==== With the help of this store item, you can make the active/passive failover functionality possible within the runtime context. ==== 2. Keynotes & restrictions==== * Note that you also need to define the correct settings in each flow to group flows together that need to use the active/passive failover functionality. * When using this configuration you can only create groups within the context of a single runtime.
212 - Failover Fiesta
Located in
- Title
212 - Failover Fiesta
- Location
-
…
212 - Failover Fiesta
- Raw document content
Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions. == **Cloud Template R20 - Double Lane** == This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup.
…The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]]. == **Feedback Items** == //__Failover setup__// New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment.
…To end this post, here are some key takeaways for you: * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] * If you have feedback or ideas for us, talk to the Platypus * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. * Clear your browser cache (Ctrl + Shift + Del) * Check out the release notes [[here>>doc:Main.Release Information.Portal.212 - Failover Fiesta.WebHome||target="blank"]] * Start thinking about how the license tracker can aid your development * Start thinking about major, minor, and patch * Keep making great integrations Let's stay in touch and till next time!
R10 Docker - Double lane
Located in
- Rendered document content
Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker. Process We upgrade in one step to use the new R10 release of the cloud template.
…Overview It adds the possibility of hosting an MQTT broker in a failover setting. Updates Run an MQTT broker in a failover setting Update Steps Use the final template (non-service affecting) (duration: 10 minutes) This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
- Raw document content
Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker. **Process** We upgrade in one step to use the new R10 release of the cloud template.
…**Overview** It adds the possibility of hosting an MQTT broker in a failover setting. **Updates** * Run an MQTT broker in a failover setting **Update Steps** * Use the final template (non-service affecting) (duration: 10 minutes) ** This step will update your cloud slot configuration to allow an MQTT broker with failover settings. * User actions after applying the final template: ** Check if all runtimes are reachable by Deploy Architecture. ** Check if all flows have been installed according to the active release. ** Check if messages pass through the model by verifying a critical message flow in external systems.
230 - Petite Peaks
Located in
- Rendered document content
New features All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step.
- Raw document content
====New features==== * All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step.
233 - Policy Polish
Located in
- Rendered document content
Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment.
…We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture.
- Raw document content
This release, we have done several improvements for our Failover functionality and added two configuration options for our SMB session factory support objects.
…This effectively disables backwards-compatible version negotiation. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas. ** We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture.
234 - Alert Adventures
Located in
- Rendered document content
Lastly, we have improved the selection visibility in data models, and have fixed a bug regarding failover containers. Please find out more on our Release blog.
…Bug fixes Deploy - Architecture: The failover container will now be shown correctly.
- Raw document content
Lastly, we have improved the selection visibility in data models, and have fixed a bug regarding failover containers. Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]].
…====Bug fixes==== * Deploy - Architecture: The failover container will now be shown correctly.
214 - System Symphony
Located in
- Rendered document content
In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days.
…Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
- Raw document content
In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days.
…====Bug fixes==== * Create - Flow Designer: The help text of the Group attribute has been improved. * Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) * Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
next page »
Page
1
2
3
4
5
RSS feed for search on ["Failover"]