Forum Replies Created
-
AuthorPosts
-
The XmlReceive pipeline uses the XmlDisassembler and the Party Resolution components.
Bringing up again
Thanks a lot vijay!
I went through some posted blogs for debatching.That was helpful.
You have create a new message of type original message and assign the values from incoming message. It will be better if you can send the schema of input as well as output expected.
thanks
vijaykishans
You might also want to check out some of the comments on this blog post: http://www.biztalkgurus.com/blogs/biztalk/archive/2008/04/28/biztalk-2006-r3-a-step-in-the-right-direction.aspx
Well, I did talked to Microsoft and they confirmed officially that it is not supported. CTP version of R3 might come up by the year end[:(].
I took a quick look, and couldn’t find anything to back up the notion of a maximum assembly size. So maybe there isn’t one.
Thanks for all of your support. I got the software installed. We should also install the below hotfix if installing BTARN 3.5 on BizTalk server 2006 R2 (if configuration manager don’t open after installing BTARN 3.5)
It turned out to be an erroneous page in Map file. Once I deleted the page I was able to build the app…
I have seen this behaviour before.
Greg –
I occasionally have the compile hang you described. Sometimes I can kill devenv and reopen and compile, othertimes I have to restart the machine.
My colleage told me there is a hard limit to the size of an assembly, I don’t know this for a fact, but I believe him.
So there are a variety of things – occasional devenv bug and the hard limit.
I guess if you restart from fresh and the compile still hangs, that would suggest that you hit the upper assembly size limit. If you put some of your artifacts in their own assemblies and reference them in your main project, you should be able to successfully compile again.
[I don’t warranty this information, a real microsoft person would be able to confirm this or deny this assessment with some authority]
…maybe I spoke too soon…
I am having trouble building on of my projects now. I recently added a a few schemas, an orchestration, a pipeline and 2 maps to the project. The build starts but seems to hang and never recovers.
I’ve had issues in the past with the Windows “Indexing Service” so I tried turning that off and building again, but it didn’t seem to help. Is anyone else experiencing build issues on big projects?
June 20, 2008 at 4:50 AM in reply to: Loosely Coupled Design – Help (Contract First Questions) #19961I have been using the RPC style approach. You’re right, the WCF publishing wizard doesn’t allow you use a message only approach. That said, I bet there is a way that you can take the service that the wizard generates and modify it to accept only the message without any wrapper.
June 20, 2008 at 1:20 AM in reply to: extract individual nodes from a collection of nodes xml #19958Check out this example from Stephen Thomas, which shows the two most common debatching techniques
http://www.biztalkgurus.com/media/p/15489.aspx
and google Aggregating Sequential Convoy for eamples for techniques on re-assembling the response. You will not require a convoy if your web service is synchronous but the re-assembly/aggregation of the web service responses will be necessary.
I am looking at the in and out structures trying to see what the issue is.
We have multiple invoices on the input and multiple invoices on the output. So there is a looping connection from Invoice to INVOICE. This tells the mapper, which generates XSLT, to put a “for each Invoice node on the input, create an output node of INVOICE”.
Second, he needs three iterations of the REFERENCE node in each INVOICE. Again this is accomplished with another looping functoid to REFERENCE. The input would be each node – BuyersOrderNumber, SuppliersInvoiceNumber, DeliveryNoteNumber. Looping does not require 1:1 loop matching, you can create output loop iterations with multiple disparate inputs to the looping functoid. (aside: You could even use a repeating node and a single field at the same time as input to a looping functoid, for example.)
The technique to control what happens in each iteration is by using a logical tied to everything that goes on that iteration. For example, “if BuyersOrderNumber is present” would be the logical test and then we would tile that logical to the the conditoinal mappers that populate the fields for this output iteration, such as REFTYPE, REFDISC, and REFCODE.
So this is how we do things with pure functoids. Six of one, half dozen of another. I can understand if you were doing more webservice oriented work, with
smaller, less complex messages, I can see where one would tend more
towards breezy, hand coded XSLT. Again the advantages of the mapper are picking the node from the tree view, which gets more important with EDI, where you have the same segment in different levels of a document. Also, with more time on the tool, you get use to laying out groups of functoids in a particular way that you can later recognize visually.Either way you do it, it’s a FUN challenge.
June 19, 2008 at 5:35 AM in reply to: Error2 The number of applications in this group has reached the maximum number allowed in this BizTalk edition. #19955You have two choices:
1. Restructure you applications to fit within the limit
2. Upgrade to an edition better suited to your needs
-
AuthorPosts