Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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.

In This Chapter

 

War deployment

War deployment is the only option for an NGClient, because a lot more resources are needed then just the solution.

In the export dialog you have get the option to select the webcomponents and services that you want to include in the generated WAR file. All the components and services you use in your solution (directly in the designer or solutionmodel/scripting) should be checked and exported.

For more info about war deployment: WAR Deployment

Supported Browsers

NGClient needs HTML5, CSS3 and WebSocket support so it will run on any browser that supports these. Some supported browsers are:

  • Internet Explorer 10 and beyond
  • Firefox 11 and beyond
  • Chrome 16 and beyond
  • Safari 7 and beyond
  • Opera 12 and beyond

 

Basic Authentication Support for Login

If a solution running in NGClient does not define a specific form as login form and doesn't have a login solution, Servoy will serve a standard SignIn page to the user (a basic html page with a username and password field).

Instead of showing the default SignIn HTML page, it's also possible to show the default browser basic authentication dialog, using one of the two following approaches:

  1. Append '?sv_auth_type=basic' to the NGClient URL. For example:  {serverURL}/solutions/{mySolutionName}/index.html?sv_auth_type=basic
  2. Or enable it for all NGClients (or in the developer for testing purposes) by setting the admin page property servoy.ngclient.basic.authentication to true
  • No labels