This post is designed to serve as a companion to my AzureCon 2015 talk titled Processing NFC Tag Reads in a Logic App. As a result, I will be recapping the talk, and digging a little bit deeper into the … Continue reading →
The post Creating a Push Trigger API App to Process NFC Tag Reads appeared first on QuickLearn Blog.
Blog Post by: Nick Hauenstein
Published By: Bill Chesnut
When I was doing some recent work with Azure Services Bus and the preview API App / Logic App, I ran into an issue with serialization of message content with the standard brokered message.
When you send a message will the brokered message client like below you end up with a serialized message in the service bus, when you try to read this message with the API app Azure Service Bus Connector, you must de-serialize the string before you can use it.
private void SendMessageToTopic(string inMessage) { string connectionString = CloudConfigurationManager.GetSetting("Microsoft.ServiceBus.ConnectionString"); MessagingFactory factory = MessagingFactory.CreateFromConnectionString(connectionString); MessageSender testQueue = factory.CreateMessageSender("statement-processfile"); BrokeredMessage message = new BrokeredMessage(inMessage); testQueue.Send(message); }
So if you want to just send a plain un-serialized string to the service bus you need to use the following code, this way processing the string in the API app Azure Service Bus Connector and your logic app is much easier.
private void SendMessageToTopic(string inMessage) { string connectionString = CloudConfigurationManager.GetSetting("Microsoft.ServiceBus.ConnectionString"); MessagingFactory factory = MessagingFactory.CreateFromConnectionString(connectionString); MessageSender testQueue = factory.CreateMessageSender("statement-processfile"); Stream streamMessage = new MemoryStream(Encoding.UTF8.GetBytes(inMessage)); BrokeredMessage message = new BrokeredMessage(streamMessage); testQueue.Send(message); }
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
Hope this help you send messages to the Azure Service Bus Queue and Topics so that you can use them in the Azure API App / Logic Apps
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
More …
Last Monday I presented my second session in the Integration Monday series (see my last post) and, as usually, I normally publish a post on my blog before the event – a way to help the organizers to advertise the event – or sometimes after the event sharing the resources but I just now realized […]
Blog Post by: Sandro Pereira
It was with great pleasure that I presented, last Monday – August 31, 2015 – my second presentation in the Integration Monday series. This time I was invited to talk about my personal experience about BizTalk NoS Ultimate and how this tool can improve our efficiency, productivity and experience while developing BizTalk projects. And for […]
Blog Post by: Sandro Pereira
With Integration Monday reaching a wider audience, we thought it would make sense to write blog posts on the events. We will keep the post very simple with brief snippets from the session and provide links to code samples/demos (if available from the presenter) which will be really helpful for our blog lovers and the […]
The post Integration Monday – BizTalk ALM appeared first on BizTalk360 Blog.
Blog Post by: Sriram Hariharan
Long running transactions are a common scenario in BizTalk integration. They are quite often designed for purpose. Let us take an example of a payment processing portal. The portal may raise a purchase order based on payment initiated by the user, but the order can be processed only after the system receiving a payment confirmation. […]
The post Monitoring BizTalk Dehydrated Orchestrations Using BizTalk360 appeared first on BizTalk360 Blog.
Blog Post by: Arunkumar Kumaresan
I’m glad to be back, once again, to Integration Monday Events! The first time I presented a session about “BizTalk Server Tips & Tricks for Developers and Admins (Deep Dive)” (June 22, 2015), a similar session that I also presented in BizTalk Summit 215 London, that you can found and watch online here. This time […]
Blog Post by: Sandro Pereira
Challenge is to build a WebJob that listens or monitors a queue in the Microsoft Azure Service Bus within a certain namespace and pick of each message that is send there by a message producer and process it. The WebJob acts as a message consumer of the messages on the queue. Below a high level diagram of a scenario that will be explained in this post and how I faced the challenge.
You can
Microsoft released “BizTalk Health Monitor” (BHM) in Jan 2014 after theBizTalk Server 2013 R2 release. From time to time, we receive queries from BizTalk people asking “What is BizTalk Health Monitor and how is it different from BizTalk360?” We do understand the fact that not everyone hasthe time to look into all the tools out […]
The post Difference Between BizTalk360 And BizTalk Health Monitor appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
If you have itineraries which are using the Itinerary Service Broker, along with the XPath filter, you might run into a very strange looking error which will take you down all kinds of rabbit holes.
Error
There was a failure executing the receive pipeline: “[fully qualified name of your pipeline]”
Source: “ESB Dispatcher” Receive Port: “[name of your receive port]” URI: “[port URI]”
Reason: The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security.
Reading this at face value, you naturally start looking into the permissions of the service account used by the BizTalk host instance linked to the receive location. It turns out the error has nothing to do with the security log, but rather a bug in the ESB Toolkit’s deployment, where the XPath Filter dll has an extra “L” added to the file extension:
Just remove the extra “L” from the file and things will once again work!.
Cheers,
Dan