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

How can you tell if Niagara Ax JACE is overloaded?

When using Workbench, right-click on the connected station in the nav sidebar and select View -> Resource Manager.

• The CPU usage should be less than 80% on a continuous basis.
• The heap.used should be less than 75% of the heap.max value. Execute garbage collection before evaluating the heap.max value by right-clicking on the connected station in the nav sidebar and selecting Spy -> util -> gc.

• For a SoftJACE ensure that the resource.total is less than the licensed resource limit. SoftJACEs are licensed for either a 10,000 KRU or 30,000 KRU limit. If actual station resources exceed 110% of the licensed limit for a SoftJACE, the station will fail to start.

If running AX 3.1 or later, when using Workbench right-click on the connected station in the nav sidebar and select 'Spy'. On the Remote Spy page select 'platform diagnostics' and then 'fd usage'. This displays a list of processes and the number of open file descriptors for each.

QNX-based JACE controllers are limited to 1000 open file descriptors. File descriptors include but are not limited to directories, files, histories, and socket connections. If the number of open file descriptors exceeds the limit, the station will behave erratically such as misreporting available file space, missing history collections, etc. A maximum of 800 histories per station is recommended to avoid exhausting the pool of available file descriptors.

What can the second Ethernet port on the Niagara Ax JACE-2 and JACE-6 be used for?

Currently the only drivers that can be configured to use the second Ethernet port are Bacnet, ModbusTCP and EibIp.

The JACE does not act as an Ethernet router or switch, meaning it does not allow TCP/IP traffic to pass from one port to the other.

The second Ethernet port can be used to isolate a BACnet Ethernet or IP network from the primary LAN. All BACnet devices would be connected on the network segment that was connected to the secondary Ethernet port on the JACE. BACnet points that are proxied in the station could then

be viewed or commanded through graphics that are served up by the webService via the primary

Ethernet port.

The Niagara Network and the webService will be available on both network interfaces. With BACnet, you select which network interface to use on the link settings of the IP-port and/or Ethernet-port object under the BACnet network. With Modbus TCP the IP layer decides which network interface to use based on the IP address assigned to the Modbus TCP Device Object.

The second port must be on a different subnet. The second subnet cannot also have a default gateway - so you will be limited to one subnet on the second network interface.