Installation guide

Chapter 3 – Managing Zebra Printers with MSP -- 13
Table 1
13. In the MSP Console UI, go to Control > Collection Requests and create a Collection
Request for the appropriate *DCC.xml file (Data Collection Category) which will collect
data from the Zebra Printer for the appropriate *DCM.xml files (Data Collection Metric).
Creating Packages for the Zebra Printer
Overview
In the past, the act of configuring a Zebra Printer required the use of a separate Zebra application
like Label Vista and a serial cable. Now, a one time network configuration needs to be performed
before MSP and the Zebra Printer MSP Proxy Plug-In can provide a means to configure
supported Zebra Printers by creating packages specifically for the Zebra Printer MSP Proxy Plug-
In. These packages can be added to a bundle and provisioned to one or more supported Zebra
printers without having to use a serial cable.
This chapter explains how to create the files necessary to configure, to print to, or to update a
Zebra Printer. The created files or the files provided by Zebra will be added by to a package by
MSP Package Builder.
Important:
An MSP Package for a Zebra Printer will contain files that must have specific extensions and the
content must be in a specific format. The file extensions with special meaning to the Zebra Printer
MSP Proxy Plug-In are “.manifest”, “.settings”, “.hex”, and “.cmd”.
Each Package must contain a .manifest file and there can be only one per Package. The manifest
file will list all the other files contained in a Package.
Manifest File
A “.manifest” file lists all the files that should either be processed by the Zebra Printer MSP Proxy
Plug-In or sent to a supported printer. There should be one file per line in the manifest file.
Each manifest file can list only one “.settings” file, or one “.hex” file, or one “.cmd” file. In addition,
the “.settings”, “.hex” or the “.cmd” file must be the last line of the manifest file if the “.manifest”
file contains other file types.