Introduction
MWE 2.0.5 is the latest release of the MWE 2.0.x series. It includes all the functionality of the MWE 2.0.0 - 2.0.4.1 releases in addition to new functionality and bug fixes.
The MWE 2.0.5 installation package is used to perform a fresh installation or to upgrade from the previous MWE 2.0.x release. If upgrading from MWE 1.4.x, the upgrade path is MWE 1.4.x > MWE 2.0.4.1 > 2.0.5. Refer to the MWE 2.0 Installation Guide for detailed installation and upgrade instructions.
See What is New for brief descriptions of the new functionality, and refer to the MWE 2.0.x release notes for details on the functionality included in previous releases.
? NOTE: MWE 2.0.5 includes a new version of the Camel interface (version 3.21.0). This new version requires a slightly different syntax in the Camel route files than the Camel version in previous MWE releases. If using Camel in an existing MWE deployment, DO NOT upgrade to 2.0.5 until Zebra Product Support reviews the existing Camel route files, as upgrading may break communication between Camel and external systems.
More details on the MWE 2.0 functionality can be found in the MWE 2.0 Installation Guide, the MWE 2.0 Configuration Guide, the MWE 2.0 User Guide, and the MWE 2.0 Device Manager User Guide.
What is New
This section describes the new functionality implemented in this release.
CLAS ATR Alerts
The Zebra CLAS software processes RFID tag blinks and calculates the x,y coordinates of the tags. A CLAS server forwards this information to an MWE server via a ZLA (Zebra Location Appliance), which subscribes to CLAS to pull the data. This has been supported in previous MWE releases. Starting with MWE 2.0.5, in addition to tag blink data, MWE also pulls from the CLAS server and displays ATR related alerts. See the System Alert Settings report in the MWE web client to review the ATR alerts that MWE reports.
New ZLA Software
ZLA software version 2.0.5-1 is included with MWE 2.0.5, and is required for supporting CLAS ATR alerts. Though not required by the ZLA 2.0.5-1 software, we recommend upgrading the nodejs version on the ZLA to the following:
| ZLA Operating System | Recommended nodejs Version |
|---|---|
| CentOS 7.9 | 17.9.0 or 17.9.1 |
| Red Hat 7.9 | 17.9.0 or 17.9.1 |
| Red Hat 8.x | 18.x.x |
| Ubuntu 22 | 18.x.x |
Refer to the MWE 2.0 Installation Guide (rev. 1.12 or higher) for instructions on installing or upgrading nodejs on the ZLA.
Pagination in History Reports
The previous MWE 2.0.4.1 release supports pagination for the Tags and Resources reports in the MWE web client; that is, report data is displayed on several pages with a maximum number of records per page configured by the user. MWE 2.0.5 adds pagination support for the following reports:
- Tags Blink History
- Call History
- Resource Zone Correlation History
? NOTE: A future MWE release will include pagination for the System Alert History and Resource Event History reports.
API Support for Historical Data
The API calls in previous MWE releases retrieve data related to the current state and configuration of the system. The MWE API in MWE 2.0.5 also supports calls to retrieve the same historical data displayed in the following reports:
- Tags Blink History
- Resource Event History
- System Alert History
- Call History
- Resource Zone Correlation History
New Blink Since Filter
The MWE web client Resources report includes a new Blink Since filter in the filter column. The default value is ALL, which displays all data regardless of the value in the Blink Timestamp column which indicates when the resources last blinked. This new filter allows specifying a particular date and time so the report displays only those resources that have blinked since.
? NOTE: The Blink Since filter has a dependency on the Location Snapshot Time filter in the same report. The Blink Since filter is enabled when Location Snapshot Time = Now, but is disabled when Location Snapshot Time = Custom. Refer to the MWE 2.0.4.1 release notes for an explanation of the Location Snapshot Time filter.
New First Blink Time Column
The MWE web client Tags report includes a new column for First Blink Time. This column displays for each tag the timestamp for the first blink received by MWE.
New Mobile Application Logs Report
A new companion MWE Mobile application runs on Zebra Android handheld devices and computers. An MWE Mobile application setting sends application logs to the MWE servers. The new Infrastructure > Mobile Application Logs report in the MWE web client displays an entry for every set of logs sent by the application. Clicking the link in the Download column in this report downloads the log set to the Windows machine running the browser.
Eliminated log4j 1.2.17 Vulnerability
The MWE services kelasticsvc and wso2 were discovered to have the log4j 1.2.17 vulnerability. log4j has been replaced with a different component to eliminate the vulnerability.
New Camel Version
A new Camel version (3.21.0) included in MWE 2.0.5 supports additional functionality, including support for the FIPS security protocol in the AWS cloud.
? NOTE: This new Camel version requires a slightly different syntax in the Camel route files than the Camel version in previous MWE releases. If using Camel in an existing MWE deployment, DO NOT upgrade to 2.0.5 until Zebra Product Support reviews the existing Camel route files, as upgrading may break communication between Camel and external systems.
Z-Lock Functionality
The MWE 2.0.5 release includes the Z-Lock functionality available in the Zebra legacy software VSS (Visibility Server Software). Useful in multi-story buildings where tag blinks can be detected by readers or sensors in the floors above and below, this feature places a Z-lock WherePort device at each floor entry point. When a tag is hit by the magnetic field of this device, the tag remains locked on that floor, even if the tag blinks are located by readers or WherePorts on other floors. A WherePort is configured as a Z-lock WherePort in the System Builder configuration tool. This is also referred to as the map-lock functionality as it can lock tags to specific maps regardless of whether the maps correspond to floors of a multi-story building. Refer to the MWE 2.0 Configuration Guide, rev. 1.06 or higher, for details.
New Technology Field in Tag Blink Messages
The Source field in MWE tag blink events was previously used for both tag product names and tag technologies. MWE 2.0.5 includes a new Technology field that specifes the tag technology, and can include the following values:
| Source (Zebra Product Name for tag) | Technology (Technology underlying the tag) |
|---|---|
| WhereNet | ISO24730, BLE, WherePort, GPS |
| Dart | UWB |
| MPACT | BLE |
| EPC | RFID |
| Unknown (if technology cannot be determined) |
The Source and Technology fields also appear in the MWE web client Tags report.
Bug Fixes
- The environment variable RESVC_AUTOASSOC_EPCTAG in /data/mwe/.env enables/disables automatic association of resource IDs to EPC tag IDs. The default value is false (disabled); setting the value to true enables this. MWE upgrade was resetting this variable to false. The installation/upgrade script has been modified so the existing value of this variable does not change during MWE upgrade.
- The Dashboard > Resources report in the MWE web client was displaying an incorrect number of unassigned tags. This issue has been corrected in MWE 2.0.5.
- In previous MWE 2.0.x releases, zooming into some maps in the MWE web client suddenly shifts the map, causing the coordinates of a point on the map to change, although usually only slightly. This issue has been fixed in 2.0.5.
- In MWE 2.0.4 and earlier 2.0.x releases, the MWE web client reports swapped Latitude and Longitude values. This issue existed only in the UI, not in MWE events or API calls. This issue has been corrected in MWE 2.0.5.
- In earlier releases of MWE, resource ID values in the GPS related columns (fields) were not cleared when associating the resource ID with a new tag ID. These values are now cleared in MWE 2.0.5.
Known Issues
In the Device Manager report > Edit Device page, if you select Operation Mode = Portal, you must provide values for the GPI Port and Signal fields before attempting to publish the configuration to the reader, otherwise the publish operation fails. The next MWE release will display a message and block the Publish operation until the required values are entered.
Requirements
Refer to the MWE 2.0 Installation Guide (rev. 1.12 or higher) for software and hardware requirements for installing MWE 2.0.5 software.
The MWE 2.0.5 installation package can be used to perform a fresh installation or to upgrade from previous MWE 2.0.x releases. If upgrading from MWE 1.4.x, the upgrade path is MWE 1.4.x > MWE 2.0.4.1 > MWE 2.0.5.
For MWE 2.0.5 deployments that require a ZLA, use ZLA software 2.0.5-1 or higher.
Firmware version 3.21.23 or higher is recommended for FX RFID readers added to MWE 2.0.5 via Device Manager. Verify the required upgrade path for FX RFID reader firmware in the firmware release notes (for example, 3.10.30 > 3.21.21 > 3.21.23). Consult with Zebra on the latest FX firmware to use with MWE 2.0.5.
Installation
Refer to the MWE 2.0 Installation Guide (rev. 1.12 or higher) and the MWE 2.0 Configuration Guide (rev. 1.06 or higher) for MWE installation and configuration instructions.
References
Other useful reference documents are as follows:
- MWE 2.0 Installation Guide, rev. 1.12 or higher
- MWE 2.0 Configuration Guide, rev. 1.06 or higher
- MWE 2.0 User Guide, rev. 1.02 or higher
- MWE 2.0 Device Manager User Guide, rev. 1.01 or higher
ZEBRA and the stylized Zebra head are trademarks of Zebra Technologies Corp., registered in many jurisdictions worldwide. All other trademarks are the property of their respective owners. © 2024 Zebra Technologies Corp. and/or its affiliates. All rights reserved. | zebra.com
P1128233-03EN Rev A
Zebra Technologies | Visible. Connected. Optimized. | Zebra
