Hardware Requirements

Size: px

Start display at page:

Download "Hardware Requirements"

Helen Dickerson
6 years ago
Views:

1 6 /... / Requirements Hardware Requirements Approved The recommended configuration should handle up up to 200 devices connected to server or up to devices in combination with Client Based Print Roaming. Server deployment Components Recommended configuration Single Server Deployment (Management server with FlexiSpooler in spooling server mode) Management, Spooler Controller, Terminal Server, WPS, FlexiSpooler : Mobile Print Server, YSoft Payment System Dual Core 2GHz or faster processor 8GB free RAM 1Gbps network connection (LAN) 100GB of free disk space (after installation) Connection to storage with a throughput of at least 150MB/s and 300 IOPS Site server with FlexiSpooler in spooling server mode Management, Spooler Controller, Terminal Server, FlexiSpooler (in spooling server mode), WPS : Mobile Print Server Dual Core 2GHz or faster processor 8GB free RAM 1Gbps network connection (LAN) 100GB of free disk space (after installation) Connection to storage with a throughput of at least 150MB/s and 300 IOPS

2 Server deployment Components Recommended configuration Site server with FlexiSpooler in non spooling server mode (CBPR) Management, Spooler Controller, Terminal Server, WPS : Mobile Print Server Dual Core 2GHz or faster processor 8GB free RAM 1Gbps network connection (LAN) 20 GB of free disk space Connection to storage with a throughput of at least 150MB/s and 100 IOPS Workstation deployment Components Recommended configuration Client Components with FlexiSpooler in spooling mode Client Components with FlexiSpooler in proxy mode Deskop Interface, Universal Print Driver, FlexiSpooler (in client spooling mode) Deskop Interface, Universal Print Driver, FlexiSpooler (in client nonspooling mode) Dual Core 2GHz or faster processor 4GB free RAM 1Gbps network connection (LAN) 2GB of free disk space (after installation) Dual Core 2GHz or faster processor 4GB free RAM 1Gbps network connection (LAN)

3 6 /... / Software Requirements server requirements Approved Supported operating systems Operating System Management Server/Site Server Mobile Print Server YSoft Payment System Microsoft Windows Server 2008 SP2 64bit Microsoft Windows Server 2008 R2 SP1 64bit Microsoft Windows Server bit Microsoft Windows Server 2012 R2 64bit Supported databases Component 6 Management Server 6 Site Server Payment System Supported data engine PostgreSQL 9.4 embedded or standalone Microsoft SQL Server 2012 (SP2/SP3)/2014/2016 Standard or Enterprise Edition, 32 bit or 64 bit No database required (internal persistent cache). PostgreSQL 9.4 embedded or standalone Microsoft SQL Server 2012/2014/2016 Express edition Microsoft SQL Server 2012 (SP2/SP3)/2014/2016 Standard or Enterprise Edition, 32 bit or 64 bit Database sizing Example based on real customer data (10 million pages per month): Management Database: 16 GB per SafeQ server

