cpaggen
Contributor
Contributor

Newbie question: ESX/VI not serving WSDL or responding to SOAP

Howdy,

Both Virtual Center and my ESX servers are reachable through HTTP and HTTPS. They show me the standard splash screen telling me I can use Web Access, Download the SDK, etc.

When I try a SOAP request to either of them however, I keep getting HTTP 531 or 565 responses. Nothing gets served (404) if I try https://my-esx-server/sdk or https://my-esx-server/?WSDL - same thing with Virtual Center. I've imported the WSDL from the SDK into SoapUI - SSL is not the issue, I have the server cert locally installed.

I read the SDK guide and it appears both ESX and Virtual Center should be "web services ready" right from the get go. Apparently mine aren't in violent agreement with the doc.

Any commands/tips to verify either ESX or Virtual Center are ready to process WS requests? If yours is working, do you get something when you https://your-server/sdk or https://your-server/?WSDL ?

Thanks,

Chris.

Tags (2)
0 Kudos
3 Replies
cpaggen
Contributor
Contributor

I took a look at /var/log/vmware/hostd.log and notice this for every SOAP request:

Request header:

POST /sdk/vimService HTTP/1.1

Content-Type: text/xml;charset=UTF-8

SOAPAction: ""

User-Agent: Jakarta Commons-HttpClient/3.0.1

Host: 172.25.89.176

Content-Length: 365

LookupByPrefix: path: /sdk/vimService

LookupByPrefix: currentPath: /sdk/vimService

LookupByPrefix: currentPath: /sdk

LookupByPrefix: no match found for: /sdk/vimService

HttpConnection::ProcessRequest: using default handler

SOAP envelope has empty Header element

0 Kudos
cpaggen
Contributor
Contributor

By looking around, I found the wsdl. It's at https://whatever/sdk/vim.wsdl - however, the wsdl has no element (therefore no binding no port exists!) - I must be missing something, so I'll shut up now and wait for someone smarter than me to educate me.

0 Kudos
tmadam
Contributor
Contributor

Try . This then points to vim.wsdl.

0 Kudos