Forum Replies Created
-
AuthorPosts
-
I know with the new WCF Adapters you have total control of the output Envelope. You should be able to use the WCF Adapter to send a message to the web service – I think? Just use the Basic HTTP Binding.
Then, you should be able to define your SOAP Envelope inside the Message tab (I think that’s what is’s called) inside the WCF Configuration.
Hope this helps.
I've been trying to post the schemas for this problem; however, it says that this forum has a moderator. So hopefully they'll eventually show up.
Thanks for your time.
AntonioL.
Ah never mind…. I rewrote the query to output each of the possible PRFX queries as a seperate SQL query and BTS picked them up and handled them as individual messages as I needed it too… Thanks!
More information…
After looking at this some more, it seems that the delay is in the response part of a Req/Res port. In my Orch, I have parallel processes, one sends the response using a removeBOM pipeline, and another just does a file drop onto a local drive using the XML Transmit pipeline.
In Hat the time between the response and the file drop is what grows. I think the time in HAT would be start time, but again I am guessing.
What would make the time between the kickoff of the file drop increase over time, and why would recycling the App Pool rest the tim?
I could be off base, but do you have a party set up in your App with that cert selected? That caused me problems when I was first working with BT and certs. Other than that, I do not know much about ssl.
good luck
Actually, I went back and looked at my code.
The code starts off as
<sql_salesorder>
<OUTBOUND_SALES_ORDER>
<PRFX></PRFX>
<PRFX></PRFX>
</OUTBOUND_SALES_ORDER>
</sql_salesorder>
My envelope processing leaves me with the message above. Which is a problem for me…. But appears to be more SQL related than Envelope processing… Anybody have an idea on how I can code an explicit XML query so that I'd get
<sql_salesorder>
<OUTBOUND_SALES_ORDER>
<PRFX>
</OUTBOUND_SALES_ORDER>
<OUTBOUND_SALES_ORDER>
<PRFX>
</OUTBOUND_SALES_ORDER>
</sql_salesorder>
Instead of the above where both of the PRFX's are in the same <OUTBOUND_SALES_ORDER> tags. I tried using a cursor to select one at a time, but it doesn't appear to be working.
November 6, 2007 at 11:40 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18344Thanks for taking the on this.
The header schema is:
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" xmlns="http://Ameritrade_History.StockTransactionHeader" targetNamespace="http://Ameritrade_History.StockTransactionHeader" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
<b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true" allow_early_termination="false" early_terminate_optional_fields="false" allow_message_breakup_of_infix_root="false" compile_parse_tables="false" root_reference="Header" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Header">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="positional" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Header_Child1" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" pos_offset="0" pos_length="81" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>The body:
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" xmlns="http://Microsoft.Samples.BizTalk.FlatFileReceive.StockTransactionSchema" targetNamespace="http://Microsoft.Samples.BizTalk.FlatFileReceive.StockTransactionSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
<b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true" allow_early_termination="true" early_terminate_optional_fields="true" allow_message_breakup_of_infix_root="true" compile_parse_tables="false" root_reference="StockTransactions" />
</xs:appinfo>
</xs:annotation>
<xs:element name="StockTransactions">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="hex" child_delimiter="0xA 0xA" child_order="infix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element maxOccurs="unbounded" name="IndividualTransaction">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="char" child_delimiter="," child_order="infix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element name="am_Date" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_TransactionId" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="2" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Description" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="3" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Quantity" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="4" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Symbol" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="5" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Price" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="6" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Commission" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="7" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_Amount" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="8" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="am_SalesFee" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="9" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>The footer:
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" xmlns="http://Ameritrade_History.StockTransactionFooter" targetNamespace="http://Ameritrade_History.StockTransactionFooter" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
<b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true" allow_early_termination="false" early_terminate_optional_fields="false" allow_message_breakup_of_infix_root="false" compile_parse_tables="false" root_reference="Footer" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Footer">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" child_delimiter_type="hex" child_delimiter="0x0A 0x0A" child_order="infix" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element maxOccurs="1" name="Footer_Child1" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" pos_offset="0" pos_length="17" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>—-
AntonioL
November 6, 2007 at 11:27 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18343Can you post your schema?
There are a number of other things it could be and going back and forth it time consuming 🙂
November 6, 2007 at 11:20 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18342Yes, I took it into account. The last comma is the delimiter before "SALES FEE" (9th. field) which happens to be empty in this sample.
November 6, 2007 at 11:05 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18341Are you accounting for the comma at the end of each line? Normally you wouldn't have a comma at the end of a line unless there is a blank field at the end of each record. I'm thinking your delimited may need to be:
0x2C 0x0A 0x0A
If your schema only has 9 records than the last comma has to be part of the delimiter.
November 6, 2007 at 10:56 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18340The syntax is 0x0A 0x0A. This part was done with the wizard by the way.
November 6, 2007 at 10:10 AM in reply to: Problems parsing "simple" flatfile (Error 80131940) #18339What's the syntax of your delimiter?
0x0A,0x0A
or
0x0A 0x0A
or
0x0A;0x0A
I can't remember off the top of my head how to specify 2 hex values for the delimiter, but if not done correctly it won't work, even though your logic is correct.
I don't have the exact error message but I remember it mentioned something along the lines of 'error before processing /r/r' and then it did show the error # 80131940.
I am already using a double linefeed (0x0A) as a delimiter.
The schema for the body was generated using BTS's wizard.
Thanks,
AntonioL
What is the error you are getting?
If the problem is the blank line between each record you could try changing your delimiter to being a double (linefeed and a new line) … don't quite know the hex off by heart.
Have you tried using the Flat File wizard in Bts 2006? It is really very good and thus far I have not had many flat files that I have been unable to use; even some very complex ones.
Can you try limiting your time frame further meaning can you break it into smaller time intervals of 3 to 4 hours etc.
Also if there are any other factors you can limit your query by like the schema name of message like (usually method name of web service call..)
then it might execute faster. You can just begin with the query in HAT and work further on it..
-
AuthorPosts