Print Server Manager

The Print Server (service) can run multiple automation components, including REST API Servers and File Triggers.

REST API Servers – print labels and perform other tasks via HTTP requests.
File Triggers – print labels and perform other tasks when specific files are modified or when new files appear in a defined folder.

You can set up multiple REST API Servers (on different ports) or configure several File Triggers to monitor different files or folders.

Use the Print Server Manager to:

Start or stop REST API Servers and File Triggers
Configure automation settings for each server or trigger
Create or delete REST API Servers and File Triggers
View logs and activity statistics

To launch the Print Server Manager, open the Start menu in Windows and select AzureLabel Print Server Manager.

Alternatively, you can use the printServerManager command-line command.

Start and Stop REST API Servers and File Triggers

To start a REST API Server or File Trigger, go to the Triggers > State tab and click the Start button. To stop it, click the Stop button.

Create a REST API Server or File Trigger

To create a REST API Server or File Trigger, go to the Triggers > Configuration tab, click the Plus button, and select the desired component type.

Optionally, set a Name and/or Description. The Name will be used throughout the interface — including in the status dashboard, logs, and statistics — to identify this component.

Configure a REST API Server

In the Triggers > Configuration tab, select the REST API Server you want to configure.

Properties

Switch to the Properties tab and adjust the necessary settings.

Enabled – disable this component by unchecking the flag.
Log input data – if enabled, all incoming data will be saved to the log.
Port – the port on which the server will listen for requests.
Log API requests – if enabled, all API requests will be saved to the log.
Reject requests with an empty or invalid API key – if enabled, any request with an empty or unrecognized API key will be rejected.

To apply the new configuration, you need to save and upload it to the Print Server. Click Save Configuration, then click Upload Configuration to Print Server.

Actions

On the Actions tab, you can add various actions to be triggered after each request. Actions can be configured with conditions.

Configure a File Trigger

In the Triggers > Configuration tab, select the File Trigger you want to configure.

Properties

Switch to the Properties tab and adjust the necessary settings.

Enabled – disable this component by unchecking the flag.
Log input data – if enabled, all incoming data will be saved to the log.
Print Data Source – defines which source will be used as the print data for the labels.
- JSON File(s) with Ready-to-Use Data – a single JSON file that includes the label, data, and print settings, ready to be printed.
  
  The file must be in JSON format as described in the "Request body" section of the "/labels/print" endpoint in the REST API documentation.
  
  In addition, one extra field must be included in the JSON:
  
  "request": "<Endpoint>"
  
  where <Endpoint> refers to the REST API endpoint, such as: "request": "/labels/print".
  
  Example JSON file:
```
{
    "request": "/labels/print",
    "label": "My label",
    "printData": {
        "source": "ready",
        "data": [
            {
                "PrintQuantity": 3,
                "Name": "AzureLabel Pro, yearly subscription",
                "Barcode": "5678901234562",
                "Price": 69,
                "Unit": "ea",
                "Code": "pro-y"
            },
            {
                "PrintQuantity": 1,
                "Name": "AzureLabel Corporate, yearly subscription",
                "Barcode": "8901234567890",
                "Price": 102,
                "Price2": 95,
                "PriceOld": 110,
                "Unit": "ea",
                "Code": "corp-y"
            }
        ]
    }
}
```
- Label's Import Settings – uses the label’s built-in import settings as the print data source. You can configure and test the import settings in the Designer, then use the label here. Before printing, data will be imported using the label's import settings.
- Shared Import Settings – uses import settings from a specified location as the print data source. You can configure and test these settings in the Designer, then use them here. Before printing, data will be imported using the specified import settings.
Detect a specific file or set of files in the selected folder:
- If the selected Print Data Source is JSON File(s) with Ready-to-Use Data, specify one or more JSON files whose modification will trigger label printing or other actions. Alternatively, you can specify a folder — any new file appearing in it will serve as a trigger.
  
  You can use wildcard characters ? and * to match multiple files, or define a folder directly.
  The server will process each file that matches the defined pattern.
- If the selected Print Data Source is Label's Import Settings, specify a label file.
  The file defined in the label’s import settings on the Connection tab will be monitored — its modification will trigger printing.
- If the selected Print Data Source is Shared Import Settings, specify an import settings file.
  The file defined in the import settings on the Connection tab will be monitored — its modification will trigger printing.

To apply the new configuration, you need to save and upload it to the Print Server. Click Save Configuration, then click Upload Configuration to Print Server.

Actions

On the Actions tab, you can add various actions to be triggered after each file trigger event. Actions can be configured with conditions.

On this page