| Table of Contents |
|---|
Summary
Network printing configurations are made possible through the use of a .properties file that the ClinSpark Agent reads from. When a list of printers are displayed to users in ClinSpark, the Agent will provide networked printers based on the configuration in the properties file.
Depending on the version of the ClinSpark Agent being used, the location and management of this properties file will vary across workstations. Customers are encouraged to first read this help guide to gain an understanding about the properties file before proceeding with modification for network printing use cases.
Prerequisites
Network printing capabilities are supported using Agent version 1.2.2, or, 1.4.1 or greater. Customers using Agent version 1.3 will need to update to 1.4.1 or greater to utilize this feature.
...
Network printing works best when using a direct network (RJ45) connection to a Zebra printer with a built-in network card. Other methods of network printing such as Windows based ‘print servers’, printer sharing, LPD, SMB, CUPS and others are not currently supported.
Setup
The ClinSpark Agent will use printers that are configured in the Agent properties file.
...
Once the properties file has been updated, users must stop and then restart the Agent in order for the changes to take affect. The simplest way to accomplish this is to right click the Agent tray icon, close the Agent, and then re-open the agent by using the ClinSparkAgent.exe executable file in the installation directory. Alternately, users can restart their PC.
Example
Here is an example of a properties file with a single networked printer, configured via IP address:
...
The name of the printer is what is displayed to users in the ClinSpark user interface. The IP address will not show. For example, if a printer defined as ClinSpark PK Lab - 192.168.100.102 in the properties file, in ClinSpark, it will show to users as ClinSpark PK Lab.
Demonstration
...
Sharing configurations across PCs
Customers that use Agent version 1.5.0 or greater across their workstations can utilize certain environment variables to establish a location where a ‘shared’ properties file is read from. For example, an environment variable could point to a shared/network drive that could be referenced across one or more PCs configured with the same variable. This will allow site IT groups to need only manage a single properties file with all available network configurations that all workstations can reference for ClinSpark use. For more details about this is possible, see this help guide.
Notes
When editing the properties file with Notepad, changes must be done by a user with Administrative privileges. User may see a message like this on save if they do not have proper permissions:
...