Forum Replies Created
-
AuthorPosts
-
You can create this using Flat File Schema Wizard. You just need to give an instance of a document you want to send.
Create a Biztalk Project –> Add New Item –> Flat File Schema Wizard
Hope this will help
September 9, 2008 at 11:45 PM in reply to: Has anybody tried custom pipeline on WCF receive port? #20666Hi ,
I have used custome pipeline components using WCF receive location for netmsmq . It’s working fine.
Best reagrds,
Nandika
While it’s been a while since I’ve worked with Flat Files… I can’t think of an easy way to accomplish what you want. The Delimiters are baked into the Schema definition.
You could have done some something custom inside a pipeline. Either a simple find and replace or some think more programmatic.
I’d probably have gone the route of 6 schemas as well. It’s straight forward. Only downside is if you need to make a change… I also think this fits the pattern a little better: one port, one schema, one format. Easy to add a 7th or turn off the 3rd.
Hope this helps.
If I remember right that’s usually a DTC problem. Or a permissions problem.
This may help: http://www.biztalkgurus.com/blogs/biztalk/archive/2005/06/21/BizTalk-2004-Installation-Problems-on-Windows-2003-With-SP1.aspx
Ensure you are installing under Group Account and your install user and other host users have the correct permissions.
Microsoft had some KB’s on this if you look around a bit I’m sure you can find them.
Yeah, a custom pipeline component would do it.
What if my correlation property is suspended on the messagebox and the correlation property is “not promoted”. Is there a way to promote that? I think I need to build a Custom Pipeline component to do that. Am i right?
The best way I have found to debug correlation is to use the admin console to run a query for all subscriptions. When your orchestration dehydrates to wait for the MDN, it should create an instance subscription based on the values on the correlation set. You can view these values and the exact filter expression using the admin console. When the MDN arrives, it should be suspended due to no subscribers found, and you should be able to check all of the context properties against the subscription.
Can you describe the problem a little more? Are the null fields causing a runtime error, or are you not able to set fields to null at design time?
Thank you for advice.
I’ve tryed with that correlation set but no luck on continuing my orchestration when MDN arrives. Is there a way (through administration or HAT) to know exactly why an orchestration and a message can’t be correlated?
I would advise against creating a schema for an MDN. MDN data is not that structured and is likely to vary by VAN and/or trading partner.
Thanks,
September 9, 2008 at 12:47 PM in reply to: Has anybody tried custom pipeline on WCF receive port? #20655I am using custom pipeline components on WCF receive locations without problem. The pipeline operates the same independent of the type of adapter.
You need to set the maxReceivedMessageSize attribute on the http transport bindings. This can be done using the receive location config UI.
That correlation should work. You can probably get by without an MDN schema. You can use xpath to pull data out of the message without having a schema. If you need to pull out lots of different fields, then it might be advantageous to define a schema with some distinguished fields and use those to extract the data. If you want to validate the MDN, then that would be a reason to have a schema. Otherwise, no schema is fine.
Yes that was one big mistake. I was looking for the EDIInt.MessageId property but I had to make reference to EDI base artifacts dll to use that property as a correlation ser definition.
The problem right now is that if I use EDIInt.MessageId or EDIInt.OriginalMessageId the orchestration stops working because the message doesn’t have that property (the AS2 properties are attached after the pipeline process the message, I think) so I’m promoting that property using MyMessage(EDIInt.OriginalMessageId) = XXX and MyMessage(EDIInt.MessageId) = XXX
So this forces that my returning MDN has as returning OriginalMessageId = XXX (so basically if my correlation set is set to use the OriginalMessageId and in both messages I have the same then the message should be correlated right?
Also I don’t now if this a problem but I’m receiving the mdn message in my orchestration as a Xlang.Any type (not sure the complete namepspace) becasue I don’t know how MDN should be created. Heres were I get the info (http://killustar.blogspot.com/2008/01/receiving-as2-mdn-in-biztalk.html). Should this be a problem? should I create an schema for the MDN?
Thanks for your time
From your post, it sounds like BizTalk is acting as a client in this scenario. Did you apply the behavior on the service side as well?
-
AuthorPosts