DSXchange

AxisFault
faultCode: {http://xml.apache.org/axis/}Call.invoke
faultSubcode:
faultString: Cannot invoke Call with null namespace URI for method MT_PostInvoice_Req
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: AxisFault
faultCode: {http://xml.apache.org/axis/}Call.invoke
faultSubcode:
faultString: Cannot invoke Call with null namespace URI for method MT_PostInvoice_Req
faultActor:
faultNode:
faultDetail:

Cannot invoke Call with null namespace URI for method MT_PostInvoice_Req
at org.apache.axis.client.Call.invoke(Call.java:2498)
at org.apache.axis.client.Call.invoke(Call.java:1753)
at com.ascentialsoftware.wsclient.OperationCall.invoke(OperationCall.java:303)
at com.ascentialsoftware.wsclient.WebService.callServiceInternal(WebService.java:1685)
at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1591)
at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1544)
at com.ascentialsoftware.wspack.Transformer.process(Transformer.java:105)
at com.ascentialsoftware.jds.StageFactory.runStage(StageFactory.java:544)
at com.ascentialsoftware.jds.StageFactory.runTransformer(StageFactory.java:361)

What are you trying to accomplish, and with what job design? Is there really an empty namespace URI where one is required?

Or are you just informing us that this error has obtained?

Details, man, details. You can't just post an error message and walk away. Well, obviously you can but it's not a good way to get help.

Hi,

Thanks for the reply.

I am using a simple job design of Dataset --> Web Services Transformer --> Dataset If successful I update the table back to Successfull or writing to rejects and updating the table to 'R'. A simple dataset in which one column has an INPUT_XML structure and calling a web service transformer in Datastage 11.5 version.

There is a default namespace defined as

xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

Is there an additional namespace should be defined for MT_PostInvoice_Req?

I would imagine you'd need to post the xsd before anyone could help with that question.

xsd is not needed, but we'll have to assume that you imported the wsdl successfully.

Difficult to say what the issue might be. Search thru the threads in the forum over the past 10 years....there has been lots of discussions about using Web Services......

...but a couple of things to note:

a) be absolutely certain that you can run the same web service using any kind of testing tool "outside" of DataStage, such as SOAPui.... and preferably also on the same platform as the engine, or at least with the same conditions for getting outside your firewalls.

b) try to get an edition of the web service for testing that does not have any security...just to keep things simple when first getting it to work.

c) have you ever run the web services tranformer before? ...or is this the first time? ...is it the first time at "this" installation? ...or the first time on "this" Server?

d) do you have access to the author/owner of the service, who knows the wsdl and everything about the service, its calling signature, what it needs as input, etc.?

Ernie

Okay, fine, so I misspelled "wsdl". Sue me.

Hi All I think you are correct the xsd did not have the namespace being populated. I found that out using the Schema Library Manager.

Asked the team to send the corrected .xsd's

...there's a confusion here.

The Web Services Transformer needs no schema. It is not based on the Hierarchical Stage, and has nothing to do with the Schema Library Manager. You don't need an xsd; you don't need to import one.

....you only need a valid WSDL, which is a SOAP specification.

Key here are the points I made earlier. Don't even try to get it working from inside of DataStage until you are very familiar with the service and are able to invoke it successfully outside of DataStage, preferably on the same platform as your engine.

Ernie