Name Description Health BizTalk Deployment A group that contains multiple runtime servers with components such as runtime rule engine. Health of this group depends on the availability of  BAM Role  BizTalk Host deployment  BizTalk Run-time Role  Rule Engine Rule BAM Role A server on which BAM component is installed. Health of this depends on the BAM Run-time Role and BAM Portal. BizTalk Host Deployment A logical entity defining the runtime parameters or boundaries for the various application artifacts to run. Several instances of this (host instances) run as NT services on different runtime servers. Health of this group depends on the availability of different instances of this host. BizTalk Run-time Role A server where BizTalk is installed. Health of this group depends on the availability of  SSO Service  Management Database  MessageBox Database  SSO Database  Tracking Database Rule Engine Role A server which has rule engine installed. Health of this group depends on the availability of Rule Engine Service and Rule Engine Database  Rule Engine Service  Rule Engine Database BAM Run-time Role A server on which BAM component is installed. The health of this depends on the availability of  BAM Primary Import Database  BAM Archive Database time
 BAM Analysis  BAM Alerts BAM Portal A Web Server which has BAM portal application installed and configured. The health of this depends on the availability of BAM portal application. Host Instance A Windows NT service configured to run on BizTalk Run-time server. The health of this is depends on the state of Windows NT service. SSO Service A Windows NT service for SSO. The health of this is depends on the state of SSO service. Management Database A SQL Server that contains one or more BizTalk databases. The health of this is depends on the availability of SQL Server database availability. MessageBox Database A SQL Server that contains one or more BizTalk MessageBox databases. The health of this is depends on the availability of SQL Server database availability. Rule Engine Service A Rule Engine Service which is used to process BizTalk rules. The health of this depends on the availability of Rule Engine Service. Rule Engine Database A SQL Server that contains one or more BizTalk Rule Engine databases. The health of this is depends on the availability of SQL Server database availability. BAM Primary Import Database A SQL Server that contains BAM databases. The health of this is depends on the availability of SQL Server database availability. BAM Archive Database A SQL Server database that contains archived data. The health of this is depends on the availability of SQL Server database availability. BAM Analysis Contains both offline and online BAM analysis data. The health of this is depends on the availability of BAM analysis data. BAM Alerts A SQL notification service. The health of this is depends on the state of notification service. BAM Service A SQL notification service. The health of this is depends on the state of notification service.
Manager event log after agent restart. Objects discovery related warnings in the Operations Manager event Log When a discovery (including relationship discovery) fails to find an instance, a warning is written to the Operations Manager event log stating that null was returned by the discovery script. Alerting in physical node in clustered environment is unreliable There are two known issues associated with monitoring in clustered environments:  When a node changes from active to passive, the monitoring status of the node and associated artifacts may not be reflected correctly in the Operations Console.  In clustered environments, the Operations Manager creates a virtual node which may display duplicate status and alerts. In clustered environments that contains active/passive nodes; rely on the monitoring information displayed in the virtual node only. This is because the virtual node always points to the physical node that is active at any point in time. Relationships and Dependency monitors The following are the known issues related to relationships and dependency monitors: This occurs mostly when the BizTalk Management Pack is re-imported on a given SCOM Server. The user is then required to see comment the previous state as given in the "Steps to Reproduce the Behavior" section.  Relationships between BizTalk artifacts are not discovered.  Dependency relationships are not displayed as expected. The workarounds to address these issues are as follows:  Restart the Operations Manager Health Service on the BizTalk machine. -OR-  Run the Flush Health Service State and Cache task. The steps to do this are as follows: a. In the navigation tree, select Operations Manager Agent Agent Health State. b. Select the computer that is running BizTalk