Dirty_Hipster
Enthusiast
Enthusiast

Problems associated with vCO Web Services and WaveMaker

Jump to solution

Hello guys,

It's been a while, but here I am again today, with more questions.:smileylaugh:

Q1. Cannot build connection to vCO through the SOAP URL:

Here is what I am trying to do: connect to vCO using wavemaker

url.PNG

I've tried the following urls:

http://157.191.16.150/vmware-vmo-webcontrol/webservice?WSDL

http://157.191.16.150:8280/vmware-vmo-webcontrol/webservice?WSDL

https://157.191.16.150:8281/vmware-vmo-webcontrol/webservice?WSDL

And I got this:

error.PNG

Q2. How to publish the wavemaker project, on a win2008R2 server?

The project is built on local, if eveything goes well, I would like to publish the whole project on a web server so that more people could access it.

Any suggestions on how I am supposed to do that? How can I address a LDAP group for the authentication control over here?

Thanks so much

DH

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
tschoergez
Leadership
Leadership

hm, the first question rather belongs to the WM communities :smileylaugh:. I would also assume that is uses the default JDK, afaik there is no need to copy the jdk anyhow.

For the certificates: Not having a proper name resolution might indeed be a problem. At least you have to ensure that the hostname in the certificate matches exactly the server name (and that also has to be the name you use when you create the service connection within WM). the filename should not matter. I am not sure though, if all that even works with IP addresses only.

My recommendation: Give it a try with hostnames, configure the hosts files on the WM box and vCO if you don't have a DNS setup.

Cheers,

Joerg

View solution in original post

0 Kudos
8 Replies
iiliev
VMware Employee
VMware Employee

In 5.5, the URL should be https://157.191.16.150:8281/vco/vmware-vmo-webcontrol/webservice?WSDL

Note the '/vco' part added after the port number.

0 Kudos
Dirty_Hipster
Enthusiast
Enthusiast

Hi Lilian,

Thanks for the advice, the vCO I am currently using is 5.1. But I also tried this https://157.191.16.150:8281/vco/vmware-vmo-webcontrol/webservice?WSDL, still got the same problem

Error occurred while importing WSDL! Error: WSDLException: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'https://157.191.16.150:8281/vco/vmware-vmo-webcontrol/webservice?WSDL'.: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

0 Kudos
Jinnie
VMware Employee
VMware Employee

This is a different error. Previously you were getting a File Not Found, while now it seems to be about not accepting the vCO certificate.

Here is an article that explains how Wavemaker handles SSL and what can be done:
mighty virtualization: WaveMaker - handling SSL certificates

Hope that helps

Dirty_Hipster
Enthusiast
Enthusiast

Hi Jinnie,

Thanks for your reply, and I am trying to do the same thing, import vCO certificate into the JVM keystore, but on a windows machine.

Do you happen to know how to do that? I tried something like this but failed.

%JAVA_HOME%\bin\keytool -import -alias serverCert -file RootCert.crt -keystore %JAVA_HOME%\jre\lib\security\cacerts



Thanks

0 Kudos
Dirty_Hipster
Enthusiast
Enthusiast

One follow up question:

if I just put this url to the browser,

with this https://157.191.16.150:8281/vmware-vmo-webcontrol/webservice?WSDL    I can see all the XMLs, which is supposed to be the correct way

with this https://157.191.16.150:8281/vco/vmware-vmo-webcontrol/webservice?WSDL  Nothing but a 404 error.

I am supposed to stick with the first link, right?

0 Kudos
tschoergez
Leadership
Leadership

Be aware that the URL for accessing the webservice is dependent on the version: in 5.5 it is ....:8281/vco/vmware-vmo......, in earlier versions it is :8281/vmware-vmo...

Also be aware that the SOAP API of vCO is legacy, and very limited in functionality. Better use the new (introduced in vCO 5.1) REST API to call vCO from outside. This API provides much more functionality, and is the way to go in future.

See https://your-vco-server:8281/vco/api/docs (in 5.5. In 5.1 skip the /vco/ part again) for the documentation and examples.

For the SSL stuff: You have to care about what Java Runtime environment your WaveMaker installation uses. I am not sure if WaveMaker on Windows uses the default JRE, or if it comes with its own one.

For your deployment question: WaveMaker projects are plain java web applications, you can export them to a .war file and deploy them on any tomcat server (well, technically even your vCO service, however I would only try this at home 😉 http://www.vcoportal.de/2011/11/using-wavemaker-as-web-frontend-for-vco/ ). Use the SecurityService features within WaveMaker to configure LDAP authentication.

These to question BTW are not really related to vCO, you should give it a try and post them on the wavemaker communities. http://dev.wavemaker.com/

(If I remember right, there are also nice tutorial how to authenticate your wavemaker application against LDAP)

Cheers,

Joerg

Dirty_Hipster
Enthusiast
Enthusiast

Hi Joerg,

Your reply is really resourceful and helped me cleared a lot of clouds.

One interesting finding is, in the following post, import certificate to Java JVM is also discussed

https://communities.vmware.com/message/2201707#2201707

it seems WaveMaker has its own java lib, at least for 6.5.2.Release. c:\Program  Files\WaveMaker\6.5.2.Release\jdk-1.6.0_24\jre\bin\keytool.exe


But for the version of WM I installed, which is 6.5.3, there is no jdk package in the WM, so I assume it will use the JDK from the local computer, right? Or do I need to copy the jdk into the WM?

I tried importing the certificates into the local java key store, but still the same error. Does the .cert name have to be exact as the server name? I don;t have a DNS name for this server, just IP, will that work?

Thanks

0 Kudos
tschoergez
Leadership
Leadership

hm, the first question rather belongs to the WM communities :smileylaugh:. I would also assume that is uses the default JDK, afaik there is no need to copy the jdk anyhow.

For the certificates: Not having a proper name resolution might indeed be a problem. At least you have to ensure that the hostname in the certificate matches exactly the server name (and that also has to be the name you use when you create the service connection within WM). the filename should not matter. I am not sure though, if all that even works with IP addresses only.

My recommendation: Give it a try with hostnames, configure the hosts files on the WM box and vCO if you don't have a DNS setup.

Cheers,

Joerg

0 Kudos