Biz Talk is a Business Process Management server from Microsoft. It is a message based integration tool. Biz Talk enables large enterprises to automate and integrate the business processes. This process is done by using adapters those are tailored for communicating among various software systems in an enterprise. It provides functions like Business Process Modeling, Business-to-Business communication, Message broker, EAI, Process automation. Biz Talk enables enterprises for integrating and managing business processes by exchanging various documents such as PO (Purchase Order), Invoices within and across boundaries of enterprises. MS Visual Studio supports development for Biz Talk server.
☆ Receive Port:
Listens for messages.
Information interchange with external systems
☆ Pipeline, dis-assembler and sub-components:
Normalizing the schema's (wire message in its native format) of the internal messages using XML as the common language.
Internal XML messages are published here and then are further consumed by Subscribers.
☆ Subscribers (Send Port and Orchestration components):
Subscribe to internal messages per metadata or message context properties.
☆ Biz-talk Orchestration Engine:
Processing the internal messages, re-publishing them to Message-box to be consumed by other subscribers.
☆ Send Port:
Consumes the internal XML messages, converts them to a wire messages through the associated pipeline and sub-component Assembler.
Conveys the wire message to the target system.
Sending messages from one orchestration to another is done by using Direct Binding technique. It is also being used for sending messages directly into the message box. It is used in publish and subscribe system in BizTalk for sending messages among orchestrations.
A pipe line is used to write Distinguished Fields in the message context when a message is received on a port. Dis-assembler pipeline component such as XML and flat file disassemble does the job of writing the message context by the pipeline. In addition to it, custom pipeline component could also be performing it.
1) By using content based routing, files can be transferred.
2) By creating receive port and send port. If send port is configuring, provide the condition as BTS.
3) Receiveportname= <receive_portname created>
Information worker can set parameters for an orchestration that implements a business process, which a business analyst may not be able to create.
Developer creating an orchestration can define parameters for an orchestration to enable information workers configure it. An information worker sets those parameters using the TPM service by specifying their values in the partner's agreement.
Information workers Manage trading partner relationships within organizations. Business Activity Services include a Trading Partner Management (TPM) component to allow them do those. TPM database stores information about trading relationships. Information workers can create and modify agreements with trading partners who use BizTalk Server.
BizTalk is a product while Web Services are a standard.
BizTalk Server is a Microsoft product whereas Web Services have been developed by many organizations including Microsoft, IBM, etc.
BizTalk Server application has been built to enable the internal business processes of organizations, operate with ease. Web Services are small applications published using UDDI to enable all the people find them.
Web services are that they are platform neutral. BizTalk can leverage Web services.
Message routing is a method of passing through BizTalk without being processed.
Content routing is a method of passing of the message which is based on certain field value of the schema.
Content-based routing provides flexibility for users who want to route messages based on envelope properties or on receive port configuration properties. Routing can be performed based on information contained in the envelope of the document or even configuration information from the receive location.
A BizTalk Server business process involves receiving, processing, and sending messages. Some messages do not require intensive processing in an orchestration. They can benefit from a simpler and more efficient solution called Content-based routing.