community-content

Forum Replies Created

Viewing 15 posts - 2,656 through 2,670 (of 9,648 total)
  • Author
    Posts
  • in reply to: Handling large messages in BizTalk #22623
    in reply to: How to send a message from BizTalk web service? #22622

    Do you mean convert biztalk orchestration into Web Service or any other biztalk component to Web Service or you need to use Web Service Adapter?

    in reply to: Sql Adapter query #22613

    Hi.

    You can add another public receive-send port(Web). you will recieve the input message from the web page  through this public port(Web), get your result from another port(SQL) and send your SQL result to through the former public port(Web).

    After you have deployed this orchestration, you will then have to expose you orchestration as a web service.

    Add this web service reference on your web application  so you can invoke it ans get the results onto your page.

    in reply to: Parsing a single Flat file to multiple XML files #22611

    It sure did help! Thanks a ton!

    Try this schema:

    <xs:schema xmlns:b=”http://schemas.microsoft.com/BizTalk/2003” xmlns:xs=”http://www.w3.org/2001/XMLSchema“>
      <xs:annotation>
        <xs:appinfo>
          <b:schemaInfo standard=”Flat File” root_reference=”Order” 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” default_child_order=”infix” child_delimiter_type=”hex” default_child_delimiter=”0x0D 0x0A” />
          <schemaEditorExtension:schemaInfo namespaceAlias=”b” extensionClass=”Microsoft.BizTalk.FlatFileExtension.FlatFileExtension” standardName=”Flat File” xmlns:schemaEditorExtension=”http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions” />
        </xs:appinfo>
      </xs:annotation>
      <xs:element name=”Order”>
        <xs:annotation>
          <xs:appinfo>
            <b:recordInfo structure=”delimited” preserve_delimiter_for_empty_data=”true” suppress_trailing_delimiters=”false” sequence_number=”1″ child_order=”postfix” child_delimiter_type=”default” />
          </xs:appinfo>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:annotation>
              <xs:appinfo>
                <b:groupInfo sequence_number=”0″ />
              </xs:appinfo>
            </xs:annotation>
            <xs:element name=”Header”>
              <xs:annotation>
                <xs:appinfo>
                  <b:recordInfo sequence_number=”1″ structure=”delimited” preserve_delimiter_for_empty_data=”true” suppress_trailing_delimiters=”false” child_order=”infix” child_delimiter_type=”char” child_delimiter=”|” tag_name=”ORDER” />
                </xs:appinfo>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:annotation>
                    <xs:appinfo>
                      <b:groupInfo sequence_number=”0″ />
                    </xs:appinfo>
                  </xs:annotation>
                  <xs:element name=”Field” type=”xs:string”>
                    <xs:annotation>
                      <xs:appinfo>
                        <b:fieldInfo sequence_number=”1″ justification=”left” />
                      </xs:appinfo>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name=”Date” type=”xs:date”>
                    <xs:annotation>
                      <xs:appinfo>
                        <b:fieldInfo sequence_number=”2″ justification=”left” datetime_format=”yyyy-MM-dd” />
                      </xs:appinfo>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name=”Items”>
              <xs:annotation>
                <xs:appinfo>
                  <b:recordInfo sequence_number=”2″ structure=”delimited” preserve_delimiter_for_empty_data=”true” suppress_trailing_delimiters=”false” child_order=”infix” child_delimiter_type=”default” />
                </xs:appinfo>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:annotation>
                    <xs:appinfo>
                      <b:groupInfo sequence_number=”0″ />
                    </xs:appinfo>
                  </xs:annotation>
                  <xs:element maxOccurs=”unbounded” name=”Item”>
                    <xs:annotation>
                      <xs:appinfo>
                        <b:recordInfo sequence_number=”1″ structure=”positional” preserve_delimiter_for_empty_data=”true” suppress_trailing_delimiters=”false” tag_name=”IT” tag_offset=”0″ />
                      </xs:appinfo>
                    </xs:annotation>
                    <xs:complexType>
                      <xs:sequence>
                        <xs:annotation>
                          <xs:appinfo>
                            <b:groupInfo sequence_number=”0″ />
                          </xs:appinfo>
                        </xs:annotation>
                        <xs:element name=”Code” type=”xs:string”>
                          <xs:annotation>
                            <xs:appinfo>
                              <b:fieldInfo sequence_number=”1″ justification=”left” pos_length=”5″ pos_offset=”2″ />
                            </xs:appinfo>
                          </xs:annotation>
                        </xs:element>
                        <xs:element name=”Description” type=”xs:string”>
                          <xs:annotation>
                            <xs:appinfo>
                              <b:fieldInfo sequence_number=”2″ justification=”left” pos_length=”12″ />
                            </xs:appinfo>
                          </xs:annotation>
                        </xs:element>
                        <xs:element name=”Quantity” type=”xs:string”>
                          <xs:annotation>
                            <xs:appinfo>
                              <b:fieldInfo sequence_number=”3″ justification=”left” pos_length=”1″ />
                            </xs:appinfo>
                          </xs:annotation>
                        </xs:element>
                      </xs:sequence>
                    </xs:complexType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:schema>

    Hi,

    Thanks for the response. This is the main issue. I have gone through the post while looking for solution. Actually Order record is a multiline record. So, with Schema I have one record for Order and next for Item (repeating record). Now If i test with 1 message, pipeline creates single xml message. If I place a repeating record in flat file, pipeline still creates a single message as it takes next order record as an item record. I have placed ORDER as Tag for the order record. Assigning Maxoccur property to order ecord will do fine for order record but not for items.

    So, If I have the above mentiones data in flat file I will get a message like

    <Order>
    </Order>
    <Item>
    </Item>
    <Item>
    </Item>
    <Item>
    </Item>
    <Item>
    </Item>

     

    in reply to: Loop is undoing changes to messages #22607

    Are you using message assignment.

    My understanding is that you must do changes on the message assignment shape. You will have to have message = $$$$$something$$$$$

    Here is a detail tutorial to debatching a flat file : http://geekswithblogs.net/benny/archive/2006/02/05/68249.aspx

    in reply to: send/receive xml message question #22605

    It depends on how you define your <Inventory> schema. If the number of occurrence of <Item> is more than 1, then you don’t have to create the envelope schema. You can just need to use a looping functoid to do the mapping.

    I guess you need to debatch the message per ORDER. You can do that using flat file dissassembler component in pipeline.

    Once you generate the schema using flat file wizard, change the “Max Occurs” property of ORDER node to 1.  Then use a receive pipeline component, drag a flat file dissassembler component and use the above schema in the “Document Schema” property. Then use the above receive pipeline to receive the flat file message.

    Hope it helps…

    SK 

    in reply to: host, host instances, and handlers #22601

    thank you. i was sure that i was missing something.

    in reply to: send/receive xml message question #22600

    But how about mapping:

    <?xml version=”1.0″ encoding=”utf-8″?>
    <ArrayOfItem xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema“>
      <Item xsi:type=”CD”>
        <ProductName>Iron Maiden</ProductName>
        <ProductPrice>99</ProductPrice>
        <ProductNumber>1</ProductNumber>
        <ProductCount>6</ProductCount>
    </Item>
    </ArrayOfItem>

    to:

    <?xml version=”1.0″ ?>
    <Inventory>
     <Item>
      <Name>South of Heaven</Name>
      <Count>666</Count>
      <Price>66,6</Price>
      <Comment>Varldens basta skiva</Comment>
      <Artist>Slayer</Artist>
      <Publisher>Def Jam</Publisher>
      <Genre>Metal</Genre>
      <Year>1986</Year>
      <ProductID>666</ProductID>
      </Item>
      </Inventory>

    Is it still necessary with an envelope schema?

    in reply to: host, host instances, and handlers #22599

    You’re confusing two concepts. The fact that the SOAP adapter supports two-way operations doesn’t change the relationship between ports, adapters and handlers.

    What I mean by this is that for a send port, even a two-way one, what matters is still the send handler associated with the adapter. The receive handler doesn’t enter the equation at all.

    Similarly, if you’re talking about a receive location, the fact that the port might be two way doesn’t change that only the receive handler is important there.

    The thing with isolated hosts and isolated handlers is related to the fact that the *receive* side of the SOAP adapter (i.e. receive locations, NOT receiving responses in send ports) runs in IIS, and thus must run in the context of an isolated host.

    Does this clear things up a bit?

    Hi Niklas,

    i’m back again in my project and got a new question: the web service in my biztalk project has no schema under reference,that’s bacause that web service return primitive types. i can create a new schema with an xml reponse example by “generated items”,you know. here is my problem; i can create an ex xml reponse but i need also an xm example to use in message transfrom (from web page input to web service request) also i’m gonna create a map for these two type of messages. Now,do i have to generate two schemas (for request and reponse) and stick them together to create a “reference.xsd”?

    hope i could tell my problem and hope to get an answer..

    thanks.

    in reply to: 2006 R2 Build problems – EDI schemas #22595

    I was getting this error as well. It turned out that my strong name file and some of my sub assemblies had different assembly versions. Insuring they were the same accross all my projects, solved the proble.

Viewing 15 posts - 2,656 through 2,670 (of 9,648 total)