This blog post serves as a quick recap of and expansion on my October 19th Integration Monday talk titled Building Push Triggers for Logic Apps. You can view the session and look through the slides over at integrationusergroup.com. In the … Continue reading →
The post Integration Monday Recap and Push-BUtton Push Trigger Introduction appeared first on QuickLearn Blog.
Blog Post by: Nick Hauenstein
In one of our earlier blog post, we mentioned how Microsoft is taking the effort to shape a community driven approach by organizing a monthly “Google Hangout session” to communicate the latest updates in the filed of Azure Logic Apps. This month’s session – fifth in the series – happened yesterday (October 29th). You can […]
The post Azure Logic Apps Monthly Update – October 2015 appeared first on BizTalk360 Blog.
Blog Post by: Sriram Hariharan
I’m writing this blogfrom Calgary, Canada where I’ll be speakingat “Azure Hybrid Integration Day” along with fellow MVP’s. This is my first time at Calgary. When the opportunity came few months ago, I decided to spend few additionaldays here to meet with fewof our long term customers. Calgary is well knownfor Energy, Oil and Gas […]
The post Why Every Company Should Visit Their Customers Frequently? appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
Further to my post about deploying BizTalk solution using Octopus found here, this post will describe the substitution of variables in Octopus 3.0 release. In Octopus 2.x.x release, we had Octopus.Platform.dll which gets the variable information from the octopus database, however in octopus 3.0 this feature is removed and not included any more. This will […]
Blog Post by: shadabanwer
We ended last post asking: Do you think the schema is entirely correct? Does it handles with all files accordingly to the expected results? Or do we need to tune some of the properties of your schema When we start working with Flat File schemas for BizTalk, we may think that just using the Flat […]
Blog Post by: Sandro Pereira
When you create a Web API you can use it for your own applications but maybe you also want to expose it to the outside world. In that case you probably want to change the behavior of the Web API. For example add security or hide properties. You can use BizTalk to create a virtual service in front of your Web API to modify the behavior but is that the smartest choice? Because BizTalk writes every message that it receives a couple of times to the MessageBox database. This increases heavily the execution time and especially with Web APIs it’s important to have a really low execution time!
Another option is to use Sentinet from Nevatech to create a virtual service in front of your Web API.
The virtual service runtime in Sentinet can also be extended with custom messages processing. Sentinet provides a number of build-in message processing components but it is also possible to create custom message processing components.
Let’s have a look at the following example where an Order Web API is used inside an organization to process orders. This Web API must also be exposed to external customers to show the status of an order but if an error occurs in the Web API or in a background process, the OrderStatus property must be modified that the order is still in progress and the ErrorMessage property with the error must not be shown to the customers. Furthermore the output of the Web API must be in XML instead of JSON.
The following steps in Sentinet are necessary to make it work:
- Add the REST service (or API) to the the Sentinet Repository
- Create a Virtual Service
- Add custom Pipeline Processing
- Test the Virtual REST Service
Sentinet makes it really easy to modify the response of a Web API. You only have to create a Virtual Service in front of it and add custom Pipeline Processing! Especially if you are already familiar with XPATH and XSLT, the example above doesn’t take long to implement.
Sentinet version 4.5
In September Microsoft added the Performance test feature in the Azure Preview Portal to check your Web App’s performance. For API Apps this is also very important and because API Apps are built on top of Web Apps I was very curious if I can also use this feature for API Apps! The Web App that hosts an API App is called the API App Host in the Azure preview portal, so on the API App host blade I tried to go to the Tools menu where the Performance test feature resides.
Unfortunately I got an error so the Tools menu doesn’t seem to work for API Apps but there is another way. You can also add the Performance test tile directly on your API App blade!
See the following steps how to do it.
|In the Preview Portal select the API App that you want to test. Then right click on the API App blade and select Add tiles in the menu.|
|In the Tile Gallery select Find Resource by Type. Then select Web Apps.|
|Select the Performance Test tile.|
|Drag the tile from the Tile Gallery to the API Apps blade.|
|The Azure Preview Portal has very powerful customization capabilities allowing you to resize or move the tile on the resource blade.|
|Click on the Done button when you are finished.|
|When you click on the Performance Test tile you see an overview of your recent runs but first you to have click on “Set Account” to choose a Visual Studio Online account to create performance tests.|
|Click on “New” to create a new performance test. Your API App’s default URL is added automatically. You have to change the URL and add “/api/” combined with the method you want to test (HTTP GET requests only).|
For more information on Performance tests in the Azure Preview Portal see:
Performance test your Azure web app under load
The first Logic Apps SDK for .NET (v0.1.0) was released on August 28th.
Stephen Siciliano covered it in the LogicAppsIO Community WebCast on August 27th.
But there haven’t been many blog posts on how to use it, nor many samples.
So here we go: How to use the SDK…
Blog Post by: Daniel Probert
As a Microsoft MVP for Integration – or however I’m categorized now – I keep a keen interest in where Microsoft is going with (app) integration technologies. Admittedly, I’ve had trouble keeping up with all the various changes, and thought… Read More ›
Blog Post by: Richard Seroter
Cumulative Update Pack 3 for Host Integration Server 2013
This cumulative update package for Microsoft Host Integration Server 2013 contains hotfixes for issues that were fixed after the release of Host Integration Server 2013.
We recommend that you test the hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included in the previous Host Integration Server 2013 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.
Important This cumulative update package includes all the component packages. However, the cumulative update package updates only those features that are currently installed on the system.
Download Link : http://support.microsoft.com/kb/3019572
Many Thanks to the Product and Support TEAM ! You’ve done a great job