Information in this document is subject to change without notice. The software described in this document
is furnished under a license agreement or nondisclosure agreement. The software may be used or copied
only in accordance with the terms of those agreements.
For further information regarding legal and proprietary statements, please go to:
SOFTWARE:zebra.com/linkoslegal
COPYRIGHTS:zebra.com/copyright
WARRANTY:zebra.com/warranty
END USER LICENSE AGREEMENT: zebra.com/eula
Terms of Use
Proprietary Statement
This manual contains proprietary information of Zebra Technologies Corporation and its subsidiaries
(“Zebra Technologies”). It is intended solely for the information and use of parties operating and
maintaining the equipment described herein. Such proprietary information may not be used, reproduced,
or disclosed to any other parties for any other purpose without the express, written permission of Zebra
Technologies.
Product Improvements
Continuous improvement of products is a policy of Zebra Technologies. All specifications and designs are
subject to change without notice.
Liability Disclaimer
Zebra Technologies takes steps to ensure that its published Engineering specifications and manuals are
correct; however, errors do occur. Zebra Technologies reserves the right to correct any such errors and
disclaims liability resulting therefrom.
Limitation of Liability
In no event shall Zebra Technologies or anyone else involved in the creation, production, or delivery of the
accompanying product (including hardware and software) be liable for any damages whatsoever
(including, without limitation, consequential damages including loss of business profits, business
interruption, or loss of business information) arising out of the use of, the results of use of, or inability to
use such product, even if Zebra Technologies has been advised of the possibility of such damages. Some
jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above
limitation or exclusion may not apply to you.
Appendix: BLE Receiver Configuration ......................................................................................... 63
3
MWE Configuration Guide
This document provides instructions for configuring the MotionWorks Enterprise (MWE) 2.0.n software
from Zebra Technologies Corporation after it has been installed. The ‘n’ in the version number indicates
the latest 2.0 release. For installation instructions and server requirements, please see the separate
document MWE 2.0 Installation Guide.
When configuring MWE, it is helpful to understand its basic architecture and the relations between its
software modules. The simplified diagram below illustrates the main MWE software components hosted by
the MWE server and some of the external clients and consumers.
4
MWE Configuration Guide
An MWE deployment may or may not require a ZLA, which is a CentOS appliance that captures data from
different types of sensors, puts the data in a standard format, and forwards it to the MWE server. For
example, MWE 2.0 supports deployment of passive RFID readers without a ZLA, sending data directly to
the MWE server. Also, you could have a location sensor or third-party application feeding data to MWE via
the MWE API. However, most type of sensors supported by MWE 2.0 do require a ZLA.
Please note that the screenshots and figures included in this document may vary slightly from the MWE
2.0.n version that you have installed, where n identifies different version or releases of the MWE 2.0
release.
5
Launching the Web Client
Once MWE has been installed, most configuration tasks can be done using the MWE web client, along
with the System Builder discussed later in this document. To launch the client, open a web browser
(Chrome, Firefox, Edge, ….) on a client machine or server on the network, and point it to
http://MWE_Server_Name, where MWE_Server_Name is the MWE Linux server name or IP address. The
login page will be displayed:
MWE Configuration Guide
Default login credentials are Username =
See Changing the Administrator Password on page 7 for information regarding how to change the default
password.
Observe the landing page and the main menu bar at the top of the page. The menu items are: Dashboard,
Reports, History, Alerts, Infrastructure, Configuration, Users, admin (the name of the account currently
logged in).
The default admin / admin account has access to all items in the main menu bar.
The following sections describe a sequence of typical steps in configuring the MWE software.
admin and Password = admin.
6
MWE Configuration Guide
Changing the Administrator Password
MWE includes a default administrator account with access to all menu items, pages and functionality
available in the web client:
•Username:
•Password:admin
To change the admin password, login using the admin account and select Change Password from the
admin tab:
admin
Enter the current password and the new password, and click Save.
Sign out by selecting admin > Sign Out from the main menu bar.
7
MWE Configuration Guide
Adding site groups, sites, and site maps
One of the core functionalities of MWE is processing and displaying asset location data from multiple sites
across a city, country, or the world. This section explains how to add sites, site groups, and site maps to
the system.
Adding Site Groups
Open the Infrastructure > Site Manager page:
If you are using the default installation world map (refer to the MWE 2.0 Installation Guide) observe a world
map with few country names in the Site Manager window. The map in the figure above corresponds to a
more detailed map (north-america_us.mbtiles) installed at installation time.
8
MWE Configuration Guide
For example, if your company has two sites in the city of Los Angeles, namely, a North LA site and a South
LA site, and you would like to group them under a group named Los Angeles. To add a site group, click the
+ Group link:
Enter the Site Group Name (Los Angeles) and click Save. The Site Manager tree-view pane will now
show the newly added site group name (Los Angeles):
Create additional site groups as needed.
9
To edit or delete a site group, hover over the site group name or next to it. Two icons become visible; a
pencil icon and a trash can icon. Click the pencil icon to edit the site group name and click the trash can
icon to delete the site group.
Adding Sites
Add the North LA Site and South LA Site sites under the Los Angeles group, and click the + Site link to
add a site.
MWE Configuration Guide
Fill in the following fields:
Site NameType in the desired site name
LocationYou can zoom and pan the map and then drag the blue pin to the correct address. Or
you can simply type the address and press the Enter key; the map will pan and zoom
and the pin will be placed in the correct location automatically.
Site GroupClick the down arrow and select the desired site group, in this case Los Angeles.
10
MWE Configuration Guide
NOTE: You will see a detailed street map, as show in the figure above, only if you have installed a detailed
map such as north-america_us.mbtiles at installation time. You will see no map in the above window if you
are working with the MWE default world map. Other than seeing no map in the above window, using the
default installation map does not affect MWE functionality.
Click the Save button and observe the North LA Site listed under the Los Angeles group:
Similarly, for the South LA Site:
11
MWE Configuration Guide
To edit or delete a site, hover over the site name or next to it. Two icons become visible, namely, a pencil
icon and a trash can icon. Click the pencil icon to edit the site, and click the trash can icon to delete the
site.
The third icon, a set of parallel horizontal lines, allows a site to be dragged to a different Site Group.
Adding Maps
One or multiple maps can be added under each site. Assets whose location is being tracked will be shown
on these maps. If you have a multistory building at a site, you may want to add a map per floor. If you have
a campus with several buildings and parking lots and you would like to add a map for each of them.
12
MWE Configuration Guide
To add a map under a site, hover over the site name or next to it, and observe the Edit icon (pencil icon)
next to it. Click the Edit icon. In the example below, we click on the Edit icon next to the North LA Site:
Click the + Upload link:
Provide the following information:
Name:Enter any map name you deem appropriate
File:Click the Select Site Map button and browse to the location on your local computer
where the map file you want to upload resides. In MWE 2.0, only windows
metafiles (.wmf) are supported.
Max Zoom Level:This defines how many times you will be able to zoom in when displaying the map
in the web client. The default value is 4 and the maximum available value is 8. For
large files, a lower zoom level will result in a smaller upload time.
13
MWE Configuration Guide
Once you have selected a map file (.wmf), the map file name will be displayed:
Click the Upload button. The upload process may take from a few seconds to many minutes, depending
on the map size and Max Zoom Level selected. The reason is that the map is both being uploaded and
tiled for later use. Tiling is done only once when uploading a map into the system. Once the upload and
tiling process is completed, you will be returned to the site properties window.
The uploaded map name will be listed under Site Maps, and the map image will be displayed in the lower
section of the window, as shown in the figure below:
You can add more maps. After adding a second map named Parking Lot, you will see:
The Edit (pencil) and Delete (trash can) next to each map entry in the figure above and allow you to edit
or delete a map file.
14
MWE Configuration Guide
Once you are done adding maps for this site, click the Save button. The tree-view pane will now show the
maps added under the North LA Site:
Clicking on a map entry displays the map image in the map window:
NOTE: In the figure above the label displayed on the lower right corner of the map window. It reads Map
coordinate system is not configured. We have uploaded a map image, but we have not calibrated the map,
that is, we have not defined an x,y coordinate system for each map in order to correctly display asset
locations on the map image.
15
Calibrating a Map
To calibrate a map, click the gear icon on the map window toolbar:
Enter the known (x,y) coordinates for two points on opposite corners of the map. The example uses the
coordinates of the lower left and upper right corners of the square surrounding the map image, known from
a site survey.
MWE Configuration Guide
Click the Next Step button indicated by the red arrow in the figure above. You will see two yellow dots
labeled Lower Left and Upper Right which you can drag to the correct position on the map:
For better accuracy, zoom in when positioning the yellow dots. You can zoom in and out using your mouse
wheel or the + and – buttons on the map toolbar.
16
MWE Configuration Guide
Finally, click the Save button:
The map is now calibrated. As you move your mouse over the map, observe the (x,y) coordinates
displayed on the lower right corner of the map window:
17
MWE Configuration Guide
Registering a Zebra Location Appliance (ZLA)
A ZLA (Zebra Location Appliance) is an appliance that collects location and telemetry data from a variety
of sensor types and location devices, runs location algorithms and filters data, and forwards data across a
network to a MWE (Linux) server. A ZLA can be a physical device as in the picture below, or a virtual
machine.
Zebra Location Appliance (ZLA)
A deployment of MWE may or may not require a ZLA. For example, MWE 2.0 supports deployment of fixed
passive RFID readers without using a ZLA. Also, you could have a location sensor or third-party
application feeding data to MWE via the MWE API. However, most type of sensors supported by MWE 2.0
do require a ZLA.
A ZLA needs to be registered with a MWE server for the ZLA to be able to forward data to that server, and
for the MWE web client to be able to monitor, configure, and update the ZLA. If a ZLA was registered as
part of the MWE software installation process (see the MWE 2.0 Installation Guide) then the ZLA will
already be listed in the InfrastructureAppliances page:
The Status column will show Failed or Activating until a site.json configuration files is published to the
ZLA using System Builder. See System Builder on page 22.
NOTE: The ZLA firmware version must be 2.0.0-1 or higher. See the MWE 2.0 Installation Guide for details
on upgrading the ZLA firmware.
If the ZLA for a site has not yet been registered, here are the steps to register it (see the MWE 2.0
Installation Guide for more details):
1. Log into the ZLA using the root account (obtain login credentials from Zebra) and open a Terminal
window. You can use Putty or similar SSH client to remotely access the ZLA.
2. Change directory to /opt/zebra/zla/icsagent and run the configure script:
# cd /opt/zebra/zla/icsagent
18
MWE Configuration Guide
# ./configure.sh
You will be prompted to enter some information and answer some yes/no questions. Answer as shown
in the figure below. For Server Host, enter the fully qualified domain server name or IP address of
your MWE Linux server.
3. Run the register script:
# ./register.sh
You will be prompted to enter some information and answer some yes/no questions. When prompted,
enter Username / Password (default is admin / admin) and enter a name of your choosing for the ZLA.
This name will be displayed in the MWE web client.
4. Restart the icsagent daemon:
# systemctl restart icsagent
At this point, the ZLA should be listed in the Infrastructure > Appliances page of a web client
pointing to the MWE server.
19
MWE Configuration Guide
Associating a ZLA with a site
Once a ZLA has been registered with a MWE server, a web client pointing to that server will show the ZLA
listed in the Infrastructure > Appliances report:
NOTE: The Status column will show Activating or Failed until a site configuration file is uploaded to
the ZLA using the System Builder tool as explained in System Builder on page 22.
NOTE: The ZLA firmware version must be 2.0-1 or higher. Refer to the MWE 2.0 Installation Guide for
details on upgrading the ZLA firmware.
The next step is to associate the ZLA with a site by specifying the site where the ZLA is located, so that
tags and assets located by that ZLA will be reported by MWE in the correct site and on the correct map.
For example, if the ZLA in the figure above, named vzla20, is physically located at our North LA Site,
receiving and processing tag blinks from sensors at that site, we need to associate this ZLA with the North
LA Site. To do so, select the ZLA (check the checkbox in the first column), click the More link on the report
menu bar, and select Edit Appliance from the popup menu:
20
MWE Configuration Guide
Click the down arrow in the Site field and select the correct site (North LA Site in our example) from the
drop-down list. Click Save. The Appliances page will now show under the Site column the site associated
with the ZLA:
A ZLA can be associated with only one logical site defined in the Site Manager page (see Adding site
groups, sites, and site maps on page 8). In practice, you can have several physical sites associated with a
single ZLA by adding multiple maps (one or more maps per physical site) under a logical site in the
Site Manager page.
21
Loading...
+ 47 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.