Configuring an XML Request-Reply Bridge
This topic provides instructions on how to configure an XML Request-Reply Bridge as part of an Enterprise Application Integration project. Note that the entry-point to an Enterprise Application Integration project must be either an XML Request-Reply Bridge or an XML One-Way Bridge. For instructions on how to configure an XML One-Way Bridge, see Configuring an XML One-Way Bridge.
An XML Request-Reply Bridge has different stages namely Validate, Enrich, Transform, Enrich (post-Transform), for the request path and then Enrich, Transform, Enrich (post-Transform), and Reply Action for the response path. This section provides instruction on how to configure each of these stages. Typically, the steps to configure an XML Request-Reply Bridge would be the following:
-
Add an XML Request-Reply Bridge to the Enterprise Application Integration project.
-
Specify the schemas for the XML messages that can be processed by the XML Request-Reply Bridge.
-
Configure the different stages of the XML Request-Reply Bridge.
The topics in this section provide instructions on how to perform each of these tasks.
In This Section
- Adding an XML Request-Reply Bridge to an Enterprise Application Integration Project
- XML Request-Reply Bridge : Specifying the Schemas for the Request and Response Messages
- XML Request-Reply Bridge : Configuring the Validate Stage for the Request Message
- XML Request-Reply Bridge : Configuring the Enrich Stage for the Request Message
- XML Request-Reply Bridge : Configuring the Transform Stage for the Request Message
- XML Request-Reply Bridge : Configuring the Enrich Stage (post-Transform) for the Request Message
- XML Request-Reply Bridge : Configuring the Enrich Stage for the Response Message
- XML Request-Reply Bridge : Configuring the Transform Stage for the Response Message
- XML Request-Reply Bridge : Configuring the Enrich Stage (post-Transform) for the Response Message
- XML Request-Reply Bridge : Configuring the Reply Action Before Routing the Response Message
See Also
© 2011 Microsoft Corporation. All rights reserved.