Configuring leostream to access virtual centre

[tekhie]

HI, i have downloaded the Leostream connection broker appliance and configured it so that it can be managed via my web browser. But when i try to add my Virtual Centre to it it cannon connect on port 443. Does an local configuration need to be performed on the server hosting the VC database ? I know it uses apache - does anyhring need to be changed here ? Thanks

[mreferre]

I had mine setup a few months ago and I don't remember doing something on the VC server itself.

Mine is a VC 2.0 server running in "legacy mode" and my connection string is as follow:

https://192.168.77.100/sdk

If you are running VC 1.x than you should put :8443 instead of /sdk.

Page 25 / 26 of the manual detail this.

Hope it helps.

Massimo.

[tekhie]

hi massimo - thanks for that - are you able to telnet to your VC server using 443 ? I am unable to do so so am wondering if there is some kind of security set up on the server. I get an error stating connection refused if i try to telnet from a windows server onto my VC server running VC2.0.1.

[mreferre]

I can't connect either with telenet on 443 but I wouldn't rely on telnet to test it.

Try this instead from any Windows pc/server :

https://VCaddress/mob/?moid=ServiceInstance&doPath=content%2eabout

I can login in from in the web session above.

Massimo.

[tekhie]

hi massimo - fix as follows ...

uninstalled VC Server

Uninstalled IIS

Restarted server

Reinstalled VC Server keeping all defaults

Fired up connection broker - straight in with connectivity to the virtual centre!!

It would appear if IIS is running when you install VirtualCentre Server it does not install itself correctly. When you come to use an app that uses the web service api it will not work !! Hope this has been helpful for you

[mreferre]

That's interesting ... I have never installed VC on a IIS enabled server so I can't tell.

Good to know.

Massimo.

[davlloyd]

That's interesting ... I have never installed VC on a

IIS enabled server so I can't tell.

Good to know.

Massimo.

The gotcha is the port mapping, as the Tomcat Web service installed with VC puts redirections on the port 80 root address it will conflict with a default installation of IIS. Easy way around it is to assign IIS to an alternate port and there is no co-existance issues.

[TomHowarth]

VC uses Tomcat an apache derivitive to do its Web bits and peices, this cannot eaisly co-exist with IIS. it is a recommendation that IIS is not installed on the server that you are going to be installing VC on

[rickyelqasem]

The key thing here is "legacy mode" its what catches most people out...>>>have you edited the registry and placed VC2 in legacy mode as discribed in the leostream manual.

[CMCC]

I can't connect either with telenet on 443 but I

wouldn't rely on telnet to test it.

Try this instead from any Windows pc/server :

https://VCaddress/mob/?moid=ServiceInstance&doPath=con

tent%2eabout

I can login in from in the web session above.

Massimo.

I can't get into tgat link... instead of VCadress I must put my VC ip right? nothing happens!

[davlloyd]

Leostream supports both VC 1.x and 2.x as of the last few revisions. Ensure that you select the correct version when creating your VC connection object and then state the URL correctly.

VC 1.x https:///sdk

Port is only required if you configure away from the standard 443