community-content

Forum Replies Created

Viewing 15 posts - 4,546 through 4,560 (of 9,648 total)
  • Author
    Posts
  • in reply to: Problems with the xs:date or xs:dateTime #19707

    Internally Biztalk works in UTC time.

    You need to adjust your dates for local time:
    eg
    localDate = date1.Add(System.TimeZone.CurrentTimeZone.GetUtcOffset(date1));

    in reply to: Problem with passthrough of an empty file #19706

     Thanks, I will do that

    in reply to: Flat File Assembling with Line Numbering #19705

     Hi Prashant,

    thx for your reply, I had already found the Iteration functoid. My Problem was, that i had a nested XML Structure in which the Iteration functoid didnt give me the total Number of existing items.

    If managed to solve my problem using two Mappings, the first converting the nested structure to a flat file and the second to count the lines.

    Dominik

    in reply to: Re-Architecting BTS 2004 pro to BTS 2006 #19704

     

    thanks nick. I will get back on this.

     

    Steve,

     

    I would like to cut the services and use BTS. Can you give me insight of what i can reap out of it

    in reply to: Problem with passthrough of an empty file #19703

    You will need to create a custom file adapter.

    Have the receive adapter create an xml message of <empty/> if the file is empty and set the BTS.MessageType to “empty”
    Declare a schema with one node called empty and no namespace (just to match the BTS.MessageType)
    Have the send adapter check the BTS.MessageType, if it is “empty” then create an empty file using the FILE.ReceivedFileName attribute.

     

    in reply to: Re-Architecting BTS 2004 pro to BTS 2006 #19701

     

    Given what you’ve explained, I don’t see a large benefit from using BizTalk2006.  If you do not need the FTP or Oracle Adapters, 2004 would work.

    You might see better performance and you would have a better deployment / admin story in 2006 – but conceptually you’ll still be doing the same thing.

    If you wanted to remove the services and get BizTalk to do more for the work I can see larger benefit in 2006. 

    But I’m a fan of if it isn’t broken don’t fix it. 

    in reply to: Re-Architecting BTS 2004 pro to BTS 2006 #19700

    VJ,

    I’m going to split the proposed architecture into two sections, a poll and publish:

    Receive Data from Oracle Database

    I see two possible options here:

    1. Use your existing .Net assembly (I’m presuming a Windows Service) to poll the Oracle database, generate and FTP the CSV file to the remote BizTalk server for later processing.

    or

    2. Use BizTalk with the Scheduling Adapter (see http://www.codeplex.com/BizTalkScheduledTask) to poll the Oracle database at specified intervals and transform the message returned by the Oracle adapter into a CSV file and FTP to the remote BizTalk server for later processing.

    I think that FTP-ing a CSV file at this point is beneficial as you will reduce the total size of the file being transferred over FTP when compared to Xml. Furthermore, if you plan on using BizTalk as the poller, I would suggest you look at either Branch or Standard Edition to reduce licencing costs (although you would lose relisiency).

    Publish Data to Remote Oracle Database

    Given that you are looking to have a single controller handle the 60 message types, I would suggest a simple custom ESB implementation. The CSV file can be disassembled and mapped (on the receive port) to a common (or set of common) canonical message formats that can be handled together rather than individually, allowing you to have just one orchestration (or maybe a small set of orchestrations) that handle message publishing to the destination Oracle database.

    The CSV file would be received and disassembled (preferably generating a single Xml message per source database record, to ensure small units of work) and the resulting messages published to the Message Box. Using direct binding, the relevant orchestration would collect the message and promote routing information to aid subscription by the send ports (allowing the send port inserting records into table A to collect messages for table A and not table B for example) – this routing information could be based on message content and facts stored in the Business Rules Engine for example. The orchestration would then publish the message back to the Message Box via direct binding, allowing the relevant Oracle  insertion send port to subscribe to the message based on its routing information. Given that the orchestration will be as generic as possible, the Send port will need to map (on the outbound stage of the port) from the orchestration canonical format to the format required by the Oracle adapter to insert into the relevant table. With Delivery Notification enabled, the orchestration will be notified of failed insertions and compensate accordingly.

    I hope this helps get you started – the original architecture was almost there so only needed a little tweaking.

    Rgds, Nick.

    in reply to: Re-Architecting BTS 2004 pro to BTS 2006 #19699

     bringing up again

    in reply to: BT2006R2 and the Oracle Adpter – Strange behaviour #19698

     Just spotted that my email at the bottom is incorrect – should by [email protected]

     

    in reply to: Problem with passthrough of an empty file #19696

     

    Hi Michael

    DId you ever find a solution to this problem.I have the same problem.

     

    in reply to: Add CRLF to Flat File #19694

    Please disregard my inquiry.

    I was succesfull in resolving my problem with the concept of having the “higher node” define the child delimiter as the 0x0D and 0x0A hex characters.

    Thinking that others may have the same confusion or problem as I had, let me describe what I did to resolve the issue on not having the CRLF after each record.

    With the schema generated from the Flat File Schema Wizard having a rootnode, and then all the elements under it. The resulting text output of the send port’s file set to “Append” in Copy mode has NO CRLF for every record. The flat file format requires the pipe as the delimiter and at the same time the column/fields are fixed – see the schema I posted previously.

    My solution to the No-CRLF problem:

    1 – Add a child node under the rootnode.

    2 – Move all the elements from the rootnode to the childnode added in step1.

    3 – Specify the rootnode to have the following child delimiter specifications:

          child delimiter: 0x0D 0x0A

          child delimiter type: hexadecimal

          child order: PostFix

    4. Specify the childnode (added in step#1) to have the following child delimiter specifications:

          child delimiter: |

          child delimiter type: Character

          child order: Infix

    I hope this is clearer for the BizTalkers who will encounter the same problem and are confused.

    Regards !

    in reply to: BAM Alert service #19693

    I will dive into this, thx.

    in reply to: Uninstall on BTS and SQL tables #19692

     I will dive into this, thx.

    The only way to promote properties from within an orchestration using a direct bound port, is to declare a correlation set containing the property and initialising this correlation set when you send the message to the direct port.

    in reply to: Add CRLF to Flat File #19688

    hello Wincy, 

    Can you describe what you did in more detail ?

    What if there is only one rootnode ? Example would be as follows:

      <?xml version=”1.0″ encoding=”utf-16″ ?>
    – <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=”SASScrapData“ child_delimiter_type=”hex“ default_child_delimiter=”0x0D 0x0A“ />
      </xs:appinfo>
      </xs:annotation>
    – <xs:element name=”SASScrapData“>
    – <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 minOccurs=”1“ maxOccurs=”unbounded“>
    – <xs:annotation>
    – <xs:appinfo>
      <groupInfo sequence_number=”0“ xmlns=”http://schemas.microsoft.com/BizTalk/2003“ />
      </xs:appinfo>
      </xs:annotation>
    – <xs:element name=”PlantOfOrigin“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”1“ min_length_with_pad=”4“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”LotID“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”2“ pad_char_type=”default“ min_length_with_pad=”13“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”LotClass“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”3“ min_length_with_pad=”13“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”ScrapDate“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”4“ pad_char_type=”default“ min_length_with_pad=”13“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”Location“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”5“ min_length_with_pad=”40“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”ScrapDescription“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”6“ min_length_with_pad=”40“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”StageNumber“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”7“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”StepID“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”8“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”MPCode“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”9“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”PlanID“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”10“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”MSL“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”11“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
    – <xs:element name=”WaferScrapQuantity“ type=”xs:string“>
    – <xs:annotation>
    – <xs:appinfo>
      <b:fieldInfo justification=”left“ sequence_number=”12“ min_length_with_pad=”20“ pad_char_type=”default“ />
      </xs:appinfo>
      </xs:annotation>
      </xs:element>
      </xs:sequence>
      </xs:complexType>
      </xs:element>
      </xs:schema>

    Thanks in Advance.

    tgbtg

Viewing 15 posts - 4,546 through 4,560 (of 9,648 total)