| Tim B. 2004-07-21, 5:50 pm |
| Thanks Adrian,
I worked on this over the last day and have filed a case SRX040720604541.
The problem I'm encountering seems to related to the use of a dynamic HTTP solicit response port. While I was able to have an http port and the orchestrations in different host instances with the sample httpsolicitReponse, its not working with my applica
tion. At this point the only apparent difference is that I'm using a dynamic port.
It does appear though, that since only one host can run the send handlers, that I can't truly segregate my application within its own host instance ??
Maybe I'm thinking about this in the wormg way, but it seems with the many reasons why one needs to restart the host instance that it would be nice to be able to contain an entire application in its own host instance.
Tim
"Adrian Hamza[MSFT]" wrote:
> Per configuration database (BizTalk group) you can have the following:
>
> - a send adapter will run under only one host (but multiple host
> instances). All instances of that host will run the send port.
> - for each receive location you can specify a receive handler to run that
> receive location. You can create new receive handlers in BizTalk MMC
> console (go to adapters->your adapter->Receive COnfiguration and create a
> new receive handler). The receive handler contains information about the
> host that runs that receive handler. This means that different receive
> locations can be run by different hosts.
>
> --------------------
> instance
> recommended that you deploy your orchestration and ports to seperate bts
> server instances. I haven't had any luck doing this, before I dive into
> this again I wondered if anyone has done this and could share some
> knowledge ??
> instance, so I can restart it without bothering anyone else using that
> server.
> non-default instance ?
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> EBusiness Server Team
>
>
|