using profile

Classic Servoy
1

Hi,

when I set the networksettings to :

SocketFactory.rmiServerFactory=com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory
SocketFactory.tunnelConnectionMode=socket

I can start smart client over my vpn connection using :
http://ibisapptst:8080/servoy-client/ibismain.jnlp

But I do not want the inhouse smartclients to use tunnel.
So I removed these settings and created a profile named vpnprofile containing :

system.property.SocketFactory.rmiServerFactory=com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory
system.property.SocketFactory.tunnelConnectionMode=socket

But when I start smarclient by using : “http://ibisapptst:8080/servoy-client/vpnprofile/ibismain.jnlp”
it starts without the tunnel.

I can even start with a non-existing profile like : “http://ibisapptst:8080/servoy-client/xxxxx/ibismain.jnlp”
and it wil still start (without tunnel)

What am I doing wrong ???

Regards,

2

You have to set globally:
SocketFactory.rmiServerFactory=com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory
SocketFactory.tunnelConnectionMode=http&socket

then in your vpnprofile profile, you only put:
SocketFactory.tunnelConnectionMode=socket

and you can also create a httpprofile profile with:
SocketFactory.tunnelConnectionMode=http

Now using:
http://ibisapptst:8080/servoy-client/vp … smain.jnlp
you should be using socket

And with:
http://ibisapptst:8080/servoy-client/ht … smain.jnlp
you should be using http

Any other http://ibisapptst:8080/servoy-client/xx … smain.jnlp
will start using the default.

3

Thanks for explaining Patrick,

But does’nt this mean that my inhouse clients and the clients connecting over vpn will both be using a tunnel ?

I wan’t the inhouse clients not the use the tunnel.

Maybe I am missing something ?

Regards,

4

Maybe I’m the one missing something! ;)

You could try creating a notunnel profile and put:
SocketFactory.rmiServerFactory=null
SocketFactory.tunnelConnectionMode=socket

or
SocketFactory.rmiServerFactory=
SocketFactory.tunnelConnectionMode=socket

then use:
http://ibisapptst:8080/servoy-client/no … smain.jnlp

Haven’t tested myself though, so please tell us if this works.

5

Noop, that does not work.

I also tried to leave network setting SocketFactory.rmiServerFactory empty.
and then set it in a profile, but that does not work !

Thanks Patrick, i’ll investigate further.

6

yes, let us know your findings!

7

Maybe one of the Servoyans can explain how to do this ?

some clients (inhouse) connecting without using a tunnel.

vpn (external) clients connecting using a tunnel.

Regards,

8

Hans, we do the same, and use 2 different urls for that.

customers can connect trough socket & tunnel by choice.

these are our settings:

[attachment=1]Schermafbeelding 2010-10-08 om 10.01.27.png[/attachment]

and make profile rule:
[attachment=0]Schermafbeelding 2010-10-08 om 10.02.59.png[/attachment]

now you have two Urls:

http://yourserverip:8080/servoy-client/mySolution.jnlp (this is socket)

and

http://yourserverip:8080/servoy-client/tunnel/mySolution.jnlp (this is tunnel)

vpn clients use the tunnel-link, and you give the internal users the socket link

works great here!

Schermafbeelding 2010-10-08 om 10.02.59.png
Schermafbeelding 2010-10-08 om 10.02.59.png919×481 68.5 KB

Schermafbeelding 2010-10-08 om 10.01.27.png

9

Works fine here to !!!
Thanks Harjo !!

B.t.w. what is sebster ??

@Paul Bakker : Maybe this can be included in the Wiki ??

10

Hans Nieuwenhuis:
B.t.w. what is sebster ??

it’s the shortname of Sebastiaan van Erk, the expert who has build this cool tunnel stuff! ;-)
Most people call him: Seb!

11

Some info:

You can’t set SocketFactory.rmiServerFactory in the profile
This is a serverside setting (and partly client side)

Only the client side can be pushed (what the client should be using sockets or http)

But in socket mode it is not really a tunnel (you don’t tunnel it over a specific protocol like http)
socket mode uses direct plain sockets and also connect to the port 1099 (if the rmi port is configured for that)
It is pretty much the same thing as 2 way, it only works differently and you have 1 other big plus: The java network connection setting (direct/proxy) don’t matter anymore…

I think in 6.0 “2 way socket” will be deprecated and by default we will have the socket factory configured in http&socket.
I will also then make all those settings way easier, and just have 1 combo there: “Http&Socket”,“Http”,“2 Way”