BizTalk Exception Management

The latest publication of BizTalk Hotrod Magazine is available and can be downloaded. The topics in this issue covered are:

• BizTalk Exception Management
• Exposing Business Rules Engine Policies as WCF Services
• Tools of the Trade
• Parallel Convoys in BizTalk
• A Glimpse of the BizTalk Server 2006 R2 WCF Adapters
• Smart Use of XSLT BizTalk
• In the beginning
• What's Under that Hood?

I have read this edition and found the BizTalk Exception Management Application is a great article. It walks you through an enterprise BizTalk Exception Management application based upon the Patterns and Practices ESB Exception Management Framework. If you have ever thought about using the ESB Exception Management Framework, this article serves as a great primer.

So I started experimenting with this Framework, not in a BizTalk 2006 R2 environment, but just BizTalk Server 2006. In my environment I had Microsoft Windows 2003 Standard Edition SP2 OS, 1,6Ghz processor and 512 Mb of RAM. It had Office, Visual Studio 2005 and SQL Server 2005 installed. Here I download Patterns and Practices ESB Guidance 1.0 November 2007. Then I took one of the examples from the SDK like HelloWorld orchestration (\\Program Files\Microsoft BizTalk Server 2006\SDK\Samples\Orchestrations\HelloWorld) and added scope and exception.













I wanted to find out how to publish the message simply to file as an experiment.

Code inside assign values shape:
//Construct a new Fault Message
FaultMessage = Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.CreateFaultMessage();
//Assign values
//FaultMessage(Microsoft.Practices.ESB.ExceptionHandling.Schemas.Property.Application)= "HelloWorld";
FaultMessage.FailureCategory = "MessageBuild";
FaultMessage.FaultCode = "NNNN";
FaultMessage.FaultDescription = "Some error occured";
FaultMessage.FaultSeverity = Microsoft.Practices.ESB.ExceptionHandling.FaultSeverity.Severe;
FaultMessage.Scope = "Execution Scope";
//Add suspended message (SourceMessage) to the FaultMessage
Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.AddMessage(FaultMessage,POMessage);
//Add the exception from the exception handler to the FaultMessage
Microsoft.Practices.ESB.ExceptionHandling.ExceptionMgmt.SetException(FaultMessage,ex);


To create an error inside the orchestration I created two variables and let a divide by zero error occur:

//Generate divide by zero exception
y=0;
x = 1/y;

When I tested it it finally resulted in a message inside a folder. Message looked like this.





Well that worked, so I am going to look into it some more. ESB Guidance package is intended for BizTalk Server 2006 R2, but Exception Management part can be implemented in BizTalk Server 2006 enviroment.

Technorati:

Comments

Post a Comment

Popular posts from this blog

DTAP Strategy: Pricing and Licensing

Image
To implement BizTalk solutions it is a good practice to have an DTAP environment in place. DTAP stands for Development, Test, Acceptance and Production. Development and test environments are equal (mirrored) and same account for acceptance and production. Deploying DTAP environments is easy, because there are many factors influencing outcome of DTAP. One factor is pricing and licensing costs. BizTalk is available in different editions and since BizTalk depends on operating system and database there are some configuration options to. Here is an overview of possible configurations for DTAP environments, hence there is a nice BizTalk Feature Dependency Matrix. Besides features, there are non-functional requirements to reckon with like fail-over, availability and scalability. On Microsoft Pricing and Licensing FAQ section of BizTalk I found this on non functional side. In a large BizTalk Server 2006 R2 deployment, two key considerations ensure redundancy in all areas of the architect
Read more

Table Operation on Oracle 11g XE with OracleDbBinding

Image
Last year I did a post on table operations on SQL Server Table with WCF-SQL Adapter from BizTalk on SQL. Now I like to do similar thing on table in Oracle 11g Express database using the Oracle Binding from BizTalk Adapter Pack 2010. Oracle 11g Express Edition is available through OTN. For downloading software you will need to have an account! It is important that when accessing Oracle you have appropriate client installed. This can sometimes be a hassle if you do not know, which client you need. When you trying to connect to Oracle you will get error messages like: Connecting to the LOB system has failed. Could not load file or assembly 'Oracle.DataAccess, Version=2.111.7.0, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.. This can be pretty annoying, but there is documentation that can help you going the right direction. In installation documentation I read that supported versions are: Oracle d
Read more

Integration, the community blasting into 2017!

Image
In the past, now and tomorrow I will keep saying that integration is relevant, even in this day and age of digitalization. Integration professionals will play an essential role in providing connectivity between systems, devices and services. Integration drives the digitalization forward by connecting everything with anything. Integration skills are still in demand. A LinkedIn study revealed a top 10 with integration and middleware in top 5 with Cloud, Data Science, UX and Web. And the expectation for 2017 is that this will be similar. Our toolbox is expanding from on premise tooling to cloud services; we have WCF, BizTalk Server, MSMQ to Logic Apps, API Management and Service Bus. Formats ranging from flat file, EDI, XML to JSON, several protocols open and proprietary, tooling from mappers to BizTalk360. It can be challenging yet much more exciting. My conclusion is more options, more fun, at least in my view. In February I, will be travellin
Read more