Forum Replies Created
-
Posts
-
I assume the proc runs where executed by isql. Have you tried having parameters in the procedure?
I usually have a begin and end statement in the proc, but maybe that is implicit.
Doug
Thanks for the ideas Stephen. I tried simplying the stored proc per your suggestion but the schema still wouldn't generate. Monitoring SQL Profiler indicates that the wizard isn't even executing the stored proc. However, if I enable the sql receive port for which I'm trying to generate the schema then I can see that it does execute the stored proc. The data link settings are the same for both, so it seems that the account has sufficient permissions. I've also tried just running a select statement instead of the stored proc at the wizard. The wizard says to not include the xmldata predicate in select statements. Is this because the predicate's native schema builder handles what the predicate does? Should I also leave the predicate out of the stored proc?
Well the main thing I need to figure out now is why the wizard isn't even able to execute the stored prod.
Truly, having common namespace and rootnames was not the solution. Creating a sql procedure adapter that takes <any> element for the input and an <any> for the response appears to work. There is a bit of mapping to recover the data, but it is just a masscopy.
"It just occurred to me that if you used that same namespace and root element name you may be able to link all 'logical' ports to the same 'physical' port. This may be an easier solution." if you run like this you will get Runtime XLANG issue, Schema Compatabulity.
Now that is an interesting idea, the adapter only determines the response root and ns, so it might handle different content structure. However, the generated port linkage in the orchestration requires a defined message. Maybe you can assign multiple sql ports to the same adapter or visa vesa. I still get confused which is the port and which is the adapter. Otherwise you would have to use an <any> element and map it back to specific results. Several procedural questions in that but I may give it a try.
It just occurred to me that if you used that same namespace and root element name you may be able to link all 'logical' ports to the same 'physical' port. This may be an easier solution.
Right now I have built an orchestration that calls a .net class that mimics the sql adapter. It does handle errors and retries, but I am sure it is missing aspects of an adapter I have not discovered.
Thanks, Doug
If you're not getting anything logged into the event log then it's likely that the ISAPI dll isn't even getting executed. I'd check to see if the virtual directory it is on is correctly configured in IIS as an application and with the right permissions to execute ISAPI Extensions.
Also, note that in IIS6 you sometimes need to explicitly enable the ISAPI extension from the Web Server Extensions thingie in the IIS manager
No error was logged at application event log. And ISAPI dll is configured and running under BizTalk Isolated Host User Group.. . I forget to mentioned tht I am using SQL two way port in my orch. It shouldn't matter I guess ???
Cheers
MohitI’m not really a SQL Adapter Expect, but I’d start by removing the where clause and the logic before the select. Just see if you can hit that to get the schema.
Also, make sure you do not have any unsupported data types like BLOB or XML DATA.
If you still have problems, maybe it’s a permissions issue with the account you are running under?
Have you tried using a Logical Function and passing False (using = and set 0 and 1 as values) to the node? That should cause the node to not show up. You can then build map logic abound when you want the node to show up.
Have you tried using a Logical Function and passing False (using = and set 0 and 1 as values) to the node? That might cause the nodes to not show up.
If not, it might be the pipelines adding the nodes. Are you using the Xml Transmit?
I don’t really know of anything.
But could you wrap all of your calls into a single SP and then call that using the SQL Adapter?
Just a thought.
I know of this KB: http://support.microsoft.com/kb/815637
But is sounds like you already tried that. Might sure you restart IIS and your hosts – maybe even the server after making changes.
That’s about all I can think of.
