1. Real World use cases for BizTalk360
Lex Hegt
@lexhegt
* Saravana has shown many of the capabilities from BizTalk360
* But how does these functionalities help solving your problems
BizTalk360
Bouvet BizTalk Innovation Event

2. Agenda Shared Infrastructure Single Operational Console
You can specify there are over 40 core capabilities in BizTalk360, but today in next 15 mins we are going to see 2 real world use cases for BizTalk360

3. Shared Infrastructure
* When we talk about a BizTalk Group, we actually talk about an Shared Infrastructure. This is because a BizTalk Group can have multiple BizTalk Applications, which can be owned by multiple business owners. So all these Business Owners use the same infrastructure for their own goods.
* Let’s have a look at why this makes monitoring a BizTalk group complex
BizTalk360

4. Shared Infrastructure
Facts:
A BizTalk Group (Environment) might have
Many BizTalk Applications
Multiple Business Owners
Problems:
Applications isolation between different business units not possible.
Support teams might have different monitoring requirements
User Access Policies
Governance/Auditing in shared infrastructure becomes important
Facts:
* Many BizTalk Applications:
* Say 25 applications with 100’s orchestrations, Receive Locations, Send Ports
* Say 20 Hosts Instances from 8 Hosts
* Multiple Business Owners:
* CRM, ERP, Line of Business applications
Problems:
* Application Isolation:
* Say you have CRM and ERP which both use BizTalk: there is no way to prevent the CRM support engineers from using the ERP Applications
* Support Teams: * Platform Support Engineers have different needs than Application Administrators * User Access: * Not all people are entitled to access all Applications and other parts in BizTalk * 1st line support engineers often not specialized in BizTalk, so you don’t want to give them the full power of the Admin Console * Governance/Auditing * Especially in case of major incidents you want to know who did what and when

5. Shared Infrastructure – Application Isolation
Business Owners
CRM
ERP
LoB
3rd Level: Technical Application Administrators
(BizTalk and Application Specialists)
* 1st Level: 24/7 Support Engineers: * Show: Platform stuff (Host Instances, SQL Jobs), Integrated Event Viewer, KB, * Don’t show: BAM Portal, resume messages/instances
* 2nd Level: System Administrators: * Show: Platform stuff (Host Instances, SQL Jobs), Integrated Event Viewer, KB,
* Don’t show: BAM Portal, resume messages/instances
* 3rd Level: Technical Application Administrators: * Show: BAM Portal, resume messages/instances from the BizTalk Application they administer, KB * Don’t show: Platform stuff
* Business Users * Show: BAM Portal
2nd Level: System Administrators
(BizTalk Specialists but Non-Application Specialists)
IT Department
1st Level: 24/7 Support Engineers
(Non-BizTalk Specialists)

6. Shared Infrastructure
* Look at this: all those artifacts * How do you keep the overview * How do you know if all artifacts are in the desired state, * How do you prevent support engineers, hitting the ‘wrong’ button.
* It takes a lot of navigating through a number of screens in the BizTalk Administration Console, to find out the states of the artifacts.
* By applying User Access Policies you can ensure that the user only sees, what he needs to see to do his job

7. Shared Infrastructure – Advanced User Access Policy
* User Access Policies: * Give your engineers the authorisations they need * Provide them with a simple User Interface

8. Shared Infrastructure – Simplified User Interface
* It’s exactly same environment, but in the background it been accessed as super user, in the front it’s accessed as custom profile.
* The dashboard are context sensitive and show only relevant information related to the user.
* Same applies to for example host instances, not all of them will be displayed.
* And if you need that overview, you can use the new Monitor Dashboard

9. Shared Infrastructure – Subscription based monitoring
* Monitor Dashboard: gives good overview, certainly on a large 40 inch screen!
* Super user can configure various alarms, and add multiple sections based on each teams requirement Example: CRM team may be interested to get notified only about CRM related applications and general infrastructure health, they are not interested in other applications deployed in the environment like ERP

10. Shared Infrastructure – Subscription based monitoring
* Alarms and notifications are based on subscriptions: * From Receive Locations to Suspended Messages * From Windows Services to CPU and Memory Load * You can get warned by or SMS if an unexpected state occurs

11. Single Operational Console
BizTalk360

12. Single Operational Console
Facts:
Administrators and support people need Multiple Consoles
BizTalk Server Administration Console
SQL Server Management Studio
Event Viewer
Performance Monitor
BAM Portal
Monitoring consoles (SCOM, HP ITO), etc.
* Facts: * BizTalk: BizTalk artifacts * SQL Server: SQL jobs and database health * PerfMon: Throttling * More consoles: SCOM, ITO, RDP, MsgBoxViewer
* Problems: * BizTalk Expert who knows where to look in all those consoles
* Security: Example SQL Server access, SCOM console access, RDP access, Administrator rights on servers etc
Problems:
You need a BizTalk expert
Various security policies need to be maintained

13. Single Operational Console
* Look at this: 4 consoles Again: how do you keep the overview...

14. Single Operational Console
How does BizTalk360 help:
One Console
No Client Deployment (SilverLight V5 must be installed)
Works on HTTP ports
* One console * BizTalk360 offers views to BizTalk related topics within the mentioned consoles * No deployment * SilverLight v5 must be installed * SilverLight is supported on IE 8+, FireFox 3+, Google Chrome * In case of outsourcing/offshoring * You don’t have to open any ‘funny’ ports * Ports 80 and/or 443 will do nicely

15. Single Operational Tool
* One console instead of many

16. An all-in-one solution to efficiently administer, operate, and monitor your Microsoft BizTalk Environments
BizTalk360