Honeywell WEBs-N4 Software Release Bulletin

1 Release Summary

The Honeywell WEBs-N4.10.0.154 release includes WEBs-N4 software builds, WEBs-N4 Alarm Portal, and WEBS Enterprise Security N4.10.0.154.

1.1 Enhancements in Honeywell WEBs-N4.10.0.154 Workbench

• System Database Support for Tag Based PX: WEBStation-N4.6 introduced System Database which dramatically decreases the amount of time to integrate remote Niagara Network stations into a Supervisor. Tag-based PX binding was introduced in WEBStation-N4.9 enabling users to develop graphics once, and then re-use them across stations. WEBStation-N4.10 integrates these two powerful solutions together to reduce the amount of time spent engineering your enterprise sites and to give you more time to spend providing value to the customer.
• Improved Graphics Performance on the JACE: Utilize new UxMedia type to achieve faster graphics load time and enable instantaneous feedback on changing values. WEBStation-N4.10 will help convert existing PX graphics to a contemporary UI based on browser standards via a built-in migration tool.
• Video Surveillance Viewer: WEBStation-N4.9 brought improvements to video processing capabilities (alarming, HTML5 views, streaming live and recorded video in browsers or mobile). In WEBStation-N4.10, the functionality is enhanced by updating the Surveillance Viewer to enable setting up and saving video layouts and clicking on any video stream to view a single camera.
• HTML-5 Tag Manager: New HTML-5 Tag Manager provides a modern and intuitive design for a more efficient tagging workflow. Features include bulk tagging via a browser, context-sensitive tagging, seamless viewing of direct and implied tags, exporting all tags to a spreadsheet for templating and ongoing management, and drag-n-drop functionality.
• Bulk Certificate Signing Tool: New Workbench tool that improves certificate signing experience. Sign one or multiple certificates in bulk with the same Certificate Authority (CA) and generate signed certificates in PKCS7 format for compatibility with browsers.
• MQTT Updates: A new MQTT Authenticator enabling JWT authentication (Google) enables seamless connectivity for Google-Cloud based applications.
• Supervisor Edge Licensing Scheme for Niagara Network Connections: A new licensing schema allows connecting 10 times more devices using the Niagara stack to a Supervisor for the same price.
• Announcing WEBs-N4.10.0.154.7 Enterprise Security: The WEBs-N4.10.0.154 Enterprise Security brings updated cyber security and visualization enhancements included in the WEBs-N4.10 framework release to customers. Version upgrades are available for purchase with a software maintenance agreement, or an active software maintenance agreement.
• PhotoID viewer has been updated to use HTML5 in the browser UI for visual verification of badge photos against live video, adding an extra level of security for sensitive or high-security areas.

1.2 Supporting Tools

The following are the tools supporting the Honeywell WEBs-N4.10.0.154 release:

The WEBs-N4 Software can be downloaded from Honeywell Buildings Forum. A license is required to use this software, which can be obtained from your distributor.

1.3 WEBs-N4.10.0.154 Software Modules

2 Hardware Compatibility – WEBs Controller

WEBs-N4.10 release software supports WEB-8000, CIPer Model 10, CIPer Model 30, CIPer Model 50, Stryker, Spyder, and Spyder Model 5 controllers.

2.1 Platform Requirements for WEBs Supervisor

IMPORTANT NOTE
WEBs-N4.10 supports only 64-bit installations. Installing WEBs-N4.10 would generate a new host ID, if you installed a 32-bit in the previous WEBs-N4.8 versions.

It is recommended to use the Echelon OpenLDV 5 Network Driver for Windows. For details refer to, https://www.echelon.com/software-downloads?ele=153-0411-01B.

2.2 Software Dependencies

WEBs-N4 system's software includes operating systems, browsers, relational databases, and video drivers. Some software modules run on the controller and others on the Supervisor PC.

3 Niagara Web Launcher

IMPORTANT: As Java SE 8 reached end-of-life, free public updates for commercial users are no longer available. Users who use Java Web Start to access WEBs JACE controller or localhost remotely for their legacy systems, need to use the Niagara Web Launcher application now.

3.1 How to install and use the Niagara Web Launcher

1. Connect the JACE or localhost via browser.
2. Pre-login page appears and provides a link under the login dialog that reads: "To connect using Niagara Web Launcher click here".
3. Click this link to download and auto-run The NiagaraWebLauncher.msi installer file. If the file download does not begin automatically, click the following link: For 64-bit systems.
4. Once the installer file NiagaraWebLauncher.msi is downloaded, it installs the Niagara Web Launcher application on your computer. If the installation does not begin automatically, access the NiagaraWebLauncher.msi file in your browser's downloads location and double-click the file to run the setup wizard.
5. Once the application has started, you may close this browser window and log in from the Niagara Web Launcher application. You may notice another file, <stationName>.nwl is downloaded to the same location. This is a text file containing information that tells Web Launcher how to connect to that particular station. On subsequent connections, there is no need to download and run the *.msi installer file again. Instead, you could double-click the *.nwl file which launches web Launcher.exe.

Tip: If a user wants to run station discovery under Niagara network of N4.10 supervisor, the user will need to add udp 1911 inbound to the firewall of their system.

For more details, refer to Discover (Fox) uses UDP multicasting in Niagara Drivers Guide, or follow the Niagara Help content link - local:|module://docDrivers/doc/aStationDiscoverUdpMulticastPorts.html#aStationDiscoverUdpMulticastPorts

