Zebra DevTalk | Testing Exported XML before EMM Deployment via OEMConfig | Feb. 2021

Submitted by Stacey Kruczek on
1 MIN READ

This session will cover the process of exporting raw XML from StageNow, testing it on a Zebra device using a simple helper utility and subsequently deploying to a device via the OEMConfig feature now available in most EMM tools including SOTI, Airwatch/Workspace One, Wizy etc. The target audience is both developers and systems/support personnel but it does not require any programming knowledge in order to use these techniques.

API Marc Test

API Marc Test - API Display Title
API Marc Test - API Secondary Heading

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

API - Technical Name 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

API - Technical Name 2

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

API - API Use Cases Title

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Pkg Bundle Title
Pkg Title

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

VisibilityIQ Newly Added Devices

Newly Activated Devices
Effectively Manage Device Deployment

Customers rolling out new device deployments often must verify the ROI of their new deployment. Tracking when devices are set up at a site and when they enter active operations, leveraging the VisibilityIQ utilization algorithm, allows managers to track against SLA and ROI metrics. Service providers and customers also can manage and optimize the workflow of devices returning from repair and entering back into use.

 

Requirements
  • Mobile device model and Android version are supported for the Mobile Computer Device Health APIs
  • Zebra Data Services (ZDS) agent is installed and activated on the Mobile Computers
  • Zebra Printers are running Link-OS 4.0 or above, i.e. firmware version X.20.01Z or later
  • Zebra Printer Connector (ZPC) agent is activated on the Printers
  • Devices have been enrolled and authorized for Zebra Savanna
Getting Started
  • To purchase, contact your Zebra Account Manager
  • Questions? Check the FAQ
  • Visit the Forums

 

Authentication

A Zebra Savanna application key is required for using and testing this API. See the Getting Started Guide

Newly Activated Devices in Action
  • First Seen Date timing correlates when a device was received at a site, unboxed & hooked up
  • First Used Date can be used when tracking ROI of device purchases and rollouts
  • Customers can review devices in repair to identify how quickly they returned to the location, when they were turned back on, and were back in service
  • Verify device deployment is on track
  • Identify the site locations where devices were newly activated

VisibilityIQ WLAN Signal Strength

WLAN Signal Strength
Identify areas with low WLAN signal strength

This per-site view of WLAN signal strength range allows users to discover trouble spots, access points, or devices by site to increase device connectivity and worker productivity. Discover changes in signal strength over time to address declining performance or changes in access point and device connectivity.

Requirements
  • Mobile device model and Android version are supported for the Mobile Computer Device Health APIs
  • Device has been enrolled and authorized for Zebra Savanna
  • Zebra Data Services (ZDS) agent is installed and activated on the device
Getting Started
  • To purchase, contact your Zebra Account Manager
  • Questions? Check the FAQ
  • Visit the Forums

Authentication

A Zebra Savanna application key is required for using and testing this API. See the Getting Started Guide

WLAN Signal Strength in Action
  • IT or Operations Managers can improve device connectivity across a site and reduce gaps in coverage
  • IT and Operations can receive notifications of unexpected reports of poor signal strength to streamline fixes

VisibilityIQ Battery Swap Activity

Battery Swap Activity
Effectively manage device roll-outs

Keep workers focused on their tasks rather than swapping batteries in their Zebra Android devices by tracking how frequently devices have batteries changed across an entire enterprise, each site, or even at the device level. Swap Activity irregularities highlight problems with battery health, charger functionality, or business process efficiencies.

Requirements

   

  • Mobile device model and Android version are supported for the Mobile Computer Device Health APIs
  • Device has been enrolled and authorized for Zebra Savanna
  • Zebra Data Services (ZDS) agent is installed and activated on the device
Getting Started
  • To purchase, contact your Zebra Account Manager
  • Questions? Check the FAQ
  • Visit the Forums

Authentication

A Zebra Savanna application key is required for using and testing this API. See the Getting Started Guide

 

Battery Swap Activity in Action
  • Make sure number of battery swaps aligns with business process to identify bad batteries, chargers, or process
  • Flag patterns that indicate batteries are not being charged long enough before put in a new device
  • Catch when chargers are no longer working or when devices are not properly put in chargers
  • Identify batteries with health issues not lasting a full shift

OAuth - Access Management

Access Management

The Access Management endpoints are for validating, refreshing, and revoking access tokens.

Getting Started

To use the OAuth APIs, you must first add them to your App in the developer portal.

Use Cases

The Access Management endpoints can be used with any of the grant types:

  • Client Credentials
  • Device Authorization
  • Authorization Flow

OAuth - Authorization Code with PKCE

production
production == Taxonomy term: Publication Status (field_publication_status) title

The Asset Ownership Service (AOS) allows a user to see what devices they own that have been enrolled in Zebra Data Services. 

The Barcode Generator API generates 1D or 2D barcode images that can be printed or scanned across 103 barcode types like QR Code, UPC, Code 128, and Data Matrix.

The Electronic Temperature Sensor APIs enable the creation of workflows that supports maintaining product stability, effectiveness, and quality.

Enterprise business offerings include Order, repair and case management capabilities for Zebra Customers

Automate the access and delivery of LifeGuard OS updates within your UEM/EMM by using Zebra's Lifguard OTA services.

Send a file to a Zebra Link-OS printer. The file can be a print job, configuration, firmware or font file.

Obtain a list of tenants that you can access.

Improve operations and optimize device fleets by providing actionable intelligence on device health, availability, utilization, and support.

OTA Update Delivery v3.0

OTA Update Delivery v3.0

Overview

The LifeGuard OTA Update Delivery application provides the ability for an Enterprise Mobility Management (EMM) server to control the enrollment and deployment of the 'last mile' delivery of Operating System (OS) updates to Zebra mobile devices.

To update the device, the EMM first determines what software is on the device by reading the Build ID from the device. This is performed by requesting detailed device information from the client. The BuildID is a critical value that can be used to compare the OS version running on the device to the newest version available.

The current standard for the BuildID allows the EMM to identify:

  • Baseline OS version
  • Patch version
  • Google Mobile Services (GMS) vs. Non Google Mobile Services (NGMS)
  • Android flavor
  • STD - standard vs. non-standard
Requirements
  • Use of the last mile OTA APIs is limited to ONLY authorized EMM clients.
  • The device must be properly enrolled. See the Zebra Device Enrollment Step by Step Guide for more details.
  • Devices must be running Android Nougat or higher.
  • A valid authorization bearer token has been obtained.
  • A valid access token has been obtained.
Authentication

A Zebra application key is required for using and testing this API. See the Getting Started Guide for instructions on obtaining a key.

Related Information

Refer to the Release Notes for details.

The Zebra OTA API Integration and Troubleshooting Guide can be found here.

The Zebra OTA API Developer Guide can be found here.

Information for the End User

The EMM is responsible for instructing the end user how to configure their devices for device enrollment. See the Zebra Device Enrollment Step by Step Guide for more details.