MotionWorks
Enterprise
2.0
Installation Guide
P1123394-03EN
ZEBRA and the stylized Zebra head are trademarks of Zebra Technologies Corporation, registered in
many jurisdictions worldwide. All other trademarks are the property of their respective owners.
© 2022 Zebra Technologies Corporation and/or its affiliates. All rights reserved.
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.
Publication Date
March 2022
2
Contents
Introduction ...................................................................................................................... 5
Minimum Server Specs.................................................................................................... 6
Multi-Site Server Specs.................................................................................................... 7
Linux Server Requirements ...................................................................................... 7
Windows Application Server Requirements ............................................................. 8
SQL Server Requirements ....................................................................................... 9
MWE Software Components.......................................................................................... 10
Installation Files ............................................................................................................. 11
Installing on the Windows Database Server .................................................................. 12
Installing on the Windows Application Server ................................................................ 14
Installing on the MWE Linux Server............................................................................... 18
Off-Line Installation................................................................................................. 18
On-Line Installation................................................................................................. 22
ZLA Network Connections ............................................................................................. 27
Ports............................................................................................................................... 28
Configuring a ZLA ......................................................................................................... 31
WHERENET_HOST_IP .......................................................................................... 31
Registering a ZLA ......................................................................................................... 34
Launching the Web Client............................................................................................. 36
Upgrading ZLA Firmware.............................................................................................. 37
Off-Line Upgrade .................................................................................................... 37
On-Line Upgrade .................................................................................................... 38
DAhostname ................................................................................................................. 39
Installing a World Map................................................................................................... 40
Upgrading Sensor Firmware ......................................................................................... 42
Configuring MWE.......................................................................................................... 43
Upgrading MWE on the Windows Servers.................................................................... 44
Upgrading MWE on the MWE Linux Server.................................................................. 45
Off-Line Upgrade .................................................................................................... 45
On-Line Upgrade .................................................................................................... 48
Reference Documents ................................................................................................... 52
3
Contents
Appendix 1: Connecting to a Physical ZLA.................................................................... 53
Connecting to a Physical ZLA ................................................................................ 53
Appendix 2: Pre-Installation Check list........................................................................... 58
MWE Windows Application Server ......................................................................... 58
MWE Windows Database Server ........................................................................... 58
MWE Linux Server.................................................................................................. 58
ZLA ......................................................................................................................... 59
4
Introduction
This document provides instructions for installing MotionWorks Enterprise (MWE) 2.0 software from Zebra
Technologies Corporation. It also provides the specifications for the servers hosting the software.
Zebra Technologies offers world-class real-time asset tracking and management software solutions to
optimize the flow of goods in complex logistical operations, increasing productivity, lowering operational
costs, and improving safety and security. Zebra Technologies uses a wide range of scalable RTLS (Real
Time Locating Systems) technologies used to generate accurate, on-demand information about the
physical location and status of assets.
MWE is a software suite that provides tools for designing, configuring, operating, and troubleshooting
RTLS solutions. MWE serves as the central repository for all the real-time location and communication
data captured by the RTLS-tracking infrastructure. MWE also provides tools for integrating RTLS data with
customer and third-party applications.
Some of the location and telemetry RFID technologies supported by MWE include:
• Passive RFID
• UWB
• Bluetooth Low-Energy
MotionWorks Enterprise Installation Guide
• Wi-Fi
• ISO 24730
• GPS
The diagram below provides an overview of some of the RTLS system components and data flow. The
over-the-air RF transmissions from tags (RF transmitters) are detected by sensors connected to a network.
This connection can be wired or wireless. The data generated by the sensors flow across the network to a
Zebra Location Appliance (ZLA) and then to the MWE server. Multiple sites are supported, each with its
own ZLA.
The ZLA can be virtual or physical. The physical ZLA is a 1U rackmount box normally installed on-site.
Depending on the RTLS technology being deployed, a ZLA can be installed on-premises at a site, or it can
be installed in a remote data center. A ZLA runs the location algorithms and feeds tag, blink, and location
data to an MWE server. The ZLA software also includes filters for removing redundant data and reducing
network traffic. The MWE server store and retrieve data from a database.
5
MotionWorks Enterprise Installation Guide
A virtual ZLA can be provided as an OVA file with pre-loaded software ready to be deployed, or a ZLA
installer is available that converts a Red Hat 7.9 or CentOS 7.9 virtual server into a ZLA appliance.
MWE 2.0 also supports direct communication from passive RFID readers to MWE running locally or in the
cloud. No ZLA appliance is required in this case.
6
MotionWorks Enterprise Installation Guide
Minimum Server Specs
Location data can flow into the MWE servers from a ZLA device or some other source. A MWE deployment
requires at a minimum one Red Hat or CentOS 7.9 server. A ZLA Appliance may or may not be required.
The minimum hardware and software requirements are given below for three different types of
deployments. A user is prompted to select one of these installation deployment types when running the
MWE installation script.
Figure 1 Production Deployment - Full Functionality
7
MotionWorks Enterprise Installation Guide
Figure 2 Demo Deployment - Full Functionality
8
MotionWorks Enterprise Installation Guide
In demo deployments with minimal load the following functionality is turned off: historical service logs,
Kibana tool, and MWE monitoring of system health. Historical application data, such as tag blink and event
history, is still available.
Figure 3 Minimal Demo Deployment - Most functionality
Notes on Linux Server Requirements
• Installation of MWE 2.0 on a Linux server requires a /data partition, that is, a partition named data
located directly under the root / directory.
• For new MWE 2.0 installations on a production system, the /data partition should have 1 TB of free
space.
• The Red Hat or CentOS installation should include at a minimum the following installation component:
Minimal Install + System Administration Tools + Compatibility libraries, as shown in the figure below.
9
MotionWorks Enterprise Installation Guide
• The firewalld daemon needs to be installed and running on the Linux server before installing the MWE
software.
• The package policycoreutils-python is installed on the Linux server. You can check by running this
command:
# rpm -q policycoreutils-python
• If the server has Internet connection, you can install this package by running this command:
# yum install policycoreutils-python
The core MWE services on the Linux server are installed as Docker containers running on a local Docker
subnet created by the installation script. This adds the following two requirements:
• The MWE installer will enable ipv4 forwarding. If a security agent has been installed on the Linux
server, it must not disable ipv4 forwarding. Similarly, any security patches applied to the Linux server
must not disable ipv4 forwarding.
• If a security agent has been installed on the Linux server, it must allow all traffic within the Docker
subnet and between the Docker subnet and the local host.
10
MotionWorks Enterprise Installation Guide
MWE Software Components
For reference, the diagram below illustrates the various MWE software components hosted on the MWE
Linux server and their relation within the MWE software:
NOTES: The arrows in the figure indicate the following:
Blue arrows http/https connections
Orange arrows TCP connections
Green arrow WebSocket connection
Purple arrow SMTP connection
• MWE Tools include System Builder and other tools.
• All the core MWE services run on the Linux server as Docker containers.
11
Installation Files
Obtain a link to download the MWE installation files from Zebra as described below. The ‘n’ in the file
names denotes the latest version available of the 2.0 release.
NOTE: Sometimes copying a command from a document and pasting it into a Putty or Terminal Window
does not work, as some characters may be misinterpreted. You may need to type some commands.
mwe-containers-setup-2.0.n-offline.tar.gz Installs/upgrades MWE core services on a Linux server.
mwe-containers-setup-2.0.n-online.tar.gz Installs/upgrades MWE core services on a Linux server.
mwe_tools_2.0.n.exe Installs/upgrades a set of MWE configuration and
MotionWorks Enterprise Installation Guide
The installer is self-contained and no Internet
connection is required.
This installer is much smaller than its offline counterpart
but requires the Linux server to have Internet access at
installation time.
diagnostic tools on any Windows PC. These tools can
connect to the MWE (Linux) server or to different types
of location sensors to perform configuration or
diagnostics tasks. Check Upgrading MWE to see what
network ports might need to be opened.
ZLA-2.0.n-1.i386.rpm Upgrades the software on a ZLA appliance (physical or
virtual). A ZLA is provided with pre-loaded ZLA software.
The ZLA-2.0.n-1.i386.rpm package upgrades the
pre-loaded software to version 2.0.n.
Note: On request, Zebra can provide an installation
script that converts a CentOS or Red Hat server into a
ZLA appliance. The script installs a previous version of
ZLA software, so the ZLA-2.0.n-1.i386.rpm package
must be applied to upgrade the ZLA software to version
2.0.n.
12
Install MWE
This section describes an off-line MWE installation for Linux servers with no access to the Internet, and an
optional on-line installation for servers that do have Internet access.
Off-Line Installation
The off-line installation option does not require the Linux server to have Internet access at installation time.
The installation procedure involves copying to the Linux server a tar.gz file that is close to 7 GB in size, so
you might want to copy it prior to a scheduled installation. Before proceeding with the installation, please
verify that the requirements listed in Minimum Server Specs on page 7 for the MWE Linux Server are met.
Initial Checks
Verify that the following requirements are fulfilled:
• A
/data partition exists on the Linux server. See details in Minimum Server Specs on page 7.
MotionWorks Enterprise Installation Guide
• The package
You can check by running this command:
• If the server has Internet connection, you can install this package by running this command:
# yum install policycoreutils-python
• The firewalld daemon is installed and running on the Linux server. You can check using this
command:
# systemctl status firewalld
The result should show the status as ‘active (running)’, as in the figure below
policycoreutils-python is installed on the Linux server.
# rpm -q policycoreutils-python
Copying and Extracting the Installation Package
1. Using WinSCP, or Putty, or a similar SSH client, copy the
mwe-containers-setup-2.0.n-offline.tar.gz installation package to the /data directory on the Linux
server.
2. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
3. Change directory to /data and extract the tar.gz file:
# cd /data
# tar -xvf mwe-containers-setup-2.0.n-offline.tar.gz
NOTE: Sometimes copying a command from a document and pasting it into a Putty or Terminal window
does not work, as some characters may be misinterpreted. You may need to type some commands.
13
MotionWorks Enterprise Installation Guide
Performing Environment Validation and Initial Setup
The setup command below verifies that the environment meets the requirements. It also installs the
Docker service and creates an mwe user account to be used by the MWE application.
1. Extract and run the following commands.
# cd /data/mwe_setup
# ./mwe_setup.sh –offline-setup
2. Select one of the four installation options.
• Production Deployment - installs full functionality and is for production deployments.
If you select Production Deployment, the installation script checks the following:
• Red Hat or CentOS 7.9 is installed
• There is at least 64 GB of memory installed
• There is at least 1000 GB (1 TB) of disk space available under
/data
• firewalld is running
• Docker is installed. If not found, setup will install it.
The installation script exits if one of the conditions above is not met.
• Demo Deployment - includes full functionality, but is meant for demonstrations or proof of concepts
with a light load.
If you select Demo Deployment, the installation script will check the following:
• Red Hat or CentOS 7.9 is installed
• There is at least 32 GB of memory installed
• There is at least 100 GB of disk space available under
/data
• firewalld is running
• Docker is installed. If not found, setup will install it.
The installation script exits if one of the conditions above is not met.
• Minimal Demo Deployment - includes most functionality and is for deployments with minimal load.
The following functionality is turned off: historical service logs, Kibana tool, and MWE monitoring of
system health. Historical application data, such as tag blink and event history, is still available.
If you select Minimal Demo Deployment, the installation script will check the following:
• Red Hat or CentOS 7.9 is installed
• There is at least 16 GB of memory installed
14
MotionWorks Enterprise Installation Guide
• There is at least 50 GB of disk space available under
• firewalld is running
• Docker is installed. If not found, setup will install it.
The installation script exits if one of the conditions above is not met.
• Quit
If all of the checks are successful, the following screen appears:
3. Press the Enter key to exit the setup.
Proceed to install the MWE software.
Installing the MWE Software
/data
1. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
2. Change directory and run the installation script:
# cd /data/mwe_setup
# ./mwe_setup.sh –-offline-install
The installer extract files and docker images from the installation files. This may take several minutes.
3. When prompted, press ENTER.
4. Next, enter the IP address of the Linux server where this installation is being done. It will be one of the
network interfaces listed by the installation script, as seen in the following figure.
15
MotionWorks Enterprise Installation Guide
Enter the number of sites this MWE installation will support.
5.
If you are not sure, enter
6. Select an authentication type.
At installation time, you can select option
1. MWE automatically adjusts this value as needed.
1. database. After installation, you can choose and configure
a different authentication type, as explained in the MWE 2.0 Configuration Guide.
7. When prompted Is the MWE installation on the cloud? (y/n), you answer depends on the MWE
deployment. This setting can be changed after installation.
If your deployment does not include passive RFID readers, answer no
(n).
If your deployment includes passive RFID readers running the R2C (Read to Cloud) application, your
answer depends on how they are deployed.
• The RFID readers and the MWE server are all on the same network, or they are on different subnets
linked by a router. The MWE server and an RFID reader can reach each other’s IP addresses and
traffic between them can flow unimpeded (after opening necessary ports; see Upgrading MWE).
In this case, answer no
(n) so that you are not asked additional questions related to the cloud.
• The RFID readers are on-premises at a site behind a local firewall while the MWE server is in a
cloud behind the cloud firewall.
In this case, answer yes
(y) to enable passive RFID readers running the R2C (Read to Cloud)
application to communicate directly with the MWE server rather than communicating with a ZLA.
You will be prompted to enter the public IP address of the MWE server in the cloud.
8. When prompted Is incoming https traffic allowed to local network? (y/n) the answer is related to
connections initiated by the MWE server in the cloud to the readers in the local network.
• The MWE server in the cloud cannot directly reach the RFID reader IP address in the local network
because the reader IP is a private IP sitting behind the site’s firewall. There is no public IP for the
reader. Therefore, HTTPS traffic from the MWE server in the cloud to a local reader is not allowed.
In this case, answer no
(n).
Note: As a result, the Initialize menu item in Device Manager in the MWE web client will be disabled,
and you will need to use the MWE RFID Initializer tool running on a local computer to Initialize an
RFID reader. See the MWE Device Manager User Guide for details.
16
• The local RFID readers do have a public Internet address, or otherwise the MWE server is in a
private cloud that allows the MWE server to initiate a connection to the reader IP address. In this
case answer yes
Note: You would register a reader in Device Manager using the reader public IP address. The
reader would be initialized using the Initialize menu item in Device Manager, whereby the MWE
server will initiate a connection to the reader and perform some configuration tasks. See the MWE
Device Manager User Guide for details.
The installation script then starts installing the Docker images. The installation typically takes several
minutes. Once the installation is complete, press Enter to exit the installation mode.
Checking Status
Verify that all MWE services are up and running. Depending on the resources (cpu, memory) on your
server, it may take a couple of minutes for all services to be up and running. The MWE services run as
Docker containers. These containers can be stopped and started. The status of the containers can be
checked using the docker and docker-compose commands.
MotionWorks Enterprise Installation Guide
(y).
1. To check the status of the MWE services, run the following commands:
# cd /data/mwe
# docker-compose ps
17
Verify that the column State shows Up for all containers. Some services also report a health condition
2.
and should show
NOTE: You may see several warnings if you run the docker-compose command under the root account.
You can ignore these warnings. If you switch to the mwe account, you will not see these warnings.
# su - mwe
# cd /data/mwe
# docker-compose ps
To switch back to the root account use:
# su -
MWE Files Location
The MWE files are copied to the following directories on the Linux server:
MotionWorks Enterprise Installation Guide
healthy
.
Installation package:
Setup files:
MWE commands and configuration (.env):
MWE Services configuration:
Docker images and containers:
3rd Party services and database backups:
Log files:
On-Line Installation
The installation procedure described in this section assumes that, during installation, the MWE Linux
server has access to the websites listed below. If this is not the case, please see OFF-LINE
INSTALLATION in the previous section. Before proceeding with the installation, please verify that the
requirements listed in Minimum Server Specs for the MWE Linux Server are met.
Performing Initial Checks
1. Before attempting the installation, verify that the following requirements are fulfilled:
• A
/data partition exists on the Linux server. See details in Full Functionality - Light Load
Deployment on page 8.
/data/
/data/mwe_setup/
/data/mwe/
/data/mwe-conf/
/data/docker/
/data/zebra
/data/mwe-logs
2. The MWE Linux server has access to the following websites:
https://registry.zebramwe.com
https://yumrepo.zebramwe.com
• To check access, you can use the curl command. For example:
# curl -k https://registry.zebramwe.com
will return quickly with no error if the server has access to https://registry.zebramwe.com. Otherwise
you will see a connection time out or similar error message.
3. The firewalld daemon is installed and running on the Linux server. You can check using this command:
18
MotionWorks Enterprise Installation Guide
# systemctl status firewalld
The result should the status as ‘active (running)’.
Copying and Extracting Installation Package
1. Using WinSCP, or Putty, or a similar SSH client, copy the
mwe-containers-setup-2.0.n-online.tar.gz installation package to the /data directory on the MWE
Linux server.
2. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
3. Change the directory to /data and extract the tar.gz file:
# cd /data
# tar -xvf mwe-containers-setup-2.0.n-online.tar.gz
You will see a set of files being extracted.
NOTE: Sometimes copying a command from a document and pasting it into a Putty or Terminal window
does not work, as some characters may be misinterpreted. You may need to type some commands.
Performing Environment Validation and Initial Setup
1. Run the command below to verify that the environment meets the requirements.
If the requirements are met, the command will install the Docker service and create a mwe account to
be used by the MWE application.
# cd /data/mwe_setup
# ./mwe_setup.sh --setup
You will be presented with four installation options.
• Production Deployment - installs full functionality and is meant for production deployments.
If you select
Production Deployment, the installation script will check the following:
• Red Hat or CentOS 7.9 is installed
19
MotionWorks Enterprise Installation Guide
• There is at least 64 GB of memory installed
• There is at least 1000 GB (1 TB) of disk space available under
/data
• firewalld is running
• Connectivity to the Internet
• Connectivity to MWE Yum repo (https://yumrepo.zebramwe.com)
• Connectivity to MWE registry (https://registry.zebramwe.com)
• Docker is installed. If not found, setup will install it.
The installation script exits if one of the conditions above is not met.
• Demo Deployment - includes full functionality but is meant for demo’s or POC’s with a light load.
If you select
Demo Deployment, the installation script will check the following:
• Red Hat or CentOS 7.9 is installed
• There is at least 32 GB of memory installed
• There is at least 100 GB of disk space available under
/data
• firewalld is running
• Connectivity to the Internet
• Connectivity to MWE Yum repo (https://yumrepo.zebramwe.com)
• Connectivity to MWE registry (https://registry.zebramwe.com)
• Docker is installed. If not found, setup will install it
The installation script exits if one of the conditions above is not met.
The display recommends 8 vCPU's (see previous figure), but the setup script does not enforce it.
You can use 4 vCPU for a demo deployment with a light load if you can tolerate occasional
response time delays.
• Minimal Demo Deployment - includes most functionality. It is meant for deployments with minimal
load. The following functionality is turned off: historical service logs, Kibana tool, and MWE
monitoring of system health. Historical application data, such as tag blink and event history, is still
available.
If you select
Minimal Demo Deployment, the installation script will check the following:
• Red Hat or CentOS 7.9 is installed
• There is at least 16 GB of memory installed
• There is at least 50 GB of disk space available under /data
• firewalld is running
• Connectivity to the Internet
• Connectivity to MWE Yum repo (https://yumrepo.zebramwe.com)
• Connectivity to MWE registry (https://registry.zebramwe.com)
• Docker is installed. If not found, setup will install it
The installation script exits if one of the conditions above is not met.
20
MotionWorks Enterprise Installation Guide
• Quit
If all the checks are successful, you will see the following screen.
2. Press the Enter key to exit setup.
Proceed to install the MWE software.
Installing the MWE Software
1. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
2. Change directory and run the installation script:
# cd /data/mwe_setup
# ./mwe_setup.sh --install
The installer extracts and copy a set of files and prompts you to press Enter to continue.
3. Enter login credentials to download the docker images from the Zebra website hosting the MWE yum
repository that contains the MWE Docker images.
a. For the yum repository user, enter mwe.
b. Enter the password. You can obtain the password from Zebra.
c. Re-enter the password.
21
MotionWorks Enterprise Installation Guide
Enter the IP address of the Linux server where this installation is being done. It will be one of the
4.
network interfaces listed by the installation script.
5. Enter the number of sites this MWE installation will support.
If you are not sure, enter
6. Select an authentication type.
At installation time, you can select option
. MWE will automatically adjust this value as needed.
1
1. database. After installation, you can choose and configure
a different authentication type, as explained in the MWE 2.0 Configuration Guide.
7. When prompted Is the MWE installation on the cloud? (y/n), you answer depends on the MWE
deployment. This setting can be changed after installation.
If your deployment does not include passive RFID readers, answer no
(n).
If your deployment includes passive RFID readers running the R2C (Read to Cloud) application, your
answer depends on how they are deployed.
• The RFID readers and the MWE server are all on the same network, or they are on different subnets
linked by a router. The MWE server and an RFID reader can reach each other’s IP addresses and
traffic between them can flow unimpeded (after opening necessary ports, see Upgrading MWE).
In this case, answer no
(n) so that you are not asked additional questions related to the cloud.
• The RFID readers are on-premises at a site behind a local firewall while the MWE server is in a
cloud behind the cloud firewall.
In this case, answer yes
(y) to enable passive RFID readers running the R2C (Read to Cloud)
application to communicate directly with the MWE server rather than communicating with a ZLA.
You will be prompted to enter the public IP address of the MWE server in the cloud.
8. When prompted Is incoming https traffic allowed to local network? (y/n) the answer is related to
connections initiated by the MWE server in the cloud to the readers in the local network.
22
MotionWorks Enterprise Installation Guide
• The MWE server in the cloud cannot directly reach the RFID reader IP address in the local network
because the reader IP is a private IP sitting behind the site’s firewall. There is no public IP for the
reader. Therefore, HTTPS traffic from the MWE server in the cloud to a local reader is not allowed.
In this case, answer no
Note: As a result, the Initialize menu item in Device Manager in the MWE web client will be disabled,
and you will need to use the MWE RFID Initializer tool running on a local computer to Initialize an
RFID reader. See the MWE Device Manager User Guide for details.
• The local RFID readers do have a public Internet address, or otherwise the MWE server is in a
private cloud that allows the MWE server to initiate a connection to the reader IP address. In this
case answer yes
Note: You would register a reader in Device Manager using the reader public IP address. The
reader would be initialized using the Initialize menu item in Device Manager, whereby the MWE
server will initiate a connection to the reader and perform some configuration tasks. See the MWE
Device Manager User Guide for details.
The installation script then starts installing the Docker images. The installation typically takes several
minutes. Once the installation is complete, press Enter to exit the installation mode.
(n).
(y).
Checking Status
Verify that all MWE services are up and running. Depending on the resources (cpu, memory) on your
server, it may take a couple of minutes for all services to be up and running. The MWE services run as
Docker containers. These containers can be stopped, started, and their status can be checked using the
docker and docker-compose commands.
1. To check the status of the MWE services (Docker containers), run these commands:
# cd /data/mwe
# docker-compose ps
23
MotionWorks Enterprise Installation Guide
Verify that the column State shows Up for all containers. Some services also report a health condition
2.
and should show
NOTE: You may see several warnings if you run the docker-compose command under the root account.
You can ignore these warnings. If you switch to the mwe account, you should not see these warnings.
# sudo su - mwe
# cd /data/mwe
# docker-compose ps
To switch back to the root account use:
# su -
MWE Files Location
The MWE files are copied to the following directories on the Linux server:
Installation package:
Setup files:
MWE commands and configuration (.env):
MWE Services configuration:
healthy.
/data/
/data/mwe_setup/
/data/mwe/
/data/mwe-conf/
Docker images and containers:
3rd Party services and database backups:
Log files:
/data/docker/
/data/zebra
/data/mwe-logs
24
Ports
MotionWorks Enterprise Installation Guide
Under normal operation, sensors communicate with a ZLA or directly with the MWE server and the ZLA
communicates with the MWE server. This requires that some ports be open on the sensors, on the ZLA, on
the MWE server, and in firewalls on the network. Additional ports are required for monitoring and
troubleshooting tools. The following tables list all of these ports.
Table 1 On MWE Server
Protocol &
Source Destination
Sensor, reader MWE server TCP 21 Required by some devices for downloading a
SSH client MWE server TCP 22 Used by SSH client to connect to MWE server.
Port
Number
certificate.
Description
Passive RFID
readers
Browser – MWE
web client
ZLA MWE server TCP 80 or
Kafka Tool,
Offset Explorer
MWE server Zebra yum
Tool on PC MWE server TCP 9092,
Passive RFID
readers
Kibana tool
running on PC
Sensor, reader MWE server TCP
MWE server UDP 53 Required by passive RFID readers running R2C
MWE server TCP 80 or
443
443
MWE server TCP 2181 For connecting Kafka tool (Offset Explorer) to the
TCP 5000 Between MWE server and Zebra yum repo web
repo web
site
9093
MWE server TCP 9000,
9443
MWE server TCP 9201 For connecting Kibana tool to Elastic Search
21100-2111
0
application (added to MWE via Device Manager).
Between web client and MWE server. Used for
http/s client connections.
Used by ZLA for http/s and web-socket
connection to MWE server.
MWE server for troubleshooting purposes.
site. Required only at installation time when
performing on-line installation.
For connecting debugging tool to Kafka for
troubleshooting purposes.
Required by passive RFID readers running R2C
application (added to MWE via Device Manager).
database.
Required by some devices for downloading a
certificate.
25
MotionWorks Enterprise Installation Guide
Figure 4 On ZLA
Protocol &
Source
Destination
SSH client ZLA TCP 22 Used by SSH clients to remotely connect to the
Port
Number
Description
ZLA.
WhereLAN III
and DVR
sensors
Telnet session
rd
or 3
party app
ZLA UDP 2496,
UDP 12273,
TCP 12285
ZLA TCP 9003 Locate data stream for third party applications.
Communication between sensors and ZLA
Also used for diagnostics and troubleshooting.
BLE Receivers ZLA TCP 8005 Default port used by MPACT BLE receivers to
send data to a ZLA. This is configurable.
MWE tools on
Windows PC
ZLA TCP 13287 Used by ZLA diagnostic/troubleshooting tools
installed on Windows PC.
GPS tag ZLA TCP 12281 Used by GPS tags sending data to a ZLA via a
WiFi access point.
Figure 5 On sensors, readers, and Dart hubs
Protocol &
Source
Destination
ZLA WhereLAN III
and DVR
sensors
MWE Tools on
Windows PC
WhereLAN III
and DVR
Port
Description
Number
UDP 12273,
Communication between sensors and ZLA
UDP 12282,
TCP 12283
TCP 12277 Used by diagnostic/troubleshooting tool installed
on Windows PC.
ZLA Dart hub TCP 22 Used by ZLA to subscribe to Dart hub using SSH
connection.
MWE server,
web browser
ZLA Passive RFID
MWE server Passive RFID
Dart hub TCP 80 or
443
TCP 5084 ZLA connects to this port on a passive RFID
reader
TCP 80 or
reader
443
26
Used by web client and MWE server.
reader using LLRP protocol.
Used by MWE server to connect to RFID reader
when running R2C application.
MotionWorks Enterprise Installation Guide
Figure 6 On Windows PC running MWE Tools
Protocol &
Source
Destination
Port
Number
Description
WhereLAN III
and DVR
sensors
Telnet session
on Windows
PC
Locate
Analyzer tools
on Windows
PC
Windows PC
running MWE
Tools
Dart Hub TCP 5117 For monitoring data output on Dart hub
Dart Hub TCP 5111,
TCP 12289,
TCP 12293
5115, 5116,
5117
Communication between sensors and MWE tools
For collecting Dart raw data from a Dart hub
27
MotionWorks Enterprise Installation Guide
Installing a Virtual ZLA
The virtual ZLA appliance is available as an OVA file with pre-loaded software that is ready to be deployed
in a hypervisor environment. A link to download this OVA file is provided upon request. Or, you can run an
installer to convert a Red Hat 7.9 or CentOS 7.9 server into a ZLA appliance. The specs for the ZLA are as
follows.
• Red Hat 7.9 or CentOS 7.9
• 2 vCPU’s @ 2.5 GHz, 4 GB RAM
• 50 GB under / (root) partition
• Static IP
Converting a Server
To convert a Red Hat 7.9 or a CentOS 7.9 server into a ZLA, request the most recent installation package
from Zebra (currently
Internet access.
1. Log into the Red Hat or CentOS server as root.
ZLA-offline.tgz). The installation package does not require the server to have
2. Copy the included installation package file (currently ZLA-offline.tgz) to the /home directory on the
server.
3. Run the following commands to create the ZLA appliance.
# cd /home
# tar -xvf ZLA-offline.tgz
# cd ZLA
# ./install_zla.sh offline
4. Verify the version of the ZLA software using the following commands.
[root@vzla]# rpm -qa | grep ZLA
ZLA-1.4.1-1.i386
5. Upgrade the ZLA software to the latest 2.0.n using the ZLA-2.0.n-1.i386.rpm package.
NOTE: Two services are installed: icsagent and zls. Near the end of the installation log these services
display as failing to start. This is okay. They will start once the configuration file
the ZLA (see the MWE Configuration Guide).
A ZLA installed using the ZLA-2.0.n-1.i386.rpm installer does not support WhereLAN sensors.
site.json is published to
28
MotionWorks Enterprise Installation Guide
ZLA Network Connections
A ZLA (Zebra Location Appliance) can be a virtual appliance (a virtual server with specialized software) or
a physical appliance. A virtual ZLA has by default a single network interface, but more can be easily added
as needed. A physical ZLA has 4 Ethernet ports labeled MGMT, WAN, LAN1, and LAN2, intended for
optional remote management (MGMT), connecting to a Wide Area Network (WAN), and connecting to two
different Local Area Networks (LAN1 and LAN2). Please see Appendix 1: Connecting to a Physical ZLA
for more details.
The diagram below shows two possible ways of connecting a ZLA to the MWE servers and to location
sensors in your deployment, namely, using a one or two network interfaces on the ZLA.
The important thing to remember is that the ZLA network interface connecting to the sensors (LAN1 in the
examples above) must be assigned a static IP address.
The configuration of the network interfaces on a ZLA will typically be done by the customer’s IT
Department. It can be done using a GUI tool or directly modifying the network interface files in the
/etc/sysconfig/network-scripts directory. Here is an example:
TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
NAME=ens160
UUID=b43ddc0a-1a8b-492b-b10e-189ea6ee2160
ONBOOT=yes
PREFIX=24
IPADDR=192.168.1.77
DNS1=192.168.1.254
GATEWAY=192.168.1.254
Reboot the ZLA after making changes to the network interface configuration files.
29
MotionWorks Enterprise Installation Guide
Upgrading ZLA Software
This section lists the steps to upgrade the software on a physical or virtual ZLA.
1. Using WinSCP or a similar tool, copy the
ZLA-2.0.n-m.i386.rpm
upgrade package to the
/home
directory on the ZLA.
The digits
2. Using Putty or a similar SSH client, log into the ZLA using the root account (obtain login credentials
n and m may change over time as new builds with minor changes become available.
from Zebra).
3. Verify that the firewalld daemon is running.
# systemctl start firewalld
# systemctl status firewalld
4. Verify that the status is reported as active (running).
5. Check the current version of the ZLA software.
# rpm -qa | grep ZLA
6. Perform the software upgrade using the following commands.
# cd /home
# rpm -Uvh ZLA-2.0.n-m.i386.rpm
Replace n and m with the values of your ZLA sof t ware.
7. Restart the services.
# systemctl restart icsagent
# systemctl restart zls
8. Check services status:
# systemctl status icsagent
# systemctl status zls
For icsagent, the status should be active (running).
For the zls service, if no
show as
(running)
9. Check the version of the ZLA software you just installed.
# rpm -qa | grep ZLA
activating or failed. If a default site.json file does exist on the ZLA, it may show active
.
site.json configuration file has yet been published to the ZLA the status may
30
Configuring a ZLA
In the current release of the ZLA software, there is one environmental variable (WHERENE_HOST_IP)
that may need to be set. Also, the time zone, system time, and hostname may need to be changed. This
section provides instructions to perform these tasks.
WHERENET_HOST_IP
If the ZLA has more than one network interface connected to the network (such as LAN1 and LAN2 in
Section 9), it is necessary to specify to the location engine running on the ZLA which interface is the one
receiving data from the Location Sensors. This is done by setting the WHERENET_HOST_IP environment
variable to the static IP address of that network card, that is, the network card on the same subnet as the
Location Sensors.
1. Log into the ZLA using the root account (obtain login credentials from Zebra), and open a terminal
window. You can also use Putty, WinSCP, or similar SSH client to remotely access the ZLA. Putty
provides a command line interface, while WinSCP provides a graphical user interface to view and edit
files and directories.
NOTE: If you have not already configured the network interfaces on the ZLA, please Section 9 and
Appendix 1. You should then have a known IP address to connect to the ZLA using Putty or WinSCP.
MotionWorks Enterprise Installation Guide
2. If using a terminal window, change directory to /etc/systemd/system with this command: # cd
/etc/systemd/system
3. Open the zls.service file for editing. You can use a text editing command such as vi or, if using
. If using WinScp, simply browse to this folder.
WinSCP, simply double-click on the file. The content of this file is shown below.
[Unit]
Description=Zebra Location Service
After=network.target
[Service]
Type=forking
Environment=ZEBRA_HOME=/opt/zebra
Environment=LD_LIBRARY_PATH=/opt/zebra/zla/zlpcore/bin
Environment=WHERENET_HOST_IP=192.168.30.120
ExecStart=/opt/zebra/zla/zlpcore/bin/start-zls.sh
ExecStop=/opt/zebra/zla/zlpcore/bin/stop-zls.sh
KillMode=none
Restart=always
RestartSec=15
StartLimitInterval=60
StartLimitBurst=3
[Install]
WantedBy=multi-user.target
4. Add or edit the line highlighted in red font above. Make sure to set the IP address to the (static) IP of the
network interface on the same subnet as the Location Sensors. Save and close the file.
5. For the changes to take effect, run this command in a terminal window:
# systemctl daemon-reload
31
ZLA Time and Date
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. To check the current time and date on your ZLA, use the timedatectl command.
3. Set the Time Zone.
In the example above, the Time Zone is set to US/Pacific (PDT). To change it to other US Time Zones,
you can use these commands:
# timedatectl set-timezone US/Pacific
# timedatectl set-timezone US/Mountain
# timedatectl set-timezone US/Central
# timedatectl set-timezone US/Eastern
MotionWorks Enterprise Installation Guide
4. To see a list of worldwide Time Zones, use the command:
# timedatectl list-timezones
5. Set the correct time.
The ZLA includes an NTP client (chrony) that will automatically sync the system clock with NTP
servers on the Internet. If the ZLA does not have access to the Internet and you would like to use an
NTP server on your local network instead, add the line highlighted in red font below to the
/etc/chrony.conf file:
# Use public servers from the pool.ntp.org project.
# Please consider joining the pool (http://www.pool.ntp.org/join.html).
server 0.centos.pool.ntp.org iburst
server 1.centos.pool.ntp.org iburst
server 2.centos.pool.ntp.org iburst
server 3.centos.pool.ntp.org iburst
server 192.168.1.50 prefer iburst
6. Replace the IP address in the example above with the IP address or name of your local NTP server.
7. Restart the NTP client for the change to take effect:
# systemctl restart chronyd
8. If you needed to manually set the date and time, you can use these commands:
# timedatectl set-ntp 0(this command will disable the NTP client)
# timedatectl set-time YYYY-MM-DD
(as in timedatectl set-time 2018-05-07)
32
MotionWorks Enterprise Installation Guide
# timedatectl set-time HH:MM:SS
(as in timedatectl set-time 14:45:05)
NOTE: ZLA supports only one time zone, so all site maps associated with a ZLA in MWE will have the
same time zone. Use separate ZLA’s for sites in different time zones.
Changing the Hostname
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.
A ZLA ships with the default hostname ZebraZLA. It is recommended that you change this default
hostname. This default name can be seen in the command line prompt as in the figure below. More
details are given by the
hostnamectl command.
2. To change the hostname to a new name NewZLAName use this command:
# hostnamectl set-hostname NewZLAName
This command will change the hostname at the Kernel level (static name). The name displayed at the
command prompt (transient name) will get updated after a reboot. The ZLA can be rebooted by issuing
a
reboot command.
33
Registering a ZLA
A ZLA appliance needs to be registered with the MWE server for the ZLA to be able to forward data to the
server, and for the MWE web client to be able to monitor, configure, and update the ZLA. To register a ZLA
with a MWE server, follow these steps:
1. Using Putty or similar SSH client, log into the ZLA using the root account (obtain login credentials from
Zebra).
2. Change directory to /opt/zebra/zla/icsagent and run the configure script:
# cd /opt/zebra/zla/icsagent
# ./configure.sh
3. You will be prompted to enter some information and answer some yes/no questions. Answer as shown
in the figure below. For Sever Host, enter the IP address or fully qualified domain server name of your
MWE Linux server.
MotionWorks Enterprise Installation Guide
4. The value shown in the square brackets [ ] is the current or default value. You can accept it by pressing
the Enter key.
5. If there is a proxy server between the ZLA and the MWE server, answer ‘yes’ to the server proxy
question and enter the URL for the proxy server.
6. Run the register script:
# ./register.sh
34
MotionWorks Enterprise Installation Guide
When prompted, enter Username / Password (default is admin / admin) and enter a name of your
7.
choosing for the ZLA. This name will be displayed in the MWE web client. It is recommended that you
use the same name configured as hostname in the previous step above.
8. Restart the icsagent daemon:
# systemctl restart icsagent
35
MotionWorks Enterprise Installation Guide
Launching the Web Client
1. Open a web browser (Chrome, Edge, or Firefox) on a client machine or server on the network, and
point it to http://MWE_Server_Name
address. The login page will be displayed. Default login is admin / admin.
where MWE_Server_Name is your MWE Linux server name or IP
NOTE: https://MWE_Server_Name
is also supported. See the MWE Configuration Guide for instruction on
how to add a certificate on the MWE server.
2. Open the Infrastructure > Appliances page to show the ZLA registered per instructions in a previous
section.
The Status column will show Failed (or Activating) until a site.json configuration file is published using
the System Builder tool (see the MWE Configuration Guide for details). If your ZLA includes a default
site.json file, the Status column may show Running. The status may also oscillate between Running
and Offline if the ZLA software has not been upgraded to version 2.0.0.
36
MotionWorks Enterprise Installation Guide
Installing a World Map
After launching the web client, if you open the Infrastructure > Site Manager page, you will see a default
background world map that does not contain much detail. It is possible to load and display a different
background map, including maps that offer street-level details for the US or other countries. This is
optional. Leaving the default world map in place will not impact MWE functionality in any way.
To load and display a different background map, follow these steps:
1. Find a map that you would like to use.
The file must be in mbtiles format (extension .mbtiles). You can go to
https://openmaptiles.com/downloads/planet/
different regions of the world.
to download a map with street-level information for
For example, you can download the file
the US. This is a large file (7 GB), so it may take some time to download and copy.
2. Assuming you have installed MWE under /data, copy the file to
/data/zebra/mwe/3rdParty/tileserver-data on the Linux server. After copying the new map file,
delete or move the previous world map from this folder. The tileserver service, which processes the file,
will read only one file from this folder.
3. Restart the tileserver service on the MWE server by running these commands:
# cd /data/mwe (assuming you have installed MWE under /data)
# docker-compose stop tileserver
# docker-compose start tileserver
north-america_us.mbtiles
that contains street-level info for
37
MotionWorks Enterprise Installation Guide
Relaunch the web client. The first time you open the Infrastructure > Site Manager page, it may take
4.
30- 60 seconds to display the map.
If you have installed the north-america_us.mbtiles map, the Infrastructure > Site Manager page in the
web client will show a more detailed world map as shown below
Furthermore, when adding a site, the Add Site window will show street level details of the US address
you have entered, as in the figure below
For other regions of the world, however, no map will be shown in the Add Site window
If you leave the default installation world map in place, you will see no map in the Add Site window for
US addresses either. But, as mentioned, this has no impact on MWE functionality.
38
MotionWorks Enterprise Installation Guide
Upgrading Sensor Firmware
MWE supports a variety of different locating sensors and technologies, including:
• BLE beacons and receivers
• Passive RFID readers
• Dart UWB sensors (ISO 24730-61)
• DVR UWB sensors
• GPS tags
• WhereLAN sensors (ISO 24730)
• Magnetic beacons
Please check with Zebra for an updated list of supported sensors and technologies.
When deploying any of the above sensor types in your MWE solution, please obtain from Zebra the sensor
firmware version that is compatible with MWE 2.0 and the firmware upgrade procedure for each type of
sensor.
For example, WhereLAN sensors require firmware v.6.5.0 or later, while DVR sensors require firmware
v.5.2.1 or later. Firmware upgrades in these two types of sensors can be done using MWE’s Sensor
Analyzer tool. The procedure is explained in separate documentation.
NOTE: Newly manufactured WhereLAN sensors require firmware v.6.5.2 or later. If you are installing
WhereLAN sensors, use firmware v.6.5.2 regardless of manufacturing date. Do NOT use firmware v.6.5.1
or earlier on new WhereLAN sensors.
39
Configuring MWE
After completing the installation steps described in the previous sections of this document, there is several
configuration steps that need to be performed to have the system fully operational. These configuration
tasks are described in two separate documents:
• MWE Configuration Guide
This document describes configuration tasks that need to be done only once or seldom after installing
the software. These tasks include creating sites and site groups, uploading and calibrating site maps,
defining zones and zone groups, specifying location devices and algorithms to be used by the system,
and more. They system is fully functional after these configuration steps.
• MWE User Guide
In addition to describing the basic functionality of the web client for end users, this document also
includes configuration tasks that further customize the application or that are performed on a frequent
basis. These tasks include adding users and user groups, defining access permissions, defining
resource types, associating tags with resources, defining data filters, configuring the various reports
(columns displayed and column order), and more.
MotionWorks Enterprise Installation Guide
40
MotionWorks Enterprise Installation Guide
Upgrade from MWE 1.4 to MWE 2.0
Upgrading to MWE 2.0 is supported only for MWE 1.4.x. If you are running an earlier version of MWE, you
need to first upgrade to 1.4.x. Consult the MWE 1.4 Installation Guide on how to upgrade to MWE 1.4.
The upgrade script transfers some, but not all, data from the SQL database in MWE 1.4 to a mongoDB
database on the MWE Linux server.
The following data is transferred and available after the upgrade.
• Users, User groups and Group permission configuration
• Contacts
• Zones and Zone groups
• Tags associated with resources
• Resource Types
• Resources
• Named resource custom fields and their values.
This applies to custom fields that are named in the Configuration > Token Replacement Settings report
in the MWE web client. For example,
field that still has its default name, such as
transferred, since it is assumed that it is not in use.
~Object Custom1~ = Color, is transferred. However, a custom
~Object Custom2~ = Resource Custom2, will not be
The following data is not transferred and not available after the upgrade.
• The Zone and Zone Group columns in the Tags and Resources report are empty until the tags blink
again.
• Unassigned tags. This applies to tags not associated with a resource ID.
• Business rules (resource alerts). A script is provided to save all business rules to a file, which you can
use after the upgrade to manually add back the business rules.
• System Alert History data
• Resource custom properties with default token names.
Custom fields that still have the default name, such as
not transferred, since it is assumed that it is not in use.
• Assignment of recipients to system alerts. If you have assigned recipients to receive email system
alerts, that information is not transferred. You must manually re-assign recipients to system alerts after
the migration.
The following data stored in the Elastic Search database on the Linux server in MWE 1.4.1 remains
accessible after the upgrade.
• Tag blink history
• Zone change history
• Event history
~Object Custom2~ = Resource Custom2, are
Requirements
MWE 2.0 requires more memory and a better CPU on the Linux host than MWE 1.4. Without enough
memory and CPU resources, the upgrade may fail or MWE services could crash after the upgrade is
completed. Please review server requirements in Minimum Server Specs.
41
MotionWorks Enterprise Installation Guide
Before performing off-line upgrades, the MWE 2.0 installation script requires you to install the Red Hat /
CentOS package
package is not installed. You can check whether this package is installed by running the following
command.
# rpm -q policycoreutils-python
If the server has Internet connection, you can install this package by running the following command.
# yum install policycoreutils-python
policycoreutils-python
Pre-Upgrade Instructions
The off-line upgrade option does not require the Linux server to have Internet access at installation time.
The upgrade procedure involves copying a tar.gz file that is close to 7 GB in size to the MWE Linux server.
Due to its size, consider copying the file prior to a scheduled upgrade.
Before proceeding with the upgrade, verify that the requirements listed in Minimum Server Specs for the
MWE Linux Server are met.
Taking a Snapshot
Following best practices, capture a snapshot of your virtual machine before attempting the upgrade, just in
case you need to roll back.
on the Linux server. The installation script will exit if this
Stopping Services
1. Stop services on ZLA’s listed in the Appliances report.
2. Stop all services on the Windows Application Server.
42
MotionWorks Enterprise Installation Guide
Stop SQL Server Agent on the Windows server hosting SQL Server.
3.
IMPORTANT: Do not stop the SQL Server service.
If you cannot stop SQL Server Agent because doing so would impact other non-MWE databases
hosted on the same SQL Server host, you can just disable all MWE database scheduled jobs in SQL
Server Management Studio.
Backing Up Business Rules
If you have defined any business rules (resource alerts) in MWE, the upgrade script does not preserve
them. A script named
use the file to manually add back the business rules after the upgrade. If you have not defined any
business rules, you can skip this section.
copyBusinessRules.sh is provided to dump the rules configuration to a file. You can
1. Copy the provided copyBusinessRules.sh script to the /data directory on the Linux server.
2. Using Putty or another ssh client, log into the MWE Linux server as root and run the
copyBusinessRules.sh script using the following commands.
# cd /data
# ./copyBusinessRules.sh
The script generates the directory /data/saved-rules where each existing business rule is saved as a
JSON file.
Upgrade Instructions
You can perform an off-line upgrade or an on-line upgrade.
• The off-line upgrade option does not require the MWE Linux server to have Internet access at
installation time. Use the installation package
off-line upgrade. Since the file is close to 7 GB in size, it is recommended to copy it prior to a scheduled
upgrade.
• The on-line upgrade requires that the MWE Linux server have open access to the Internet at installation
time. Use the installation package
upgrade.
Copying and Extracting the Installation Package
mwe-containers-setup-2.0.n-online.tar.gz for an on-line
mwe-containers-setup-2.0.n-offline.tar.gz for an
1. Using WinSCP, or Putty, or a similar SSH client, copy the
mwe-containers-setup-1.4.n-offline.tar.gz installation package to the /data directory on the
Linux server.
2. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
43
MotionWorks Enterprise Installation Guide
Change the directory to
3.
# cd /data
4. Extract the files.
• For an off-line upgrade, enter the following.
# tar -xvf mwe-containers-setup-2.0.n-offline.tar.gz
• For an on-line upgrade, enter the following.
# tar -xvf mwe-containers-setup-2.0.n-online.tar.gz
A set of files is extracted.
NOTE: Sometimes copying a command from a document and pasting it into a Putty or Terminal window
does not work, as some characters may be misinterpreted. You may need to type some commands.
Running the Upgrade Script
1. Change the directory to /data/mwe_setup.
# cd /data/mwe_setup
2. Run the upgrade script.
• For an off-line upgrade, enter the following.
# ./mwe_setup.sh –-offline-upgrade
and extract the tar.gz file.
/data
• For an on-line upgrade, enter the following.
# ./mwe_setup.sh –-upgrade
3. When prompted, enter the number of sites this MWE installation will support.
If you are not sure, enter
1. MWE automatically adjusts this value as needed.
The upgrade script begins upgrading the Docker images.
4. When prompted, enter your login credentials.
These are the same admin account login credentials you use to login in to the MWE web client. You
can use the admin account or any other account in the MWE Administrator user group.
These login credentials are used by the upgrade script to log into SQL server and migrate the data in
the SQL db_MWE database to a mongoDB database on the MWE server.
NOTE: No characters are shown when you type the password. If you enter the wrong password, you
are prompted to re-enter the login credentials.
The upgrade/migration script runs for a few more minutes.
44
MotionWorks Enterprise Installation Guide
Once the upgrade is complete, press
5.
Running the Upgrade Again
When the migration script encounters some inconsistencies in the data being transferred from SQL server
to the mongoDB databases, it posts an error message and exits without completing the migration. If this
happens, use the following steps to run the upgrade again.
1. Check the details in the migration log
2. Correct the issue.
3. Run the upgrade script again using the following commands.
• If performing an off-line upgrade:
# cd /data/mwe_setup
# ./mwe_setup.sh –-offline-upgrade
• If performing an on-line upgrade:
# cd /data/mwe_setup
# ./mwe_setup.sh –-upgrade
to exit the upgrade mode.
Enter
/var/log/zebra/mwe/db_migration.log
.
If you encounter an issue you cannot resolve, restore the original MWE 1.4.x snapshot and contact Zebra
Product Support for assistance.
Validating the Upgrade
Once the upgrade script completes the upgrade, perform the following checks and validations.
1. Verify that all MWE Services are up and running by loggin into the MWE Linux server using Putty or
similar ssh client and running the
Depending on the resources (CPU and memory) on your server, it may take a couple of minutes for all
services to be up and running.
# su – mwe
# cd /data/mwe
# docker-compose ps
docker-compose ps command as mwe user.
45
MotionWorks Enterprise Installation Guide
The State column should display Up for all services, as shown in the following figure.
2. Login to the MWE web client as admin and verify or spot check the data in the following reports.
• Configuration/Contacts
• Configuration/Zone Settings
• Configuration/Resource Types
• Reports/Tags
• Reports/Resources
• Infrastructure/Site Manager/Configure zones
NOTE: If you get an error message when trying to open a report, clear your browser cache.
Restoring Login Accounts
After the upgrade script runs, the local admin account has full access to MWE reports and data entries.
However, you need to manually restore login for other accounts.
1. Log into the MWE web client as admin and go to the Users > User Groups page.
2. Select a User Group (check the checkbox on the left column).
3. Click the Edit Group link on the report toolbar.
4. Click Save in the Edit Group dialog window.
Repeat these steps for each User Group.
46
MotionWorks Enterprise Installation Guide
Upgrade from MWE 2.0.0 to MWE 2.0.1
If you initially installed the MWE 2.0.0 beta release and need to upgrade to the 2.0.1 production release,
you can follow the instructions in this section. You have an option between performing an off-line upgrade
or an on-line upgrade:
• The off-line upgrade option does not require the MWE Linux server to have Internet access at
installation time. For an off-line upgrade, use installation package
mwe-containers-setup-2.0.1-offline.tar.gz. This file is close to 7 GB in size, so it is
recommended to copy it prior to a scheduled upgrade.
• The on-line upgrade requires that the MWE Linux server has open access to the Internet at installation
time. For an on-line upgrade, use installation package
Taking a Snapshot
Following best practices, capture a snapshot of your virtual machine before attempting the upgrade, just in
case you need to roll back.
Copying and Extracting Installation Package
mwe-containers-setup-2.0.1-online.tar.gz.
1. Using WinSCP, or Putty, or a similar SSH client, copy the
mwe-containers-setup-1.4.n-online.tar.gz installation package to the /data directory on the Linux
server.
• For an off-line upgrade, use installation package
• For an on-line upgrade, use installation package
2. Using a Terminal window, Putty or some other SSH client, log into the MWE server using the root
account.
3. Change directory to /data and extract the tar.gz file:
# cd /data
4. Extract the file.
• If performing an off-line upgrade, use the following command.
# tar -xvf mwe-containers-setup-2.0.1-offline.tar.gz
• If performing an on-line upgrade, use the following command.
# tar -xvf mwe-containers-setup-2.0.1-online.tar.gz
You will see a set of files being extracted.
NOTE: Sometimes copying a command from a document and pasting it into a Putty or Terminal window
does not work, as some characters may be misinterpreted. You may need to type some commands.
mwe-containers-setup-2.0.1-offline.tar.gz.
mwe-containers-setup-2.0.1-online.tar.gz.
47
MotionWorks Enterprise Installation Guide
Running the Upgrade Script
1. Change the directory.
# cd /data/mwe_setup
2. Run the upgrade script.
• If performing an off-line upgrade, use the following command.
# ./mwe_setup.sh --offline-upgrade
• If performing an on-line upgrade, use the following command.
# ./mwe_setup.sh --upgrade
3. If prompted, enter the number of sites this MWE installation will support.
If you are not sure, enter
4. When prompted, press the ENTER key to exit upgrade mode.
Validating the Upgrade
When the upgrade is complete, check the status of the MWE services (Docker containers). Depending on
you server resources (CPU and memory), it may take a couple of minutes for all services to be up and
running.
1. Run the following commands.
# cd /data/mwe
# docker-compose ps
1. MWE automatically adjusts this value as needed.
48
MotionWorks Enterprise Installation Guide
Verify that the column State shows Up for all containers.
2.
Some services also report a health condition and should show healthy.
NOTE: You may see several warnings if you run the docker-compose command under the root account.
You can ignore these warnings. If you switch to the mwe account, you will not see these warnings.
# su - mwe
# cd /data/mwe
# docker-compose ps
To switch back to the root account use:
# su -
If your deployment includes a ZLA, upgrade the ZLA software from v.2.0.0-1 to v.2.0.1-1. See Upgrading
ZLA Software.
49
MotionWorks Enterprise Installation Guide
Reference Documents
• MWE 2.0 Configuration Guide
• MWE 2.0 User Guide
50
MotionWorks Enterprise Installation Guide
Appendix 1: Connecting to a Physical ZLA
Connecting to a Physical ZLA
A physical ZLA device has 4 Ethernet ports labeled MGMT, WAN, LAN1, and LAN2, providing optional
connections for remote management, a WAN (Wide Area Network) and two different LANs (Local Area
Network) respectively.
1. To connect a laptop to a ZLA for the first time to configure network parameters, power on the ZLA and
use one of the following methods:
• The LAN1 ethernet port on the ZLA is configured by default to acquire an IP address from a DHCP
server. Connect LAN1 to the network using an ethernet patch cable. Use PUTTY, WinSCP, or
another SSH client to connect to the default hostname ZebraZLA. If you know the IP address
assigned by the DHCP server, you can connect the SSH client to this IP rather than the ZebraZLA
hostname.
• The LAN2 ethernet port on the ZLA is configured by default with static IP 192.168.5.1. Configure a
laptop with an IP 192.168.5.x. Connect the laptop ethernet port and LAN2 to a hub using ethernet
patch cable, or alternatively connect the laptop ethernet port directly to LAN2 using an ethernet
crossover cable. Use PUTTY, WinSCP, or another SSH client to connect to 192.168.5.1 or to the
default hostname ZebraZLA.
• Connect a USB port on the laptop to the Console port on the ZLA using an Ethernet to USB cable,
or a USB to Ethernet adapter and an ethernet cable. Then bring up Putty (Serial mode) or a
HyperTerminal session on the laptop, and select a COM port (typically COM1 or COM3) to connect
to. See connection settings below.
2. If you are using Putty, select SSH and enter the ZLA IP address or default host name ZebraZLA.
51
MotionWorks Enterprise Installation Guide
Click Open. You will be prompted to enter a login account and password:
3.
You are now in a Linux command shell where you can issue commands and edit configuration files.
4. If you are using HyperTerminal (or Putty with Connection Type = Serial), select COM1 or COM3, and
use these settings.
This will give you access to a Linux command shell where you can execute commands and edit
configuration files.
If you are using WinSCP, you will have a graphical user interface similar to Windows Explorer. You can
open text configuration files for editing by simply double-clicking on them. You can also easily drag and
drop files between the Windows laptop hosting WinSCP and the ZLA.
52
MotionWorks Enterprise Installation Guide
Configuring IP Addresses
The diagram below shows two possible ways of connecting a ZLA to the Location Sensors and to the
MWE servers.
Remember that the ZLA Ethernet card connecting to the sensors (LAN1 in the examples above) must be
assigned a static IP address.
The operating system on a ZLA is CentOS Linux, so in what follows we will be using some common Linux
commands.
1. To view a list of Network Interface Cards (NICs) installed on the ZLA and their state, use the # nmcli d
command. An example is shown in the figure below:
The mapping between the NICs device names assigned by Linux and the Ethernet ports on the front of
the ZLA box, are as follows:
enp37s0: LAN1
enp38s0: LAN2
enp43s0: MGMT
enp44s0: WAN
53
MotionWorks Enterprise Installation Guide
To view the current configuration of the Ethernet cards, use the
2.
$ ip address
command.
In the example below, the output of the ip address command shows that the interface named enp37s0
has IP 10.21.2.59 and the interface named
enp18s0 has IP 192.168.30.247.
The corresponding NIC configuration files for the four NICs in the ZLA are found in the
/etc/sysconfig/network-scripts directory and are named ifcfg-enp37s0, ifcfg-enp38s0,
ifcfg-enp43s0, and ifcfg-enp44 respectively. The following screenshot shows these four files as
displayed by WinSCP.
In our example, the contents of
ifcfg-enp37s0 (for LAN1 port) and ifcfg-enp38s0 (for LAN2 port) are
shown below:
54
MotionWorks Enterprise Installation Guide
NOTE: ifcfg-enp37s0 is configured for dhcp while ifcfg-enp18s0 is configured with a static IP.
3. You can modify the NIC’s configuration by directly editing the above files using the Linux vi command,
or the WinSCP tool, or another command or tool of your choice.
Applying Your Changes
After modifying the NIC’s configuration files, use the following command to restart the network service for
the changes to take effect.
# systemctl restart network
55
www.zebra.com
Loading...