␡
- 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
- Tracking
- BizTalk Licensing
- Time Estimate
- Cost Estimate
- Implementation
- Conclusion
- References
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Proposed Solution: Hardware
Archie comes up with a hardware solution, as follows (see Figure 2):
- BizTalk Server 2004 configuration and messaging databases will be installed on the existing SQL Server cluster.
- The BizTalk Server 2004 software itself will be installed on two PII 3GHz single CPU servers with 1GB RAM and 20GB hard disk.
- The BizTalk Server 2004 needs the SSO (single sign-on) service that has to be installed on a clustered server for failover scenarios. SSO service provides message security when integrating with third-party sites. SSO is a mandatory component of BizTalk Server 2004. Archie decides to install this service on the SQL Server cluster. The service itself has a small footprint, so it will not affect the performance of other applications.
)
This configuration satisfies the following objectives set by PinkAndBlue Management:
- Low hardware cost: The two servers cost just $5K each.
- Automatic failover capability: The two servers act as a failover for each other (if one of the machines fails, the other machine will take over any receive ports and orchestrations that were being processed by the failed server). This process is automatic; it needs no manual intervention.
- The configuration has the added bonus of load balancing and scalability: The two BizTalk Server 2004 machines are both actively processing messages at any given time, which provides scalability of the solution. As more capacity is required, more similar BizTalk Servers can be added.