NGClient deployment


NGClient is one of the ways to deploy Solutions to end users.

NGClient is a browser-based application of which the UI is rendered in the browser using pure HTML, CSS and a bit of JavaScript for event handling and communication with the Servoy Application Server (HTML5, CSS3 and websockets communication is used). The business logic of the Solution that is running in the NGClient is executed on the Application Server for security reasons: the code of the business logic is not exposed in the webpage markup.

Servoy NGClients run in a browser and can be started by accessing a URL on the Servoy Application Server, which are plain start urls with the solution name in it (with or without arguments for the onsolution open) or direct deeplinks for calling directly a method with arguments.

NG Client Start URL:


Opens a page that lists all available ng-client solutions. It is available only if solution browsing is enabled; see Solution browsing.


Opens the specified solution.


Opens the specified solution. The argument value is passed into the Solutions onOpen event handler.


The same as the previous scenario, but with additional custom keys for additional arguments.


Opens the specified solution and executed the specified method after the solution is opened.


The same as the previous scenario, but specifying a single value to be passed as an argument into the onOpen event handler and deeplink method.

Please note that if the solution is not loaded, the onSolutionOpen method is called before the deeplink method and only the deeplink method gets the arguments.


The same as the previous scenario, but with custom keys for additional arguments.

Parameters encoding In order to make sure UTF-8 encoding is used for url parameters, you must look for value of URIEncoding setting from Tomcat connector. Beware that if useBodyEncodingForURI setting is used as well, it will have higher priority for used encoding. See Tomcat documentation for more details.

Starting with Servoy version 8.3, if 'index.html' is missing from the URL, it will be automatically appended and a redirect to the new URL will take place. Ex. {serverURL}/solutions/{mySolutionName} will redirect to {serverURL}/solutions/{mySolutionName}/index.html and {serverURL}/solutions/{mySolutionName}?a={value} will redirect to {serverURL}/solutions/{mySolutionName}/index.html?a={value}.

Last updated