Error WS: Cannot find dispatch method for

[Legacy User]

Hi,

I am implementing a WS call for CAWA DE 11.3 using Web Service Document/Literal job. When I execute it, i am getting an error which says "Cannot find dispatch method for". The job configuration is correct because it is gotten by wizard, then i dont know why return that error. I have attached the request and wizard of job configuration.

 

Thanks a lot for your help.

 

Thanks,

Isaac

Attachment(s)

OdiInvoke.xml.zip   2 KB 1 version

[Steven Bartolini]

Hi Isaac,

 

Please open a case with our Support team so we can assist you.

 

Thank You,

Steven Bartolini

Sr. Support Engineer

CA Support

[Legacy User]

Hi Barts,

We have created the support case, it is 00910349 whitout solutions.

 

Thanks for your help

[Richard Kao]

It is hard to tell what the problem is given the included information.  My guess the SOAP body is not correct. Can you attach a copy of the WSDL and the agent logs?

[Nitin Pande]

Hi,

It looks the agent is getting an error because of empty namespace.  

 

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:odi="xmlns.oracle.com/odi/OdiInvoke/">

    <SOAP-ENV:Header/>

    <SOAP-ENV:Body/>

</SOAP-ENV:Envelope>

 

Request execution failure because of a WebService Exception

javax.xml.ws.soap.SOAPFaultException: Cannot find dispatch method for {}

@at cybermation.commonservice.webservice.ws.binding.CybHttpSoapBinding.invoke(CybHttpSoapBinding.java:538)

@at cybermation.commonservice.webservice.ws.CybDocumentLiteralInvocator.invokeWS(CybDocumentLiteralInvocator.java:345)

There can be an issue with URL of you end-point.  Please make sure your WSDL has all the correct elements in it.

 

I would also recommend to open an issue with CA Support to check you have correct  CA WA WS Agent Plugin.

 

Thank you,

 

Nitin Pande

CA Technologies

[Richard Kao]

It is not due to a empty namespace.  The problem is the job definition.  The Operation Parameters are not correct.  But I need to see the WSDL in order to determine what is the proper Operation Parameters to use.

[Richard Kao]

If request.txt is a working example of the SOAP request.  Then the Operation Parameters should be like this.

 

Parameter Name	Defined as	Parameter Value(s)/Job
/OdiStartScenRequest	Value
/OdiStartScenRequest/Credentials	Value
/OdiStartScenRequest/Credentials/OdiUser	Value	ODIDSCAWA
/OdiStartScenRequest/Credentials/OdiPassword	Value	(REDACTED)
/OdiStartScenRequest/Request	Value
/OdiStartScenRequest/Request/ScenarioName	Value	MAINFLOW_INT2363
/OdiStartScenRequest/Request/ScenarioVersion	Value	001
/OdiStartScenRequest/Request/Context	Value	GLOBAL
/OdiStartScenRequest/Request/Synchronous	Value	false
/OdiStartScenRequest/Request/LogLevel	Value	5

 

 

There are other elements but they seem to be optional.

[Legacy User]

Hi Richard,

Thanks for your help. I have attached wsdl file. We can execute the method using SoapUI and it work well, but CAWA is not.

 

Thanks a lot for your help

 

Isaac

Attachment(s)

OdiInvoke.xml.zip   2 KB 1 version