01
No: the Java runtime is already included in the package
The native Nebulas Print Client packages already include the Java 17 runtime the application needs, so no manual installation is required from the user or the IT team.
This avoids a technical step that often creates friction for people working in sales, back-office, or customer support roles who simply need to print documents arriving from the business system.
02
How the client connects the business system and the printers
Steps
- The client is the desktop agent that securely connects Nebulas Cloud Printing to local print queues.
- It opens outbound HTTPS connections to the Print Gateway, without requiring inbound connections into the company network.
- The current version processes PDF documents and sends the job to the local queue indicated by the business system.
- Tray, paper size, and other hardware preferences are configured in the operating system's print queues.
03
What to have ready before activation
Prerequisites
- A Nebulas User account with the Cloud Printing module active.
- The correct package for the workstation connected to the printers, downloaded from the official release.
- An operating system queue configured for each tray and paper size combination needed.
04
A hypothetical case: the sales team printing quotes
Hypothetical case: a sales team receives PDF quotes from the business system and needs to route them to two printers with different paper sizes, one for standard documents and one for special formats. The IT team downloads the package for that workstation, installs it without having to manage Java separately, and configures two operating system queues, one for each tray and paper size combination needed.
05
What to check after activation
- The client applies controlled retries and automatically resumes if the internet connection drops.
- Each device's authorization is periodically verified and can be revoked centrally by the IT team.
- Revoking a PC stops polling and heartbeat with the service.
06
What the company can configure with Nebulas Print Client
Launcher and MSI installer are signed and verified in the release pipeline, so the IT team can confidently distribute the client across multiple workstations connected to physical printers.
For technical evaluation on macOS, packages not yet notarized with an Apple Developer ID are available, useful for controlled testing before a broader rollout.
07
Practical sequence to activate the client
Steps
- Check that the account has the Cloud Printing module active.
- Map in advance the tray and paper size combinations needed by the connected printers.
- Configure a queue in the operating system for each combination identified.
- Download and install the official package for the workstation: the Java runtime is already included.
- Send a test PDF from the business system and verify it reaches the correct queue.
08
Next step
If a team manages multiple workstations connected to different printers, it helps to define the full list of tray and paper size combinations first, so activating the Print Client on each workstation only takes one configuration pass.
FAQ
Frequently asked questions
Do I need to install Java separately on the workstation?
No. The native Nebulas Print Client packages already include the necessary Java 17 runtime, so no additional manual installation is needed.
Does the client open ports in the company network to work?
No. The client only opens outbound HTTPS connections to the Print Gateway and does not require inbound connections into the LAN.
What happens if there's no internet connection during printing?
The client pauses the cycle, applies controlled retries, and automatically resumes as soon as the service becomes reachable again.
✓