Ability to monitor SSO service and clustered services
Our BizTalk runs on two application servers and two Db servers. We are facing one problem where we have now clustered our SQL server enterprise single sign on service, so if one of the sql server is down, the SSO sign on service will move to another node.
Earlier the monitoring setup in BizTalk360 was Ent SSO service on both the sql nodes were set as started. Now it is running on one node at a time and the second is inactive. There can be a condition where this node can be down, so other SSO service node will be started automatically. So how to set this monitoring in BizTalk360, so that it can check for active node only on which SSO is running.
Services that are clustered should also be monitored.
- Idea shared by Akash (TCS).
Brian Foley commented
Another example of this is when you have a clustered MSDTC service on your SQL Servers. If you are doing any monitoring from BT360 of your SQL Servers, you will get an alarm notification every time the clustered MSDTC service fails over from one server to another, because BT360 sees this as an orphaned service on the server that the MSDTC service was originally on.