3.2 Using Web Launcher with WEBStation N4.10

Web Launcher 20.4.2 was recently revamped for WEBStation-N4.10 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 275 and certificate management has been updated to work with WEBs-N4.10 along with any legacy or prospective release. Prior to using Web Launcher with WEBs-N4.10, customer should update Web Launcher accordingly (see steps below).

How to update Web Launcher?

Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version.

3.3 Upgrading WEB-8000 controller

This WEBs-N4.10 software allows you to install distribution (dist) files from your Workbench PC to the remote host platform.

NOTE
WEBStation-N4.10 requires all modules to be signed with a valid certificate. If you are using third-party modules, ensure that they are signed with a valid certificate using Niagara's Jar Signing Tool. For more details on the Niagara Third-Party Module Signing procedure, refer to the Niagara Third-Party Module Signing link or below Niagara internal help links (ORDs).

• Signing A Third Party Module: module://docModuleSign/doc/CreateCodeSigningCertificate-28E327C0.html
• Staged roll-out: module://docModuleSign/doc/StagedRoll-outModuleSigning-182E7CCO.html
• Verification modes: module://docModuleSign/doc/VerificationModesModuleSigning-182D0E86.html

If you attempt to upgrade an existing WEB-8000 controller with an unsigned module, the station will not start.

Steps To Upgrade WEB-8000 controller

1. Connect to the WEB-8000 Platform.
2. Log in to the Platform of the WEB-8000 using the WEBStation-N4- N4.10.0.154 workbench.
3. Run the Platform Administration from platform view and Select Commissioning Wizard.
4. Uncheck all default checkboxes, except “Install/Upgrade core software from distribution files” and click Next.
5. Select the licensing options and click Next.
6. Select the runtime profile and click Next. All WEBStation 4 platforms require the base “RUNTIME” (-rt) module JARs, so it is pre-selected/read-only. For QNX-based JACE platforms (which run the “Java 8 compact 3” VM), you can also select “UX” (-ux) and “WB” (-wb) module JARs, but not “SE” (-se) module JARs.
   NOTE
   During WEB-8000 commissioning, on Enabled Runtime Profiles screen, select “UX” and “WB” checkboxes if not already checked by default. These boxes may not be checked by default in the case of a new WEB-8000 controller or immediately after a “cleandist” has been performed.
7. If you have a specific station database ready to install in the WEB-8000 controller, you can specify it at this step in the wizard. Or, simply accept the default “(Don't transfer a station)” and click Next. You can create a station later using the New Station Wizard, and install it using the platform's Station Copier. Or you can simply select an existing station to install using the Station Copier.
8. Click Next to continue.
9. NOTE
   Do not click the Upgrade All Out of Date during the Install/Upgrade core modules step.
10. NOTE
    When upgrading a WEB-8000 from an installed older release to WEBStation-N4.8 the persistent log files under /var/slog will not be preserved. The reason is that WEBs-N4.10 contains an OS upgrade from QNX6.5 to QNX7.0 which uses a different log file format. During the upgrade, the old QNX6.5 log files are deleted and new QNX7.0 files are created. If the existing log files are needed, make a copy prior to upgrading.
11. Click Next to continue.
12. Configure TCP/IP settings and Click Next.
13. Configuring system passphrase and click Next. A strong password is required (a minimum of 10 characters and include at least one uppercase character, at least one lowercase character, and at least one digit).
14. Review the changes in Commissioning Wizard and click Finish. Wait for several minutes to complete the controller upgrade. After the upgrade is complete you will be able to log in to the platform of the controller.

3.4 Verify Upgrade

After upgrading the WEB-8000 controller, verify the firmware and software tool version. Log in to the Platform of the controller and then go to Platform Administration, and verify the updated versions installed. Refer to the below image, highlighting installed versions on the controller.

Platform Administration

3.5 Restoring WEB-8000 controller

The WEB-8000 controller can be restored to WEBs-N4.9U1 or WEBs-N4.1 version with two different Clean Dist files.

Choose one of the following "CleanDist" files to delete and restore settings on the CIPer Model 50 controller.

NOTE

• Back up any station files as well as any other files needed later, for example, digital certificate keys.
• Always export certificate keys for any TLS-configured unit (and store the exported keys in a safe place), such that if the controller needed to be replaced (hardware swap-out), you could re-import those keys.

Before performing the WEB-8000 controller restoring process, make sure to copy the clean dist files (tridium-qnx7-n49u1-titan-am335x-clean.dist and tridium-qnx65-n41-titan-am335x-clean.dist) in the C:\Honeywell\WEBStation-N4-4.x.x.xxx\cleanDist folder.

Steps to restore WEB-8000 Controller:

1. Connect and enter login details of the WEB-8000 platform.
   NOTE
   Users must keep a record of login credential details for the WEB-8000 platform.
2. Select Distribution File Installer.
3. Select the file tridium-qnx65-n41-titan-am335x-clean.dist from the list and click the Install.
4. Removing a file system takes a few minutes, then the controller automatically reboots. Wait for the reboot to complete.
   NOTE
   After reboot from a clean dist install, the controller requires port (3011). The default platform passphrase will be active after reboot, enter default login/login credentials for the platform. After entering logging credentials Licenses and Certificates and TCP IP Address Settings will retain.
   This action will delete all the modules, station and station data will be erased. Now the Firmware is retained.
5. Click Close after completing the installation.

4 Known Issues & Workarounds