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.  Document Snyc Problem

    Posted Thu May 25, 2006 08:07 PM

    Hi ,

    When I am doing selected document Snyc getting Warnings Like

    warningMessage: [ISC.0107.9002] Cannot create field ‘*body’ in Broker document type for ‘Enterprise.enterpriseDocuments:Status’; this field name is not valid on the Broker. The Broker will transport the field contents, which will be visible to Integration Server clients only.





    Warning: 1

    warningMessage: [ISC.0107.9002] Cannot create field ‘@unitOfMeasurement’ in Broker document type for ‘Enterprise.enterpriseDocuments:Status’; this field name is not valid on the Broker. The Broker will transport the field contents, which will be visible to Integration Server clients only.



    I don’t know why I am getting these warnings .,
    I appretiate your reply

    RAJ


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


  • 2.  RE: Document Snyc Problem

    Posted Thu May 25, 2006 09:31 PM

    Hi Raj,
    As evident from the warning messages you get:
    While * and @ are acceptable as the elementName in a IS Document, same is not allowed by Broker. So in your IS Document Enterprise.enterpriseDocuments:Status change the field names from *body to body and @unitOfMeasurement to unitOfMeasurement and so on…

    Regards,
    Bhawesh


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


  • 3.  RE: Document Snyc Problem

    Posted Thu May 25, 2006 09:48 PM

    Thanks Bhawesh ,
    I appretiate your reply …


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


  • 4.  RE: Document Snyc Problem

    Posted Fri May 26, 2006 12:02 AM

    And if you do this that document will not be usable for creating or reading XML documents of that type, which is presumably why you have @ and * in the first place.

    The warning is only meaningful if you have non-IS components subscribing to the document type. Otherwise, there is no impact and the warning can be safely ignored.


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