Page History

The bootstrapper (bootstrap.jar in application_server\server\web-app\root) can be used in 2 ways:

1> with a bootstrap.jnlp (and starting it up through webstart)

2> as a standalone launcher, by downloading the jar and double click (java -jar boostrap.jar), supported with Servoy 8.3.2+

in both ways, you can rename the jar (or jnlp file) to what ever you want like "yoursolution.jar/jnlp" and have multiply copies of it for specific clients (like tenants)

With this new release (8.3.2) the bootstrapper has support for native libs  or native resources. The correct resources should be downloaded and native libs are added to the system path so that they can be used with System.loadLibrary(name)

Through webstart:

To speed up (especially under windows) the smart clients startup, you can use a special bootstrapperbootstrap.jar 

From Servoy 8.1.0 ang higher you can find the bootstrapper.jar in the SERVOY_INSTALL/application_server/webapps/root directory.

...

bootstrap.jar and bootstrap.jnlp are found in the ROOT of the context
So that is in a default servoy installation: \application_server\server\webapps\ROOT
in a war file it should be in the root of the war file

Then you can access it through:

http://hostname:port/bootstrap.jnlp

(and the above code base should be then http://hostname:port)

Standalone starter: (since 8.3.2)

With the stand alone starter the customer doesn't download the bootstrap.jnlp file but the boostrap.jar file itself.

the configuration that you normally would do in the bootstrap.jnlp must then be done by editing the bootstrap.properties file that sits in the root of the bootstrap.jar.

by default some examples are given:

codebase=http://localhost:8080/test/
solution=test
bootstrapthreadpoolsize=8
arg0=system.property.MyKey=MyValue
arg1=argument:owner:1
arg2=owners:2
#jnlp.bootstrapper.home.dir=

codebase: is the same as the code base property in the jnlp file above. This must be the application servers url to the root of the servoy application.

solution: the solution name to load

bootstrapthreadpoolsize: Same as above, the number of threads handling the download

jnlp.bootstrapper.home.dir: The dir where the downloaded files should go into (standard is this {user.home}\.servoy\libCache)

Arguments can be given with sequence numbers argX=

Where system properties can be set like system.property.MyKey=Value

What is currently not supported in this way is system properties or vm arguments that needed to be set before starting java. (like max memory)

Because the starter is started with plain java -jar and doesn't currently relaunch itself.

If you  change the properties file then the signing will be broken, the signing must then be removed (META-INF\*.RSA and *.SF) or better resigned with your own certificate.