IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

unexpected prefix located before the Rosettanet pip document type

  • 1.  unexpected prefix located before the Rosettanet pip document type

    Posted Sat July 12, 2008 07:19 AM

    Hi,

    I import PIP3C3_R11.05.00F_NotifyOfInvoice.zip by Modular PIP Import function of RosettaNet Module successfully, but I find the document type in the package WmRNPips is a little strange.Some tags have an unexpected prefix , such as tns110, tns70, tns74,tns114 and so on.In fact , I don’t find the prefix in the xsd for the Pips which is imported by Rosettanet Adapter.How do these prefixes come out ?What’s its impact when mapping and validation ?Accoring to the 3C3 sample in the zip file, it seems the prefixes such as tns110, tns70, tns74,tns114 and so on are not correct, but there are many properties about name space should be defined in the document type. How to define it to the document type ?

    Thanks.
    Crane


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: unexpected prefix located before the Rosettanet pip document type

    Posted Tue July 22, 2008 01:27 PM

    We had same tns struture for 3B3 and managed by adding name space declaration in TPA of 3B3

    Please find attached document for the same… (PIPInfo–>NSDecls)
    TPA.jpg


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: unexpected prefix located before the Rosettanet pip document type

    Posted Mon July 28, 2008 08:46 AM


  • 4.  RE: unexpected prefix located before the Rosettanet pip document type

    Posted Mon July 28, 2008 08:49 AM

    Yes, after adding the name space to NSDecls, pips can be sent successfully now. However, our partner get the pip with unexpected prefix such as tns 110, tns114, tns103 and so on.Any way can remove the unexpected prefix ?Thanks.


    #webMethods
    #Integration-Server-and-ESB
    #Adapters-and-E-Standards


  • 5.  RE: unexpected prefix located before the Rosettanet pip document type

    Posted Tue April 28, 2009 12:53 PM

    Hi Cran,

                       Even i am trying to do PIP 3C3 .I already have PIP3C3 invoice notification zip file.
    

    I did importing stuff and all …

    when i come to developer portion…i need to map documents (i.e pipeline input ) to rosettanet PIP doc.so in pipeline input i have taken my own XML which contains some of the fields which i required to map to rosettanet PIP doc which is in pipeline out.

    so could you please suggest me the way…how to proceed.


    #Integration-Server-and-ESB
    #Adapters-and-E-Standards
    #webMethods