Determining how to efficiently manage logs for your large scale application(s) can be a daunting task. This is particularly important when running PaaS services, such as App Services, Web Jobs, and Azure Functions, where real-time access to application log files is not easily accessible. One effective solution leverages the log4net framework and a number of Microsoft Azure services for a surprisingly intuitive and scalable architecture. Most logging solutions allow for similar customizations. NLog is another popular logging framework that can also be customized to perform the same function. The following demo is done in C#.
How to Create a Custom Appender using Log4Net:
1) Create an Azure Service Bus Queue.
This step requires that you have an active Microsoft Azure subscription. You will have to first create a new Service Bus in the Azure portal. Azure Service Bus is a scalable and robust platform for…
Today we will be going over how to send a message from a Dell Boomi process to an Azure Service Bus queue, and then read that message off the queue, again in a Dell Boomi process.
In Boomi, we can interact with the Service Bus via simple HTTP Post. We will be calling these with the HTTP Connector shape in our Dell Boomi process, from there we will be able to construct our request in full. Then we will show that we can find the message in our queue.
Setting up the Process
Start off by creating a new process in the Atomsphere dashboard and give it an associated name, then click create:
This will bring up our blank process. It will prompt us to setup the Start Shape, select “No Data”, we will be manually creating a sample message for the time being….
Recently, I presented a webinar “Secure Integration Messaging with BizTalk and Windows Azure Service Bus (formerly known as AppFabric Service Bus). The webinar and slide deck and be viewed here.
I’d like to take some time and walk through creating the solution. In this webinar, I demonstrated how to process inbound orders from external trading partners into our on-premise middle-ware platform (which routes orders to the fulfillment order processing systems). One of the key components to solving this integration problem was Windows Azure Service Bus. The Windows Azure Service Bus exposes an endpoint and acts as a relay service to external endpoints. BizTalk 2010 can now natively connect to the Service Bus using the AppFabric Connect feature. This feature can be installed from the BizTalk 2010 installation media.
Here is the overall architecture:
Below illustrates the integrated external B2B partners into our internal LOB systems flow…
I Just returned from TechEd 2012 and one of my favorite sessions was ‘Application Integration Futures – The Road Map and What’s Next in Windows Azure‘. It was refreshing to see the first slide’s title “Key takeaways: we are innovating in BizTalk”.
Here is the abbreviated message from the slide deck:
Continued investment in BizTalk – take your investment forward
BizTalk Server: releasing 6 months after Windows 8
Enabling new Azure based BizTalk scenarios in IaaS & PaaS
Bringing together BizTalk on-premises and Azure
Bet on BizTalk and continue to buy
BizTalk on IaaS coming soon – reduce hardware procurement lead time; reduce time & cost setup and configuration (expect “base BizTalk images”; move apps to Azure and back easily
BizTalk on PaaS – we are already seeing EAI & EDI on Service Bus using Bridges, Transforms, and trading partner management
Here is the timeline (taken from the presentation slide deck)