community-content

Forum Replies Created

Viewing 15 posts - 1,756 through 1,770 (of 9,648 total)
  • Author
    Posts
  • in reply to: EDI Implementation in BizTalk 2004 #24037

    Hi Nick,

    Thanks for Prompt response….Can I have your IM/Skype ID for further communication with my Biztalk Consultant(Developer). I will arrange the call with my developer for further communication.

     

    Regards,

    Mike

    in reply to: Access denied during deployment #24035

    Also you have to run/start VS2008 as admin if you develop right on W2K8 R2. This worked for me.

    Alex

     

    This worked for me too

    Parvez

    in reply to: EDI Implementation in BizTalk 2004 #24034

    Mike,

    There is very limited documentation on the BizTalk 2004 EDI Base Adapter, but there is:

    http://msdn.microsoft.com/en-us/library/ee276946(BTS.10).aspx and

    http://msdn.microsoft.com/en-us/library/ee276975(BTS.10).aspx

    I would suggest that look at using a later version of BizTalk, either 2006 R2 or 2009.

    Rgds, Nick.

    in reply to: EDI Implementation in BizTalk 2004 #24033

    Hi Cecillia,

                      I have the Covast adapter with me, I need Map siggestions for XML to EDI X12.

     

    Mike

    THANK YOU very much

     

    this is real great help. I appreciate your time and info.

     

     

    in reply to: EDI Implementation in BizTalk 2004 #24031

    Hi Nick,

                 Thanks for prompt response. I have to transfer XML to ESI X12. Can you suggest me on this on BizTalk 2004.

                            Thanks In Advance…..Mike

    in reply to: Multiple XML files to 2 flat files #24030

    I created the maps already which wasn’t too bad, but I need more information on sequential convoys. I’ve searched google and found some, but can you give me any more on it?

    in reply to: Error add Service Reference hosted in IIS7 #24029

    Normal
    0

    21

    false
    false
    false

    DE
    X-NONE
    X-NONE

    MicrosoftInternetExplorer4

    <!–
    /* Font Definitions */
    @font-face
    {font-family:”Cambria Math”;
    panose-1:2 4 5 3 5 4 6 3 2 4;
    mso-font-charset:1;
    mso-generic-font-family:roman;
    mso-font-format:other;
    mso-font-pitch:variable;
    mso-font-signature:0 0 0 0 0 0;}
    @font-face
    {font-family:Calibri;
    panose-1:2 15 5 2 2 2 4 3 2 4;
    mso-font-charset:0;
    mso-generic-font-family:swiss;
    mso-font-pitch:variable;
    mso-font-signature:-1610611985 1073750139 0 0 159 0;}
    /* Style Definitions */
    p.MsoNormal, li.MsoNormal, div.MsoNormal
    {mso-style-unhide:no;
    mso-style-qformat:yes;
    mso-style-parent:””;
    margin-top:0cm;
    margin-right:0cm;
    margin-bottom:10.0pt;
    margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;
    mso-ansi-language:DE-CH;
    mso-fareast-language:EN-US;}
    .MsoChpDefault
    {mso-style-type:export-only;
    mso-default-props:yes;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;
    mso-fareast-language:EN-US;}
    .MsoPapDefault
    {mso-style-type:export-only;
    margin-bottom:10.0pt;
    line-height:115%;}
    @page Section1
    {size:612.0pt 792.0pt;
    margin:70.85pt 70.85pt 2.0cm 70.85pt;
    mso-header-margin:36.0pt;
    mso-footer-margin:36.0pt;
    mso-paper-source:0;}
    div.Section1
    {page:Section1;}
    –>

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:”Normale Tabelle”;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:””;
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:”Times New Roman”;
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}

    Old

       
    [ServiceContract(Namespace =
    “http://myservice.ch/contract/IServices/v1&#8221;)]

       
    public interface IMaxService

        {

           
    [OperationContract]

           
    [FaultContract(typeof(IServices.ServiceModel.ServiceRequestFaultExceptionSystemFailure))]

           
    MaxRequest MaxFunction(MaxRequest request);

    ——————————————————————————————————

    New

       
    [ServiceContract(Namespace =
    “http://myservice.ch/contract/IServices/v1&#8221;)]

       
    public interface IMaxService

        {

           
    [OperationContract]

           
    <b>[DataContractFormat]</b>

           
    [FaultContract(typeof(IServices.ServiceModel.ServiceRequestFaultExceptionSystemFailure))]

           
    MaxRequest MaxFunction(MaxRequest request);

    in reply to: Error add Service Reference hosted in IIS7 #24028

    Thanks it’s a good point.

    Could you help me how I can switch to DataContractSerializer?
    What should I change? I have a WCF Service which I consume in BTS and then BTS publish the Service in IIS 7.

    In my WCF CODE
    Old
    [ServiceContract(Namespace = “http://myservice.ch/contract/IServices/v1&#8221;)]
    public interface IMaxService
    {
    [OperationContract]
    [FaultContract(typeof(IServices.ServiceModel.ServiceRequestFaultExceptionSystemFailure))]
    MaxRequest MaxFunction(MaxRequest request);
    ——————————————————————————————————
    New
    [ServiceContract(Namespace = “http://myservice.ch/contract/IServices/v1&#8221;)]
    public interface IMaxService
    {
    [OperationContract]
    [DataContractFormat]
    [FaultContract(typeof(IServices.ServiceModel.ServiceRequestFaultExceptionSystemFailure))]
    MaxRequest MaxFunction(MaxRequest request);

    Is there everthing else to change in BizTalk?

    in reply to: biztalk to use without schema #24027

    BizTalk can handle un-typed messages. Basically any binary stream can be passed thru BizTalk.

    You need to use pass-thru pipelines and if using orchestrations you can declare the messages as type System.Xml.XmlDocument. This is slightly perverse, but System.Xml.XmlDocument is XLANGS untyped message.
    I have processed binary image files thru orchestrations quite successfully

    in reply to: Error add Service Reference hosted in IIS7 #24026

    The problem may be the serializer that is used. I believe you need to use the DataContractSerializer to support List<T> structures, however this serializer only supports specific xml schema patterns. If this serializer fails the XmlSerializer is used.

    What I have done in the past is to create the contract in .Net using the DataContractSerializer attributes, then generated an xsd from this class and added this schema to Biztalk.

      

    in reply to: Batching output #24025

    This can be done in a map. When mapping the header fields use the iteration, equal and value mapping functoids

    Input Record  —- Iteration —— Equals 1 ——— Value Mapping ——-OutputHeader field
                                                                                                  |
    InputHeader field ———————————————-|

    InputDetail field ———————————————————————–OutputDetail field

    This is a classic Biztalk pattern, receiving multiple messages of different formats and updating a single back-end system (SQL database).

    1. Create message for updating your SQL database.
    If you use the new WCF SQL adapter you can use tables, rows, stored procedures, you can even pass a table to a stored procedure if you have SQL 2008.

    2. Create a schema for each different input message type
    3. Create a map from each input message type to your SQL message.

    This should be easy for the comma and tab delimited files.
    For the partial files you will need to implement an aggregator sequential convoy to aggregate the separate text files into a single message before mapping into the SQL message. http://abdulrafaysbiztalk.wordpress.com/2009/11/07/enterprise-integration-pattern-part-5-aggregator-sequential-convoy/
    Not really sure what is happening with the SSH tunnel, but  /n software have a SSH adapter http://www.nsoftware.com/products/biztalk/adapters/ssh.aspx  

    in reply to: Multiple XML files to 2 flat files #24023

    You will need to implement an aggregator sequential convoy
    http://abdulrafaysbiztalk.wordpress.com/2009/11/07/enterprise-integration-pattern-part-5-aggregator-sequential-convoy/

    Once you have aggregated all your invoice files you will need 2 maps, one to create the invoice header message and the other to create the invoice lines message.

    in reply to: Incoming FTP file is LOST in PipeLine #24022

    The “root element is missing” error means the Xml Disassembler or endpoint manager cannot find the message.

    It is possible that the stream you returned from your custom archive component has not been reset to the start position.
    Does your custom component read the stream and write the file before returning? If so you need to reset the stream position to zero.

Viewing 15 posts - 1,756 through 1,770 (of 9,648 total)