cannot find data service

[alb]

Ok
I am running servoy 5.01 on windows 2003 + SQL2005. Web client runs perfectly. I have tunneling enabled. I can ONLY use standard ports - eg 80 and 443 due to restrictions elsehwre in the network. In addition, the servoy server share an IP with IIS - there is oly one IP.
Web client runs fine on: https://server.com/servoy-webclient
can connect, browse data etc etc.
Note: The 443 (SSL) port is managed by IIS and is running the TomCat redirector ISAPIFilter to redirect servoy URLs to tomcat and let the rest pass through the IIS (so that the existing OWA solution will continue to run). Tomcat filter processes:

/servoy*=worker1
/images*=worker1
/lib*=worker1
/beans*=worker1
/lafs*=worker1
/plugins*=worker1

This ensures webclient runs just fine.
However smart client runs into problems. IF I start the client using the URL
https://server.com:8443/servoy-client/s ... lient.jnlp from INSIDE the firewall then it all works fine. BUT if I use the URL https://server.com/servoy-client/servoy-client.jnlp the client starts but fails with 'Cannot find dataservice, it may not be running on server'. This isnt much of a solution as port 8443 WONT pass through corporate firewalls.

what might be casuing the data connection to fail?
I have tried different values for java.rmi.server.hostname but it makes no difference.

I *think* I have http tunneling running - but how would I know?

Questions:
a) Does the web client use http tunneling? - if it does then tunneling is working
b) what should the value of java.rmi.server.hostname be? Should it be the EXTERNAL dns/IP of the server? If it is what port does the smart client try to connect on?

I thought that if tunneling was used then both ALL the traffic ame in on the web (80/443) ports and nothing came in on 1099. Is this correct? How can I tell whether tunneling is working?

Any other ideas?

Al

[alb]

Fixed it!
worked out that there is an *extra* URL redirection required to get the tunnel to work for the Smart client.
I needed to edit the uriworkmap.properties file for the isapi_redirect.dll to that the \tunnel URI would be redirected to tomcat:

#
# Sites to be redirected to Tomcat
#
# redirect servoy URI to tomcat worker
/servoy*=worker1
/images*=worker1
/lib*=worker1
/beans*=worker1
/lafs*=worker1
/plugins*=worker1
/tunnel*=worker1

after doing this the Smart cleint can find the data source and all works just fine on port 443. Great
Weird thing is that the web slient didnt need this redirection (\tunnel) so it obviously doesn come into the data service in the same way?

So now I have IIS (windows 2003 server):

Standard OWA running on https://server.com/exchange
servoy webclient on https://server.com/servoy-webclient
servoy smart client on https://server.com/servoy-client/servoy-client.jnlp

all running on the same IP!
neat.

Al.