Forum Replies Created
-
AuthorPosts
-
You can find System.SystemException under the mscorlib reference when choosing the .NET Exception option in the Exception Object Type property for the Catch Exception block.
ok thanks
CommunicationException and endpointnotfoundexception doesn’t work and the system.systemexception isn’t in the System reference list.
Do you have an other idea?Try using CommunicationException instead, as EndpointNotFoundException inherits from that class. If that doesn’t work, you can always use System.SystemException to handle the error.
I referenced the System.ServiceModel but the problem is that in the exception handler scope the endpointnotfault can’t be catch. I think the type is wrong?
November 11, 2009 at 8:15 AM in reply to: Why Microsoft can not support SQL adapter for 64 bit BizTalk instance #23732Thanks Nandika, this is good information to know…
Hi,
You would need to reference the System.ServiceModel assembly in your orchestration project (which is a .NET Framework 3.0 assembly), then use a Scope shape with an exception handler for that type of exception.
Daniel.
November 10, 2009 at 8:29 PM in reply to: Why Microsoft can not support SQL adapter for 64 bit BizTalk instance #23727more info
BizTalk Server 2009
The SQL Adapter is fully supported in BizTalk Server 2009 but is planned for removal in future versions. Consider using the Microsoft BizTalk Adapter for SQL Server provided in the Microsoft BizTalk Adapter Pack 2.0.
http://msdn.microsoft.com/en-us/library/aa559720(BTS.10).aspx
it seems that users have to move to WCF SQL adapter
November 10, 2009 at 7:31 PM in reply to: Why Microsoft can not support SQL adapter for 64 bit BizTalk instance #23726Thanks Daniel.
I would like to share the information I got from LinkedIn professional groups.
It seems that SQL Adapter uses SQLXML internally and that had issues with native 64bit.
But I have seen the following @ http://msdn.microsoft.com/en-us/library/ms171744.aspx .
“To allow 32-bit SQLXML applications to run under Windows on Windows (WOW64) on 64-bit Windows operating systems, run the 64-bit SQLXML 4.0 SP1 package, named sqlxml4.msi”
It seems SQL Adapter can support 64 bit with this version of SQLXML .As I know even SQL adapter with BizTalk 2009 (not WCF) or BizTalk 2006 r2, does not support 64 bit (only with 32 host instance).
AND I would like to suggest to Microsoft , if they support the standard SQL adapter on 64 bit ( I mean run on 64 bit host instance not 32 bit host instance), It will help to millions of customers who used SQL adapter on 64 bit and can get the real advantage of 64 bit.
Using WCF SQL adapter is not the option people who used standard SQLNovember 10, 2009 at 3:33 PM in reply to: Adding Namespace and xsi:type to the XML element field #23725Hi,
Use a Scripting Functoid of type Inline XSLT in your map to accomplish this.
Daniel.
Hi Diego,
Read the following blog by Richard Seroter on suspended messages in BizTalk and the use of the Suspend shape in an orchestration.
http://seroter.wordpress.com/2007/01/02/orchestration-handling-of-suspended-messages/
This should give you clues on how to design your solution.
Daniel.
Hi Krishna,
See this previous BizTalkGurus thread for more information:
http://www.biztalkgurus.com/forums/t/13544.aspx
Daniel.
November 10, 2009 at 9:42 AM in reply to: Why Microsoft can not support SQL adapter for 64 bit BizTalk instance #23719Hi Nandika,
It is a fact that MS does not support SQL Adapter in 64-bit host instances, as stated in this MSDN article:
http://msdn.microsoft.com/en-us/library/aa560166(BTS.10).aspx
Check this Hotfix for running 32-bit program in a 64-bit Windows 2003 server:
http://support.microsoft.com/kb/910907
Also, here are a couple of related blogs talking about custom bindings and configuration in 64-bit setups:
http://kentweare.blogspot.com/2009/08/biztalk-2009-64bit-missing-sapbinding.html
I hope this information helps.
Daniel.
Hi,
See the responses below (in bold)…
[quote user="Anonymous"]
Yes the remote App is build using .NET from which the BTS is suppose to send/receive messages from.
1) I guess If the remote App is using VS 2005 (i.e. 2.0 Framework) then probably I need to use Soap Adapter for both consuming web services or publishing orch as web services.
In this case, yes.
2) if the remote App is using VS 2008 (i.e. 3.0/3.5 Framework) then probably I need to use WCF adapter-basicHTTP for both consuming wcf services and publishing orch as WCF services
Yes again. Using WCF adapter is your best bet.
3) OR if I am using VS 2005 (i.e. Framework 2.0) and I am using BTS 2006 R2 then BTS orchestration can be published as a WCF service to receive message from a Web Service build using VS 2005 (i.e. Framework 2.0) … only thing as you mentioned it won’t support the WS-* standards ….
As Greg mentioned, there are a lot more options with regards to implementing WS-* standards when publishing your BTS orchestration as a WCF service, moreover, it’s interoperable with other non-Microsoft technology stacks and platforms, which makes more flexible and appealing if you are dealing with a heterogeneous computing environment.
Please do clarify the same…
[/quote]
November 10, 2009 at 6:41 AM in reply to: Orchestration exposed as a WCF can be exposed on the BTS box itself #23716You can host the services in another box but then you need to install ISA (Internet Security and Acceleration ) server which would make it ultimately point it to BT box.
Yes the remote App is build using .NET from which the BTS is suppose to send/receive messages from.
1) I guess If the remote App is using VS 2005 (i.e. 2.0 Framework) then probably I need to use Soap Adapter for both consuming web services or publishing orch as web services.
2) if the remote App is using VS 2008 (i.e. 3.0/3.5 Framework) then probably I need to use WCF adapter-basicHTTP for both consuming wcf services and publishing orch as WCF services
3) OR if I am using VS 2005 (i.e. Framework 2.0) and I am using BTS 2006 R2 then BTS orchestration can be published as a WCF service to receive message from a Web Service build using VS 2005 (i.e. Framework 2.0) … only thing as you mentioned it won’t support the WS-* standards ….
Please do clarify the same…
-
AuthorPosts