Forum Replies Created
-
AuthorPosts
-
Yes[:D]
BizTalk can certainly be used as an Enterprise Service Bus, the Microsoft Patterns and Practices ESB Guidance is based on BizTalk Server and .NET components (see http://www.codeplex.com/esb and http://msdn.microsoft.com/en-us/library/cc487894.aspx)
There are somegood discussions on BizTalk as an ESB over on the InfoSys blog (http://infosysblogs.com/microsoft/2006/09/biztalk_as_an_esb_2.html) and the Developer Network Journal (http://www.dnjonline.com/article.aspx?ID=dec05_biztalk).
You might also want to read the Microsoft ESB Guidance over on the Microsoft BizTalk pages (http://www.microsoft.com/biztalk/solutions/soa/esb.mspx).
Rgds, Nick.
Baba,
Try a Google search for ‘BizTalk Exception Handling’, also, a good starting point would be: http://www.codeproject.com/KB/biztalk/ExceptionDemo.aspx
HTH, Nick.
ps. You are posting from Redmond – do you work for Microsoft?
Baba,
It sounds like you are simply trying to call a WCF Service that resides in another subnet, and you call (from BizTalk) needs to traverse the firewall, similar to a LAN -> DMZ call.
If this is the case, you will need to speak with your network guys and ask them to enable your BizTalk server to call the WCF Service over port 80 (or whatever port you use) through the firewall. This shouldn’t be a massive problem as LAN->DMZ isn’t as big a security headache as DMZ->LAN. Furthermore, you will be initiating the call from known server/servers to further lock down the security.
HTH, Nick.
Some kind of CIO exception to open a port into the Corpnet
for a new application.Thanks for the quick reply.
Baba,
Do you have an example of the exception/s?
Nick.
Ruselw said: ‘This method is very quick and effective, but it makes you feel kind of dirty 🙂‘
Its not just me then!
😉
Yossi has a blog on the subject which goes into detail: http://www.sabratech.co.uk/blogs/yossidahan/2008/03/creating-message-from-scratch.html
Kape,
Changing the namespace of the project changes the Type Name of the various artifacts in your project (i.e. schemas, maps etc.), however you’re right about orchestrations – the Type Name here is not changed and does need to be changed manually.
However, there is no need to go into the .cs files generated from the orchestration – these are automatically generated by the X:ANG/s compiler every time you build the orchestration. Instead, open up the orchestration and go into the orchestration properties window (the part where you create new messages and variables etc.) and change the Type Name (and Namespace if necessary) there.
Bear in mind that if you already have an orchestration that is referencing maps and/or schemas (through ports for example) and you change the Type Name of those artifacts, your orchestration will complain and fail to compile. You will need to update these references to point to the new {Type] names of your artifacts.
HTH, Nick.
Is this statement part of the message assignment shape?
msgOut.MsgPart1 = msgIn
September 4, 2008 at 12:49 PM in reply to: Feedback on 3rd party PGP encryption/decryption tool #20576Hi Nick,
Thanks for your suggestions. After doing some further digging on the Internet, I came across this custom PGP pipeline component through this link:
http://bajwork.blogspot.com/2007/08/pgp-pipeline-component.html
It’s a wrapper C# class built on .NET framework 2.0 and using the Bouncy Castle framework. I think you and other folks will be interested in having a look at it. I am currently testing this module out in BizTalk 2006 R2 and its application looks promising for the processes that we are targeting it for in our business.
Best,
Daniel.
Also, here is a good tool for testing XPath: http://www.bizbert.com/bizbert/CommentView,guid,b3765922-23df-4db8-8b16-2c340873b4c9.aspx#commentstart. It will make your life way easier to get your XPath working in the tool before trying it out in a BizTalk app.
September 4, 2008 at 1:46 AM in reply to: Reason: Could not find file ‘C:\WINDOWS\system32\Shipment.dtd’ #20570Dhaval,
Repeat with me: DTD’s in BizTalk are bad, waaaaay bad.
I would remove any evidence of DTD’s from messages that are traversing through BizTalk as Xml; if you need to include this tag for delivery to an end system, I would suggest using a simple encoding pipeline component to do the work for you, just before BizTalk passes the message to the FTP Adapter.
Funnily enough, I encountered exactly the same problem on BizTalk 2004 some years ago and wrote a component to do this – see Add DOCTYPE Declaration Encoding Pipeline Component (version 1.0) on the downloads page of my blog.
Bear in mind that this component was written for the .Net 1.1 runtime, so will need to be recompiled for BizTalk 2006.
Rgds, Nick.
What happens if you take the custom functoid out of the map and execute (test) the map – do you still receive the same error?
Can you elaborate on what you are trying to do with the functoid and we may be able to suggest better ways to accomplish the same thing.
Rgds, Nick.
Wonder (?!?),
It looks as though your XPath is incorrect; I’ve just knocked up a quick schema that looks like the one above and I came out with the following XPath:
count(/*[local-name()=’tasks’ and namespace-uri()=’http://iTask/task.xsd’%5D/*%5Blocal-name()=’task’ and namespace-uri()=”])
Notice that the ‘task’ element doesn’t have a namespace-uri (I’m presuming here that your schema has the Element FormDefault setting set to ‘Default’, which is unqualified) – I think this is where you are going wrong.
HTH, Nick.
September 3, 2008 at 12:22 PM in reply to: Exception while sending message thru WCF-BasicHTTP adapter #20566Ruselw,
Thanks for your reply.
I didn’t enable tracing. I checked it with svcconfigeditor tool and tracing in BTSNTSvc.exe.config file is turned off. Can there be any other reason due to which this exception can occur?
Thank you
-
AuthorPosts