BPM, Workflow, and Case

  • 1.  Cannot acess web-service endpoint

    Posted Tue August 24, 2021 05:46 AM
    Good day,

    I would like to know how to setup external service.

    What im trying to do is go thru external service setup in BAW, chose "web service from URL" then complete every input such URL, username and password but while trying to finish the setup it gives me an error:



    Now at this point im stucked, even when i did some certification setup's in Websphere console -> SSL certificate and key management -> SSL configurations -> CellDefaultTrustStore/NodeDefaultTrustStore -> Signer certificates. 

    P.S.: Logs doesn't gave me any additional information, just and GUID for the error =/

    ------------------------------
    Vladislav Tishchenko
    ------------------------------


  • 2.  RE: Cannot acess web-service endpoint

    Posted Tue August 24, 2021 12:42 PM
    While the logs may just have the guid in the line that it was printed to, what does it show before and after that guid was printed?

    ------------------------------
    Rackley Boren
    ------------------------------



  • 3.  RE: Cannot acess web-service endpoint

    Posted Tue August 24, 2021 01:03 PM

    Before:

    [8/24/21 16:59:32:464 UTC] 0013da7e ClientService E   CWLLG2229E: An exception occurred in an EJB call.  Error: Encountered an error while trying to discover services.
                                     com.lombardisoftware.core.xml.schema.xs.WSDLParseException: Encountered an error while trying to discover services.
    	at com.lombardisoftware.server.ejb.clientservices.WSDLSupport.getWSDLData(WSDLSupport.java:214)
    	at com.lombardisoftware.server.ejb.clientservices.ClientServicesCore.getWSDLData(ClientServicesCore.java:449)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    	at java.lang.reflect.Method.invoke(Method.java:508)
    
    



    After:

    [8/24/21 16:59:32:466 UTC] 0013da7e RestHelper    E com.ibm.bpm.rest.util.RestHelper getExceptionResponse Encountered an error while trying to discover services. Error while loading document. Search for 'aae1bc9f-4f3a-42c3-b2a5-432c2e6b8ff9' in the logs to see the error details.
                                     com.lombardisoftware.core.xml.schema.xs.WSDLParseException: Encountered an error while trying to discover services. Error while loading document. Search for 'aae1bc9f-4f3a-42c3-b2a5-432c2e6b8ff9' in the logs to see the error details.
    	at com.ibm.bpmsdk.rest.stp.ServiceWSDLResource.discoverPortTypes(ServiceWSDLResource.java:221)
    	at com.ibm.bpmsdk.rest.stp.ServiceWSDLResource.discoverPortTypeListByURL(ServiceWSDLResource.java:359)
    	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
    	at java.lang.reflect.Method.invoke(Method.java:508)
    	at org.apache.wink.server.internal.handlers.InvokeMethodHandler.handleRequest(InvokeMethodHandler.java:63)
    	at org.apache.wink.server.handlers.AbstractHandler.handleRequest(AbstractHandler.java:33)
    	at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    	at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    	at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:75)
    	at org.apache.wink.server.internal.handlers.CreateInvocationParametersHandler.handleRequest(CreateInvocationParametersHandler.java:54)
    	at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    
    


    ------------------------------
    Vladislav Tishchenko
    ------------------------------



  • 4.  RE: Cannot acess web-service endpoint

    Posted Tue August 24, 2021 02:30 PM
    It looks like the logs labeled as after are referring to a different guid than the first. I did not mean to imply focusing on the single log line before and after the original guid. Typically when I am diagnosing things from the logs, I will look at the logs printed around the error guid until it is clear whatever is printed before or after is not related. So if you observed that it took a while between clicking discover and the error message, you may need to go back a few minutes in the logs prior to the noted guid and a little bit after as well. It is always easier if you are the only one in the environment doing work when trying to recreate and diagnose things like this to help prevent confusion.

    After some quick searching around, there are a number of things this could be from authentication issues to possible namespace issues in the WSDL.

    If you are unable to determine cause from looking at additional logs and searching via Google, I would suggest looking into the must gather to open a ticket with IBM and recreate the issue after the appropriate trace is in place.

    ------------------------------
    Rackley Boren
    ------------------------------



  • 5.  RE: Cannot acess web-service endpoint

    Posted Wed August 25, 2021 07:10 AM
    Thank you very much for the reply, i guess i have found some of the "make-sense" log outputs that can be usefull.



    i hope that's the main issue that causes error duing web-service setup. Other thing is that every WSDL validation tool is okay with some duplication of the name of elements and i have no idea what to change since "ExternalID" is just some variable in the API functions that is used across it.


    ------------------------------
    Vladislav Tishchenko
    ------------------------------



  • 6.  RE: Cannot acess web-service endpoint

    Posted Wed August 25, 2021 08:20 AM
    That's great that you found it. Here was the link to what I saw yesterday while searching the internet regarding schema issues during WSDL discovery. Looks like there are a couple of suggestions on how to get around this issue.

    https://www.ibm.com/support/pages/apar/JR41344

    ------------------------------
    Rackley Boren
    ------------------------------