Forum Replies Created
-
AuthorPosts
-
Hi Greg,
Thanks for helming me out.
FYI……Greg actually made a schema for me.
Regs,
Bhupal.
Hi Greg, thanks for the reply …
I have mentioned my doubts/queries below inline:
If you use an MSMQ independent client on the same machine as your application, then you will get the guaranteed delivery i.e. your application uses fire and forget and this will work even if Biztalk is down.
Is this what you meant that my remote App which is a .Net based application is on Server A, should the MSMQ be insalled on the same computer that is Server A or it can be installed independently on a diff Server that is Server B and if we deloy the MSMQ on the different Server how would the remote App on Server A would send messages to the MSMQ which is on Server B and also If have my bizTalk application is on Server C which would consume the messages from MSMQ which is installed on Server B, how will this enviornment work, please do share your thoughts …
What if your web service machine is down? You will need to implement some error recovery/retry capability in your application to handle this. In this case it would make more sense to just host the web service in BizTalk.
So, over here probablu you meant is you create an Orchestration to subscribe the message and expose this orchestration as a web service which can probably easily have retry capability and this webservice can be called by passing the XML message itself as a parameter ??? or how will it work
Please do let me know the above 2 queries
Thanks.
The adapter created proxy dlls for each RFC and cached in the bin folder of the <Adapter Install Directory> .
These proxies might have been created using the non-unicode server.
Deleting these proxise from bin folder might help.
If you use an MSMQ independent client on the same machine as your application, then you will get the guaranteed delivery i.e. your application uses fire and forget and this will work even if Biztalk is down.
However, if your application is Linux based and must call a web service on a Windows machine before it hits the queue then you will lose the guaranteed delivery. What if your web service machine is down? You will need to implement some error recovery/retry capability in your application to handle this. In this case it would make more sense to just host the web service in BizTalk.Likewise with message order. If you use a local queue then the message will be delivered in the order they were written to the queue. With a Web Service in front of the queue you cannot guarantee the messages are written to the queue in the same order they were sent, unless you implement your own ordering mechanism across the web service interface.
If your remote application is running on a Windows server with access to MSMQ and you need ordered and/or guaranteed delivery then definitely use MSMQ. Otherwise consider WMQ.
In BizTalk Server 2009
Thanks, i will try this solutions.
Hi Greg,
Please do reply. Thanks.
Hi Jason,
I am not sure if this error has something to do with the way the adapter was set up or installed, but I found this link to a set up guide of the Oracle LOB adapter 3.0 online:
http://mymsgbox.files.wordpress.com/2009/02/setuporaclewcfadapterv2.pdf
I hope this helps, if not, it was worth a try (from my perspective). 🙂
Daniel.
Hi Neal,
WCF does allow overloading of methods, and you will have to modify the Operation Contract attribute of these methods on the WCF side in order to properly consume the service in BizTalk, as described in the following two links:
http://jeffbarnes.net/blog/post/2006/09/20/Overloading-Methods-in-WCF.aspx
http://igloocoder.com/archive/2008/05/28/overloaded-methods-as-wcf-operationcontracts.aspx
I hope this information helps…
Daniel.
HI,
One suggestion is to look at your “SOAP action header” setting in your ports configuration. If you used the default bindings which were created when generating your schema, they are usually created wrapped within an operation.
Unless the send port within your orchestration’s operation matches the same name as the enclosing operation tag in the “SOAP action header” sending messages using the default setting will fail.
So to ensure that your send port works just supply a URL for the “SOAP action header” setting.
I hope this helps.
October 27, 2009 at 4:52 PM in reply to: Get data from xmldocument for BAM with repeating item #23553Johan —
This is definitely possible. What was the answer you received? Is this message flowing through BizTalk, the WCF Interceptor, or the WF Interceptor? Do you have a copy of your tracking profile?
Jeff Sanders
http://stackoverflow.com/questions/1631721/net-wcf-calling-asmx-with-ws-security
Well, I finally got someone to confirm that WCF can talk to .asmx with WS-Security – so I guess that’s the way to go, i.e. use the WCF adapters in BizTalk. I just didn’t know for sure it was possible.
Neal
Hi Greg,
Just now sent to you file.
Thanks for help.
Bhupal.
Thanks for your reply.
My requirement is the remote application sends some 15000 to 20000 messaages to be processed and as you said if this remote application happens to be done using microsoft technology then the remote application can directly add messages to MSMQ and then using the MSMQ adapter of BizTalk the messages can be picked up for further processing.
As you said MSMQ is used for In-Order delivery but at the same time it does not require the other application to be online that is if the messages coming are too much as mentioned above then they can very well sit in the qeue and wait for it to be picked by the MSMQ adapter, so I guess my driver along with the ordered delivery messages it is also the number of messages coming and processing the same.
So, I was thinking of having MSMQ, so that the remote app can send the message to the MSMQ and the Biztalk would pickup the messages using the MSMQ adapter for further processing.
Also, about using Web Services to get rid of the queing software I guess when there are loads of messages comng in then store and forward capibility of the queuing software would be very crucial instead of having a Web Service… what is your thoughts ?
Using a web service to send a message to MSMQ is technically possible, but removes whatever benefit using MSMQ delivers. You use queuing software for guaranteed ordered delivery. As soon as you put a web service in front of the queue you lose these benefits. If guaranteed ordered delivery is a requirement then the remote application must talk directly to the queue. You might as well use a web service adapter (SOAP, WCF) on Biztalk and eliminate the queuing software.
MSMQ is the answer if all your remote applications are Windows based and can talk to MSMQ. Otherwise WMQ is the answer. There are gateway products that will connect WMQ and MSMQ but then you have the cost of WMQ plus the complexity of developing and maintaining two queuing infrastructures.
What is your driver for using queuing software?
-
AuthorPosts