Forum Replies Created
-
AuthorPosts
-
October 28, 2008 at 6:58 PM in reply to: SQl server db dead locks when Biztalk writes to Private queues #21071
What SQL table are the errors logged into? Is it the same one where the data is supposed to be logged, or is it a different one? In BizTalk, do you see any suspended or dehydrated messages or errors in the event log?
The message type property is is constructed as targetnamespace#root
Are you using the XmlReceive pipeline, it is the Xml Disassembler that promotes the BTS.MessageType property
You might like to check the the message context of the suspended message to and use the actual value of the BTS.MessageTypeOctober 28, 2008 at 10:43 AM in reply to: SQl server db dead locks when Biztalk writes to Private queues #21067yes We are using NETMSMQ binding. The errors are logged in the sql table . So it looks like Biztalk thinks it is successful but ideally it is not
Thanks
Are you sending this file or recieving the file? If you are recieving the file you create a recieve pipeline (select flat file disassembler and set document) and it will break the file into single files easier for mapping.
I recommend that you use Tomas Restrepo’s excellent Pipeline Testing Library which allows you to write unit tests for your pipelines.
Further information can be found on his website at http://www.winterdom.com/weblog/2006/04/24/TestingPipelineComponents.aspx and you can download the library from GitHub at http://github.com/tomasr/pipelinetesting/tree/master
I also did a write up on the library over at my blog: http://www.modhul.com/2008/03/11/testing-pipeline-components-the-pipeline-testing-library/
Rgds, Nick.
Yes, two orchestrations could do it. If you create two orchestrations and bind them to a single receive port, then when the receive port receives a message, each orchestration will receive a copy of it. Thus, you have received the same message twice. Is this making more sense or should I elaborate? If you want me to elaborate, could you give some more details about why you need to receive the message twice and what you want to do with it?
Hello Rusel,
Thanks for the reply, but I didn’t understood it, could you please be more precise on this?
Do i need two orchestrations for this ?
Thanks in advance
Receiving a message twice is no problem. BizTalk is designed with such requirements in mind. BizTalk uses a publish/subscribe model. You only need a single receive location to receive the message. When the message is received the location publishes the message into the message box. To receive the message twice you just need two subscribers (send ports or orchestrations). To configure an orchestration to subscribe to the receive location you could either bind it to the receive port or use a filter on the orchestration receive shape. To configure a send port to subscribe you have to use a filter expression. Example: BTS.ReceivePortName = “MyReceivePortName”.
hi Russel,
The problem is solved. Actually, everytime I validate the xml file, i was always missing one attribute. I don’t know how but my eyes missed it completely. It was now that it checked the file and schema, element to element and found a Case Level mistake. In the file it was ***Id and in the schema it was ***ID.
Anyways the problem is solved.
Thanks For your time and help.
Hello Rusel,
Thanks for the reply. I want to know, what are the possible ways for receiving same message twice using two different ports or with single port having single or multiple operations..
What could be the complications i will face?
My requirement is such, that i want to receive same message twice anyhow!!
Please help, thanks alot in advance.
Regards,
harry
yes, I did and there were no problems.
I tried another way to check if the WS schema was alright.
Lets say i have
1) an XML file “OrderFile.xml”
2)Internal schema “PurchaseOrder.xsd”
3)WS Schema “Order.xsd”
4)an object of WS Schema “POrder”.
OrderFile.xml is picked up and validated against PurchaseOrder.xsd, which in turn is mapped to Order.xsd.
Now, if I use an internal port to save the resultant file validated against Order.xsd, everything is fine. The results are exactly what I need. But if I use the webport, it gives the error, that “POrder” (which an object of Order.xsd passed as a parameter to a webmethod), could no be serialised into the type “Order”, using namespace “http://PSchema.NewOrder“.
Have you validated the mapped web message XML? To do this validation you can use the Test Map command in Visual Studio. Just make sure that Enable Output Validation is selected in the map properties.
Thanks for a quick reply.
There is an xml file and it is validated against an internal schema. That internal schema is then mapped to the schema of the webservice. The parallel shape sends a kind of confirmation that the xml file is validated against the internal schema.
That error usually means that the message you are trying to send through the web port is not valid against the schema. How are you constructing the web message? What is the significance of the parallel shape? The way to debug a serialization error is to validate the web message XML against its schema.
Yes, you can have as many receive locations as you want in a receive port. There is not any order among the receive locations. The receive locations execute whenever they receive messages.
-
AuthorPosts