Biztalk360 Case Study
Rationale
Both products deal with core Application Health scenarios very well. Good visibility exists when determining the health of an application.
Both products deal with Host Instance health scenarios very well. Good visibility exists when determining the health of a Host instance.
Both products provide capabilities when it comes to determining Host Throttling. However, BizTalk360 provides a more comprehensive experience and allows you to historically go back to determine exactly when and why you were throttling.
Both products provide suitable functionality in this area.
Both applications do provide this support. BizTalk360 provides a very friendly user experience whereas SCOM provides deeper functionality that is found in the SQL Server …show more content…
No top grade though as Message Box Viewer is deprecated and its successor BizTalk Health Monitor should be supported.
No integration exists between Message Box Viewer and SCOM. Custom development is required in order to provide this functionality.
Rationale
Both products receive partial scores for these features. Currently BizTalk360 provides no capability around parsing log files. It does provide support for SQL Server databases but not others.
SCOM does provide support for both Log and Database Monitoring. The downside is that these features often require custom scripts to be written in order to support the requirement. SCOM loses marks on the usability aspects of implementing these functions.
SCOM uses a data warehouse for reporting and long-term data storage. Because of the extended reporting capabilities, though not easy to use, SCOM gets the higher grade.
BizTalk360 provides a customizable Analytics Dashboard and many widgets give insight in the performance and processing of messages through …show more content…
While a SCOM administrator can provide an override when it comes to a Host Instance or Receive Location, if someone starts or enables that BizTalk Service no notifications are generated.
SCOM does provide additional features like running Synthetic Transactions from different servers within the environment. SCOM also provides deeper interrogation of these downstream applications by using .Net Application Performance Monitoring. BizTalk360 provides good capabilities that will satisfy most requirements. Besides checking for expected HTTP return codes, it is also possible to fire custom requests and check for certain responses/response times.
Rationale
SCOM provides broad integration with many other Monitoring Platforms and Service Desk applications.
BizTalk360 integrates with HP Operations Manager, Slack, ServiceNow and provides a simple and elegant way of doing so. One could also develop custom Notification Channels to integrate with other Service Desk applications.
Both products provide this capability. BizTalk360 gets a higher grade for the simplicity of the
Both products deal with core Application Health scenarios very well. Good visibility exists when determining the health of an application.
Both products deal with Host Instance health scenarios very well. Good visibility exists when determining the health of a Host instance.
Both products provide capabilities when it comes to determining Host Throttling. However, BizTalk360 provides a more comprehensive experience and allows you to historically go back to determine exactly when and why you were throttling.
Both products provide suitable functionality in this area.
Both applications do provide this support. BizTalk360 provides a very friendly user experience whereas SCOM provides deeper functionality that is found in the SQL Server …show more content…
No top grade though as Message Box Viewer is deprecated and its successor BizTalk Health Monitor should be supported.
No integration exists between Message Box Viewer and SCOM. Custom development is required in order to provide this functionality.
Rationale
Both products receive partial scores for these features. Currently BizTalk360 provides no capability around parsing log files. It does provide support for SQL Server databases but not others.
SCOM does provide support for both Log and Database Monitoring. The downside is that these features often require custom scripts to be written in order to support the requirement. SCOM loses marks on the usability aspects of implementing these functions.
SCOM uses a data warehouse for reporting and long-term data storage. Because of the extended reporting capabilities, though not easy to use, SCOM gets the higher grade.
BizTalk360 provides a customizable Analytics Dashboard and many widgets give insight in the performance and processing of messages through …show more content…
While a SCOM administrator can provide an override when it comes to a Host Instance or Receive Location, if someone starts or enables that BizTalk Service no notifications are generated.
SCOM does provide additional features like running Synthetic Transactions from different servers within the environment. SCOM also provides deeper interrogation of these downstream applications by using .Net Application Performance Monitoring. BizTalk360 provides good capabilities that will satisfy most requirements. Besides checking for expected HTTP return codes, it is also possible to fire custom requests and check for certain responses/response times.
Rationale
SCOM provides broad integration with many other Monitoring Platforms and Service Desk applications.
BizTalk360 integrates with HP Operations Manager, Slack, ServiceNow and provides a simple and elegant way of doing so. One could also develop custom Notification Channels to integrate with other Service Desk applications.
Both products provide this capability. BizTalk360 gets a higher grade for the simplicity of the