community-content

Forum Replies Created

Viewing 15 posts - 346 through 360 (of 9,652 total)
  • Author
    Posts
  • in reply to: Building schema for external partners #26079

    Hello,

      In step 2, the easier approach is to expose your schema as a web service (or better as a WCF service) in BizTalk, by following the steps outlined in the following articles:

     

    http://iaimtomisbehave.org/2007/12/12/how-to-expose-your-schemas-as-web-services-in-biztalk

     

    http://msdn.microsoft.com/en-us/library/bb246047.aspx

     

      Good luck.

    in reply to: Debugging orchestrations #26078

    Hello,

      If you have Visual Studio and BizTalk application installed on the same server for development purpose (recommended approach), you can debug your orchestration in the Visual Studio project, by following the steps outlined in the article below:

    http://www.enterpriseapplicationsdevelopment.com/…/biztalk-orchestration-debug.html

      Hope this helps.

    in reply to: http adapter #26076

    Application pool or identity which your are using should the doman\username

    try this schema xsd:

    <?xml version="1.0" encoding="utf-16"?>

    <xs:schema xmlns="http://BizTalk_Server_Project2.FlatFileSchema2&quot; xmlns:b="schemas.microsoft.com/…/2003" targetNamespace="http://BizTalk_Server_Project2.FlatFileSchema2&quot; xmlns:xs="http://www.w3.org/…/XMLSchema"&gt;

     <xs:annotation>

       <xs:appinfo>

         <schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="schemas.microsoft.com/…/SchemaEditorExtensions" />

         <b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="complexity" lookahead_depth="10" 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="Input" />

       </xs:appinfo>

     </xs:annotation>

     <xs:element name="Input">

       <xs:annotation>

         <xs:appinfo>

           <b:recordInfo structure="delimited" child_delimiter_type="hex" child_delimiter="0xD 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="schemas.microsoft.com/…/2003" />

             </xs:appinfo>

           </xs:annotation>

           <xs:element maxOccurs="unbounded" name="Group">

             <xs:annotation>

               <xs:appinfo>

                 <b:recordInfo sequence_number="1" structure="delimited" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" child_delimiter_type="hex" child_delimiter="0x0D 0x0A" />

               </xs:appinfo>

             </xs:annotation>

             <xs:complexType>

               <xs:sequence>

                 <xs:annotation>

                   <xs:appinfo>

                     <b:groupInfo sequence_number="0" />

                   </xs:appinfo>

                 </xs:annotation>

                 <xs:element minOccurs="1" maxOccurs="1" name="Header">

                   <xs:annotation>

                     <xs:appinfo>

                       <b:recordInfo structure="delimited" child_delimiter_type="char" child_delimiter="," child_order="infix" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" sequence_number="1" />

                     </xs:appinfo>

                   </xs:annotation>

                   <xs:complexType>

                     <xs:sequence>

                       <xs:annotation>

                         <xs:appinfo>

                           <groupInfo sequence_number="0" xmlns="schemas.microsoft.com/…/2003" />

                         </xs:appinfo>

                       </xs:annotation>

                       <xs:element name="Header_Child1" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="1" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Header_Child2" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="2" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Header_Child3" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="3" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                     </xs:sequence>

                   </xs:complexType>

                 </xs:element>

                 <xs:element minOccurs="1" maxOccurs="unbounded" name="Details">

                   <xs:annotation>

                     <xs:appinfo>

                       <b:recordInfo structure="delimited" child_delimiter_type="char" child_delimiter="," child_order="infix" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" sequence_number="2" />

                     </xs:appinfo>

                   </xs:annotation>

                   <xs:complexType>

                     <xs:sequence>

                       <xs:annotation>

                         <xs:appinfo>

                           <groupInfo sequence_number="0" xmlns="schemas.microsoft.com/…/2003" />

                         </xs:appinfo>

                       </xs:annotation>

                       <xs:element name="Details_Child1" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="1" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Details_Child2" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="2" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Details_Child3" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="3" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Details_Child4" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="4" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Details_Child5" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="5" />

                           </xs:appinfo>

                         </xs:annotation>

                       </xs:element>

                       <xs:element name="Details_Child6" type="xs:string">

                         <xs:annotation>

                           <xs:appinfo>

                             <b:fieldInfo justification="left" sequence_number="6" />

                           </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>

    in reply to: Create Agreement using C#: BizTalk 2010 #26072

    Hi Mohit,

    Thanks for the reply…I'm able to create the single party binding xml by editing the globalpartyBinding.xml file.

    My requirement to have an utility/.net component which will extract one entire party details(profiles, partnership, agreement,batching) based on the input and creates same party in Target machine.

    Regards,

    Karthick

    there is not fixed limit defined or documented any where , so you can create any number of Receive location

    in reply to: Create Agreement using C#: BizTalk 2010 #26069

    Once you export the Binding File from BizTalk Admin Console, you can manually edit the xml file to have only the Party you want.

    hi, parameter data type is ntext

    Hi ,

    A receive port can have any number of Receive locations ( But the message type should be same if want those to be processed ). As from Orchestration perspective its only one location which gets message(single logical port), .

    in reply to: Input string was not in a correct format #26064

    Hi ,

    From the error message it is pretty much clear that its your helper class " StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)" which has the problem, so can you please have look into the helper class  and also call your helper class in the Atomic scope.

    I hope this helps!!

    //Mahesh

    in reply to: Input string was not in a correct format #26063

    Hi ,

    From the error message it is pretty much clear that its your helper class " StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)" which has the problem, so can you please have look into the helper class  and also call your helper class in the Atomic scope.

    I hope this helps!!

    //Mahesh

    in reply to: Processing pdf and Updating Database… #26061

    well, thanks for the post ,but however ,I don”t find any proper solution to this problem.and also ,I found pdf processing tutorails on Google.

    it gives the details about processing in Biztalk,sending these files to the destination .Someone need help may check it out.

    in reply to: Input string was not in a correct format #26060

    How many Send ports do you have?

    Is it failing on first send port?

    Is there any helper class?

    what is the data type of parameter your stored procedure expects ?

    please check the itinerary status of your project if it is published please make it deployed. and then check it Itinearary database where the nstatus value is 1 or not

Viewing 15 posts - 346 through 360 (of 9,652 total)