Skip to Content

Integration to external Service desk using wsdl fails


We are trying to establish connection between Solman Service desk and external Service desk tool.

We have followed the steps in this blog -

However while trying to configure Service consumer we are unable to create the logical port.

The external service desk has provided a URL and a wsdl file.

Problem is that both are failing with error - "Error during WSDL parsing - error received from library handler"

We tried to analyze the WSDL file using SOAManager -> Tools -> WSDL Analyzer

It fails with "Unknown reference type" error.

However, the WSDL file itself is fine, it is of style-document and we have a doubt that problem is because SIDL library is being called to parse this file.

I did check the Note 1801866 and set the value NO_RPC_STYLE to X in SPROXSET.

But the problem is that we need to use this WSDL file from the standard method for Logical port creation and not to create a custom proxy as described in the Note.

Any help in this area will help us a lot to proceed further. Thanks.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Sep 15, 2016 at 02:24 PM

    Hi Mahadevan,

    I am also having the same issue, could you please let me know how did you resolve it ?



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 16, 2016 at 05:37 AM

    Hi Mahadevan

    Doesn't the external service desk have an endpoint so you can create the logical port using create - manual configuration instead?

    In tab "Transport Settings" of the Consumer Proxy I end with something like this:

    URL Access Path: /WebServices/SolMan --> the end-point as defined on external service desk which is called to call the different web service operations on their side

    Computer Name of Access URL: hostname_of_external_service_desk

    Port Number of Access URL: 2060 for example

    When you would configure it like this, once you try to insert the logical port into transaction ICTCONF, the RequestSystemGUID operation would be called on the external service desk to test the connection. The "Ping Web Service" might fail though in SOAMANAGER, it's not always reliable because not all the external service desks can handle the ping request properly so you could ignore certain errors trying that.

    Best regards


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.