Forum Replies Created
-
AuthorPosts
-
Whatever service you use to get the data across, you are going to have to get your security guys to open a port. WCF, MSMQ, and SQL all use different ports by default, so they would probably need to open one for each. Usually the port they are most willing to open is port 80 going out (CorpNet -> DMZ). That means BizTalk would need to connect to the service in the DMZ or Extranet and pull the data in. Then you shouldn’t have any problems getting the data across domains. You do need to make sure that you use a proper security model for the services. Certifiates would be a good choice but NTLM will give you problems when you try to authenticate across domains.
September 5, 2008 at 7:24 AM in reply to: Exception while sending message thru WCF-BasicHTTP adapter #20608Yes, I tried that to know the same thing and I came to know that it’s giving the same error in new project as well. So, I thought it’s a issue with WCF itself. But till a week back I was able to work with the same orchestration and not now. The only change I made was changing the password of my account which was expired. Is there any possibility that it is an issue because of that?
September 5, 2008 at 7:20 AM in reply to: Exception while sending message thru WCF-BasicHTTP adapter #20607That error makes me suspect it is a problem with the WCF or BizTalk install. To test, I would stand up the absolute simplest WCF service possible, and write an orchestration to consume it. If you still get the error, then it is an install problem. If you don’t get the error, it is a bug in your code.
No, BizTalk is not an ESB. It is a great platform for building an ESB though. BizTalk does most of the core ESB functions such as transformation, routing, and messagin patterns, but you need hardcore developers to make these things happen. I feel like an ESB should be more configuration based so that it is accessible to less technical people. Microsoft did provide a guidance package that shows how you can build an ESB with BizTalk. It demonstrates some really nice ESB patterns, but it still takes a lot of developer effort to get it running. You can download it here: http://www.codeplex.com/esb.
Regards,
I think your best bet would be to use XPath to pull out the data. For example, you could use the xpath function in an expression shape to extract a value:
strData = xpath(soapMsg, “string(//*[local-name()=”Data”])”);
You can use the Dan Sharp XML Viewer to build and test your XPath statements: http://www.bizbert.com/bizbert/2007/11/25/DanSharp+XmlViewer.aspx. Just run the tool and open a file, then drill down in the XML tree to the data you wan, and it builds the XPath for you.
September 5, 2008 at 5:25 AM in reply to: Error :The Messaging Engine failed while executing the inbound map for the message coming from source while using custom functoid #20604Are you sure you are using the same input file while testing in Visual Studio vs BizTalk? Is the file maybe getting updated in a pipeline so it is different when it hits your map? It might help to debug the XSLT in VS:
- In Visual Studio, validate the map.
- Open the output XSLT file (don’t CTRL click, copy and past the location into File -> Open so it will open in the XML editor instead of browser).
- Now a new XML menu will appear on the top menu.
- Click XML -> Debug XSLT.
- You will receive a warning that there is no input file. Click OK and choose an input file.
Now you can step through the XSLT just like you were stepping through a C# file. When an exception occurs, you will be able to see the actual exception details, intead of a masked exception like you would get from Test Map or in a BizTalk app.
Dunno if this helps any, but if I were using with XPath, it would be like this:
//*[local-name()=”taskid”]
I have found that when namespaces are involved, I need to use the local-name() function because standard XPath like //taskid doesn’t work.
Well, that depends on what type of pull clients you are talking about. Can you explain a little more? It can actually work in either mode. All BizTalk adapters opeate in either pull or push mode, so it really just depends on which adapters you are using. For example, if BizTalk consumes data using the SQL receive adapter, it is operating in pull mode. However, if BizTalk consumes data using a WCF receive adapter, it is operating in push mode (WCF client pushing data in).
You can also find a good exception handling framework with the ESB Guidance: http://www.codeplex.com/esb. This framework has a very nice way of logging the BizTalk messages associated with the exceptions and capturing a lot of BizTalk specific data automatically (which application, which server, orchestration vs. messaging, etc.)
thank you. I tested Nicks solution with that tool. We will be using it from now on.
Thank you.
your solution works. I needed this so I can debatch the xmlmessage in the biztalk orchestration.
I am still new to biztalk.
Thank for the help
Sorry, I just had to use a valid account for the host.
Problem solved !
Thanks Greg, Thats,Exactly simililer framework I am looking for,
Thanks,
Baba
Also check out the first article in the latest Biztalk Hotrod by Jean Paul Tabja
http://cid-b6c859f7a5f75e63.skydrive.live.com/self.aspx/Public/Q2FY08_biztalk.pdf
I have just implement an exception handling process that uses a pattern similar to the Enterprise Library Logging Block.
I have a logger that generates different messages, via a System.Diagnostics.TraceSource. I then have a number of listeners:A trace listener for all messages – writes to an Xml trace file (using orchestration instanceId as the activityId) that can be opened using svctraceviewer.exe
A logging listener that accepts warning and error messages and logs to the event log
A WMI event listener that accepts error messages and fires a custom WMI event. The customer uses CA-Unicenter to monitor and route these events. You could use MOM, IBM Tivoli or similar to do the same. We also monitor Biztalk suspended message and service WMI events.
Thanks for reply nic, As you said call from LAN->DMZ Isnt an issue ,you are 100% correct But in my case call is from DMZ->LAN thats the problem. And in Extranet Service could be anything like WCF Or it could be any source like MSMQ,Sql etc,
Thanks,
Baba
-
AuthorPosts