Andrew I have implemented solutions using almost all different configuration approaches, in production.
The BRE approach I used was based upon calling the rules engine with a xml-message and letting the rule engine fill in certain nodes with values based on the configuration. What you need to do next is read the xml node values from inside the orchestration. If you make your vocabulary simple enough you can very easily learn an admin how to update the values. Another possibility is to use the excel file from Scott to enter the configuration and the accompanying tool from http://www.traceofthought.net/CategoryView,category,Deployment%20Framework.a spx Briefly it works like this: a SSO application is created and the values exported from excel are deployed there using a command line tool. You can use another supplied library to read the values from orchestration. The values are not strongly typed so you have to cast them. There is also a tool from Jon Flanders, which I have never used, that does basically the same but is strongly typed. You can find more about it on his blog. The enterprise library is another option - but not a trivial one. You will have to invest some time to learn it. If you want to have different BizTalk servers share the same configuration then you need a central place to keep it such as inside the SSO DB. There is only a sample available from MS that shows how this can be done. Remember it's only a sample - not as thoroughly tested as other MS code and not supported for production. We have used this sample code and discovered some issues with it, which were later fixed by the author (but not a short time span). Now it looks to be stable for our scenario's and we have incorporated the deployment of the SSO apps into our installation scripts. So far about configuration. For logging you can go for LOG4NET (or also the EL) or the default .NET System.Diagnostics tracing for simple cases. For exception handling I would personally advise to use the default shapes from orchestration and do some additional logging there. Do not try to combine the EL exception handling approach with orchestrations, it is targeted at .NET apps. Hope this helps... Br, Gregory van de Wiele -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Hatch Sent: maandag 20 augustus 2007 7:39 To: BizTalker@listserver.readify.net; BizTalker@listserver.readify.net Subject: [***SPAM***] RE: [BizTalker] test message Thanks Bill I have been researching storing .NET Configuration information in the BRE but can't seem to find any reliable source that demonstrates how to do it. The only two options available appear to be to use SSO or modify the BTNTSvc.exe.config file. The latter solution I am trying to avoid as a bit of a risk mitigation strategy for developers inadvertently wrecking the file! ________________________________ From: [EMAIL PROTECTED] on behalf of Bill Chesnut Sent: Mon 20/08/2007 10:56 AM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message Andrew, I have a sample BizTalk application that used most of what I spoke of in the download section of my website, www.biztalkbill.com <http://www.biztalkbill.com/> , I have an update for the sample that should be on my site when I get back to Melbourne on Wednesday, currently in country Victoria without very good internet connect. Regards, Bill Chesnut Readify - Senior Consultant M: +61 404 063 648 | C: [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Hatch Sent: Monday, 20 August 2007 10:52 AM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message Thanks Bill Is there a good example/best practice sample somewhere on the web that I can take a look at? ________________________________ From: [EMAIL PROTECTED] on behalf of Bill Chesnut Sent: Mon 20/08/2007 10:13 AM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message Andrew, I have seen the SSO implementation of a configuration store, it seems to require lots of work to me. I have been using the Business Rules Engine to store all my BizTalk configuration since BizTalk 2004, I like the visibility and external tools to manage it without Visual Studio. I also think that Enterprise Library is an overkill for managing exception and logging in BizTalk, I typically use a very simple logging mechanism is a .net help and make sure that BizTalk handles most of it own exceptions, that way your administration people have visibility to these exceptions. So, my quote for the day is "think like a BizTalk developer not a .Net developer". :) Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Hatch Sent: Monday, 20 August 2007 8:17 AM To: BizTalker@listserver.readify.net; BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message Okay I'll bite as well. I am planning to make use of the Microsoft Enterprise Library to do my exception and logging management in a new BizTalk project I am currently designing. I found an excellent post on MSDN in the server code samples about incorporating Version 2.0 and using SSO as the config store. However has anyone actually done this in a production environment and would they recommend using 3.1 as opposed to 2.0? I would like to use 3.1 but am planning on erring on the side of caution and using 2.0 as I have used it before without too many dramas. ________________________________ From: [EMAIL PROTECTED] on behalf of Bradley, Peter Sent: Sun 19/08/2007 8:19 PM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message I think it got taken over and people just stopped posting. I guess the list is unmoderated. Either that, or the moderator's gone AWOL. There was a time when this list was very useful. It would be great if the list could re-establish itself. In the meantime, the best resources I know of are the microsoft.public.biztalk.general list and Jan Eliasens blog. HTH Peter -----Original Message----- From: [EMAIL PROTECTED] on behalf of Kent Wallace Sent: Fri 8/17/2007 4:51 PM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message You know people; I am disappointed in this list server. I am on other list servers that have a great conversation about technical issues. I see more porn request and job opportunities on this list. Kent Wallace Boise, Id ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bradley, Peter Sent: Friday, August 17, 2007 8:21 AM To: BizTalker@listserver.readify.net Subject: RE: [BizTalker] test message Works for me. Just to prove someone is listening Peter ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Chesnut Sent: 17 August :44 To: biztalker@listserver.readify.net Subject: [BizTalker] test message Hello All, Just a test message to make sure the list is still working. Regards, Bill Chesnut BizTalk Server MVP Readify - Senior Consultant Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia M: | E: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> | C: [EMAIL PROTECTED] <sip:[EMAIL PROTECTED]> | W: www.readify.net <http://www.readify.net/> ________________________________ The content of this e-mail, including any attachments is a confidential communication between Readify Pty Ltd and the intended addressee and is for the sole use of that intended addressee. If you are not the intended addressee, any use, interference with, disclosure or copying of this material is unauthorized and prohibited. If you have received this e-mail in error please contact the sender immediately and then delete the message and any attachment(s). to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net <http://www.readify.net/> <http://www.readify.net/> to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net <http://www.readify.net/> <http://www.readify.net/> to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net <http://www.readify.net/> <http://www.readify.net/> IMPORTANT 1. This email and any attachments are confidential. Any unauthorised dissemination or other use of these materials is prohibited. If received in error, please contact us and delete all copies. 2. Before opening or using attachments, check them for viruses and defects. Our liability is limited to resupplying any affected attachments. 3. Protecting your privacy is important to us. Our privacy statement and further information is available at www.oakton.com.au. to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net <http://www.readify.net/> to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net <http://www.readify.net/> to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net IMPORTANT 1. This email and any attachments are confidential. Any unauthorised dissemination or other use of these materials is prohibited. If received in error, please contact us and delete all copies. 2. Before opening or using attachments, check them for viruses and defects. Our liability is limited to resupplying any affected attachments. 3. Protecting your privacy is important to us. Our privacy statement and further information is available at www.oakton.com.au. to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net to unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by http://www.readify.net
