|
Home > Archive > BizTalk Server General > July 2004 > issue with enlisting an orchestration on a joined biztalk server
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 |
issue with enlisting an orchestration on a joined biztalk server
|
|
| biztalker 2004-07-29, 8:46 pm |
| hello
first question: if i already have biztalk server 2004 installed on box 1 with the databases residing on a separate sql server, and if i were to install bts 2k4 on box 2 and configure it to 'join' the pre-existing biztalk server, i have essentially created
a cluster. and all joining one bts to another bts does is share the same set of databases. is that correct?
second: i already had some biz projects deployed and running on box 1. when i configured bts on box 2 (joining it to another installation), everything went smoothly. to test, i created a simple filedrop biz project that would receive an xml doc in a folde
r and ship it off to another folder. so i deployed the project, and in the biztalk explorer, binded stuff. however, when i tried to enlist the orchestration, the biztalk explorer - express enlisting dialog popped up, but apparantly, the system hung up on
me. i was not able to do anything in vs. when i checked the event logg, saw a couple of errors where it was trying to find physical receive/drop locations defined for other projects deployed on box 1. and i saw similar errors on box 1 where it was trying
to find the receive/send location defined in the newly created test project on box 2.
i tried connecting to box 1, and from there, i was able to enlist and start box 2 project without any problems. however, the test project would not work unless i stopped the biztalk host on box 1.
can someone make me see the light and show me where the picture starts going wrong?
| |
| Matt Milner 2004-07-30, 5:49 pm |
| See my other response on your other post, but one more thing:
When you have this setup, the concept of hosts and host instances becomes
very important to understand because this is what determines:
where your stuff (orchestrations, pipelines, ports) runs
what security context the stuff runs under (authentication trusted, etc.)
how the load is distributed
Matt
"biztalker" <biztalker@discussions.microsoft.com> wrote in message
news:7E7C8829-FF11-4F37-BC2E-ED7755B7B36F@microsoft.com...
> hello
>
> first question: if i already have biztalk server 2004 installed on box 1
with the databases residing on a separate sql server, and if i were to
install bts 2k4 on box 2 and configure it to 'join' the pre-existing biztalk
server, i have essentially created a cluster. and all joining one bts to
another bts does is share the same set of databases. is that correct?
>
> second: i already had some biz projects deployed and running on box 1.
when i configured bts on box 2 (joining it to another installation),
everything went smoothly. to test, i created a simple filedrop biz project
that would receive an xml doc in a folder and ship it off to another folder.
so i deployed the project, and in the biztalk explorer, binded stuff.
however, when i tried to enlist the orchestration, the biztalk explorer -
express enlisting dialog popped up, but apparantly, the system hung up on
me. i was not able to do anything in vs. when i checked the event logg, saw
a couple of errors where it was trying to find physical receive/drop
locations defined for other projects deployed on box 1. and i saw similar
errors on box 1 where it was trying to find the receive/send location
defined in the newly created test project on box 2.
>
> i tried connecting to box 1, and from there, i was able to enlist and
start box 2 project without any problems. however, the test project would
not work unless i stopped the biztalk host on box 1.
>
> can someone make me see the light and show me where the picture starts
going wrong?
|
|
|
|
|