Ce contenu n’est pas disponible dans votre langue. Voici la version anglaise.

Integrating BizTalk Services

Integrating BizTalk Orchestration Services and BizTalk Messaging Services allows you to control the exchange of documents and messages between your trading partners and internal applications using multiple transport services. It also provides:

  • Control over complex, long-running transactions and business processes.

  • Reliable delivery of documents and messages.

  • Data validation by verifying each document instance against a specification.

  • Data mapping by using maps to transform document structure and format.

  • Data security and integrity by using encryption and digital signature certificates.

  • Support for receipt generation and correlation.

While there are many ways to integrate BizTalk Orchestration Services and BizTalk Messaging Services, this section presents a common scenario.

In this scenario, you configure an XLANG schedule instance on the source system to initiate and send a message to a destination system of a trading partner, wait to receive a return message from that partner, and then deliver that return message to the same XLANG schedule instance that sent the initial message. One example of a common business process where you might apply this configuration is for sending a purchase order and waiting to receive a purchase order acknowledgment before continuing the process.

The topics in this section explain the configuration steps required for exchanging messages between your business and a trading partner by using an HTTP transport and a non-HTTP transport. However, you can use a similar configuration to control the exchange of messages between applications within your business.

Because BizTalk Server 2000 can serve either as the source system, which sends the initial message, or the destination system, which sends the return message, this section provides the configuration steps required for both. This also allows you to see the entire configuration that is required.

For samples of XLANG schedules that reflect these configurations and other related files, browse to the \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\Integrating BizTalk Services folder.

Ee264589.note(en-US,BTS.10).gif Notes

  • The term messaging port, which is used in BizTalk Messaging Services, and the term port, which is used in BizTalk Orchestration Services, have entirely different meanings.
    • A messaging port is a set of properties that directs BizTalk Messaging Services to transport documents to a specified destination by using a specified transport service.

    • A port is a named location that uses a specific implementation. In an XLANG schedule, ports facilitate synchronous and asynchronous communications and are used to pass messages into or out of the schedule.
  • Action events related to messages processed by an XLANG schedule that are either sent to or received from BizTalk Messaging Services can be tracked in the Tracking database. For more information, see Tracking XLANG schedule events in the Tracking database.

The following topics are covered in this section:

Related Topics