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
Back to discussions
Expand all | Collapse all

[ISS.0088.9139] Output parameters do not conform to targetOutputSignature:

  • 1.  [ISS.0088.9139] Output parameters do not conform to targetOutputSignature:

    Posted Tue November 13, 2018 05:52 AM

    Hello All,

    I am new to webMethods and i was working on creating a new interface for my client. All in all it looks to be working fine, adapter can fetched data with the query written. But after that we have a service which is suppose to login to salesforce and get a session ID and other details. But somehow that service provides fault messages as mentioned below.

    Any help on this is appreciated.

    Below is immediate error when the login sevice step is completed.

    [b][ISS.0088.9139] Output parameters do not conform to targetOutputSignature:
    errorCode=VV-005
    pathName=/tns:loginResponse/tns:result/tns:userInfo/tns:chatterExternal
    errorMessage=[ISC.0082.9034] Field is absent, field must exist

    errorCode=VV-005
pathName=/tns:loginResponse/tns:result/tns:userInfo/tns: orgDefaultCurrencyLocale
errorMessage=[ISC.0082.9034] Field is absent, field must exist[/b]

    Just for additional information i checked salesforce login history and it says login was sucessful.


    #webMethods
    #soa
    #API-Management


  • 2.  RE: [ISS.0088.9139] Output parameters do not conform to targetOutputSignature:

    Posted Wed November 14, 2018 05:01 PM

    Check the WSD descriptor properties to turn off response validation if that is not needed.

    The error is obvious because the response fields as mentioned above are not optional.


    #soa
    #webMethods
    #API-Management


  • 3.  RE: [ISS.0088.9139] Output parameters do not conform to targetOutputSignature:

    Posted Fri November 16, 2018 08:27 AM

    Hi,

    Besides what M@he$h said, I think it would be useful to find the root cause.

    The error message states that several fields that are mandatory in the contract (WSDL) are not present at runtime.

    On the long run, it is not OK to have this.


    #API-Management
    #webMethods
    #soa


Related Content