Servoy 2020 Documentation
Child pages
  • NGClient deployment

Versions Compared

Old Version 15

changes.mady.by.user Johan Compagner (wiki)

Saved on

compared with

New Version 16

changes.mady.by.user Andrei Costescu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

An NGClient is bound to a Tab in the browser, ; the session will not be shared over multiply multiple tabs as it is happens with the WebClient. It does use the http session on the server for better security and also support for load balancing servers.  But there can be multiply multiple NGClients for 1 http session.

By default browser sessions will not timeout while the brower tab is open, no matter what the value is of the the containerscontainer's/tomcat's session timeout , this is. This is because NGClient uses a WebSocket that is a persistent connection between server and client.  If you need to automatically log-out idle clients - that left their browser tab open, plugins can be created to do that via the Servoy plugin API.

Starting Servoy NG Clients (giving arguments or using a deeplink)

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

What is does

{serverURL}/servoy-ngclientOpens a page that lists all available ng-client solutions. It is available only if solution browsing is enabled; see Solution browsing.

{serverURL}/solutions/{mySolutionName}/index.html

Opens the specified solution

{serverURL}/solutions/{mySolutionName}/index.html?a={value}

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

{serverURL}/solutions/{mySolutionName}/index.html?a={value}&{name1}={value1}&{name2}={value2}

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

{serverURL}/solutions/{mySolutionName}/index.html?m={myMethodName}

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

{serverURL}/solutions/{mySolutionName}/index.html?m={myMethodName}&a={value}

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

Info

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.


{serverURL}/solutions/{mySolutionName}/index.html?m={myMethodName}&{name1}={value1}&{name2}={value2}

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


Note
titleParameters 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.

...