Verifying the solution

We need to test sending two kinds of messages: one from the corporates and the other coming from the website:

• Load the MessageReceiver sample in VS and build the solution. From the output bin folder, run the following in a command prompt window:

  MessageReceiver.exe ServiceBusNS owner issuerkey USAddressRelay OneWayRelay

  Here, ServiceBusNS is the namespace where the relay is running and MyRelayTestSvc1 is the endpoint information configured in the bridge configuration.

• Load another MessageReceiver in a new command window.

  MessageReceiver.exe ServiceBusNS owner issuerkey IntlAddressQueue Queue

  Here, ServiceBusNS is the namespace where the Queue has been precreated and IntlAddressQueue is the endpoint information configured with the bridge.

• Load the MessageSender sample in VS and build the solution. <yourdeployment> is the URL where BizTalk Services was provisioned earlier.

  MessageSender.exe BizTalkSvcACS owner issuerkey https://<yourdeployment>/default/OrderProcessingBridge instance.xml application/xml

  Here, BizTalkSvcACS is the namespace of the BizTalk Service deployment ACS, owner and issuerkey are the ACS credentials of that namespace, and instance.xml is the OrderFF.xsd instance in XML format.

• The output is observed in the MessageReceiver of the relay.

• Edit instance.xml with location=EU and run the MessageSender command again. This time the output will be observed in the MessageReceiver of the Queue.

• Drop a flat file in FTP with location=US and observe the output in the relay service window.

• Drop a flat file in FTP with location=EU and observe the output in the message receive queue.

Northwind can now process both flat files and XML orders from either HTTP or FTP endpoints. You can delete the bridge from the BizTalk Services portal Bridge view or by using PowerShell.