This document discusses monitoring on-premise BizTalk applications using cloud-based Power BI SaaS. BizTalk was used for real-time and batch processes integrating various systems like Guidewire, OnBase, and a customer portal. Power BI was chosen as the monitoring solution because it provided rich dashboards and reports without requiring installation. Key performance indicators like volume, duration, message size, and throughput were monitored from BizTalk and other data sources. Alerts were generated when service level agreements were not met. The demonstration showed important visualizations and alerts in Power BI for monitoring a business process.

1. Sponsored & Brought to you by
Monitoring on premise BizTalk
applications using cloud based
Power BI SaaS
Jaidev Kunjur
https://www.linkedin.com/in/Jaidev-Kunjur-63961015

2. Monitoring on premise BizTalk applications
using cloud based Power BI SaaS
Jaidev Kunjur
jkunjur@enkaytech.com
www.enkaytech.com
9/13/2016
2

3. 9/13/2016
• Introduction
• Demo
• Q&A
Agenda
3

4. 9/13/2016 4
Guidewire
• Claims Center
• Policy Center
• Billing Center
OnBase
Document
Management System
Source HOV
Document Creation
System
Customer Portal
• Claims
• Policies
• Bills
• Certificates
Legacy
Document
Storage System
BizTalk Enterprise Service Bus (ESB)
Other
Applications
What was BizTalk used for?
Real-time Processes
• GW to OnBase
• Doc archive
• Doc retrieve
• Doc update
• Doc delete
• GW to SHOV
• Create
template
• Customer Portal
• Search and
retrieve from
either TCI
and/or OnBase
Batch Process
• GW to SHOV to
OnBase

5. Why Power BI?
9/13/2016 5
• We needed an easy to use monitoring solution for the 7x24 Network Operations Center staff (who had no knowledge of BizTalk)
and were the first to be called if business users were experiencing any issues with the system
• We had already implemented BAM Portal for tracking message properties, milestones, durations etc. as part of our development
process but wanted a richer user interface than what BAM Portal provided
• BAM was instrumented post deployment as we didn’t need to make any application code changes to track data
• BAM provided both real-time transactional view and historical aggregated view of each business process. For example, we could:
• Query and find a message associated with a particular Transaction Id or Account Number or Policy Number
• Search for policies by customer name and address or agent name
• Get the duration for Guidewire (GW) user claims document storage request and response
• Get the Document Id for a document archived to OnBase from Source HOV (SHOV) on a particular day and time
• View performance for different stages within a business process, including sub integrations, over an extended period of time
• For a real-time document query via customer portal, how long did the search take for searching TCI compared to searching OnBase?
• For SHOV batch process, how long did it take to process all the records in the file, update OnBase and update GW Db?
• BAM tracking was used to continuously check to see if SLAs were being met
• BAM allowed us to collect both real-time (transactional) data and historical (aggregated) data
• view changes in business process over time so we can proactively make changes if we can predict load is increasing
• historical data allows us to go back in time and use the charts to correlate events that caused failures e.g. timeout events
• we could compare KPIs for different time periods (e.g. current week versus previous week) to debug performance impact of a new release compared to
baseline performance
• We wanted to display data from ESB exceptions database so we could provide more visibility to failed messages

6. • Better user experience than BAM Portal for displaying aggregates, as dashboards display intuitive line graphs and
maps with easy transitions from hourly to daily or weekly or monthly statistics
• Dashboard provided additional visibility (in addition to BTS Admin Console, BAM Portal, ESB Portal, and BHM) for
developers, business analysts and support when debugging production issues that happened in the past
• Usually fast and responsive, with no delays when displaying large amounts of historical data (e.g. six months)
• SaaS cloud based Power BI required no installation on premises except for data access gateway and outbound
firewall rules change
• We started out displaying BAM data but later used Power BI to display exceptions and business data since we were
able to build reports very quickly
• types of claims that were coming in for different lines of business
• heat map that displays geo location information so business can see where claims are coming from during a disaster
scenario
• Azure subscription based model, with lower cost entry point, and customer pays for what they use, easily adding
or removing users
• Production support team includes these KPIs as part of their daily ESB health check reports to business and
stakeholders so they can see the value BizTalk ESB provides in processing claims, policies, and bills
• Power BI allowed us to aggregate information from multiple on premise data sources, making the platform more
customizable and useful over time
Why Power BI?
9/13/2016 6

7. What we monitored?
• Monitored application key performance indicators (KPIs), service level agreements (SLA), failures, and
business information
• KPIs were reported in separate Power BI dashboards for each business process, batch and real-time, by the
hour, day, week, month and included the following:
• Volume (e.g. Number of claims successfully processed and the number that failed to process)
• Is volume unusually high or way below expected volume?
• Is the volume trending upwards at a faster rate than expected with this new release and will we have
adequate resources to handle the increased load?
• Do we have an unusual number of failures at a particular point in time?
• Duration (e.g. Time taken for the claim to be processed in seconds)
• Is a search request from customer portal exceeding SLA?
• Is the new release impacting claims processing?
• Message size (for both request and response in Kb)
• We’re seeing customer portal host throttling, so are policy search responses from customer portal
returning unexpectedly large payloads?
• Throughput (e.g. claims processed/hour)
• Is the rate at which we’re processing records meeting SLAs?
• Alerts were generated when SLAs were not met and alerts were based on aggregates, so a single min or max
value will not cause an alert
• Tracked end to end KPIs, and in some cases, KPIs for specific stages (sub-integrations)
• Provided the ability to compare KPIs for two time periods e.g. last week compared to this week
9/13/2016 7

8. • This is a demo site is not the customer production site
• Only one business process is being shown as part of this demo, although customer production site included
several dashboards for multiple business processes, batch and real-time
DEMO
9/13/2016 8

9. Power BI Portal : https://app.powerbi.com
Database
BAM & other
Application data
KPI Measures
Custom Filters
Power BI
Dataset
Measures,
BAM Table
data and
Connection
String to
database
Power BI
Dashboard
Important
Visualizations
pinned from
the Report
Power BI
Report
Pages having
detailed
information
displayed
through Charts
and other
visualizations
POWER BI
Architecture
9/13/2016 9

10. Alert Sample
9/13/2016 Confidential 10

11. Useful links
9/13/2016 11
• On-premises data gateway - https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem/
• Power BI Gateway - Enterprise in-depth - https://powerbi.microsoft.com/en-us/documentation/powerbi-
gateway-enterprise-indepth/
• Upgrading the Analysis Services Connector to the Power BI Gateway – Enterprise -
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-enterprise-upgrade-as-connector/
• Monitoring BizTalk Server - https://msdn.microsoft.com/en-us/library/aa577454.aspx

12. Thank You
Twitter: #integrationmonday
Website: http://www.integrationusergroup.com/