Step 7: Test the Azure BizTalk Solution
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
Test the BizTalk Services EAI scenario by sending a XML sales order message to the endpoint where the XML Request-Reply Bridge is deployed.
To send a message to the bridge
Download the MessageSender tool from Azure BizTalk Services Samples.
Build the project and use the resulting MessageSender command line executable to send messages to the deployed bridge. This tool accepts command line parameters; the sequence and usage of those parameters are:
MessageSender.exe <ACSNamespace> <IssuerName> <IssuerKey> <RuntimeAddress> <MessageFilepath> <ContentType>
Where:
Parameter name
Description
ACSNamespace
The Access Control namespace
IssuerName
Issuer Name for the above namespace
IssuerKey
Issuer Key for the above namespace
RuntimeAddress
Runtime address or the endpoint URL where the bridge is deployed. You got this address in Step 6: Build and Deploy the Project.
MessageFilePath
Path to the file that contains the request message to be sent to the bridge. This request message must be compliant with the ECommerceSalesOrder.xsd schema.
You can create an XML instance request message using the request schema you created in Step 2: Create SalesOrder Schema. Alternatively, you can use the SalesOrder.xml sample message available in the sample at MSDN Code Gallery.
ContentType
Determine whether it’s an XML message or an EDI message:
For XML message, set this to application/xml.
For EDI message, set this to text/plain.
For this tutorial, to test the EAI scenario, open a command prompt, go to the solution where you built the MessageSender project, and run the following command:
MessageSender.exe <ACSNamespace> <IssuerName> <IssuerKey> <endpoint URL of the bridge > <complete path to the request message> "application/xml"
This application sends the message to the deployed endpoint and prints the success/failure message.
Upon successful completion, the SalesOrder table in Northwind’s database has a new sales order entry created.