SharePoint User Group - Leeds - 2015-09-02

Editor's Notes

• #12: Customer moving infrastructure to cloud BizTalk was being upgraded and they wanted to host new version in the cloud BizTalk still needed to access many resources on premise with no significant re-development This is also great for dev/test scenarios and temporary environments
• #13: Customer moving infrastructure to cloud BizTalk was being upgraded and they wanted to host new version in the cloud BizTalk still needed to access many resources on premise with no significant re-development This is also great for dev/test scenarios and temporary environments
• #15: If we have an existing MPLS network with out network provider then we can work with the network provider to add Azure so it appears like another site on the WAN
• #16: By adding Azure to the MPLS network servers in Azure just appear like any other server on the WAN. We can create a read only copy of AD in Azure to improve performance Extended data centre opens up lots of opportunities for cloud hosted IaaS Burst load Dev / Test environments Backup Hardware reduction Infrastructure cost saving
• #17: SQL Data Warehouse in Azure to support large scale compute based BI How do we get the data to the data warehouse? We wanted to bulk load data from databases in each site to a cloud hosted SQL Data Warehouse MPLS network allows SSIS to reach the databases in each site Express Route allows us to pull large amounts of data with good bandwidth
• #19: We were creating a global BizTalk development environment hosted in Azure Most developers were easily able to access VM over public internet In UK on premise restrictions stopped us doing that Point to Site VPN was used to tunnel over HTTP using SSTP allowing developers to connect the VPN software and access VM
• #21: Why did we choose Relay and not VPN Cost Setup Time Fewer infrastructure challenges Fail fast & Cheap Don’t have to worry about controlling access to other resources, the endpoint is the only resource Can easily expose to other consumers Why not just expose the services publically I don’t need to worry about my DMZ I don’t need to worry about DOS I don’t need extra infrastructure Why did we use WCF Routing Service Allowed us to expose non Microsoft technologies Routing Service can forward calls to another web service WCF Routing Service was a simple listener We can control which services are exposed via routing rules
• #24: Key Benefits Decoupled architecture with API not aware of each business Supports publish / subscribe pattern One way and two way messaging Plug in new business units
• #25: In this example BizTalk is using a SQL Query to get some recent changes, debatches them and then publishing event messages for each change Service Bus Queues support a good on-premise to cloud integration pattern Queues are a good way to deal with high volume event publishing Receivers can be inside the organisation or outside of it Key Benefits Low cost No infrastructure requirements Queue is PaaS so can be accessed from anywhere Supports the Pull based integration pattern
• #27: Why did we choose Relay and not VPN Cost Setup Time Fewer infrastructure challenges Fail fast & Cheap Don’t have to worry about controlling access to other resources, the endpoint is the only resource Can easily expose to other consumers Why not just expose the services publically I don’t need to worry about my DMZ I don’t need to worry about DOS I don’t need extra infrastructure Why did we use WCF Routing Service Allowed us to expose non Microsoft technologies Routing Service can forward calls to another web service WCF Routing Service was a simple listener We can control which services are exposed via routing rules
• #29: BizTalk Adapter Service is really about taking advantage of the LOB Adapter SDK + BizTalk Adapter Pack but in Cloud Scenarios The Key benefits are around the simplicity for connecting to LOB applications We chose the BizTalk Adapter Service because of the specialist capabilities for connecting to SAP or any other application we need to connect to
• #31: In the scenario we move the website to the cloud We still need to connect to the on premise oracle data base If we set up BizTalk Services Hybrid Connections we are able to reach through to the Oracle Database We are unlikely to need to change any code our ODP.net code would be routed through hybrid connections simply by changing the connection string Key Benefits Migrate to the cloud with potentially no code changes Can support almost any port so its open for a wide range of connectivity types Lower level of abstraction than Service Bus Relay which is WCF this can be any port Word of Caution Your application authorization model may be affected if your no longer on premise
• #37: Point to Site VPN – You can connect to the network with vpn but as you wouldn’t really need to log into a VM this isn’t really a likely scenario
• #40: Why did we choose Relay and not VPN Cost Setup Time Fewer infrastructure challenges Fail fast & Cheap Don’t have to worry about controlling access to other resources, the endpoint is the only resource Can easily expose to other consumers Why not just expose the services publically I don’t need to worry about my DMZ I don’t need to worry about DOS I don’t need extra infrastructure Why did we use WCF Routing Service Allowed us to expose non Microsoft technologies Routing Service can forward calls to another web service WCF Routing Service was a simple listener We can control which services are exposed via routing rules