Hi all,
we have developed application on BTS 2004. Adapter receive locations were
configured on development machines. Application was deployed on production
environment - Windos Server 2003 + BTS 2004 (with no development tools). Now
we encoutered a problem because we need to reconfigure receive locations (to
change passwords, remote hosts, etc.). On development environment it was
possible using VS.NET and BizTal Explorer, but we dont want to install
VS.NET on production environment. It is odd to install VS.NET just to be
able to configure receive location anyway, isn't it? It is possible to
configure receive handlers using Biztalk administration console, but receive
locations not. What's the reason for this behavior? What is the recomended
way to configure receive locations on production environment.

Thanks for help,
eXavier

[ Post a follow-up to this message ]

Use the BizTalk Deployment wizard to Export port / orchestration bindings -
which will produce an XML config file that you can manually update, then use
the deployment wizard to re-import the bindings into the production
environment.

"eXavier" <fhns@centrum.cz> wrote in message
news:eNxcoay8EHA.2016@TK2MSFTNGP15.phx.gbl...
> Hi all,
> we have developed application on BTS 2004. Adapter receive locations were
> configured on development machines. Application was deployed on production
> environment - Windos Server 2003 + BTS 2004 (with no development tools).
Now
> we encoutered a problem because we need to reconfigure receive locations
(to
> change passwords, remote hosts, etc.). On development environment it was
> possible using VS.NET and BizTal Explorer, but we dont want to install
> VS.NET on production environment. It is odd to install VS.NET just to be
> able to configure receive location anyway, isn't it? It is possible to
> configure receive handlers using Biztalk administration console, but
receive
> locations not. What's the reason for this behavior? What is the recomended
> way to configure receive locations on production environment.
>
> Thanks for help,
> eXavier
>
>

[ Post a follow-up to this message ]

Hi Hugo, thanks a lot. But this seems to me rather as a workaround than
administrator's tool, this procedure I consider as developer approach -
<CustomProps> XML is escaped under <ReceiveLocationTransportTypeData>
element and it is not very readable.

I found quite nice tool:
http://www.gotdotnet.com/workspaces...br />
a88f7464
but still don't understand what lead Microsoft to not provide Receive
Location editation from within Biztalk administration console. It is strange
assumption that developer should configure production environment.


"Hugo Rodger-Brown" <hugo@coldhams.com> wrote in message
news:uz3wIry8EHA.2452@TK2MSFTNGP14.phx.gbl...
> Use the BizTalk Deployment wizard to Export port / orchestration
bindings -
> which will produce an XML config file that you can manually update, then
use
> the deployment wizard to re-import the bindings into the production
> environment.
>
> "eXavier" <fhns@centrum.cz> wrote in message
> news:eNxcoay8EHA.2016@TK2MSFTNGP15.phx.gbl... 
were[vbcol=seagreen] 
production[vbcol=seagreen] 
> Now 
> (to 
> receive 
recomended[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Try using Biztalk Explorer , which is available from GotDotNet.

http://www.gotdotnet.com/Workspaces...br />
a88f7464

Regards

Stuart

"eXavier" wrote:

> Hi Hugo, thanks a lot. But this seems to me rather as a workaround than
> administrator's tool, this procedure I consider as developer approach -
> <CustomProps> XML is escaped under <ReceiveLocationTransportTypeData>
> element and it is not very readable.
>
> I found quite nice tool:
> http://www.gotdotnet.com/workspaces... />
cba88f7464
> but still don't understand what lead Microsoft to not provide Receive
> Location editation from within Biztalk administration console. It is stran
ge
> assumption that developer should configure production environment.
>
>
> "Hugo Rodger-Brown" <hugo@coldhams.com> wrote in message
> news:uz3wIry8EHA.2452@TK2MSFTNGP14.phx.gbl... 
> bindings - 
> use 
> were 
> production 
> recomended 
>
>
>

[ Post a follow-up to this message ]

You can use both the BizTalk ExplorerOM directly or use the WMI classes to
create small configuration applications.

--
Jon Flanders [DevelopMentor]
http://staff.develop.com/jfland/
http://www.develop.com/courses/biztalk
"eXavier" <fhns@centrum.cz> wrote in message
news:uK8Jofz8EHA.3416@TK2MSFTNGP09.phx.gbl...
> Hi Hugo, thanks a lot. But this seems to me rather as a workaround than
> administrator's tool, this procedure I consider as developer approach -
> <CustomProps> XML is escaped under <ReceiveLocationTransportTypeData>
> element and it is not very readable.
>
> I found quite nice tool:
>
http://www.gotdotnet.com/workspaces...24-4dcba88f7464[v
bcol=seagreen]
> but still don't understand what lead Microsoft to not provide Receive
> Location editation from within Biztalk administration console. It is[/vbcol]
strange
> assumption that developer should configure production environment.
>
>
> "Hugo Rodger-Brown" <hugo@coldhams.com> wrote in message
> news:uz3wIry8EHA.2452@TK2MSFTNGP14.phx.gbl... 
> bindings - 
> use 
> were 
> production 
tools).[vbcol=seagreen] 
locations[vbcol=seagreen] 
was[vbcol=seagreen] 
be[vbcol=seagreen] 
> recomended 
>
>

[ Post a follow-up to this message ]