Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Logging WCF SQL Adapter
- This topic has 10 replies, 1 voice, and was last updated 8 years, 4 months ago by
community-content.
-
AuthorPosts
-
-
August 3, 2010 at 4:43 AM #25484
Hi.
Is it possible to let BizTalk write a logfile for the WCF SQL Adapter?
That means in a receive pipeline I call a stored procedure in a WCF SQL Adapter and these stored procedure gives back if there is something to do or not (result = 0 or higher).
Now I want to know if BTS write a log where I can see when the WCF SQL Adapter was working and if it has to do something or nothing.
Thanks in advance.
Wolfgang
-
August 3, 2010 at 9:26 AM #25488
Hi Wolfgang,
BizTalk does not have a logging feature out of the box, you would either have to implement a separate external C# assembly (called from BizTalk) or implement Microsoft Enterprise Library’s Logging Application (and modify the BTSNTSvc.exe.config file in the BizTalk installation path). Those are the two options I can think of, you might also want to check the Codeplex website (http://www.codeplex.com) for any open source alternatives.
Best,
Daniel.
-
August 3, 2010 at 9:38 AM #25489
Hi Daniel.
Thanks a lot for reply and tipps.
Actually I don’t know exactly what is the benefit of seperat logging system beside the one BTS has. Because BTS will only logging something if something runs into an error or BTS will run into an error. So for me it is fine if I get just an error message if something coming up and I get the error in the event viewer or in the normel BTS log.
I don’t want thousends or more of logfiles and each says – “ok, everything is fine!”
Do you think BTS’ logging system is sufficient?
Thanks
Wolfgang
-
August 3, 2010 at 9:58 AM #25491
Hi Wolfgang,
We use separate logging system in production to troubleshoot our BizTalk orchestrations, so that we can pinpoint what is failing when some BizTalk process goes down. The error messages in the Event Viewer are sometimes too verbose, and you have to dig in deeply to find out the root cause of what is failing and that takes time and effort. So, for us anyway, there is a tremendous benefit in having a separate logging system.
Cheers,
Daniel.
-
August 3, 2010 at 10:09 AM #25492
Hi Daniel.
Yes, you’re right, it make sense to me, if I have an orchestration or some more programming stuff in it. But just to see if a WCF Adapter is up and running each 5 minutes?? I think this will work fine and just in case of an error there will be the BTS log enough, I’m I right?
Thanks.
Wolfgang
-
August 3, 2010 at 10:24 AM #25493
Hi Wolfgang,
Just for your WCF adapter scenario, you can go to the Transport Advanced Options tab on your Send port and check the “Enable routing for failed messages” checkbox to capture any failed messages that come back in the response from the call to the WCF adapter. You can then set up another Send port to filter on these failed messages from the WCF adapter and save them as files to the file system, and you can have a third-party file watcher program to notify you of any new files created in that folder.
Just a suggestion which does not involve any external logging component, and something more substantial than periodically checking the Event Viewer for any error messages logged by BizTalk engine.
Daniel.
-
August 4, 2010 at 1:05 AM #25499
Hi Daniel.
Thanks for your information – I didn’t no (too much properties I can configure in BizTalk! ;))
Some more question – just to be sure. [:D]
There is no logging property I can activate for this Receive WCF SQL Adapter to see that this Adapter is running every five minutes (I have adjusted it)?
Or do I have to use the way you said … build another Send Adapter and set a filter for any messages coming form the Receive WCF SQL Adapter (when it is possible because it is a receive adapter)?
In case of use the tracking tab:
If I use the “Request message before port processing” property in the receive port, will this be a way to know each time the wcf sql adapter is running and if yes, how I hve to configure a new send adapter which is listening for this message?
Thanks a lot.
cheers
Wolfgang
-
August 4, 2010 at 7:36 AM #25507
Hi Wolfgang,
Here’s an MSDN article on Message Tracking in BizTalk:
http://msdn.microsoft.com/en-us/library/aa560149(BTS.70).aspx
I suppose you can run queries against the BizTalk MessageBox database or use a WMI script to fetch back messages, if that’s the scenario you are looking for…
Daniel.
-
August 4, 2010 at 8:34 AM #25510
Hello Daniel.
Yes, this helps a lot. I think for my scenario I can use message tracking for body. [;)]
Last question:
I was searching for a help site which explains all the filter proberties which are selectable – do you know one?
Thanks a lot for your help and tipps so far.
cheers
Wolfgang
-
August 4, 2010 at 9:58 AM #25512
Hi Wolfgang,
If you do use message tracking, make sure that SQL Server agent is enabled so that the agent jobs that do periodic cleanup of MessageBox and Tracking databases are set up to run (so that those databases do not continuously grow and take up disk space).
As for your last question, I haven’t found much material on either Books Online or MSDN website explaining the different filter properties. so good luck with that.
Daniel.
-
August 5, 2010 at 1:10 AM #25524
Hi Daniel.
Thanks … so I have to check this out.
Wolfgang
-
-
-
-
-
-
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.