R – BizTalk 2006 R2 EDI

Below is a description of how to do this - I'm going to presume at least basic knowledge of things like BizTalk mapping, please let me know if you need any more detail and I'll update.

After generating the items in BizTalk you should have (at the least):

• An orchestration file with Messages and Port Types created
• A schema that describes the messages you send and receive from and to your WCF service

• A .Binding.xml file that describes the service contract exposed by the WCF service and allows easy configuration in BizTalk

  1. Open the orchestration file. This should be empty.

• Drag a Port from the toolbox onto the orchestration designer surface.

• Name the port appropriately.
• Select "Use an existing Port Type" - one of the existing port types will be your WCF service (created by the Add Generated Items wizard)
• Specify that you will be sending and receiving messages
• Specify Bind Later

This port should have Request and Response operation messages and they should have been automatically configured to use the messages for your WCF service. If your service exposes multiple operations, you will see that reflected here.

2. Using standard BizTalk mapping methods, map the data you want to send to the WCF service into the request message for the WCf port. (you may want the change the message names in the orchestration designer to be something better than the default message_1, message_2...)

3. Drag Receive and Send shapes onto the orchestration designer and connect them to the right Port messages.

4. Wire up the rest of the BizTalk orchestration to take data from appropriate source systems (this is just basic BizTalk, not WCF)

5. Deploy the BizTalk application.

   The application is now ready to go, you can deploy it to BizTalk.

6. Configure the BizTalk application

   • Open the BizTalk Server 2006 Administration Console and find the application containing the orchestration you just deployed.
   • The orchestraion will be unenlisted, you need to bind all of its ports
     For most of the ports this is just like any other BizTalk application - only the ports that deal with the WCF service differ.

For the WCF ports you have (at least to begin with) two main options:

1. Import the bindings file made by the BizTalk Generate Items wizard (right click on the applicaiton and import - navigate to the .xml binding file) - Perhaps advisable until you have an idea of how Biztalk represents all the WCF binding options.

2. Configure your own WCF send port.

   • For this the port needs to be Solicit-Response to match the WCF service.
   • Choose one of the WCF Send Port types to match the binding type of your WCF service.
     To begin with (for a basic Webservice) this will often be WCF-BasicHttp.
     Once you have the basics working you might want to return here and experiment with the options available in the Custom binding - there is a LOT there!
   • Configure the send port.
     • In the general tab enter the url where the .svc file is specified
       e.g. http://localhost/WCF/myservice.svc
     • Set the Action to match the action specified in the WCF service .wsdl file
       e.g. http://tempuri.org/IMyContract/MyMethod

With your WCF port now created you can bind the orchestration ports to it.

Once all this is done, you should be able to start the BizTalk application and things should work.

One thing that may help - errors will be written to the event log, they may not be helpful, but you should also be able to see any soap fault messages returned from the service in the suspended message view.

Good luck!

I can't see anything glaringly obvious, possibly other than the shoutcase of utf-8 in the charset Content Type header.

And I've assumed the soap body payloads (........) are identical - you might check whether the Soap Action is specified in the message as well as the header - I'm not sure if SAP web service is SOAP 1.1 or 1.2 WCF Soap Actions in HTTP header or SOAP header?

One possible thing to try is to use the XmlTransmit send pipeline on your send port and experiment with Preserve BOM (i.e. Add / Remove the UTF BOM on the payload) and also try the target charset set to shoutcase UTF-8.

As a last resort, instead of using WebServices, try the Consume Adapter Service for SAP - see here and here