Forum Replies Created
-
Posts
-
What authentication do you have setup on the BTSHTTPReceive.dll in IIS. If it is anonymous, the there are no user credentials. You will need to use Basic or NTLM
What error do you get when the BTSHTTPReceive.dll call fails?
When i have to convert an xml file to CODECO EDI D95B message format , i am using Passthru Send Pipeline (as XML Transmit pipeline was giving some error).
But i am not getting any output, infact the error msg is "the required segment is not documented" But i have created my the CODECO EDI D95B schema with all the standards in mind.
Pls suggest me where i am going wrong. Is it the issue of my schema or a Send pipeline , do i have to use any other pipeline or create any custom pipeline?
Thank you
Gaurav Garg
I am doing the integrity check in the beginning of my orchestration and I would like to parse it as
Root
<Data>
</Data>
So if you could tell me how to use the pipeline in my orchestration it would be really great.
Thanks for your Help!!!!!!!!
It seems you want to define the parsing schema as
<Rootnode>
<Header> (0,1)
<Data> (0,1)
<Trailer>(0,1)
So your batch is the whole file and each individual XML instance will either be a header, a data or a trailer record.
Then ignore the header and trailer in your application. This obviously does not preserve your integrity check, but it parses the instances like you want.
Hope that is useful
– weak architect
My uneducated guess would be that it doesn't have permission to see the external file path when it executes in Biztalk.
So although the function works, it effectively can;t do what you want because of security concerns. That would explain why it works in .net but not Biztalk.
-weak architect
I am pasting an Instance of my Schema
Header,Date,SystemID,Location
Data,Name,Amount,Customer,Location,Rating,Year,POSID
Trailer,DataRec
The above is my data file with the the data line Max occurance set to unbounded, As a matter of fact Every line starts with Header, Data or Trailer so we know what we are looking at.
The specs are
Header (1,1)
Data (0,Unbounded)
Trailer(1,1)
-Thanks
Hi Stephen,
Thanks for the reply. Here I am trying to avoid the Orchestration. I am using the custom xsl stylesheet(option to select the stylesheet in map properties), because when I use the BizTalk mapper my application gets hung and that is not serving my purpose. In the Biz Talk Mapper Tool scripting functoid I could call a dotnet component. But I am not able to use the Mapper and custom xsl together. Is there any way I can come to know if a particular xslt function is supported or not by the BizTalk Map.
Thanks
Hello Greg,
Thanks for your offer. I actually found the solution in a reply that you made to post #3557 that you made to someone else!
Cheers
You need to implement your own COM Property Page;
You register the CLSID in the registry – see Configuration Property Pages on this page
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS06CoreDocs/html/bc85b96e-7b7b-4131-88ec-87b419a61bc2.aspThere are very few details about creating this property page. I gave up and used the standard interface, which you can extend with dialogs
It looks like you missing the NAD loop in the input document you are trying to serialize.
Either add the data, which may not be an option for you , or remove the requirement for it in the schema. I am not sure how to do that in this hacked context, maybe you can figure it out.
Any chance of getting a whole file. With trailer records, it is not so much the Trailer record itself, as the preceding records which determine how you would debatch
The error indicates that the message has made it thru the pipeline and has been published to the message box but cannot find a matching subscription. i.e. a send port or orchestration that will process the message. You need to check the subscriptions (use BTSSubscriptionViewer.exe) and match with the promoted properties.
What pipeline are you using?
If you have 2 schemas with the same MessageType (targetnamespace#rootnode) then you can specify the required schema in XML Disassembler pipeline component ( with BTS2004 you need to use a custom pipeline containing the Xml Disassembler)
Another option is to declare a single Envelope schema and debatch and forward the content of the envelope. You need to declare separate schemas for the content messages. I have not used SAP with Biztalk, so am not sure if this is possible
Hey Bob,
I see your dilemma, as it's a common one when dealing with already-existing stored procs. First, this is a great BizTalk paper on the SQL Adapter (http://msdn2.microsoft.com/en-us/library/ms935658.aspx), so check that out.
To your point, I wouldn't say that using a component to call a proc is "bypassing standard BTS functionality." When using the SQL Adapter, one of the primary "value adds" is the generation of schemas. That's not really useful in your case. Given that you're just getting a value back from your call, you could still store that value in an orchestration variable, and use the BizTalk workflow to drive a next step based on it. The SQL Adapter is just one piece that you can choose to use, or ignore. There's still lots of other interfaces you can talk to besides SQL, and the workflow piece doesn't really care where the data comes from!
Does that help at all?
Hi
no there is no xml auto … it does work though if the reponse is char rather than int – I would have expected that not to work either.
I am working with several hundred legacy stored procs on an MSSQL 2000 db, so I can't go changing them. It'd be a shame to have to bypass all of the standard BTS functionality … in fact it would be a major problem since we are supposed to be adopting BTS as our corporate standard workflow / interfacing tool !
Thx for the reply
Bob
