Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Profiles provide the option to differentiate settings used by Smart Clients.

This functionality can be use to deal with Smart Clients connecting to the server from behind different types of firewalls and/or proxies, which would require different settings.

Each profile has a name and by adding the name of the profile to the URL that is used to launch the Smart Client, settings provided in the Profile overrule the default settings and/or settings provided in the URL itself.

Code Block
titleDeeplink into specific solution using a named Profile

The profile part of the URL is only relevant for the launch of the Smart Client. When deeplinking into running Smart Clients the profile can be omitted from the deeplink URL. For more info on all possible options for Smart Clients URL's, see Starting Smart Clients

A profile can contain one or more settings. There are two basic types of settings:

  1. Deeplink settings
  2. Configuration settings

Deeplink settings
Through profiles it's possible to specify startup arguments and/or a deeplink method, by adding one of the following properties:

  • solution={solutionName}
  • method={globalMethodName}
  • argument={someValue}
  • {someParam}={someValue}

For the solution, method and argument settings, it's also possible to use the short syntax (resp. s, m and a).

Configuration settings
Configuration properties are properties that start with "". Any property that starts with this will be send to the launched Smart Client. This can be either standard Java system properties or Servoy specific system properties, including Tunnel configuration properties.

Java system properties
Any system property that Java has can be added to the Profile. Whether or not the property has any relevancy depends on the property. 

Servoy configuration properties
There are two Servoy specific system properties that can be used within a Profile: 

  • include and set to true for Kerebos support
  • specifies the tunnel connection mode, either "http" or "socket".
    For this setting to have effect, the SocketFactory.tunnelConnectionMode setting under Network Settings on the Admin page needs to be set to "http&socket"

Tunnel configuration properties
The Tunnel has an extensive set of configuration options to allow optimal operation for any combination of firewalls and proxies. More information on the configuration options for the tunnel can be found here.