does not support the automatic upgrade of a MotionWorks Enterprise RFID Reader Management (1.0) instance to
Resonate
. Instead, it provides a Device Migration utility and an adoption mode for the
Resonate Device Initializer
utility, which together allow you to import your instance. Use Device Migrator to add site and reader information into
Resonate
; then, use
Resonate Device Initializer
to load
Resonate Agent
onto each reader and transfer control to it.
Device Migration Utility
The Device Migrator utility adds site and reader information into
Resonate
. The utility is a self-contained executable (
rm-device-migrator-<VERSION>.exe
) without an installer. It is distributed in the
resonate-<VERSION>.tar.gz
file that you received from Zebra.
The utility takes as input a standard XLSX spreadsheet file that lists all of your readers with the required information. The spreadsheet must have the column headers detailed in the Additional Information subsection of Device Migration Utility; there must be a record (row) for each reader with this information. If the reader's site exists in
Resonate
, just specify its site's name; otherwise, specify its site's name and full address. An example record is shown below.
Example Spreadsheet with the Minimum Required Columns for
Resonate
You can find the required reader information in the MotionWorks RFID Reader Management screens or in your external reader install records.
As the script runs, it works through the spreadsheet and adds that information into the
Resonate
instance databases. If it sees a new site, it adds it. If the site already exists but with a different address, it updates the site's address. It adds each reader to its specified site. The migration script automatically skips duplicate entries and entries with incorrect or misformatted information. During operation, the migration utility shows its status on the command line or PowerShell console, noting records (rows) skipped and showing total aggregated statistics at the end; it also includes the number of attempts made before reporting invalid or skipped. You can run Device Migrator again; it will skip existing migrated devices or sites. In general, the Device Migrator utility migrates all devices to build a database that is as complete as possible.
After it runs, you can see the list of (not fully) migrated readers on the
Infrastructure
Discovered Devices
page. You must then run the
Resonate Device Initializer
utility to adopt them into Resonate RFID Reader Management.
Resonate Device Initializer
Utility in Adoption Mode
When
Resonate Device Initializer
is run with
--no-ws
, it logs in to the
Resonate
instance to get the list of (not fully) migrated readers. Then, one by one, it loads
Resonate Agent
on each reader, taking over the reader's management connection. It disconnects its ZIoTC’s Control and Management interfaces, removing it from MotionWorks RFID Reader Management 1.0 if applicable. It securely connects each reader to
Resonate RFID Reader Management
, and turns over control to
Resonate Agent
.
Resonate Agent
automatically upgrades the reader's firmware if it is below
Resonate
's minimum required version.
When
Resonate Device Initializer
is run using
--metadata
with one or more site IDs, you can specify to adopt readers from a single site or a limited number of sites at a time. This is useful for adopting readers from one site, verifying that everything is working correctly, and then proceeding with additional sites. When run with
--metadata *
, the utility adopts all (non-fully) migrated readers.
What is Migrated and What is Not
If the readers were operational before being initialized, some of the reader configuration will survive the initialization process and remain in effect and operating on the reader(s)1:
Certificates already downloaded to the reader remain on the reader, but might need to be reassigned to the new
Resonate
-based connections.
When
Resonate Agent
starts, it reports the existing RFID read configuration on the reader to
Resonate RFID Reader Management
, establishing it as the reader's base configuration.
Some MotionWorks RFID Reader Management 1.0 information is not migrated with these utilities and must be entered manually:
Users: Add users manually to the
Resonate
web interface, using
Infrastructure
Users
Keycloak
.
Zones: Recreate any zones previously created in MotionWorks RFID Reader Management 1.0 (on Site Floorplans) in the
Resonate
web interface, using
Infrastructure
Site Manager
.
Floorplan images: Although the Device Migrator utility creates sites in
Resonate
to match those in the existing solution, it does not automatically import background floorplan images. You must upload and recalibrate these images for each site as needed.
Some MotionWorks RFID Reader Management 1.0 features are not yet supported in
Resonate
, so they are not migrated with these utilities, nor can they be added manually:
Customer and partner-provided on-reader device applications (DA) are currently not supported due to potential conflict with
Resonate Agent
.
User-specified background maps are currently not supported, so you cannot use your high-density or regional maps to incorporate detailed tile sets at this time. The web interface includes a low-density background world map.
1
All readers must use the same password, or they must all still use their factory-default password. You can change all reader passwords to match, or reset the readers to their factory-default state before running the utility. A reset removes a reader's configuration even before migration.
