Moving from SOAP Adapter to WCF-basichttp adapter

we are migrating the BizTalk server 2009 application into BTS 2013.In The BTS 2009 application ,some of ports are configured with SOAP and SQL Adapters.
So I recommended to customer that move from SOAP Adapter to WCF-BasicHttp and SQL to WCF-SQL.
But customer asked me is that the best practice MS recommended for moving from SOAP to WCF-BasicHttp?
Customer is asking let me explain few points why i have to move from SOAP to WCF-Http?
Could you please help me how to convince him?
Regards BizTalkWorship

The SOAP adapter is deprecated in BizTalk Server 2010. You should use the WCF-BasicHttp to communicate with Web services and clients that conform to the WS-I Basic Profile 1.1. To communicate with Web services and clients that conform to
WS-*, use the WCF-WSHttp adapter.
Key benefits of WCF Framework
Because WCF can communicate using Web services, interoperability with other platforms that also support SOAP, such as the leading J2EE-based application servers, is straightforward.
. You can also configure and extend WCF to communicate with Web services using messages not based on SOAP, for example, simple XML formats like RSS.
. Performance is of paramount concern for most businesses. WCF is developed with the goal of being one of the fastest distributed application platform developed by Microsoft.
. To allow optimal performance when both parties in a communication are built on WCF, the wire encoding used in this case is an optimized binary version of an XML Information Set. Messages still conform to the data structure of a SOAP message, but their
encoding uses a binary representation of that data structure rather than the standard angle-brackets-and-text format of the XML 1.0 text encoding. Using this option makes sense for communicating with the call center client application, because it is also built
on WCF, and performance is an important concern.
. Managing object lifetimes, defining distributed transactions, and other aspects of Enterprise Services are now provided by WCF. They are available to any WCF-based application, which means that the rental car reservation application can use them with any
of the other applications it communicates with.
. Because it supports a large set of the WS-* specifications, WCF helps provide reliability, security, and transactions when communicating with any platform that also supports these specifications.
. The WCF option for queued messaging, built on Message Queuing, allows applications to use persistent queuing without using another set of application programming interfaces.
Thanks
Abhishek

Similar Messages

Error while posting to Webservice using WCF-BasicHttp adapter

