cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Address Location

sap_cohort
Active Contributor
0 Kudos

Is there any way to tell what the SOAP Address Location on our Netweaver is?

I'm being told by the queryview web service WSDL call that it is

http://<server>:<port>/sap/bw/xml/soap/queryview?sap-client=100

I'm not sure if this is correct, because I can't get the queryview webservice to work correctly with adobe flex and that is the URL string it is balking at.

Any help is greatly appreciated!

Accepted Solutions (0)

Answers (2)

Answers (2)

sap_cohort
Active Contributor
0 Kudos

Hmmm.. When I call the SOAP Address provided by the WSDL URL I get an IE page error "The page cannot be displayed"

http://<server>:<port>/sap/bw/xml/soap/queryview?sap-client=100

Funny thing is the Web Service works through Microsoft InfoPath so I can't imagine that this SOAP address is a problem.

So if you are getting something returned when you call your SOAP address we must have something configured wrong on our end? Any ideas how to proceed?

Thanks again!

athavanraja
Active Contributor
0 Kudos

1. uncheck "show friendly HTTP error messages" check box from your browser tools->internet options->advanced and call the soap address again and see what message you are getting

2. which version of WAS you are on? i have tested it on WAS6.40

Regards

Raja

sap_cohort
Active Contributor
0 Kudos

Thanks for the quick reply back. When I did as you suggested I did get the same response you did. So everything must be configured correctly on the Web AS side.

I looked at the RFC trace and I see an error:

"Deserialization Failed"

I found OSS Note 892944 which describes the problem in only the most basic sense. "Try reactivating the Virtual Interavce and Service Definition." I did reactivate both from SE80 and the problem still exists.

Any ideas what this Deserialization Failed Error is about and how to get past it?

Thanks for any ideas!

Former Member
0 Kudos

Hi,

i have the same problem.

Have you solved the problem?

regards

Former Member
0 Kudos

Hi,

i have the same problem.

Have you solved the problem?

regards

Reza

athavanraja
Active Contributor
0 Kudos

soap address location is correct

i havent worked with adobe flex, but to consume webservice using the wsdl, you have to create a client proxy (in the environment where you want to consume) and use the client proxy to consume the webservice.

Regards

Raja

sap_cohort
Active Contributor
0 Kudos

I am setting up the web service correctly in flex. It looks like other people are having problems as well with Flex Web Services in general.

OK. Great so I have the correct SOAP address. Can you tell me what you get when you execute the address? I just want to be sure it's not really supposed to return anything when you execute it... Gotta cover all the bases.

Thanks again!

Ken Murray

athavanraja
Active Contributor
0 Kudos

when you simply call this url from browser you would get the following messages

- <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
- <soap-env:Body>
- <soap-env:Fault>
  <faultcode>soap-env:Server</faultcode> 
  <faultstring xml:lang="en">SOAP processing failure, error id = 112</faultstring> 
  </soap-env:Fault>
  </soap-env:Body>
  </soap-env:Envelope>

Regards

Raja

Consider rewarding points to helpful answers and mark it answered once you question is answered.