Forum Replies Created
-
AuthorPosts
-
Thanksfor the reply.
I investigated more… first, of course i initialize my correlation set, no problem… my properties are in the context and promoted.
So, i found the problem, before sending my message, i log all the properties needed to be promoted. 3 properties :
- CustomProperty1
- CustomProperty2
- BTS.MessageType
All this properties have a value.
But when i send my message I promote (initializing the correlation set) the MessageType (i treat only xml document) and the property is empty even if i logged it in the previous Shape (and i saw the good value).
When i use Orchestration Debugger and save the context of each message processed by my orchestration, the only difference is messageType is missing when the message falls in routing failure.
I can’t explain it… sequencing messages using Biztalk is not easy!
So i’m going on to search a solution…
October 24, 2008 at 7:13 AM in reply to: How to avoid deadlock while executing SQL Procedures #21044The best fix would be to modify the stored procedures so they can be run concurrently without deadlocking. You can configure BizTalk to send the SQL messages one at a time, but the problem is that you could end up with a huge backlog of messages over time. If the SP takes 12 minutes to run, and you receive messages every 5-8 minutes, something has to give. Is there any window where you don’t receive the messages so that BizTalk will be able to finish processing the backlog?
To make BizTalk send the messages one at a time, here are some options:
1. Mark the SQL send port for ordered delivery. This should make the messages go through the port one at a time, forcing one message to complete before another one can begin. I can’t remember whether this is done in the orchestration in VS, or on the physical send port through the BizTalk admin console. Just check the settings both places.
2. Use a sequential convoy pattern. You would need to modify your orchestration to receive messages in a loop. This would mean that you would only have one active instance of the orchestration and the orchestration would control the timing of the messages sent to SQL and you could avoid deadlocks.
Are all of the properties promoted? The properties need to be promoted to satisfy a subscription. Setting the properties in an orchestration does not guarantee that they are promoted. To promote the properties, you need to initialize a correlation set containing the properties on your send to the message box.
October 24, 2008 at 6:16 AM in reply to: SQl server db dead locks when Biztalk writes to Private queues #21042Can you give more details? Is your WCF service using the NetMSMQ binding? Where are you seeing that error? Does the message suspend in BizTalk, or does BizTalk think it was successful?
By the way, the updated JDEOW adapter DLLs have version 1.0.5012.0 but the port seems to be looking for 1.0.1069.0.
Thanks!
You could use a free account at box.net to host the images.
XmlStringStreamProivider how can I setup that.
I get to the Task properties -> Find Task -> Browse
after that I’m stuck, the Select button is grayed out and the text area is disabled
Any help?
I have the exact same problem, does anyone have an idea how to solve it?
/ceceThe example from Gotdotnet disappeared when Gotdotnet was shutdown.
Basically the example used the Ibex PDF Creator http://www.xmlpdf.com/ which is capable of converting an XSL-FO stream into a PDF stream. You still had to write a transform to create the XSL-FO stream, which was not a trivial task.
While the pipeline component was free, the IBEX PDF generator was licensed (by developer not a server or runtime license)
If you are interested email me and I will see if I dig up the original source.
Separate orchestration instances is a more scalable approach since the instances can be distributed across multiple servers. I would probably go that route.
Also, in your class, I would probably use a caching pattern with periodic refresh rather than a pure static variable.
I am not able to see it under the provided link could you please guide me to the correct location
Thanks
Thank you Rusel, I didn’t realize a new instance of the orchestration would be created for each message. I should be able to adjust my class to handle that pretty easily.
In a best practices sense, would it be better to break the message in the pipeline (which i’m doing now) or loop through the messages in the orchestration and use the orchestration variables?
Thank you,
Are you using a loop in your orchestration to iterate over the messages, or are you splitting the messages in the pipeline and processing each message with a new instance of the orchesration? If you are using separate orchestration instances, then you are getting new instances of the variables, so the token will be null. In that case you might want to look at using a helper class with a static variable to hold the token.
You need to use delivery notification.
Put your first send shape in a scope with Synchronised = true
Set Delivery notification = Transmitted on the port
October 20, 2008 at 12:42 PM in reply to: Major Flaw in R2 EDI capability – AN data type validation #21020Does someone know how to get to the missing 4060 EDI schemas?
Thanks!
-
AuthorPosts