- This topic has 9 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Can anyone suggest the best place to store configurations for a project?
Some of the options that I've come accross so far are:
- BTSNTSvc.exe.config
- Rules Engine
- The Configuration Management Application Block for .NET
- SSO
They all seem to have pros and cons and I am trying to determine the best method.
-
I guess it depends a lot on what your configuration is for and what technical restrictions you have in place.
Personally, I try to avoid using .config files, as they are a pain to update on a multi-server environment. For technical component configuration, I tend to favor using the SSO: It's easy to use and works great for across a biztalk group. Either that, or some other central-database oriented schema.
For business level configuration, though it makes a lot of sense to encapsulate that in rules in the Business Rules Engine, though.
-
In this instance, I have a URL value that I will need to use in multiple orchestrations. I would rather have this URL stored in one place rather than hard code it into each orchestration.
I guess that security isn't an issue and it is not a value that will be changed all that often but it would be good to have it defined in only one place.
-
-
I am trying to avoid the BtsntSvc.exe.config file due to the issues that I may experience when we deploy the solution on a cluster. I believe that this would require having the value stored in the BtsntSvc.exe.config file on each server.
I am looking at a method suggested in chapter 5 of BizTalk 2006 Recipes where I create the value within a vocabulary in BRE and code a .Net helper class to allow Biztalk to access that value within an expression. This means that the value can be easily updated. Can you see any downsides to this approach?
-
In this Scneraio …wont u need to to GAC the helper class dll in all Biztalk Application Servers.If you are using NLB then any Server may access the incoming request.So wht do u say…writing one line of code is better using BTSntSvc.exe.config or calling the helper class and using BRE.
I think you have the answer…..BtsntSvc.exe.config.
See the only disadvantage of using BTSntSVc is the URL is exposed to one and all….and one should be careful while updating it.
Other then that I dont see any pitfalls.
-
That sounds great for one config value; but what about when in further iterations of the application more config values need to be added, are you going to add them all to the config file?
Also the config file provides no visibility without finding the file and opening it.
-
Glenno,
From future compatibility point of view SSODB is any day better as it can encrpty our key/value pairs and we just need to store them in a single Central SSODB database.
But according to Grondal's current Scenario , he just wants to access one URL from all Orchestrations so BtsntSvc is better.
Also every Biztalk Developer knows where BtsntSvc.exe.config is located …anybody can search it thru Windows File Search Tool.
-
[quote user="NISHIL"]
But according to Grondal's current Scenario , he just wants to access one URL from all Orchestrations so BtsntSvc is better.
[/quote]
Hi Guys,
You are correct that I only want to access the one value at this point in time. However, I suspect that over time I am going to need to store extra values as Glenno suggested. Are you suggesting that SSO is the way to go long term?
-
-
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.