RE: BizTalk server Topology & scalibilty

HaloX,

I'm afraid the simple answer to your question is No.

What you are essentially asking is to split different but related activities
within the BizTalk engine across multiple engines on different servers. As
Hugo points out BizTalk is stateless, that is to say all state is maintained
only in the SQL server databases (unless one inadvertently starts creating
stateful adapters, orchestrations, etc but that's another story). This
includes orchestrations, pipelines etc. So, in a non-deterministic way the
load from receive to send *may* be processed by different servers, for
example if the orchestration instance is dehydated to the SQL store and
subsequently rehydrated on another box.

But this is non-deterministic and as such you aren't able to *specify*
particular servers for particular tasks at this granularity. The only way to
achieve this is to perform routing between servers (by name) within say an
internal service such that a received request is passed by an orchestration
on box A to box B which will send a reply. This would require some
hoop-jumping though to avoid a request/reply pattern just passing straight
back through both boxes for the response. It probably wouldn't buy you much
either if perf or scalability is what you're after.

However, if you are not using a request/reply pattern, say you are using a
one-way request and one-way response, then you could just deploy each of
these to different machines (groups - that don't share the same SQL config)
and configure it to achieve what you want. The connection (if any) between
the two though then has to be handled by you explicitly i.e. you'll have to
do your own correlation.

Hope this helps clarify it a bit for you. I am interested why this is your
desired config?

"HaloX" wrote:

> Looking through the BizTalk documentation and books I see recommended
> configuration of hosts. There are the following configurations:
>
> 1) Single server: Single server runs ALL BizTalk and SQL operations
> 2) Two Server: A single server runs SQL while another runs all BizTalk
> operations.
> 3) Multiple Server: Multiple servers running BizTalk and configured with
> each machine host running specific isolated functions to scale out the
> receive, processing, transmitting and tracking. One or more (recommended for
> this configuration) servers running SQL in cluster.
>
> Now, the issue is I have a SQL cluster running SPS. I want to leverage this
> cluster because it is hardly tasked and I will have BizTalk run on a seprate
> SQL instance. I would like to have two machines running BizTalk:
>
> * One configured a Message Box Master Recieve, and Tracking
> * One configured for Transmit and Orchestrations
>
> Will BizTalk support this configuration. Nothing in the documentation
> identifies if certain configs AREN'T supported, but from my experience this
> doesn't mean much. In SPS there are certain configs not supported and
> nothing in the initial documentation identified this.
>
> Thanks
.

Relevant Pages

  • Re: BizTalk server Topology & scalibilty
    ... BizTalk itself is 'stateless' and so can run on any machine that has access ... host instances is unrelated to the distribution of databases across SQL. ... could have all dbs installed on a single SQL server, or each on its own SQL ... > configuration of hosts. ...
    (microsoft.public.biztalk.server)
  • Re: BizTalk Server 2004 ConfigFramework.exe error
    ... I have problem to pass the SSO setup during the configuration process. ... > and trying to configure this server 2nd. ... > the SSO server needs to be the first server configured in a BizTalk group. ... Do you mean that your SQL Server is on different box from the ...
    (microsoft.public.biztalk.general)
  • Re: Installation problem
    ... I checked the sql log most of the times it says user logged in successfully ... (User being sa, local admin on BizTalk server, part of SSO ... created and the error didn't occur until the configuration started on ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk server Topology & scalibilty
    ... ard bound to a host, and orchestrations can be bound to a host. ... > within the BizTalk engine across multiple engines on different servers. ... >> this configuration) servers running SQL in cluster. ...
    (microsoft.public.biztalk.server)
  • SQL 2005 servers with multiple instances
    ... I have an interesting configuration that I was hoping others might comment ... consider the two servers with many small drives for the 'Live' data ... is being shared for the Live data and the Redundant data/logs. ... To my knowledge, SQL provides no prioritization, other ...
    (microsoft.public.sqlserver.setup)