Forum Replies Created
-
AuthorPosts
-
A WCF Service is a web service, you just have a lot more options in regard to implementing WS-* standards. WCF based web services are interoperable with most other web service stacks including asmx, WSE3, even Java.
If you publish web services on Biztalk using the WCF adapter these can be consumed by almost any other web service stack, although if you implement a service requiring WS-Transactions and federated WS-Security then you client stack must also support these standards.
If you are consuming web services from Biztalk, then the WCF adapter will give you the best interoperability.
If you are goind to consume Biztalk web services or create web services for Biztalk to consume then you can use any web service stack. If you are working with .Net, then the best option would be to use WCF
Will there be any change in the implementation if I use WCF adapter, I mean instead of writing web services do we have to write WCF services and I guess also the binding I would use would be WCF-BasicHTTP ??
Yes, that is correct.
If you are using Biztalk 2006, you only have the option of using the Soap adapter. If you have Biztalk 2006 R2 or Biztalk 2009 then the WCF adapter is the best choice. The Soap adapter is deprecated in Biztalk 2009 – it willnot be available in the next major release.
So, basically If I am suppose to receive a soap message from webservices in BizTalk then the BizTalk Orch itself needs to be exposed as a Web Service for it to receive a soap message from a web service and when the Orch needs to send a soap message then it needs to consume a Web Service ….
I hope my understanding is right …
The concept of Enlisting is creating the necessary subscriptions in the MessageBox database so unenlisting is removing the subscription so that the orchestration no longer processes messages.
Once the message has processed and no more subscriptions , the message will be deleted from the messagebox.So you can’t process the message by Subscriber1.
But if you stopped Subscriber1 ( Without unenlisted), you can process the message after starting the Subscriber1 because the message will be suspended for Subscriber1.
Nandika
sometime a postfix delimiter (\r\n) solves this issues..bellow is such an issue i encountered sometime back,
grp1_record1\r\n
grp1_record2\r\n
grp1_record2\r\n\r\n
grp2_record1\r\n
grp2_record2\r\n
grp2_record2\r\n\r\nIn this case if you set the delimiter as postfix for the group, the last line break will be ignored. Also dummy elements were also helpful in some cases..
November 9, 2009 at 12:49 PM in reply to: how to access error informations from BizTalk Message #23707Check out this blog post, he is doing much what you are trying to do…
Hi,
In your orchestration define a port (in the flow of your orchestration) with the following properties (when running the wizard):
– Existing or New Port Type: New
– Communication Pattern: Request-Response
– Access restrictions: Public – no limit
– Port direction of Communication: I’ll be receiving a request and sending a response
– Port Binding: Specify later
Once you deploy your orchestration, use the BizTalk Web Services Publishing Wizard to expose the physical port as a Web port, and there you have it.
Daniel.
yes I am trying to receive a message from a WebService in BizTalk thru a Soap Adapter for further processing, I mean the direction of communication would be “Receiving a request and sending a Response” and also I am suppose to write the webservice 🙁
November 9, 2009 at 8:37 AM in reply to: Mapping a filed frm the Repeating record to a field of the Non-repeating record #23701Hi,
Use a combination of logical Equal functoid with Value Mapping (Flattening) functoid for each case, linking from your source node n101 to your target nodes an8 and shan.
Daniel.
Hi,
Messages in the BizTalk engine are in XML format. Are you trying to connect to a Web service from BizTalk? If it’s an ASMX web service, use SOAP adapter; otherwise, if it’s a WCF service, use the WCF adapter.
Daniel.
You can use inverse partner direct binding (recipient list pattern) for the behavior you are looking for.
Multiple Schemas with same Root Nod and Namespace is bound to fail.
So better use only one Schema and populate different Sections of the Schema as per the incoming xml.
Set min occurs =0 for the Records which wont appear in XML1.
Thank you Greg,
-
AuthorPosts