Sorry to posting this question...i know this is very basic question...

but i got stuck in the application where i am not able go to correct direction my requirement is as follows: 

Application A ---> Biz-talk Application  ---> Application B.

Flow : 

1) Application A will send message to Biz-talk application and waiting for response (Application A is simple Web service).

2) Biz-talk will process this message and business logic in orchestration and will send it to Application B.

3) Application B will process and will send response back to Biz-talk application (Application B is REST Service - needs to use Basic -WCF Web Http Adapter).

Any Example for simple Web Service will also do.

Biz-talk Application will send the response back to Application.

The response will be only one field with string message in it....

can any one please help or point me to the blog where i will we more details on

This is a simple pattern. What you need to do is to expose your BizTalk Application as a web service. Refer https://msdn.microsoft.com/en-us/library/aa561883.aspx for that.

In regards to your response schema it is a simple schema with a root node and a single element within the message of type string. When you expose the orchestration as a web service, this message definition will be available to the client through the WSDL you share.

Regards.

Hi Shankycheil...thanks for help ...

I want help on the Orchestration --- how to create logical port ----messages assign it to construct shape and transform in orchestration and the create two way send  port.

Hi Nitin,

You can use BizTalk PUB & SUB architecture for this requirement, BizTalk Application A will process the message and push the same message to message BOX and on the basis of receive port filter condition you can use the message to subscribe by your Application B and then application B will process the message and send to message BOX and then Application A will subscribe that message using convoy pattern.

Regards,

Sharad

Hi Nitin,

You should refer the code sample provided by Steef.

BizTalk Server 2013: WCF-WebHttp Adapter Sample

Scenario similar to what you trying to achieve is explained. Refer the flow application as below:

Other resources related to the WCF-WebHttp worth to check out are:

• Exploring REST Capabilities of BizTalk Server 2013 (Part 1: Exposing REST Endpoints)
• Exploring REST Capabilities of BizTalk Server 2013 (Part 2: Consuming REST Endpoints)
• REST (WCF-WebHttp) adapter in BizTalk Server 2010 R2  and code
• BizTalk and Rest Example from BizTalk Saturday

Read Richard Seroter's article on how to consume REST services at https://seroter.wordpress.com/2012/11/19/exploring-rest-capabilities-of-biztalk-server-2013-part-2-consuming-rest-endpoints/ and if you want to expose it as a REST endpoint then the Part 1 of the article will help you expose the orchestration as a REST endpoint.

Regards.

This is a simple pattern. What you need to do is to expose your BizTalk Application as a web service. Refer https://msdn.microsoft.com/en-us/library/aa561883.aspx for that.

In regards to your response schema it is a simple schema with a root node and a single element within the message of type string. When you expose the orchestration as a web service, this message definition will be available to the client through the WSDL you share.

Regards.

• Proposed as answer by Kjetil Tonstad 13 hours 8 minutes ago

This is a simple pattern. What you need to do is to expose your BizTalk Application as a web service. Refer https://msdn.microsoft.com/en-us/library/aa561883.aspx for that.

In regards to your response schema it is a simple schema with a root node and a single element within the message of type string. When you expose the orchestration as a web service, this message definition will be available to the client through the WSDL you share.

Regards.

• Proposed as answer by Kjetil Tonstad Monday, July 27, 2015 5:57 PM

This is a simple pattern. What you need to do is to expose your BizTalk Application as a web service. Refer https://msdn.microsoft.com/en-us/library/aa561883.aspx for that.

In regards to your response schema it is a simple schema with a root node and a single element within the message of type string. When you expose the orchestration as a web service, this message definition will be available to the client through the WSDL you share.

Regards.

• Proposed as answer by Kjetil Tonstad Monday, July 27, 2015 5:57 PM

This is a simple pattern. What you need to do is to expose your BizTalk Application as a web service. Refer https://msdn.microsoft.com/en-us/library/aa561883.aspx for that.

In regards to your response schema it is a simple schema with a root node and a single element within the message of type string. When you expose the orchestration as a web service, this message definition will be available to the client through the WSDL you share.

Regards.

• Proposed as answer by Kjetil Tonstad Monday, July 27, 2015 5:57 PM

Read Richard Seroter's article on how to consume REST services at https://seroter.wordpress.com/2012/11/19/exploring-rest-capabilities-of-biztalk-server-2013-part-2-consuming-rest-endpoints/ and if you want to expose it as a REST endpoint then the Part 1 of the article will help you expose the orchestration as a REST endpoint.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 5 hours 18 minutes ago

Read Richard Seroter's article on how to consume REST services at https://seroter.wordpress.com/2012/11/19/exploring-rest-capabilities-of-biztalk-server-2013-part-2-consuming-rest-endpoints/ and if you want to expose it as a REST endpoint then the Part 1 of the article will help you expose the orchestration as a REST endpoint.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 03, 2015 1:49 AM

Read Richard Seroter's article on how to consume REST services at https://seroter.wordpress.com/2012/11/19/exploring-rest-capabilities-of-biztalk-server-2013-part-2-consuming-rest-endpoints/ and if you want to expose it as a REST endpoint then the Part 1 of the article will help you expose the orchestration as a REST endpoint.

Regards.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 03, 2015 1:49 AM

Before worrying about REST or looking at any code samples, you should do all of the BizTalk Tutorials.  They will answer most of you initial questions.

https://msdn.microsoft.com/en-us/library/aa560270.aspx?f=255&MSPPError=-2147217396