| Author |
Deploy same assembly to different hosts???
|
|
| Morten Overgaard 2004-11-15, 7:46 am |
| Hi
Is it possible to deploy the same assembly on the same BT2004 server into
differents hosts on that server?
Lets say we have a US and a CAN host - and we want to run the assembly in
both hosts.
Regards Morten
| |
| Scott Cairney 2004-11-15, 5:49 pm |
| Hi Morten, as far as I know, you can only deploy 1 version once in the
GAC... so your orchestrations and other artifacts will belong to 1 host.
As a workaround you could have 2 versions of the assembly - but that would
be silly not to mention a maintenance headache if they were the identical.
Or run them in a NorthAmerica host... question is why do you need to isolate
them in hosts?
"Morten Overgaard" <mov@oticon.dk> wrote in message
news:uu46QAwyEHA.2788@TK2MSFTNGP15.phx.gbl...
> Hi
>
> Is it possible to deploy the same assembly on the same BT2004 server into
> differents hosts on that server?
>
> Lets say we have a US and a CAN host - and we want to run the assembly in
> both hosts.
>
> Regards Morten
>
>
| |
| Morten Overgaard 2004-11-15, 5:49 pm |
| Our initially reason were
1) different receive locations and send locations existed for the 2 US and
CAN
2) Different configuration files are neede by orchestration dependent on the
Site. (We are using Database lookups - and the databases varies based on US
or CAN etc. )
But I can get around this by putting an ID in the message header which
determine the origin of the message. Any comments on this is appreciated?
Thanks for your answer.
Regards Morten
"Scott Cairney" <Scott@ScottCairney.Com> wrote in message
news:%23LwV0cyyEHA.3624@TK2MSFTNGP09.phx.gbl...
> Hi Morten, as far as I know, you can only deploy 1 version once in the
> GAC... so your orchestrations and other artifacts will belong to 1 host.
>
> As a workaround you could have 2 versions of the assembly - but that would
> be silly not to mention a maintenance headache if they were the identical.
>
> Or run them in a NorthAmerica host... question is why do you need to
isolate
> them in hosts?
>
>
> "Morten Overgaard" <mov@oticon.dk> wrote in message
> news:uu46QAwyEHA.2788@TK2MSFTNGP15.phx.gbl...
into[vbcol=seagreen]
in[vbcol=seagreen]
>
>
| |
| Scott Cairney 2004-11-16, 7:46 am |
| Hi Morten, you should not have a problem specifying different locations for
US and Canada also, I don't know that you need a header, the receive
location information will be available to you in the orchestration.
This will be much easier to manage, and implement... just a decision shape
in BizTalk.
Good luck!
Scott
"Morten Overgaard" <mov@oticon.dk> wrote in message
news:#mfS9s1yEHA.2600@TK2MSFTNGP09.phx.gbl...
> Our initially reason were
> 1) different receive locations and send locations existed for the 2 US and
> CAN
> 2) Different configuration files are neede by orchestration dependent on
the
> Site. (We are using Database lookups - and the databases varies based on
US
> or CAN etc. )
>
>
> But I can get around this by putting an ID in the message header which
> determine the origin of the message. Any comments on this is appreciated?
>
> Thanks for your answer.
>
> Regards Morten
> "Scott Cairney" <Scott@ScottCairney.Com> wrote in message
> news:%23LwV0cyyEHA.3624@TK2MSFTNGP09.phx.gbl...
would[vbcol=seagreen]
identical.[vbcol=seagreen]
> isolate
> into
> in
>
>
| |
| Morten Overgaard 2004-11-16, 2:28 pm |
| Thanks for your help :-)
Regards Morten
"Scott Cairney" <Scott@ScottCairney.Com> wrote in message
news:OaurQW%23yEHA.1396@tk2msftngp13.phx.gbl...
> Hi Morten, you should not have a problem specifying different locations
for
> US and Canada also, I don't know that you need a header, the receive
> location information will be available to you in the orchestration.
>
> This will be much easier to manage, and implement... just a decision shape
> in BizTalk.
>
> Good luck!
>
> Scott
>
>
>
> "Morten Overgaard" <mov@oticon.dk> wrote in message
> news:#mfS9s1yEHA.2600@TK2MSFTNGP09.phx.gbl...
and[vbcol=seagreen]
> the
> US
appreciated?[vbcol=seagreen]
host.[vbcol=seagreen]
> would
> identical.
assembly[vbcol=seagreen]
>
>
|
|
|
|