- The Company
- Order-Fulfillment Process
- Problems with the Current Implementation
- Solution Requirements
- BizTalk Server 2004A Brief Introduction
- Proposed Solution: Hardware
- Messaging Protocols
- Proposed Solution: BizTalk Application
- Business Rules
- BizTalk Licensing
- Time Estimate
- Cost Estimate
Archie does not like the fact that the two BizTalk server machines will be a single CPU; he prefers them to be dual-CPU servers for robust message processing. So he researches BizTalk Server 2004 licensing options.
BizTalk Server 2004 comes with two major licensing options: the Standard edition and the Enterprise edition. Archie cannot use the cheaper Standard edition (which costs only $5K) because the Standard version cannot be used for multi-server configurations; it is limited to one single-CPU server. For the Enterprise edition, one license is required per CPU. So if he were using dual CPU servers, he would need four licenses and the cost of the licenses would double: to $100K. Obviously, this figure does not meet his budget guidelines. So Archie decides that two single CPU servers are the best option for now.
He has another bottleneck with respect to SSO Server licensing, which will be installed on the SQL Server cluster. (SSO service needs to be fail-proof so it needs to be installed on a cluster.) The cluster consists of two dual-CPU servers. Microsoft specifies that SSO service can be installed only on as many CPUs as the number of BizTalk Server licenses purchased. This requirement poses a problem because PinkAndBlue will be buying only two licenses.
Archie lets the bosses know about this problem and leaves it up to them to negotiate a workaround with Microsoft. They work this out with Microsoft, possibly by indicating the intent of future BizTalk license purchases.