jump to navigation

BizTalk Server 2004 August 12, 2005

Posted by Coolguy in Microsoft Technologies.
  • Tool to integrate systems.
  • It supports the goal of creating business processes that unite separate applications into a coherent whole
  • A business process is a set of actions that together meet some useful business need.
  • It connects diverse applications, and then to graphically create and modify business processes that use the services that those applications provide
  • BizTalk Server 2004 is built completely around the .NET Framework and Microsoft Visual Studio® .NET.

Usage scenarios

  • BizTalk Server is used for application integration in the following scenarios:
  • Connecting applications within a single organization commonly referred to as enterprise application integration (EAI). (70 percent of BizTalk deployments are for EAI)
  • Connecting applications in different organizations, often called business-to-business (B2B) integration

BizTalk Server engine

  • Engine works only with XML documents internally
  • Whatever format a message arrives in, it is always converted to an XML document after it is received.
  • Similarly, if the recipient of a document cannot accept that document as XML, the engine converts it into the format expected by the target application.


  • A message is received through a receive adapter.
  • An adapter is an implementation of a communication mechanism, such as a particular protocol.
  • BizTalk Server 2004 provides built-in adapters, and adapters have been created for popular applications such as SAP.
  • A developer can determine which adapters to use in a given situation, or can create custom adapters for specific needs.
  • E.g’s of Adapters:
    SOAP adapter.
    BizTalk Message Queuing adapter.
    File adapter
    HTTP adapter
    SMTP adapter
    SQL adapter.
    Base EDI adapter.
    FTP adapter


  • Processing of the message can involve multiple steps, and it is performed by a message pipeline.
  • Incoming messages are processed through a receive pipeline, while outgoing messages go through a send pipeline
  • A developer can also create custom pipelines by using the Pipeline Designer tool.


  • After a message has passed through an adapter and a receive pipeline, the business process must determine where it should go.
  • A message is most often targeted to an orchestration, but it is also possible for a message to go directly to a send pipeline, using the BizTalk Server 2004 engine purely as a messaging system
  • In either case, messages are matched with their destinations through subscriptions
  • For example, an orchestration might create a subscription that matches all messages of the type “Invoice”, or all messages of the type “Invoice” received from Woodgrove Bank, or all messages of the type “Invoice” received from Woodgrove Bank that are for more than $10,000.


  • Enables you to create a business process graphically.
  • Tools available are:
    BizTalk Editor: Creating Schemas using XSD
    BizTalk Mapper: Mapping Between Schemas using XSLT transformations Orchestration Designer: Its used to defining business processes.
  • Some of the tasks available include Receive,Send,Port, Decide. Loop. Construct Message. Transform. Parallel Actions. Scope. Message Assignment
  • Ultimately, the group of shapes that you define in BizTalk Server 2004 becomes just a standard .NET assembly

Business Rule Engine

  • Enables more business-oriented users to directly create and modify sets of business rules.
  • These rules are created by using a tool called the Business Rule Composer, and then executed directly by the engine. This technology is new in BizTalk Server 2004.
  • The change takes effect immediately. And while orchestrations are typically created and maintained by developers, business rules are readable enough to be modified by business analysts without the need to involve more technical people
  • Additional features in Biztalk server 2004 include:
    Enterprise Single Sign-On Business Activity Monitoring


  • Are used to support specific industries and scenarios
    HL7: Messaging solution for patient information within and between healthcare systems HIPAA : Health Insurance Portability and Accountability Act
    SWIFT: Financial institutions

User Roles

  • Three roles are necessary to create and maintain BizTalk Server 2004 applications.
    · Business analyst.
    · Developer.
    · Administrator.

Editions and Licensing

  • Enterprise Edition: Unlimited CPU’s, unlimited number of internal applications and external trading partners
  • Standard Edition: Single CPU and integration with up to 10 applications and 20 trading partners, no fail over and scalability
  • Partner Edition: Integration with up to three applications and three trading partners.
  • Developer Edition: Designing, developing, and testing purposes
  • BizTalk Server 2004 requires Microsoft SQL Server and Microsoft Windows Server 2003 to install.
  • BizTalk Server require one production license for each processor


  • webMethods
  • BEA
  • OpenEAI
  • Tibco
  • SeeBeyond
  • Vitria






No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: