|
Home > Archive > BizTalk Server General > June 2004 > biztalk distinction between an application and a trading partner
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 |
biztalk distinction between an application and a trading partner
|
|
| biztalker 2004-06-30, 5:55 pm |
| quoting from the pricing info site for biztalk :
"BizTalk Server 2004 Enterprise Edition is designed for customers who require high volume and high availability, and scalability to an unlimited number of CPUs. This edition supports integration with an unlimited number of internal applications and extern
al trading partners. BizTalk Server 2004 Standard Edition supports integration with up to 10 applications and 20 trading partners. BizTalk Server 2004 Partner Edition supports integration with up to three applications and three trading partners."
what does bizTalk view as an application and as a trading partner; how does it differentiate between the two? does it (logically) tie a receive port to an application, and a send port to a trading partner?
thanks
| |
| Gilles [MSFT] 2004-06-30, 5:55 pm |
| Hello,
>quoting from the pricing info site for biztalk :
>
>"BizTalk Server 2004 Enterprise Edition is designed for customers who require high volume and high availability, and scalability to an unlimited
>number of CPUs. This edition supports integration with an unlimited number of internal applications and external trading partners. BizTalk Server 2004
>Standard Edition supports integration with up to 10 applications and 20 trading partners. BizTalk Server 2004 Partner Edition supports integration with
>up to three applications and three trading partners."
>
>what does bizTalk view as an application and as a trading partner; how does it differentiate between the two? does it (logically) tie a receive port to an
>application, and a send port to a trading partner?
The licensing FAQ at http://download.microsoft.com/downl...icensingFAQ.doc
addresses this. For your reference, I copied and pasted the question here:
<quote>
Q: What is the definition of an internal application and a trading partner?
A: Although this definition is not in the EULA or Product Use Rights (PUR), we define an internal application as a distinct application that runs
on a single logical machine within the firewall of an organization. We do not require customers to count each end-device or application, just the
application that integrates directly with Microsoft BizTalk Server. For example, this means customers who have BTS04 STD edition
can connect to an ERP system, a CRM System, a SCM System, a legacy app on the mainframe, and a database as five distinct internal applications
under the STD license. As another example, this also means that customers who have BTS04 STD Edition could make a single internal
connection to another EAI product that in turn brings together data from seven other applications or databases. In this scenario, that would only
count as one internal connection, not seven.
Although this definition is not in the EULA or PUR specifically, we define a trading partner as a distinct parent entity across the Internet.
We do not require customers to count each end-device, application or logical machine, just the parent entity that integrates directly with Microsoft
BizTalk Server from across the firewall. For example, a customer who is using BTS04 STD edition to connect to a large trading partner that has three
divisions, each located at different sites around the world, needs only one external trading partner connection, not three.
</quote>
Thanks.
-Gilles.
|
|
|
|
|