Hi,

Can anyone please direct me to a good article about biztalk load balancing ,
The thing is that I want two identical biztalks servers wich will perform
the same jobs ober load balancing
In all the articles that I red so far the tasks is devided between several
biztalk servers some of them
are doinf receive some orchestration etc...

Do I need BizTalk Enterprise for this ?

Many thanks in advance
Zahi Savion

[ Post a follow-up to this message ]

If you havent seen the architecture webcast, it will probably clear up some
of your questions:

http://msevents.microsoft.com/CUI/E...e=en-U
S

C.


"Zahi Savion" <nospam@go.com> wrote in message
news:OJRUvBxPEHA.3348@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> Can anyone please direct me to a good article about biztalk load balancing
,
> The thing is that I want two identical biztalks servers wich will perform
> the same jobs ober load balancing
> In all the articles that I red so far the tasks is devided between several
> biztalk servers some of them
> are doinf receive some orchestration etc...
>
> Do I need BizTalk Enterprise for this ?
>
> Many thanks in advance
> Zahi Savion
>
>

[ Post a follow-up to this message ]

The load balancing in BizTalk is achieved via the concept of BizTalk hosts. 
A host can be deployed on multiple boxes and if one of them goes down, the o
ther host instances will take up the load. You can also have multiple hosts 
on the same box, which mean
s that you have a myriad of options as to how you can deploy hosts and how m
any boxes you deploy each to.

[ Post a follow-up to this message ]

Here is a brief description on how load is balanced on the BizTalk Servers:
[vbcol=seagreen] 
Scaling Out BizTalk Servers
The four BIZTALK tiers can be broadly viewed as follows:
Receiving Servers (RxHost)
FILE: Either local or UNC path
HTTP/SOAP: Multiple NLB servers (for example, Port: 80)
MSMQT: Multiple NLB servers (for example, {Port: 1801/3527)
FTP/SQL: Multiple Receiving servers
Processing Servers (PxHost)
Multiple orchestration servers
Transmitting Servers (TxHost)
Multiple sending servers
Tracking Servers (TrkHost)
One or more Tracking servers[vbcol=seagreen] 
The BizTalk Service (BTSNTSvc.exe)
The BizTalk service is not a cluster-aware service and does not need to be
installed on a cluster. High Availability is provided by setting up
multiple redundant servers at each tier. The BizTalk Server functionality
can conceptually be divided into four tiers: Receiving, Processing,
Transmitting, and Database. At the Receiving tier, depending on the
transports used to solve the business needs, either NLB (Network Load
Balancing) can be used for the following transports HTTP/SOAP/MSMQT or
multiple servers can be deployed to provide high availability. At the
Processing (Orchestration) tier where business process workflows are
executed, multiple servers can be deployed to share the work and provide
high availability. At the transmitting tier for all transports, multiple
servers can be deployed to share the work and provide high availability.
The BizTalk service makes extensive use of memory and, depending on the
transport used, may extensively use system resources. For example, FILE
transport needs access to the file IO system. HTTP and SOAP use the HTTP
transport and require IIS. The SSO service instances use RPC to communicate
with the SSO-Master Secret Server. All BizTalk service instances use MSDTC
to commit or roll back transactions. It is not necessary to have SQL
installed locally on the BizTalk machines as long as SQL client
connectivity tools are installed. This BizTalk service also hosts the
Tracking Sub-Service and the MSMQT Sub-Service.[vbcol=seagreen] 
Scaling Out SQL Servers
BizTalk servers are by design stateless with no data persisted locally. All
data is stored in a central location within the SQL Server databases. It is
the SQL Server databases, specifically the BizTalk Management database,
which brings multiple BizTalk servers together as a single group. BizTalk
has a hard dependency on SQL Server being installed. Because SQL Server is
essential to the running of the BizTalk service, it is strongly recommended
that SQL be installed in a Highly Available manner on an MSCS cluster,
using either RAID5 or SAN disks with backup power supply. These databases
should be backed up regularly using SQL Server best practices. The BizTalk
service is designed to automatically recover from a SQL Server connection
failure. Depending on the features configured, multiple databases are
created.[vbcol=seagreen] 


Thanks,
MRoze

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]