Hi,
I am getting the below exception when i am posting a request to a .asmx webservice using the Wcf-BasicHttp adapter.
I am able to call the same service with the SOAP adapter successfully. Could you please let me know any resolutions for the same.
The adapter failed to transmit message going to send port "MySendPort" with URL "http://myservice.com/Web.Services/service1.asmx". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.ProtocolException:
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes
of the response were: '
<html>
    <head><link rel="alternate" type="text/xml" href="/Web.Services/Service1.asmx?disco" />
    <style type="text/css">
       BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; }
       #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; }
       A:link { color: #336699; font-weight: bold; text-decoration: underline; }
       A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; }
       A:active { color: #336699; font-weight: bold; text-decoration: underline; }
       A:hover { color: cc3300; font-weight: bold; text-decoration: underline; }
       P { color: #000000; margin-top: 0px; margin-bottom: 12px; font-family: Verdana; }
       pre { background-color: #e5e5cc; padding: 5px; font-family: Courier New; font-size: x-small; margin-top: -5px; border: 1px #f0f0e0 solid; }
       td { color: #000000; font-family: Verdana; font-size: .7em; }
       h2 { font-size: 1.5em; font-weight: bold; margin-top: 25px; margin-bottom: 10px; border-to'.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
Regards,
Ujjwal
-Ujjwal

Where does the HTML indicate that the Service is not running??
The error message " The content type text/html; charset=utf-8 of the response message does not match
the content type of the binding (text/xml; charset=utf-8)" points to a bug in the WCF-BasicHttp described here:
http://social.msdn.microsoft.com/Forums/en-US/11796bf5-ba6a-4878-977e-5c854642f67c/the-content-type-textxml-charsetiso88591-of-the-response-message-does-not-match-the-content?forum=biztalkgeneral
Although not 100% the same, the conclusion here was to still use the old Adapter :-(
Morten la Cour

The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location

Could anyone please help in resolving the following
error:
Server Error in '/BizTalkXXXMyAppWcfService' Application.
The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc".
Please verify that the receive location exists.
It does exist: When I go to All Artifacts >> Receive Locations I can see: WcfService_BizTalkXXXMyAppWcfService/XXXMyApp
Also it is Enabled, green, up and running.
…and that the isolated adapter runs under an account that has access to the BizTalk databases. – Checked, the BizTalkUser has all the permissions to access BizTalk databases.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc". Please verify that the receive
location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[COMException (0xc0c01666): The Messaging Engine failed to register the adapter for "WCF-BasicHttp" for the receive location "/BizTalkXXXMyAppWcfService/XXXMyApp.svc". Please verify that the receive location exists, and that the isolated
adapter runs under an account that has access to the BizTalk databases. ]
   Microsoft.BizTalk.TransportProxy.Interop.IBTTransportProxy.RegisterIsolatedReceiver(String url, IBTTransportConfig callback) +0
   Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfIsolatedReceiver`2.RegisterIsolatedReceiver(Uri uri) +318
[AdapterException: Failed to register isolated receiver for address "/BizTalkXXXMyAppWcfService/XXXMyApp.svc"; receive location does not exist or is disabled.]
   Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfIsolatedReceiver`2.RegisterIsolatedReceiver(Uri uri) +875
   Microsoft.BizTalk.Adapter.Wcf.Runtime.WebServiceHostFactory`3.CreateServiceHost(String constructorString, Uri[] baseAddresses) +363
   System.ServiceModel.HostingManager.CreateService(String normalizedVirtualPath) +1423
   System.ServiceModel.HostingManager.ActivateService(String normalizedVirtualPath) +50
   System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) +1132
[ServiceActivationException: The service '/BizTalkXXXMyAppWcfService/XXXMyApp.svc' cannot be activated due to an exception during compilation. The exception message is: Failed to register isolated receiver for address "/BizTalkXXXMyAppWcfService/XXXMyApp.svc";
receive location does not exist or is disabled..]
   System.Runtime.AsyncResult.End(IAsyncResult result) +890624
   System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +180062
   System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +107

Hi,
This seems to be a permission issue.
Makesure account used in the application pool is a member of the BizTalk Isolated Host Users group.
Also its working considering either make the ASPNET user account a member of your BizTalk Isolated Host Users group to make sure it has access to the biztalk databases (or change the asp.net services to run under a different account, which would need
to be done from the framework's core .config files)
Regards
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

The Messaging Engine failed to register the adapter for "WCF-BasicHttp"

Hi,
I have a strange problem with BizTalk 2013 on Windows 2012.
It is with exposing an orchestration or schema as a web service, I always get the error "The Messaging Engine failed to register the adapter for 'WCF-BasicHttp' "
This happens also am sure I did the followings:
-Enabled the receive location
-Have separate pool for each web service
-The pool user is part of the Isolated Group & IIS_Users group
-The user has access to BizTalk databases
I tried the procedure on different environment, and it works just fine, what is causing this on this environment really I don't know!!
Is there something I should do on the IIS?

I just resolved it, the issue was with the server name exceeding 15 characters; which resulted in mismatch in credentials, since Windows will only take the first 15 characters.
So, I shortened the server name to 15 characters, and everything now works fine.
Thanks again,

HTTP adapter vs WCF-based adapter

i have a requirement working with third party CRM system . Right now they are offering SOAP web service and saying HTTP adapter works, but I want to go for advanced technology like WCF based adapters. Which option is better? HTTP or WCF-based?? if it is
WCF , what is the right WCF adapter to use. NOte: they are offering only SOAP.

Hi,
Off-course the WCF based option is better. And for your requirement you have to use WCF-BasicHttp adapter which is meant for ASMX-based
Web services and clients that conform to the WS-I Basic Profile 1.1.
SOAP VS WCF-BasicHttp Adapter points from MSDN article:
WCF adapters documents per second rate is general be better than SOAP adapter.
SOAP adapter has the disadvantage of serializing and deserializing messages between .NET types and raw XML data which in some cases could result in unwanted data modification. WCF adapters take the approach of preserving the data stream.
WCF adapters publish what is essentially the same schema as will be used in the BizTalk runtime. In contrast, SOAP adapter returns metadata generated by reflecting on the .NET classes generated to represent the schemas. Since .NET does not preserve
all the nuances of XSD schemas, the exposed WSDL may not accurately reflect the schemas used by the BizTalk runtime.
It is easier to migrate from WCF-BasicHttp to WCF-WSHttp if needed.
Maheshkumar S Tiwari|User Page|Blog|BizTalk
Server : How Map Works on Port Level

UsnernameToken authentication failed using WCF-BasicHttp adapter

I have read the other topic that is identical to this, but there is no detail as to what was actually changed to allow Kerrey to override the default 256 character limit. So I figured I would start a new thread and see if someone can show me what my binding
file should include to override this setting.
thanks,
Chuck
Charles

So, the problem is that somewhere in the BizTalk/WCF bridge layer, a password is cut off at 256. The WCF-Custom Adapter has the same issue.
You have two options.
Biding File:
Export a binding file.
Trim all but the one Send Port where you need the long password.
Fine the Password element in the TransportTypeData blob. Yes, it's escaped Xml so edit carefully.
Enter you long password, save.
Import Binding file, then delete (so you don't have the clear test password anymore).
SSO: (This is the 'better' option)
Create an SSO Affiliate Application
Set the Service Credentials. SSO will accept the long password.
Set Use Single SignON and your Affiliate application in the Client Credentials dialog on the Security Tab.
Somewhere prior to the Adapter (Orchestration, Send Pipeline) set the BTS.SSOTicket Context Property
I've never tried the binding file option but SSO works great and is designed for such scenarios (storing passwords).

Sending an XML that contains CDATA to a SOAP service using wcf-webhttp adapter

I've run into a rather unique problem when trying to send an xml that contains the <![cdata[]]> tag to a soap service. Without the tag the xml sends through without issue. However, when I add the cdata tag within the xml, BizTalk immediately
fails without even attempting to send to the service. I receive the following error:
"The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not
been promoted. Please use the Biztalk Administration console to troubleshoot this failure. "
I have ensured that the send adapter is enlisted and started.
This is on a BizTalk 2013 installation.
Any and all help is appreciated!
Thanks

as per my understanding, if you use the
<![cdata[]]> tag in sending message, BizTalk is not able to send the message as it is not matching with your send message schema that is why error 'The
published message could not be routed because no subscribers were found.....'
Please compare the message format or configured schema in send shape and message which suspended when
used <![cdata[]]> tag used.
Regards
Suman

Messaging only: WCF-BasicHTTP adapter Request-Response correlation

Hi,
we have a solution where we make a soap web service call to a third party.
we do not want to use orchestrations.
we are in need to pass a value to the third party service and we would
like to have that value passed back to us in the response.
However, the third party is not guaranteeing this.
as an alternative, i tried promoting a property into the context
before the outbound call and check if this is still available in the context when the response come thru.. but no luck here.
IS there any other way to achieve this?
regards,
MS

Hi MS,
What is your question? When you use Request-Response (Receive) port and solicit-Response (send) port, the correlation would happen out-ob-box with the help of EpmRRCorrelationToken, CorrelationToken and RouteDirectToTP
properties.
Are your not using the solicit-Response (send) which would take care of the correlation to Request-Response (Receive) port. Ensure you're using the XML-Transit (on send) and XML-Receive (on receive) pipelines on these two way ports (in both Request-Response
(Receive) port and solicit-Response (send) port)
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

WCF wsHTTP adapter: How to control WS-A elements, attributes.

Hello,
we have a third party soap web service that we invoke using Biztalk BasicHTTP adapter.
This wasn't working.
That's when we were told the web service is a Soap1.2 endpoint.
So we have changed the adapter to wcf-wsHTTP adapter. This still doesn't work!!
we get an error like: Must Understand check failed for header
http://www.w3.org/2005/08/addressing : To
I traced the outgoing call from the adapter via Fiddler.
I see this:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
  <a:MessageID>urn:uuid:637ec5d5-f7c3-</a:MessageID>
  <ActivityId CorrelationId="b56a4554-c373-4479" xmlns="00000000-0000-0000-0000-000000000000</ActivityId">http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">00000000-0000-0000-0000-000000000000</ActivityId>
  <a:ReplyTo>
           <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
  </a:ReplyTo>
  <a:To s:mustUnderstand="1">https://xxx.xxx/xx</a:To>
if i change the mustUnderstand attribute to 0 in the To element, the web service returns
the right response. This was tested using Fiddler.
I understand the adapter is adding the headers like To,ReplyTo etc. but not sure
why. How do i disable them getting generated? or How can i set the mustUnderstand to 0?
Any suggestions please?
thanks
MS

Hi,
Refer the SOAP Header Action mustUnderstand Exception.
Add the addressing annotation to the Web Service class @Addressing(enabled=true, required=true)
Change namespaces in the <Envelope> tag from:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
to
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:a="http://www.w3.org/2005/08/addressing">
Both SOAP 1.1 and SOAP 1.2 specifications enable you to use mustUnderstand attributes with SOAP headers. Not handling these headers properly is a common concern during Web service
interactions.
Refer: Understand the Famous "Did not
understand MustUnderstand header(s)"Error
Rachit
Please mark as answer or vote as helpful if my reply does

How to send EDI from WCF adapter to WCF service

Hi,
1. I have created an orchestration which is published as WCF service.
2. I have created an orchestration which receives an XML from WCF client and process it.
3. I have created a WCF dynamic send port.
Problem: From this dynamic send port, I want to send EDI file to a WCF service that will receive this EDI file. How can I achieve this. Below are my concerns:
-> For creating this WCF service, I need to know the contract of Biztalk WCF adapter which sends EDI file.
Thanks ...

Hi,
How can we create WCF service to receive the EDI sent by the BTS. What contract should be used for receiving this EDI file in WCF service.
What changes have to be made in the orchestrations to send the EDI file to the WCF send Dynamic port. Below is the code i am using.
EDIOutboundPort(Microsoft.XLANGs.BaseTypes.Address)="URL Address";
EDIOutboundPort(Microsoft.XLANGs.BaseTypes.TransportType)="WCF-basicHttp";
Please correct me if i am wrong
Thanks
"How can we create WCF service to receive the EDI sent by the BTS. What contract should be used for receiving this EDI file in WCF service" - This is two different questions.
"How can we create WCF service to receive the EDI sent by the BTS" - Using BizTalk WCF Services Publishing Wizard, the wizard would ask for the "Create BizTalk receive locations in the following application " for creating
the receive location for the message published to the exposed WCF service. Through this receive port/location, the service would receive the message.
In this case, I am not sure why do you want to expose the Orchestration as WCF Service when you want to send message to this Orchestration/WCF service (which after converting from Orch) through another orchestration. You could either use call/start orchestration
to send message from one to another.
"What contract should be used for receiving this EDI file in WCF service" - may be this question is not correct. You have created a Orchestration which you exposed as WCF service. So while creating the Orch you know the type of message this Orchestration
is bound to, so use the same contract. Or as mentioned in my earlier reply, use "Consume WCF wizard" to consume the WCF service which would create the web message for you.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

How do you configure a WCF-SQL adapter to write data from a SQL2012 "always on" database?

Hi All,
I have a BizTalk environment. I have to write the data from BizTalk to the database which is configured using ALWAYS ON availability group.
I use WCF-SQL adapter to write the data. My question is this setup a supported?

The answer is NO.
Refer: Can
I use a BizTalk WCF-SQL send adapter with a SQL 2012 Always on Database?
A snippet quoted below.
In summary (in order of preference):
Disable AlwaysOn Availability Groups / Mirroring on SQL server if you need to connect to this SQL server which has this enabled
Disable transactions and implement logic to be able to handle duplicates .
Disable transactions and handle the duplicates or lost messages with custom logic (e.g. Send twice and compare and implement error handling). You need to write your own DTC handling this which
is probably very complicated.
Disable transactions and live with risk of duplicates or lost messages without handling duplicates.
Refer: SQL Server AlwaysOn feature does not support MSDTC transactions.
Rachit
Please mark as answer or vote as helpful if my reply does

How to save the Response message from SOAP adapter

Dear Friends,
I am sending the FIle details webserver.here sender is FILE adapter and receiver is SOAP adapter.
FIle to SOAP working successfully, but I need response from SOAP.
Sender QoS is BE, so the response is coming to XI, but in SXMB_MONI it is showing DO YOU WANT TO SAVE IT or DISPLAY IT.
my requirement is response message is directly updated in XI system.
For response Can I use BPM or which method I need to use.
Please suggest me how to do the resonse message(SOAP to FILE).
Regards,
Shalini Shah.

Sender QoS is BE,
File adapter does not support sync communication. Therefore the scenario won't work as it is.
What are you planning to do with the response? If you want to process is further, then:
1. One way without BPM would be use of adapter module.
File - RFC - File without a BPM - Possible from SP 19.
2. Or you may use BPM with Async Sync bridge
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards,
Prateek

Polling records from mulitiple table(61 Tables) using WCF-SQL adapter

Hi,
I would like get some suggestion from this forum. I've a scenario, in which I need to poll the records from multiple table(61) which are related and may have one to many relationship. what's the best way to poll the records from SQL table to BizTalk.
Thanks in advance..
Regards,
Karthick

Karthick,
Write a SQL stored procedure with joins from your 61 tables (!!!) . Use WCF-SQL adapter to invoke the procedures.
Following references shall help you:
Executing Stored Procedures in SQL Server by Using BizTalk Server
Performing Composite Operations on SQL Server by Using BizTalk Server
Bing-Results: biztalk wcf sql
adapter polling stored procedure
I don’t know your exact requirement. Consider using SQL-SSIS for ETL process depending on your requirements. Anyway if your requirement really needs BizTalk, above suggest
should solve your problem.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

Retrieving(Inbound) IDOC from SAP Error WCF-SAP Adapter

I am attempting to retrieve data from SAP using WCF-SAP Adapter. I used the wizard to retrieve the IDOCTYP(PEXR2002) and the appropriate docrel=740. Whenever I send the IDOC to BizTalk I receive the error below. Anyone have insight to what could be
the problem. BizTalk is not resolving the IDOC types properly.
Also: I am using the schema in a flat file disassembler in the receive pipeline.
Reason: Unexpected data found while looking for:
'E2EDKA1003'
'E2IDBL2000'
'E2IDB02002'
'E2EDL02'
'E2EDL03'
'E2IDLU5001'
'E2IDPU1'
'E2IDBW1'
The current definition being parsed is E2IDKU5001GRP. The stream offset where the error occured is 1483. The line number where the error occured is 11. The column where the error occured is 0.

Hi Jordan ,
This really happens when you receive untyped message from your SAP System . Its been well described in below link
Receiving Idocs - getting the raw idoc data
Better option here is to create a pipeline component which will be responsible for your message parsing or try something like below
During the configuration of your one-way Receive Location using WCF-Custom, navigate to the Messages tab. Under the section "Inbound BizTalk Messge Body", select the "Path" radio button, and:
(a) Enter the body path expression as:
/*[local-name()='ReceiveIdoc']/*[local-name()='idocData']
(b) Choose "String" for the Node Encoding.
Thanks
Abhishek

Moving from SOAP Adapter to WCF-basichttp adapter

Similar Messages

Maybe you are looking for