Problem starting Web Client

[johnh]

Hi all

First post for me and looking forward to the world of Servoy.

But I cannot get a solution to run in the web client.
The web browser opens up ok and displays "http://localhost:8080/servoy-webclient/solutions/solution/servoy_sample_crm"
and responds with "The webpage cannot be found"

Running on Windows XP with IIS5 installed.
Just testing the IIS service, I can get a response with "http://localhost/" which defaults to "http://localhost/localstart.asp" and that tells me the default directory is c:\inetpub\wwwroot\

The Smart Clent runs and behaves nicely

Have installed v6.0.4 several time (uninstalled previous version)

So the questions become :-

Do I need to have IIS running at all in the Servoy Developer ?
Do I need to configure IIS ?
Do I need to configure Servoy ?
Have I completely missed the point conceptually ?

TIA
John

[Harjo]

Hi John, welcome to the forum!


Servoy ships with his own Tomcat server, so no need for ISS to be installed.
(better to shut it off, IMHO) and default Servoy Tomcat port is :8080

SO:

Do I need to have IIS running at all in the Servoy Developer ? No
Do I need to configure IIS ? No
Do I need to configure Servoy ? No
Have I completely missed the point conceptually ? I don't know, you can learn always

[johnh]

Lots of thanks !

Problem was enviroment specific- but in case others may be down this track at some time.

Discovered using "netstat -ano" windows command that port 8080 was being used by SQL 2008 Reporting services.

By good luck, assistance was given to similar post viewtopic.php?f=11&t=17467
where Gordon suggested a a change to the Tomcat port.

and that referenced Doc was
http://wiki.servoy.com/display/public/D ... d+settings

So from there,

The HTTP port, used to expose many of the services of the Servoy Application Server can be configured by editing the server.xml file located in ../application_server/server/conf. This file contains the following entry by default
<Connector
port="8080"
protocol="HTTP/1.1"
maxThreads="500"
connectionTimeout="60000"
redirectPort="8443"
useBodyEncodingForURI="true"
/>
:

and changeing to port 8085 did the trick