Gateway Guide
SAFEQ Cloud uses a gateway (secondary server) on the customer site to route traffic securely between the primary server and printers. Using a local gateway, the document data itself does not have to leave the company network, increasing security, responsiveness and reducing Internet bandwidth. The gateway can be compared to a network router, and similar simple devices routing data.
The Gateway is simply installed on a prepared hardware or software appliance using the SAFEQ Cloud installer.
This Gateway Guide contains all information needed to have a fully working gateway, including hardware recommendations, appliance preparations and installation guidelines.
After the installation, perform Secondary Gateway mapping.
Different Gateway options
The gateway can be installed on a hardware appliance, a software appliance or on existing server infrastructure. You can also choose to use only the SAFEQ Cloud Client as a Gateway.
Hardware Appliance — A hardware appliance can be a new dedicated appliance for routing print traffic, comparable to an internet router. For YSoft OMNI Bridge device, see Setting up OMNI Bridge.
Software Appliance — The virtual software appliance is a pre-configured virtual machine image, ready to run on a hypervisor such as VMWare ESX, Xen or Hyper-V or similar Infrastructure-as-a-Service solutions.
Existing Server Infrastructure — The gateway can run in a virtual environment on existing server infrastructure.
In preparation of the installation, the following pre-requisites have to be verified:
- No Firewall is blocking outbound communication on defined TCP ports to the Primary server in the Cloud. See the Ports and Protocols section Server to Server.
- No Proxy server filtering outbound communication to the Primary server in the Cloud. The gateway needs a direct connection to the Primary server as it creates a secure channel (TLS 1.2) that a proxy cannot handle
Secondary Gateways Metrics Collection
Understanding what data is collected from secondary gateways, why this information is gathered, and how telemetry can be managed is important for maintaining transparency and control. This overview details the specific metrics monitored to ensure optimal system performance, explains the purpose behind collecting this data, and outlines the available options to configure telemetry settings according to your preferences.
Please note that this feature is currently available only in certain regions, and may not be accessible everywhere at this time. Availability varies depending on your deployment region.
Data Collected
The following metrics are retrieved from each secondary gateway to monitor system health and performance:
Customer domain
Secondary gateway version
Uptime duration
Gateway name
Authentication success and failure rates
Authentication process duration
Print success and failure rates
Printing process duration
JVM memory (RAM) usage
JVM CPU utilization
Storage requests per minute (covering storing, deleting, and retrieving documents)
Configuration
You can control whether telemetry data is sent by accessing the Server information page for the selected secondary gateway. The available options are:
None: Telemetry is completely disabled, and no data is collected or transmitted.
Logs: Metrics are stored locally on the gateway, with no external transmission.
Live: Data is transmitted continuously to the endpoint for live monitoring.
The collected data is automatically transmitted to a secure endpoint at https://pushprox.prod.eu-west-2.ysoft-stats.com/ only if the telemetry option is set to Live. When this setting is enabled, data is sent continuously and in real time, allowing for immediate monitoring and analysis of gateway performance across regions. This facilitates quick detection of issues, trend analysis, and proactive management.
We want to assure you that no private or personally identifiable information is collected through this process. This means usernames, document names, document contents, or any other sensitive data are not included. The data collected is solely focused on system performance metrics, ensuring transparency while prioritizing your privacy and data security.