Jon Flanders posted an article on using the SSO database as a configuration database for your own BizTalk applications. Great stuff, this is a great idea, and one that Microsoft should've made easier to realize given the fact that they already store all the port and handler configuration inside the SSO DB, anyway.
I think this is very useful, and has lots of potential. For example, if the user's are not too technically savvy (yes, I've several systems administrators that don't qualify in that category ;)), one could do a simple Web dynamic UI to drive the configuration settings, or heck, even create custom InfoPath forms for each application's settings and use a WebService to update the configuration in the SSO database. Yes; lot's of potential here...
Jon: Minor nitpick at the code: In the Helper ServicedComponent class, in the Enlist() method you take an ITransaction argument, and then proceed to ignore it and use ContextUtil.Transaction anyway ;)
