Forum Replies Created
-
AuthorPosts
-
December 27, 2006 at 7:06 AM in reply to: Prefix a tag to a record in a flat file and then send to process #17079
Post some sample source data and destination schema.
I have heard very little about vNext (BizTalk 2008) and nothing on timelines.
I’d guess that anything anyone said now would just be a guess… as I think the focus is getting R2 out the door.
If I remember right, you can create a XLang Message by loading from String, Xml, or Stream. Check the help guide to be sure.
Might also want to note that you can not construct new messages per say in .net code. You can only return messages or change messages passed in. Make sense?
I’d probably just use System.IO to load the message as a stream or something easer to work with than a byte array.
David-
What you are experiencing only occurs the first execution after a host restart, which on a production server should be infrequently. Like any other .NET application BizTalk assemblies are only compiled to MSIL. On first execution JIT compilation takes place so it takes a bit longer than usual to execute. I don’t know of any work around and it is in my understanding happening “as designed”.
For this reason I suggest that before doing any perf testing, (or before demoing BizTalk to others) that you run sample messsages all the way through the process, (JIT happens more granularly than the assembly level). This will get the JIT "out of the way" and be ready to rock!
Hey,
So you're strong-naming the C# assembly, correct? When you say "only BT assemblies are eligible for the GAC", how are you GAC-ing the assembly? Just dragging the compiled .dll into the C:\Windows\Assembly folder?
Once GACed, your reference in the BTS project should work fine at runtime. If not, let me know.
Previously, it was running onloy with valid permission/access on various objects. Now, i made the current account as an administrator. But, no use.
Thanks
Venky
Have you Serialized that Assembly.Try it and then GAC it.
Let us know your findings.
Here you need to have custom .net component which will moniter the AD and post data to biztalk whnver the Account expires.Once data is posted to biztalk then you can mail it up through SMTP adapter.The custom component could be a Windows Service which moniters the AD and posts data to biztalk Receive folder.
(I had been away for several days so couldn't see the latest response) Sorry for not making it clearer in earlier posts. In addition to passing the location of the file to map, the Xml is being used to pass other "context" information so I cannot pass the original file instead of Xml.
I am now faced with a problem which might have an easy solution but is not obvious to me right now!
In my Orchestration, I am using a .NET component to read the input file that gives me a byte array in the return value. I am using Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecuteReceivePipeline to execute the pipeline. However this method requires an XLANGMessage object as its 2nd parameter. I do not know how to convery my byte array to an XLANGMessage object for passing it to my pipeline. I hope you could help.
Thanks
December 24, 2006 at 8:26 AM in reply to: Port is constantly retrying after code change/service resuming #17068Not really sure about your problem. But I’ve seen custom pipeline components actually crash BizTalk due to exception handling. I’m guessing there is something not being done correctly in terms of how the failed message is handled.
Just a guess though. I’d probably check the help guide and Charles Young’s blogs for some hints.
I wan't to look at a specific attribute (expiration date) on all accounts in a specific OU. When an account expiration date is passed I want to send e-mails to different parties within the organisation.
Hi Tom,
This was a suitable answer.
Regards,
Vinu Natarajan
Thanks alot Tom,
Your explaination pretty much clears the point.
Regards,
Sajid.
Are you getting an adapter timeout or a sql timeout error?
Note to boss. Retry warning as a sign of proper programming and retry engineering. The problem that I have seen is that the retry interval and number of cycles is set for the adapter and therefore when given a large load, it tends to cycle rather than spreading the work load.
Make sure you catch the final error after the number of retries and reinitiatize the sequence. Do that and do some optimization on the procedure if possible.
No answer, but are you working in minimum access/permission scenario or a full-open 'developers' mode.
-
AuthorPosts