Skip to main content
Skip table of contents

Basic Information

The guide is intended for administrators, as it describes the installation and administration of a MyQ Roger tenant. You learn how to log in to your MyQ Roger tenant, how to manually create, import, and edit users, how to modify device and security settings, and how to establish the connection between your MyQ Roger tenant, your MFDs and your smartphones.

The below server technologies are used in MyQ Roger. They are maintained by MyQ and are automatically included when upgrading to new versions:

  • ASP.NET Core REST API technology.

  • Angular front-end compiled to JavaScript which runs on the client browser side.

  • Hosted in Azure and orchestrated by Kubernetes, which provide plenty of abilities like:

    • Scalable solution - The MyQ Roger instances run in virtual machines (Docker). They are continuously monitored by an automatic scaler. When the CPU or memory trigger the set limits of the load, it automatically adds a new instance to the new virtual machines. The net traffic also affects the CPU load. The Load Balancer automatically directs any incoming requests to less loaded instances.

    • Regional hosting - The application is designed to have tenants in a standalone database. This is great for any regional independent hosting. To reduce and minimize the distance latency, it is possible to run it from any region available in Azure.

    • Monitored solution - The solution is continuously monitored.

    • Static files CND distribution - The MyQ Roger set of web static files has more than 10MB. To provide the best user experience, Content Network Distribution is used to distribute those static files across the world.

Prerequisites before the installation

  • An account with administrator rights to the MyQ Roger tenant.

  • Make sure that the https port 443 is allowed in the firewall.

  • Make sure that TCP outgoing traffic to the internet is allowed on the device.

Make sure your SNMP settings are correct to avoid printing disruptions.

Communication ports and protocols

PC / MyQ Roger Client (MRC)

Target

Protocol, Port

Description

MyQ Roger Server
https://eu.roger.myq.cloud
https://us.roger.myq.cloud
https://discovery.myq.cloud/regions

HTTPS, 443 | TLS secured

MyQ Roger Client authentication

User authentication

Reporting jobs

Event Bus

AMQP, 5671 | TLS secured

Events Release, Delete, etc.

Printer

SNMP, 161,162

Get machine Serial Number to confirm a job release target

Printer

Raw, 9100 | IPPS, 10012

Job release / printing

Printer

Target

Protocol, Port

Description

MyQ Roger Server
https://eu.roger.myq.cloud
https://us.roger.myq.cloud
amqps://eu.amqp.myq.cloud
amqps://us.amqp.myq.cloud
https://discovery.myq.cloud/regions

HTTPS, 443 | TLS secured
amqps, 5671

MyQ Roger authentication

General communication

Print and scan jobs

MyQ Roger Mobile App

Target

Protocol, Port

Description

MyQ Roger Server
https://eu.roger.myq.cloud
https://us.roger.myq.cloud
https://discovery.myq.cloud/regions

HTTPS, 443 | TLS secured

Authentication, general communication, print and scan jobs

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.