We are trying to use the SDK for the first time, in order to get our vmware provisioning
automation product working.
We are running Vctr 2.5/two esx servers at 3.5. the web infrastructure access service
is started (and set to automatic).
However, when we run: https:///SDK the browser hangs up and never
comes back. (firefox just gets a blank screen). Am not sure exactly what we
should be looking at at this point, but this doesn't seem right.
No messages appear in the vpxd.log when we attempt the connection.
We downloaded the sdk from the main screen you get when accessing one of the
ESX servers, and from the 'VI SDK 2.5 Installation Guide' that was part of what
unloaded, took all the steps:
obtained certificates for vctr and also the two esx hosts using browser
exported certificates
ran keytool to import the certificates, and can list out all certificates that were imported
Also just in case it would help, we also downloaded jkd/jre, axis, and the sdk on the vctr system, installed
them, updated the env variables, and tried again, no luck.
I do notice that on vctr, the vpxd.cfg looks a bit too small (below) but it is what vctr installed.
Anyone seen this before? What should we be looking at when we bring up a browser and enter https://
*
Hi,
I didn't quite understand why you would be trying to access . To use the sdk or run the samples provided, you will need to
1. Configure environment and other settings on the workstation (as detailed in the appropriate language-specific sections in the Developer's Setup Guide), or in the respective readme files (readme_java.html, readme_dotnet.html) for the samples.
e.g. To run a java sample, you will need to provide the user name, password, the webservice url to connect to. In the webservice parameter, you would need to specify the vc/host address, e.g. :port>/sdk/vimService.
c:> run.bat com.vmware.vimsample.SampleName <webserviceurl> <username>
If your intention is to check that the VirtualCenter Web service is installed properly:
Using a Web browser, open the document "Documents And Settings\All Users\Application Data\VMware\VMware VirtualCenter\VMA\login\login.html." Fill in the three fields: user name, password, and the full Web service URL; for example, https://localhost:8443. If an XML document appears in your browser, the Web service is running and responding.
If your intention is to open the WSDL file programatically?
Access the vma.wsdl file by placing ?wsdl after the Web service URL; for example, https://localhost:8443?wsdl.
Configure environment and other settings on the workstation (as detailed in the appropriate language-specific sections in the Developer's Setup Guide), or in the respective readme files (readme_java.html, readme_dotnet.html) for the samples.
I hope this information helps.
The reason we are trying to see if https:///sdk or it's something else. it seems to connect, but we
can't really tell.
I tried to follow the instructions in this part of your answer:
If your intention is to check that the VirtualCenter Web service is installed properly:
Using a Web browser, open the document "Documents And Settings\All Users\Application Data\VMware\VMware VirtualCenter\VMA\login\login.html." Fill in the three fields: user name, password, and the full Web service URL; for example, https://localhost:8443 (https://localhost:8443/). If an XML document appears in your browser, the Web service is running and responding.
but there is no VMA folder under virtualcenter. I scanned my vctr 2.5 system for files named login.html and VMA, and
did not find any. This is an out-of-the-box virtualcenter. In the documentation, it says that SDK comes installed.
There is no reference that we can find in the Tivoli documentation about preparing the VCTR system for Tivoli, so are
not sure what, if anything, needs to be done with an out-of-the-box vctr to get ready for Tivoli.
Is there any other way to verify that the SDK is working?
Thanks for the feedback....Vicki