Forum Replies Created
-
Posts
-
From the Orchestration point of view, you would send a request and receive a response back.
As far as the exact problem, I’m not really sure. That sample is 2 ½ years old. I quickly review it and it looked like it should work. I think what should happen is to send a message and return an errors / status from SQL.
Maybe a better place to look is the SQL Adapter White Paper or some of the sample that might be around for BizTalk 2006.
And the only way I can connect to the sql ports is the send_1 to the SQL2WSendPort(response) and the receive_2 to SQL2WSendPort(request), which is the opposite way around?!? :S
The receive pipeline debatching process is one large transaction. This is why you see nothing happening for the first 10 minutes. If something was to fail (not so much so in BizTalk 06 and you can sometimes bypass this) the whole process would roll back – thus getting no messages out.
There are some ways around this… Matt has some good stuff on this blog. One is: http://objectsharp.com/blogs/matt/archive/2005/08/31/3209.aspx
I don’t know much about the size of the databases.
Hope this helps.
Not really a tool for that.
You can usually tell by the shapes you are using inside the Orchestration. The help guide lists them all, like Send Shape, Transactional Scopes, etc.
I think you’d need to build a windows service to response to the WMI event of the receive location shutting down.
I think the TopXml Adapter supports Exchange.
Take a look at:
http://www.topxml.com/biztalkutilities/ and
http://www.topxml.com/biztalkutilities/tutorial/BizTalk_and_Exchange.asp
Hope this helps.
A lot of the document doesn’t apply to what you want, but the AD and Group setup is very important.
To sum it up here is what you need to do:
Need to be on a Domain
Need to manually create required AD Accounts and Groups
Need to make sure remote access is enabled
Need to make sure the user you are using to install everything has the correct permissions on SQL and BizTalk box
Need to make sure you use the domain groups for the installation like DOMAIN\GROUP
These are the key things not to miss out on. The doc covers this, I think. You just have to sort out the items that do not work for you. I think some of this is also coved in the single computer install doc.
Hope this helps.
Sure, it all depends on what security they use.
BizTalk supports certificates so messages can be encrypted and decrypted. Also, transmission can be over HTTPS.
I think there is something about this in the Help Guide.
I think it’s something about the transactions the adapter uses. It can’t have inner transactions. I could be way off… I think it is cover dint he SQL Adapter – Receive Location section of the docs.
I would guess, you’d just need to change the line objInst.Enable to objInst.Disable (or whatever the Method is). You can probably find the method name in the help guide.
I have very little EDI Experience….
But, it sounds like you are missing something inside the map that maps to a required segment? Are you using a Validation component? If so, that could cause this problem. Or the validation might be done automatically by the EDI system.
Sorry, this probably will not help much.
There was a sample on this for BizTalk 2004 and an older version of InfoPath.
The key back then was to set the processing instructions on the XML document. I think I blog on this a few years ago (http://www.biztalkgurus.com/blogs/biztalk/archive/2004/10/13/How-To-Assign-an-InfoPath-Form-to-a-Message-in-BizTalk.aspx).
I’d guess for InfoPath 2007 this would still be the same approach.
I haven’t seen any sample with BizTalk 06 / Infopath 07 yet.
To test the HTTP Receives, in the past I’ve just built a simple WinApp to do a post.
As for as your problem, it sounds like you might have your party defined incorrectly? Is it possible you have the Name, Qualifier, and Values mixed up? Just a thought.
Sure it's possible. Just bind the physical port to all necessary orchestrations. Projects have nothing to do with it because messaging ports are purely a configuration-time concern. Note, however, that if the ports and orchestrations are in different BizTalk Applications, you'll need to add a reference from one application to the other in the biztalk management console.
It sounds like you have two schemas deployed, one with a namespace and one without.
A message arriving with a namepsace gets a message type of http://www.iba.ch/cxml#cXML. A message arriving without a namespace gets a message type of #cXML.
The orchestration is subscribing to a message type of http://www.iba.ch/cxml#cXML and will not process any other message type.
If you wish to use messages without the namespace you will need to change the message type definition in the orchestration. The message that is received by the activation receive shape needs to use the schema without a namespace.
