Forum Replies Created
-
AuthorPosts
-
November 15, 2007 at 10:17 AM in reply to: Processing Different Message Types Through The Same Send Port #18436
Kent:
I am almost to the pint where I think I can get this working – after initial trouble with referencing the SendImputPipelineMessages in the orchestration and getting the dreaded ‘unknown exception occured’ message – but there is one thing: the ExecuteSendPipeline method expects an XLangMessage as its’ third paramter, and in your code sample I don’t see you doing any cast or anything. What do you suggest? A Cast? Or?
Kevin
The first thing that you are going to want to do is use the Flat File schema wizard to generate a schema that you can use in your Orchestration. You may want to use distinquished fields for the elements that you want to validate on. It is just an easy way to retrieve your values. Otherwise you can also use XPath to look for these values as well.
I am not sure what your plans are for your Error message. If it was me, I would define another XML schema that would represent my “Error Message” and then include this message in your error message.
Kent
Hi Oxon,
Using WMI to detect this is pretty easy to do. Check out my blog:
http://kentweare.blogspot.com/2007/11/wmi-scripting-for-biztalk-operations.html
Kent
November 14, 2007 at 9:40 PM in reply to: Processing Different Message Types Through The Same Send Port #18430Kevin,
You got it…. Since you are calling the Send Pipelines inside of the orchestration and all of your files are flat files then you can re-use a send port that is sending out messages that are of type “Raw String”.
Kent
Thanks Kent.
I will let you know when we resolve the issue.
Nick
November 14, 2007 at 1:00 PM in reply to: Processing Different Message Types Through The Same Send Port #18424Kent:
Let’s make sure I am following you here:
- You have one or more receive shapes which receives your flat file schema as a message
- You a Construct Message shape on your orchestration design surface and insert the folowing code into it:
msg_Output_FF = new Helper.RawString();
PipeMsg = new Microsoft.XLANGs.Pipeline.SendPipelineInputMessages();
PipeMsg.Add(msgX);
Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecuteSendPipeline(typeof
(MyPipelines.SendX),PipeMsg,msg_Output_FF); - Are you then using the returned RawString ( msg_Output_FF ) to send through a Send Port which expects a RawString? Meaning, I could send any type of message I like though my send port and then configure the port in BizTalk Admin to output the text file to a particular directory?
Thanks for your help!
Sincerely,
Kevin Parkinson
November 14, 2007 at 12:13 PM in reply to: Processing Different Message Types Through The Same Send Port #18423It is a custom pipeline(but not a custom pipeline component). Basically I have created a pipeline and included my flat file schema as the “document schema”. Note that you can place more than one flat file schema in 1 pipeline and the pipeline will figure out which message type to assemble.
November 14, 2007 at 12:03 PM in reply to: Processing Different Message Types Through The Same Send Port #18422Thanks Kent! In your first article on MSDN, you state “Here is my code for the Send Pipeline…”. Can you clarify what you mean by that i.e. had you written a custom pipeline component?
Kevin
Anon,
Not exactly. On biztalk 2004 and up, all messages need to be submitted through an adapter. You can still submit them programatically by, say, doing an HTTP post to an HTTP receive location.
An alternative is to compile and install the SubmitDirect sample adapter that’s in the SDK; it allows you to call a push a message programatically directly; though it is still an adapter and receive locations need to be configured and so on.
Hi Nick,
This how we solved the problem, check out the 4th post in this link:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2316907&SiteID=1
For us we have the “work” file and a “sig” file. The sig file is our trigger that lets the middleware(or in this case BizTalk) that a work file is ready for consumption. So we have a script that is scouring the sig folder every 5 minutes. When it finds a sig file it will look for the partner work file in the work folder. The script will then append a “.BIZ” onto the work file and will delete the sig file. We then have BizTalk looking for “.BIZ” files. With this scenario we have not had any problems with BizTalk consuming partial files.
Ken
Kent,
Yes, lack of locking implementation in FTP/UNIX scenario is my major supposition at the moment. But http://ftp.log confuses me in that theory.
I communicate with support team of the legacy system trying to find out any issues on their side or review the files creating script. The idea is to use file with temporary name in the same folder while writing the content, and just rename the ready to go file from temporary name to the appropriate one.
I would try everything I could to resolve the issue. Your help would be highly appreciated.
Thanks,
Nick
Hi Nick,
I was just going through my notes…it has been a busy past 6 months. One of the symptoms that we had was that our receive location would just lock up. We would get a zero byte file in the FTP Temp folder and the receive location would still be enabled. It was much like a deadlock. We were issued a private hot fix for this but that does not sound like the same issue you are talking about. I don’t remember what the log file said and I can’t find it in my notes…sorry. So we contacted Microsoft Premiere Support and they issued us a hot fix. I don’t have a “fix number” just our case number.
Since you are not using a clustered host our other scenario does not apply to you.
Something else to consider is that when you are picking up these Files, the FTP adapter does not respect file locks from your legacy system. When performing load tests, we had a test harness that would load up the Unix directory with Files. We would leave the receive location on and would find that the occaisional partial file was being delivered. I do not recall what was in the FTP logs. Does this scenario apply to you? If so let me know and I can share how we got around this.
Kent
Hi Kent,
Thanks for the reply.
Our configuration is quite simple in this case. It’s single host instance, no clusters, local ftp-log file. And yes, from time to time we’ve got stripped content (zero byte file). But did your log show correct file size when you received a zero-byte result? That’s what it shows for us and I wonder how can it be.
How did you fix the problem?
Regards,
Nick
Hi Nick,
Can you describe what your FTP Adapter configuration is like? I.e Is it clustered, single host instance? Do you have a local log file? I ask as we ran into two problems with the FTP client that prompted hot fixes. If you symptoms are simlar to ours you may have impacted the same way.
For us we are using a Clustered Host and were storing the log file on a clustered resource drive. That was a problem, if it is on a local drive then it is ok. We also had problems where content was being stripped (zero byte files). We would try to receive 600 10k files and would regularly find that 1 or 2 of them would have its content stripped. For that issue we were issued a private hot fix.
We are also using Unix
Kent
November 13, 2007 at 3:25 PM in reply to: Processing Different Message Types Through The Same Send Port #18410With BizTalk Server 2006(and R2) you can call Pipelines inside of your Orchestration. So you can have a message type of String or Raw String that gets sent out through a Static or Dynamic Send Port. I have some sample code on how to run a pipeline inside your orchestration here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2390531&SiteID=1
If you need to go the dynamic port route check this out
http://geekswithblogs.net/edmundzhao/archive/2006/03/06/71555.aspx
-
AuthorPosts