4 Database settings and configuration provides automated database maintenance tools. Scheduled database maintenance is strongly recommended. The following configuration is required for different database s. Common settings : Login credentials for access, with ownership rights to its database Collation case insensitive Reliable low latency network connection (if the DB server is on another server) Microsoft SQL Server configuration : Correct collation: Case Insensitive and Accent Sensitive (language_ci_as) where applicable The user that uses to connect to the databases must have the default language set to English (but not British English) in the SQL Server Enabled TCP/IP connection or named pipes Enable Simple recovery model Connecting to SQL server that requires encrypted connection is supported, however requires several manual steps (see comments). To install 6 the following database role is required: db_owner and following server role is required: securityadmin. To update/upgrade 6 the following database role is required: db_owner and following server role is required: securityadmin. To run 6 the following database roles are required: db_datareader, db_datawriter, db_ddladmin, db_accessadmin, db_securityadmin and following server role is required: securityadmin. In case that you are going to use the external MS SQL server with named instance, you will need following to be allowed between SafeQ server and MS SQL server: a) UDP, both directions, local port on MS SQL server is This communication is used to query the SQL server (its SQL Browser service). The SQL Browser service will respond and inform the requester about the port it shall connect to via TCP. b) TCP communication, direction from SafeQ to SQL, port "random". The port number is dynamically assigned by the SQL Browser service ( PostgreSQL configuration : UTF 8 collation 9.4 version only Non local admin account for running PostgreSQL system service (Windows OS) To install, update or run 6 Management Server database user postgres must have superadmin role.

5 6 /... / Architecture Overview Network Communication This page provides a complete list of the ports and protocols that must be enabled on firewalls in order to ensure 6 system functionality. Network Communication Overview Workstation to server communication (server inbound rules) Required? Type Port Communication data volume Description (communication from the user) Mandatory TCP 80/443 HTTP/HTTPS For access to the administration/reporting web interface Mandatory TCP 9090/9443 HTTP/HTTPS For access to the End User UI web interface (if using a workstation client) (If spooling on a server) TCP 9100 proprietary compressed 10 kb 1 GB per print job TCP 515 LPR 10 kb 1 GB per print job Job reception from client workstations (TCP/raw communication) Job reception from client workstations (LPR) /Recommended (monitoring only) /Recommended (monitoring only) /Recommended (monitoring only) /Recommended TCP JMX Management Service system health monitoring via JConsole Configurable by the cmljmxserverport property in YSoft SafeQ system settings. TCP 9696/9002 JMX Management Service LDAP replicator system health monitoring via JConsole TCP 9898 JMX SpoolerController system health monitoring via JConsole SpoolerController only: Configurable by the orsjmxserverport property in system settings TCP 9999 JMX SpoolerController group system health monitoring via JConsole (monitoring only)

6 Required? Type Port Communication data volume Description (communication from the user) /Recommended TCP 9000 JMX Management Service auxiliary internal port used by JMX server Management service only: Configurable by the jmxrmiserverport property in YSoft SafeQ system settings /Recommended /Recommended (If spooling on a server) Mandatory on Site server TCP JMX The SpoolerController group service auxiliary internal port used by JMX server TCP 4000 HTTP/HTTPS Communication between Terminal Server and Workflow Processing System TCP 5559 YMQ Communication between Non spooling FlexiSpooler and Spooling FlexiSpooler TCP 5555 YMQ Communication between FlexiSpooler (and its Desktop Interface) to Spooler Controller a FlexiSpooler shared folder TCP UDP 137/ /138 SMB Shared folder for uploading jobs Server to Printer Communication (Server Outbound Rules) Required? Type Port Communication data volume Description (communication from the user) (required with server spooling) TCP 631/80 IPP Jobdata delivery to printer (IPP) (required with server spooling) (if using print data encryption) (if using print data encryption) TCP 9100 RAW 10 kb 1 GB per print job TCP 80/443 IPP/SSL 10 kb 1 GB per print job TCP 9100 proprietary SSL 10 kb 1 GB per print job Job data delivery to printer (Raw TCP) Job data delivery to printer (IPP over SSL) Job data delivery to printer (compressed via Terminal Professional) UDP proprietary broadcast (only within one subnet) Terminal Professional/UltraLight discovery

7 Required? Type Port Communication data volume Description (communication from the user) TCP 4095 proprietary Terminal Professional/UltraLight remote configuration embedded terminals TCP 50001/50003 proprietary WS SSL (KM, Xerox, Sharp) remote configuration Ricoh TCP 80, 443, 8080, proprietary Ricoh installation and automatic configuration used by RXOP libraries Ricoh configuration online print/copy tracking Toshiba Xerox/Fuji Xerox UDP 161 SNMP Online accounting of network printer MFD TCP 49629, HTTP/HTTPS Toshiba installation TCP 80, 443 HTTP/HTTPS Xerox/Fuji Xerox installation Konica Minolta TCP 80, HTTP, proprietary WS SSL Konica Minolta installation Sharp Samsung Terminal installation TCP 80 HTTP Sharp installation TCP 80 HTTP Samsung installation UDP 161 SNMP Terminal installation MFD check Printer to server communication (server inbound rules)

8 Required? Type Port Communication data volume Description (communication from the user) (if using time synchronization with a Terminal Professional or Payment machine) UDP 37 Time protocol Time synchronization between a Payment machine and the server. When the system parameter timeserverenable is enabled, the server is listening on UDP port 37. The terminal connects to this port upon restart. Ricoh TCP 5012, 5021, 5022 HTTP/HTTPS Accounting and charging Terminal Application communication YSoft SQTA or Browser (Sharp) TCP 5021, 5022 HTTP/HTTPS Terminal Application communication KM TCP WS SSL low volume, low latency Terminal (KM) authentication and session control HP Toshiba Network Card Reader (if using scan via SMTP) TCP 5025 HTTP/HTTPS Webservices for Terminal (HP) TCP 389 LDAP Internal LDAP for Toshiba When 389 is blocked (by an already running AD on a domain controller), 6 installer will display a warning and use 390 port instead TCP 5011/5012 Proprietary SSL Network Card Reader authentication TCP 25 SMTP Scanning from MFDs via (optional, depending on MFD capabilities) WebDAV scanning TCP 443 Secured WebDAV/HTTPS Scanning from MFDs via scan workflow (optional, depending on MFD capabilities) (if using scan via SMB) embedded terminal scanning TCP 139 SMB Scanning from MFDs via scan to folder (optional, depending on MFD capabilities) TCP 21 FTP Scanning from MFDs via scan to folder (optional, depending on MFD capabilities)

9 Required? Type Port Communication data volume Description (communication from the user) Passive FTP transfers (for embedded terminal scanning) TCP >1023 FTP Range of ports for passive FTP transfers (optional, depending on setting, configurable by ftppassiveports ) Mandatory TCP 5555 proprietary 1 kb per request Communication between Spooler Controller, Terminal Server and Payment System Inter server communication (inbound and outbound rules) Required? Type Port Communication Description (communication from the user) Management Service cluster SpoolerController TCP 4099 Management Service > Management Service proprietary ~1kB per print job TCP 6010 SpoolerController > Management Service proprietary ~40 60 kb per print job Application level cluster synchronization Spooler Controller to Management Service communication and synchronization Mandatory TCP 5556 TerminalServer > SpoolerController proprietary Terminal Server (TS) component (required for Terminal support), communication with server application job roaming load balancing TCP 8000 SpoolerController > Management Service TCP 6020 Management Service > Management Service Job data transfer for roaming jobs (uncompressed) Internal communication between Management Service instances near job roaming UDP Multicast configurable SpoolerController > SpoolerController Near Roaming Group synchronization. roaming groups with 10+ SpoolerController servers. near job roaming AP Connector TCP 7800 SpoolerController > SpoolerController TCP 5556 AP Connector > SpoolerController Near Roaming Group synchronization. Required for roaming groups up to 10 SpoolerController servers. AP Connector component, communication with server application for etcd TCP 2380 etcd > etcd Default value of port for communication between etcd nodes

10 Required? Type Port Communication Description (communication from the user) for etcd TCP 2379 TerminalServer > etcd Default value of port used by the Terminal Server to communicate with the local etcd job roaming TCP 81/446 SpoolerController > SpoolerController Job roaming via distributed layer FlexiSpooler shared folder or Mobile print web uploads TCP UDP 137/ /138 SMB Shared folder for uploading jobs AP Connector, Mobile Print and job transfers Mandatory on Site server Mobile print SafeQ infrastructure service Mandatory when WPS is installed on different machine than TS TCP 5559 HTTP/HTTPS Exchanging job data between spoolers, sending jobs from Mobile Print TCP 5555 YMQ Communication between FlexiSpooler (and its Desktop Interface), Mobile Print to Spooler Controller TCP 110/143/995/993 POP3/IMAP/POP3S/IMAPS Mobile Print downloads s from mail server TCP 7347/7348 HTTP/HTTPS Manages updates of TP4/eDEE/SafeQube/FlexiSpooler TCP 5600 HTTP Endpoint for communication with between WPS and Terminal Server Other communication Required? Type Port Communication Description (communication from the user) LDAP synchronization TCP 686 Management Service > LDAP LDAP integration (server > LDAP controller) secured over SSL TCP 389 Management Service > LDAP TCP 3268 Management Service > LDAP LDAP integration (server > LDAP controller) LDAP integration (server > LDAP controller) (global catalogue) (if using Payment system) TCP 4196 Payment Machine > YSoft Payment System Management connection

11 Required? Type Port Communication Description (communication from the user) (if using Payment system) (if using Payment system) (if using Payment system) (if using Payment system) (if using Payment system) TCP 4197 Payment Machine > YSoft Payment System TCP 4198 Payment Machine > YSoft Payment System TCP 4199 Payment Machine > YSoft Payment System TCP 8080 Terminal Server > YSoft Payment System TCP 8443 Terminal Server > YSoft Payment System Management connection over SSL this port is needed to be set up in Payment Machine service menu during the configuring of the Payment System server address Main connection Main connection over SSL Web, rest services (APIs) Web, rest services (APIs) TCP 25 SMTP (as per scan size) SMTP (Scan job delivery, notifications to administrator and users) Mandatory (if using external MS SQL server with named instance) UDP 1434 Management Service / Payment System > MSSQL DB This communication is used to query the SQL server browser service. The SQL browser service will respond with the TCP port number that will be used for the rest of communication. Mandatory (if using external MS SQL server with a named instance) TCP see description Management Service / Payment System > MSSQL DB The port number is dynamically assigned by the SQL browser service, see us/library/cc aspx for more information. AP Connector AP Connector UDP 5353 AP Connector > subnet AP Connector component multicast to subnet using Bonjour TCP 8050 client > AP Connector Job delivery from ios or MAC client to AP Connector over IPPS is the default but configurable port. Cluster installation

12 Required Type Port Communication Mandatory TCP 4001 Management Service Description (communication from the user) Internode communication Workstation (outbound connection) Required Type Port Communication Description (communication from the user) Mandatory TCP 5555 Management Service YMQ Communication between FlexiSpooler (and its Desktop Interface) to Spooler Controller when not spooling on server HTTP(s) 5559 FlexiSpooler > FlexiSpooler File transfer between spoolers Mandatory YMQ 5558 (localhost only) Desktop interface > FlexiSpooler Internal communication between FlexiSpooler service and Desktop Interface when printing via RAW TCP raw 9100 FlexiSpooler > MFD Print when printing via IPP(s) when authenticating on Azure AD IPP(s) 80/443/631 FlexiSpooler > MFD Print HTTPS 443/(80) FlexiSpooler > Azure AD Authentication on Azure AD Workstation (inbound) Workstation inbound communication is always within localhost. There is no component that will try to connect directly to the workstation. Required Type Port Communication Mandatory YMQ 5558 Desktop interface > FlexiSpooler Mandatory LPR 515 Windows Spooler > FlexiSpooler Description (communication from the user) Internode communication Receiving jobs

September 08, SYSTEM REQUIREMENTS YSOFT SAFEQ 5 SERVER

September 08, SYSTEM REQUIREMENTS YSOFT SAFEQ 5 SERVER 3.2 SYSTEM REQUIREMENTS 3.2.1 YSOFT SAFEQ 5 SERVER Please refer to Hardware requirements and Software requirements for server specific prerequisites. Before deploying YSoft SafeQ in your environment, we