How to configure Niagara Web Start Java AX 3.8.111

Following the gradual abandonment of Java plugins in almost all internet browsers, Tridium has finally adapted its 3.8 platform to use Java WebStart

Java web Start is an external application that does not use the browser, which makes it easy to connect to the control system without using a plugin.

NOTE

If you have a Supervisor server

In order to use the web start, you must have previously installed the Niagara AX 3.8.111 version in your supervisor or controller

You must also have JAVA installed in your PC ( http://www.java.com/en/ )

For more information, please consult Integra Controles

Prerequisites

You must make sure that JAVA is installed on your PC before

The java is available for free here https://www.java.com/en/download/windows_xpi.jsp

Disregard any incompatibility warnings as Java will not be used with the browser.

Following the installation of JAVA, pass the the next step

To use Java Web Start

Open your browser 

In the address bar of your browser type the address of your Jace

At login, Click on "Click here"  , at the bottom of "To connect using java web start" 

When the file is downloaded to the desktop, close the browser.

Click on the new icon "JACE NAME.jnlp"  (saved on  the desktop or downloads)

The first time click on "do not show this again ..." and press "Run"

From now on you will no longer use an internet browser.

Click on the icon " name of your .jnlp system " and enter your user and password the Web Start interface is similar to that of a browser, but it does not require any plugin

Chrome says it no longer supports the Niagara ax wbapplet plug-in

Upon a log-in attempt via chrome, wbapplet does not start and the browser states "This plug-in is not supported."

There are changes Java compatibility in Chrome:

NPAPI support by Chrome

The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has long been, and currently is, supported by all major web browsers. Google announced in September 2013 plans to remove NPAPI support from Chrome by "the end of 2014", thus effectively dropping support for Silverlight, Java, Facebook Video and other similar NPAPI based plugins. Recently, Google has revised their plans and now state that they plan to completely remove NPAPI by late 2015. As it is unclear if these dates will be further extended or not, we strongly recommend Java users consider alternatives to Chrome as soon as possible. Instead, we recommend Firefox, Internet Explorer and Safari as longer-term options. As of April 2015, starting with Chrome Version 42, Google has added an additional step to configuring NPAPI based plugins like Java to run — see the section Enabling NPAPI in Chrome Version 42 and later below.

Enabling NPAPI in Chrome Version 42 and later
As of Chrome Version 42, an additional configuration step is required to continue using NPAPI plugins.

1. In your URL bar, enter:  chrome://flags/#enable-npapi 
2. Click the Enable link for the Enable NPAPI configuration option.
3. Click the Relaunch button that now appears at the bottom of the configuration page.