Fault Tolerance options can be set only for TIBCO BusinessWorks processes. TIBCO Adapter services cannot be assigned fault-tolerant options. You can start one or more process engines in the FT group. If more than one engine has started, only one is displayed as Running and all other engines are displayed as Standing By.
I have deployed the same BW process instance twice on my machine which are available in admin as shown below:
We can use the JMS_Controller:getServerInfo method to monitor the FT failover and develop a rulebase which triggers the mail.
Tibco support doesn’t provide best practices to implement FT in Tibco adapters but advice to use Hawk to implement this. In this case, you can send messages on the bus under certain circumstances on one server and on the other services you can get such messages to trigger your local hawk rules. About cross-referencing engines deployed on different servers we have messaging micro agent in hawk.
As we know, a hawk agent can use and invoke only the micro-agents available on its own machine. To create dependencies across several servers we need extra methods like for example messaging micro agent.
The common way is, to use a script that runs the application and you could execute this script from Hawk as part of the action part,( invoke the script with custom micro agent) by testing for that specific application process count == 0.
Another way if your application can run like a service in Win platform, start the service (form Services micro agent)
Ravindra Savaram is a Content Lead at Mindmajix.com. His passion lies in writing articles on the most popular IT platforms including Machine learning, DevOps, Data Science, Artificial Intelligence, RPA, Deep Learning, and so on. You can stay up to date on all these technologies by following him on LinkedIn and Twitter.