Almost three weeks ago in my last post I release a SQL script to manager and delete the unnecessary records in the BizTalk “MarkLog” tables according to some of the best practices (you can read more here: Managing and cleaning BizTalk Server MarkLog database tables according to some Best Practices), however I knew in advance […]
Blog Post by: Sandro Pereira
Blog Post by: AxonOlympus
Blog Post by: AxonOlympus
With the ESB Toolkit you get BAM out of the box. There are already two activity definitions created that give information about itineraries that are processed in BizTalk and about Exceptions that occur in BizTalk. You only have to deploy the definitions with the Bm.exe tool to enable BAM tracking so it’s very easy to use BAM with the ESB Toolkit.
When you deploy the activity definitions are several BAM tables en views created in the BAMPrimaryImport database. They contain very valuable information but the strange thing is that you cannot link the Itineraries data to the Exceptions data. The data is stored in different tables and there is no foreign key to join the tables. This is very unfortunate because now you know for example that an error has occurred in an Itinerary Service but you don’t know in which itinerary. Also if you want to have an overview of the running itineraries you have to link the data because if an exception has occurred in an itinerary that itinerary is not running anymore but you don’t have information about that in the Itineraries data. How can you fix this? By creating a custom Foreign Key!
In the bam_ItineraryServiceActivity_CompletedInstances view you have the InterchangeID that is set by the Messaging Engine for each message that arrives on the Server. In the bam_EsbExceptions_CompletedInstances view you don’t have it but you can use other fields to store it in. The FaultCode field is a suitable candidate because it has the same data type as the InterchangeID and you can set the FaultCode inside an Orchestration when an Exception occurs.
Use the following code to get the InterchangeID and to create a Fault message when an Exception occurs. The data of the Fault message is stored in the EsbExceptionDb database but also in the BAMPrimaryImport database.
// Get Context properties interchangeID = msgInbound(BTS.InterchangeID); // Create FaultMessage msgFault = Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.CreateFaultMessage(); // Set Fault Message Properties msgFault.Body.FaultCode = interchangeID;
.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; }
Create a SQL query in SQL Server Management Studio on the BAM views in the BAMPrimaryImport database. Use the InterchangeID and FaultCode fields to link the views.
In the following example are the bam_ItineraryServiceActivity_CompletedInstances view bam_EsbExceptions_CompletedInstances view joined to get an overview of Itineraries with errors.
In the following example are the bam_ItineraryServiceActivity_CompletedInstances view bam_EsbExceptions_CompletedInstances view joined to get an overview of all the running Itineraries.
For more information see:
Using BAM in the ESB Toolkit
Recently had to field some questions regarding Office 365 and SharePoint online. Thought it would be beneficial for others looking for similar information. Leave a comment if you have additional input on any of these or have other questions regarding this topic:
Category
Question
Response
Performance, Scalability
On SharePoint online are farms replicated Globally? Where are they replicated? What control […]
Blog Post by: Reddy Kadasani
In this post I try to explain how to automate your deployment using the MSBuild Extension Pack. First I work through a general scenario, deploying your assemblies on your Development machine, extracting an MSI and deploying that to Test. At the end I included some extra scenarios.
I tried to create a SQL Server Lob target from within Visual Studio and got this error. The URL I was trying to use was http://localhost:8080/BAService/ManagementService.svc/. Some have said to use https://localhost:8080/BAService/ManagementService.svc/ but this caused more errors. Eventually I discovered that I had Imported the BizTalk Service self-signed certificate to the Trusted Root Certificate Authority […]
Blog Post by: mbrimble
It’s time for the second part of my blog series about configuring 2way SSL Authentication using certificates in BizTalk. In this second part I will describe how to setup IIS and a receive location in BizTalk in order to receive messages using 2Way SSL Authentication.
Blog Post by: AxonOlympus
Microsoft IDC (India Development Center), Hyderabad is one of the important location for Microsoft, as far as I know even though Microsoft have offices pretty much in every major country in the world, the product development happens only in 4 major places US (Redmond), Israel, India (IDC), and Shanghai. BizTalk Server is one of the […]
The post Experience visiting and working at Microsoft IDC, Hyderabad for a week appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
Blog Post by: AxonOlympus