In this session Kent will take a real world business scenario from the Power Generation industry. The scenario involves real time data collection, power generation commitments made to market stakeholders and current energy prices. A Power Generation company needs to monitor all of these data points to ensure it is maintaining its commitments to the marketplace. When things do not go as planned, there are often significant penalties at stake. Having real time visibility into these business measures and being notified when the business becomes non-compliant becomes extremely important.
Learn how Windows Azure and many of its building blocks (Azure Service Bus, Azure Mobile Services) and BizTalk Server 2013 can address these requirements and provide Operations people with real time visibility into the state of their business processes.
Boost PC performance: How more available memory can improve productivity
Windows Azure Mobile Services to Exposing Operational Data for Mobile Devices
1. brought to you by
Exposing Operational data to Mobile
devices using Windows Azure
Kent Weare
2. About me
• Senior Enterprise Architect @ Large Power Generation Company
• 9+ years working with BizTalk
• 7 time Microsoft MVP (BizTalk/Integration)
• Author
• Blogger
• Speaker
• Grad Student @ Arizona State University
3. Agenda
• Why are we talking about Mobility here?
• Introducing Windows Azure Mobile Services
• How does BizTalk participate in Enterprise Mobility Architectures?
• Demo
• Summary
5. Why are we talking about Mobility here?
Every CIO has mobility “on their list”
• What is important to my boss is important to me
Enterprise Mobility brings some unique challenges:
• Diverse Eco-Systems
• Android, Apple, Windows Phone, Windows Store apps
• Skillset fragmentation
• Node.js, Angular.js, HTML5 vs XML, XSD, Xlang, WF
• Authentication
• Can’t use Facebook credentials to submit timesheet
• Network boundaries
• Can’t put everything in the DMZ
• Legacy
• Flat files, XML
• JSON
• Point to Point is evil!!!
• More education is required
11. Azure mobile services - feature rich
Provision cloud-connected app
in a few clicks, little code
Support for Android, iOS,
HTML5, Windows 8, and
Windows Phone 8/7.5
Different clients can share the
same backend
Easy authn and authz using
Google, Microsoft Account,
Facebook, or Twitter
Push notifications
Scheduled tasks support
Backend scripting with Node.js *
Custom API support
Push your code via
portal or git
Extend backend with third-party
services
18. Enterprise Mobility Challenges
Format?
Mobility Platform?
Storage/Cache?
Availability?
Security?
LOB System
Mobile Services
SQL Databases
Service Bus
Active Directory
BizTalk Server/Services
“Enterprise Mobility Stack”
19. Demo Scenario
• Deregulated Power Generation company
• Power Generator Commitment includes:
• Declared: Potential amount of Power available
• Dispatched: Actual amount of Power that is being generated
• Some small variance is expected
• When a generator doesn’t meet their commitment there are
penalties $$$
• Over generating is just as bad as under-generating
• Not a replacement for a BI or SCADA solution
20. Scenario #1 – Updating Dashboard
Mobile Services
SQL Database
Service Bus
Historian #1 Historian #2 Historian #3
DEVICES
21. Scenario #2 – Push Notifications
Mobile Services
SQL Database
Service Bus
Historian #1 Historian #2 Historian #3
DEVICES
Push Notification
Out of bounds
Notification
33. Mobile Services Solution
Reading from a Mobile Services table
Var declare = await
App.MobileService.GetTable<PlantCommitmentsModel>()
.Where(x => x.plantname == "NorthWest U.S.")
.OrderByDescending(x =>
x.transactiondate).Take(1).ToListAsync();
45. Resources
• Twitter @wearsy
• Blog kentweare.blogspot.com
• Mobile Services Announcement http://tinyurl.com/lcnrnzg
• #msbts
Notes de l'éditeur
talk about the challanges that I’ve met while using this for a while, and sort of justify each component in the architecture.
talk about the challanges that I’ve met while using this for a while, and sort of justify each component in the architecture.
talk about the challanges that I’ve met while using this for a while, and sort of justify each component in the architecture.
Why BizTalk in this scenario?
Protocal mediation
Legacy Historians
One historian just announced WCF support
Flatfiles are still popular in this space
ODBC
Allows BizTalk to perform transformations into a format that is easily digestible by Mobile Devices/Services
Messages are usually sent every 15 minutes and are time waited averaged but for now we will send them in an adhoc fashion
Product: Windows Azure Service Bus Relays
Tag Line: Services that span boundaries
Most Recent Release:
Capabilities:
Core Use Cases:
Buy-Hold-Sell: Strong Buy
Product: Windows Azure Service Bus Relays
Tag Line: Services that span boundaries
Most Recent Release:
Capabilities:
Core Use Cases:
Buy-Hold-Sell: Strong Buy