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
  • 1.  RosettaNet namespace issue of XSD

    Posted Tue May 20, 2014 06:47 AM

    Hi,
    I am implementing RosettaNet PIP3B2 V11.00 with partner.
    I have a question about namespace issue in service content, can you let me know which one is correct?
    Thanks.

    format 1:
    <AdvanceShipmentNotification
    xmlns=“urn:rosettanet:specification:interchange:AdvanceShipmentNotification:xsd:schema:02.01”
    xmlns:tns=“urn:rosettanet:specification:interchange:AdvanceShipmentNotification:xsd:schema:02.01”
    xmlns:da=“urn:rosettanet:specification:domain:Manufacturing:Axis:xsd:codelist:01.03”
    xmlns:dacc=“urn:rosettanet:specification:domain:Procurement:AccountClassification:xsd:codelist:01.03”
    xmlns:dad=“urn:rosettanet:specification:domain:Manufacturing:AttachmentDescription:xsd:codelist:01.03”
    xmlns:dbpq=“urn:rosettanet:specification:domain:Procurement:BookPriceQualifier:xsd:codelist:01.04”
    :
    :
    :


    upi:SpecifiedFullPartner
    uci:ContactInformation
    uci:ContactString</uci:Contact>
    uci:EmailString</uci:Email>
    uci:FaxString</uci:Fax>
    :
    :
    :

    upi:SpecifiedFullPartner
    uci:ContactInformation
    uci:ContactString</uci:Contact>
    :
    :
    :

    ssdh:DocumentHeader
    ssdh:CorrelationInformation
    ssdh:ContractInformation
    ssdh:ContractIdentifierString</ssdh:ContractIdentifier>
    ssdh:ContractTypeString</ssdh:ContractType>
    :
    :
    :

    Format 2:

    <tns:AdvanceShipmentNotification
    xmlns=“urn:rosettanet:specification:interchange:AdvanceShipmentNotification:xsd:schema:02.01”
    xmlns:da=“urn:rosettanet:specification:domain:Manufacturing:Axis:xsd:codelist:01.03”
    xmlns:dacc=“urn:rosettanet:specification:domain:Procurement:AccountClassification:xsd:codelist:01.03”
    xmlns:dad=“urn:rosettanet:specification:domain:Manufacturing:AttachmentDescription:xsd:codelist:01.03”
    xmlns:dbpq=“urn:rosettanet:specification:domain:Procurement:BookPriceQualifier:xsd:codelist:01.04”
    :
    :
    :
    tns:AdvanceShipment
    tns:PurchasedBy
    upi:SpecifiedFullPartner
    uci:ContactInformation
    uci:ContactString</uci:Contact>
    uci:EmailString</uci:Email>
    uci:FaxString</uci:Fax>
    :
    :
    :
    tns:ShipFrom
    upi:SpecifiedFullPartner
    uci:ContactInformation
    uci:ContactString</uci:Contact>
    :
    :
    :

    ssdh:DocumentHeader
    ssdh:CorrelationInformation
    ssdh:ContractInformation
    ssdh:ContractIdentifierString</ssdh:ContractIdentifier>
    ssdh:ContractTypeString</ssdh:ContractType>
    :
    :
    :


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


  • 2.  RE: RosettaNet namespace issue of XSD

    Posted Tue May 20, 2014 07:49 AM

    Hi Julian,

    Both formats are correct. IMHO, stick with first one.

    HTH.

    Thanks,
    Rankesh


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


  • 3.  RE: RosettaNet namespace issue of XSD

    Posted Tue May 20, 2014 11:16 PM