Fault tolerance is ability of a system or an application to gracefully cope with an unexpected situation and continue its services as normal. For applications developed and deployed in TIBCO, Fault tolerance can be achieved by using multiple machines with primary, secondary relationship. In this tutorial, I’ll explain how you can run your services and processes in TIBCO administrator in FT mode to ensure high availability.
Let’s go step by step to run our application in Fault Tolerant mode in TIBCO administrator.
Step 1: Add Process to multiple machines
Fault tolerance can be achieved for a TIBCO process only if process has been added to at least two different machines. In order to add a process in multiple machines, go to Application Management–>Application Name–>Configuration–>Process Archive.par–>General
Now click on Add to Additional Machines option. Choose the machine where you want to additionally deploy the process and then click Apply/Save button.
Step 2: Configure FT Group Settings for a TIBCO Process
After adding a process to multiple machines, second step is to configure FT group. Under FT Group Settings, check Run Fault Tolerant option.
Specify Heartbeat Interval in milliseconds. Heartbeat interval is the time after which primary/master engine sends a broadcast message to all secondary/slave engines to inform them about its liveliness.
Then specify Activation Interval. This field specifies the amount of time to expire since the last heartbeat from the master before the secondary restarts the process starters and process engines.
Then specify Activation Delay. This field is used to specify a delay before the master engine restarts after coming up from a crash. This delay is useful to ensure a clean shutdown of secondary engine before resumption of primary engine.
Now we need to specify master-child or peer-peer relationship. For this, Under the FT Weight column select one process instance as Primary and the remaining instances as secondary.
Members of a fault-tolerant group can be configured as peers or as master and secondary engines. If all engines are peers, when the machine containing the currently active process engine fails, another peer process engine resumes processing for the first engine, and continues processing until its machine fails. If the engines are configured as master and secondary, the secondary engine resumes processing when the master fails. The secondary engine continues processing until the master recovers. Once the master recovers, the secondary engine shuts down and the master takes over processing again.
Now your Fault Tolerance configurations are done. Deploy the services and your server is ready in FT mode.