BackGround:

We have 2 BizTalk servers and we have only been using 1 of them. 1 has just
been collecting dust in a corner.  We now want to turn up the 2nd BizTalk
server.  We have a current process that uses an FTP receive adapter, and
there were issues when we first started using BizTalk (and had both servers
running) because of the known issue with FTP receive ports not playing nice,
(both instances will receive a message coming into the BizTalk group from an
incoming FTP site, and both instances will process the message through the
orchestration. The net effect of these actions is that the message will be
processed twice) we turned off the 2nd server.





After doing some research and getting some help, we came up with a solution
to run both servers in an active/passive manner.  We never did implement
this solution, and now we are thinking we want to go with an active/active
solution. here is some information on how we see it running.



We have both biztalk servers up and running using the same host (the
BizTalkServerApplication host).  We have 1 SQL server (or maybe 2 that are
clustered).   Because the 2 BizTalk servers are using the same host, they
will 'load balance' all the processes we have running.  We still have an
issue with the 1 process that is using the FTP receive adapter, and this is
how we propose handling it.

1)      I create a new In-Process host (on BOTH BizTalk servers).  I set the
name, the windows group (I am setting this to the same value as the
BizTalkServerApplication host), and I check the Host tacking check box.

2)      I create a new instance of this host, and start it

3)      Now (on BizTalk server 01) in the orchestration for the process that
uses the FTP receive adapter,  I set the host to be the one I just created.

4)      Now (on BizTalk server 02) in the orchestration for the process that
uses the FTP receive adapter,  I set the host to be the one I just created.
BUT, on this server, I stop the host so the process won't run on the
server - we will just manually start this host if the BizTalk server 01
fails.

5)      QUESTION/CONCERN - I think the above will work, but on the actual
FTP receiver location, I am not able to set the Receive Handler to the new
host I created, so I'm afraid the files will still be picked up by this
receive location (the one where the orchestration host is set to the host
that has stopped).



Thanks!

[ Post a follow-up to this message ]

I got the anser from Jon Flanders... thanks Jon!


ANSWER:
Hey Brian - I think you have it all right - the thing you have to do is go
into the BizTalk Admin MMC and make the host you created a registered
Receive Handler for the FTP adapter (you do this under the FTP adapter
node - right-click on it and say "Add Receive Handler).

"Brian Cesafsky" <brian.cesafsky@autotrackerplus.com> wrote in message
news:uwI659wMGHA.1288@TK2MSFTNGP09.phx.gbl...
> BackGround:
>
> We have 2 BizTalk servers and we have only been using 1 of them. 1 has
> just been collecting dust in a corner.  We now want to turn up the 2nd
> BizTalk server.  We have a current process that uses an FTP receive
> adapter, and there were issues when we first started using BizTalk (and
> had both servers running) because of the known issue with FTP receive
> ports not playing nice, (both instances will receive a message coming into
> the BizTalk group from an incoming FTP site, and both instances will
> process the message through the orchestration. The net effect of these
> actions is that the message will be processed twice) we turned off the 2nd
> server.
>
>
>
>
>
> After doing some research and getting some help, we came up with a
> solution to run both servers in an active/passive manner.  We never did
> implement this solution, and now we are thinking we want to go with an
> active/active solution. here is some information on how we see it running.
>
>
>
> We have both biztalk servers up and running using the same host (the
> BizTalkServerApplication host).  We have 1 SQL server (or maybe 2 that are
> clustered).   Because the 2 BizTalk servers are using the same host, they
> will 'load balance' all the processes we have running.  We still have an
> issue with the 1 process that is using the FTP receive adapter, and this
> is how we propose handling it.
>
> 1)      I create a new In-Process host (on BOTH BizTalk servers).  I set
> the name, the windows group (I am setting this to the same value as the
> BizTalkServerApplication host), and I check the Host tacking check box.
>
> 2)      I create a new instance of this host, and start it
>
> 3)      Now (on BizTalk server 01) in the orchestration for the process
> that uses the FTP receive adapter,  I set the host to be the one I just
> created.
>
> 4)      Now (on BizTalk server 02) in the orchestration for the process
> that uses the FTP receive adapter,  I set the host to be the one I just
> created. BUT, on this server, I stop the host so the process won't run on
> the server - we will just manually start this host if the BizTalk server
> 01 fails.
>
> 5)      QUESTION/CONCERN - I think the above will work, but on the actual
> FTP receiver location, I am not able to set the Receive Handler to the new
> host I created, so I'm afraid the files will still be picked up by this
> receive location (the one where the orchestration host is set to the host
> that has stopped).
>
>
>
> Thanks!
>
>
>

[ Post a follow-up to this message ]