Forum Replies Created
-
Posts
-
As far as I know, in any custom adapter you are responsible for setting any context properties yourself. So if you want the file name you will need to promote it.
Check the server's application event log; you should see an error entry for this, and let us know what it says. The most common issue is security when the HTTP ISAPI dll is not configured in an AppPool that runs under an account that is part of the BizTalk Isolated Host Users group.
This is a public queue, and rest of the messages belong to another external Application.
However i am trying to convince my project manager to use a reserve queue to achive the correlated message.
Thank'x
Shamim
You have to promote the property FILE.ReceivedFileName in a custom pipeline, it is not promoted by default. Even if you use an orchestration you won't get the file name if it's not promoted on the FILE receive port…
I don’t really know of any docs or links.
There is a lot out there on Adapters. The BizTalk 2004 Unleashed books covers it well and MSFT has a few white papers on it too.
Not 100% sure, but I think were you get the DLL from doesn’t matter. I think it’s just reading the Orchestration and Public Port information. Even if the DLL is in the GAC you can’t pick it. I’d just make sure you have the dll available someplace to be able to use it for the Wizard. It should exist someplace on your dev system
Hope this helps.
I don’t really think you can do this. I think you can do some types of restrictions but not based on some correlation property that only BizTalk knows about.
What is the problem with the rest of the messages getting published into BizTalk?
As far as classes, QuickLearn.com has some good BizTalk classes but they are not really for the beginner.
The best place to get started I think is the MSDN Virtual Labs. They have some for BizTalk 04 and 06. All would be good to look at.
After that, the tutorials and examples in the SDK is always good too.
Hope this helps.
Well the fast ways is to by pass BizTalk and import the flat file into BizTalk using SSIS.
If the file is smaller, then using BizTalk would be ok and easy to set up. Plus you have a lot of control over routing and mapping.
Hope this helps.
I don’t think you can get this information from the HTTP Adapter. It doesn’t really have the concept of a file name. You can look in the help guide under Message Contact Properties and see what HTTP has to offer. But I don’t think anything will be a file name.
I have found this to usually be a namespacing issue, at least, when it has happened to me. In discussion with MS, I have found that when this happens as an output of a mapping transform, the cause is that source elements are not detected because the namespace is different. No input means no output. Oddly when you try to validate the instance against the schema, validation passes because nothing is matched for testing. I suggested that this should emit a warning.
Doug
i saw this behaviour some times, because of system is running bussy (i.e Sql server, Antivirus or services still in starting mode)
Check this Blogs you might get some info:
http://www.biztalk-server.com/forum13.html
http://blogs.msdn.com/BizTalkB2B/
Thanks
Nar-
