|
Home > Archive > BizTalk Server Orchestration > November 2005 > read web.config from BizTalk
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
read web.config from BizTalk
|
|
| kplkumar@gmail.com 2005-11-29, 5:55 pm |
| I have an orchestration published as a websevice.
My orchestration calls another .NET dll for business logic and database
access. I have the connection string information for database access in
the web.config that was created when I published my orchestration.
I am not able to read the web.config entry from the .NET dll that lies
behind the BizTalk orchestration.
Any ideas??
The flow is webui --> webservice --> orchestration -->.NET dll --> DB
I need to read the web.config that's part of the webservice from the
..NET dll
Is this possible? Is there a work around?
| |
| Greg Forsythe 2005-11-29, 5:55 pm |
| The web service runs in an application pool in IIS, receives the message and
publishes to the message box.
The orchestration processing the message runs in the Biztalk host process.
Try putting your connection string in the BTSNTSvc.exe.config file
Greg
<kplkumar@gmail.com> wrote in message
news:1133295462.573654.72340@f14g2000cwb.googlegroups.com...
>I have an orchestration published as a websevice.
> My orchestration calls another .NET dll for business logic and database
> access. I have the connection string information for database access in
> the web.config that was created when I published my orchestration.
> I am not able to read the web.config entry from the .NET dll that lies
> behind the BizTalk orchestration.
> Any ideas??
>
> The flow is webui --> webservice --> orchestration -->.NET dll --> DB
>
> I need to read the web.config that's part of the webservice from the
> .NET dll
>
> Is this possible? Is there a work around?
>
| |
| Marian Drumea 2005-11-29, 5:55 pm |
| BTSNTSvc.exe.config is a good solution, but will set parameters for the
entire BizTalk installation, not only for your application. It is a
good workaround. Other option is to use the Configuration Management
that comes with Microsoft's Enterprise Library. Then, you can have your
own set of parameters, in your own XML file or SQL Server database,
that you can share across applications.
Good luck!
Marian
http://www.MarianDrumea.com/BizTalk
| |
| Scott Colestock 2005-11-30, 5:52 pm |
| Yet another possiblity is to use the SSO as a configuration store. Both
Flanders (masteringbiztalk.com) and I have written a bit about this.
Scott Colestock
www.traceofthought.net
"Marian Drumea" <mdrumea@gmail.com> wrote in message
news:1133307910.023975.292040@g47g2000cwa.googlegroups.com...
> BTSNTSvc.exe.config is a good solution, but will set parameters for the
> entire BizTalk installation, not only for your application. It is a
> good workaround. Other option is to use the Configuration Management
> that comes with Microsoft's Enterprise Library. Then, you can have your
> own set of parameters, in your own XML file or SQL Server database,
> that you can share across applications.
>
> Good luck!
>
> Marian
> http://www.MarianDrumea.com/BizTalk
>
|
|
|
|
|