June 11, SYSTEM REQUIREMENTS YSOFT SAFEQ 5 SERVER

Transcription

1 3.2 SYSTEM REQUIREMENTS YSOFT SAFEQ 5 SERVER Please refer to Hardware requirements and Software requirements for server specific prerequisites. Before deploying YSoft SafeQ in your environment, we always recommend to understand the environment from the perspective of network communication, review the information about typical deployments and run pre-installation checks. Network communication overview Typical deployment scenarios Pre-installation checklists WORKSTATION SOFTWARE Workstation requirements HARDWARE REQUIREMENTS MINIMUM / RECOMMENDED HARDWARE REQUIREMENTS Hardware requirements are always highly dependent on customer environment. The number of devices, remote sites, users, print job sizes, output volumes, usage frequency. If you are not certain about the customer environment, please consult with Y Soft representative the appropriate hardware sizing for your customer. There are several considerations in every deployment: Windows print queue the input/output print queue inside operating system. The print queue is a mechanism that provides print driver to a client software (e.g. to create a PCL/PS file, receive data stream over a network, store it on the hard drive and serialize it to the printer). YSoft SafeQ print queue print queue inside YSoft SafeQ which can be connected to a specific printer, terminal (reader) or group of users. From the perspective of Windows print queue, this represents (LPR) queue name in the print queue backend. YSoft SafeQ server has an internal mechanism to balance the load by partially serializing the incoming traffic; in theory there is no limit on how many Windows print queues can be connected to the YSoft SafeQ server. Network Device physical printing device (single or multifunction printer) with terminal and card reader. YSoft SafeQ server sends print jobs to the device. One network device typically represents one or multiple Windows print queues. YSoft SafeQ CML Server main YSoft SafeQ server on a physical or virtual server. CML server uses SQL database to retain print job data, LPR subsystem that receives prints from print server or client workstations, web administration interface, system for managing requests from terminals and readers and LDAP integration subsystem. YSoft SafeQ server can handle up to 200 network devices on a single server and up to 1600 in 4- node Windows cluster installation (note that reasonable hardware or virtual platform is required). YSoft SafeQ ORS Server spooler server on a physical or virtual server. Multiple ORSes can build a roaming group which is able to handle up to 2000 devices in a 25-node system. Each YSoft SafeQ ORS server can handle up to 200 network devices. YSoft SafeQ 5 227

2 JVM is very memory intensive. When using virtual machines, servers shall have configured memory reservation based on the maximum heap size of YSoft SafeQ CML/ORS server. See hardware requirements for Windows Servers at /bb See best practices for sizing Windows Print Servers at /14/best-practices-on-deploying-a-microsoft-windows-server-2008-windows-server-2008-r2-print-server.aspx See Network communication overview for more details on YSoft SafeQ communication. CML server cluster (main sites) CML server (main sites) Up to 50 devices per YSoft SafeQ server or server cluster Recommended hardware Recommended hardware Dual Core 2GHz or faster processor 2GB free RAM 1Gbps network connection (LAN) 20GB free disk space Connection to storage with a throughput of at least 120MB/s and 100 IOPS (for 50 devices; no parser used) Up to 200 devices per server ( 100 devices if only a single server is used) YSoft SafeQ server or server cluster YSoft SafeQ Central Reporting Services Dual Core 2GHz or faster processor 4GB free RAM 1Gbps network connection (LAN) 100GB free disk space Extra space 100GB (or more, depending on the storage strategy) for YSoft SafeQ Central Reporting Server data objects. Connection to storage with a throughput of at least 150MB/s and 300 IOPS Up to 100 remote sites and total of 500 devices Up to 500 remote sites and total of 1000 devices Additional remote sites (up to 2000 remote sites) ORS (remote sites) One CML server. Two cluster nodes, each with 6GB RAM. For every 500 remote sites, add one cluster node. Make sure to add 500MB RAM for every 100 connected sites. Recommended hardware YSoft SafeQ 5 228

3 CML server cluster (main sites) Up to 200 devices/server YSoft SafeQ ORS (requires connection to a central server) Recommended hardware Dual Core 2GHz or faster processor 2GB free RAM (4 GB RAM recommended), 1GB Network Equal VM with at least 2 cores 20GB available disk space (disk size highly depends on job size, print spooler and parser settings) Connection to storage with a throughput of at least 150MB/s and 300 IOPS disk performance is highly affected by replication buffer persistence settings (cachereplicationbufferpersistent) if the expected load is higher than 2000jobs /hour, it is recommended to disable cachereplicationbufferpersistent option to lower disk load and keep ORS and CML in the same data center. CRS (reporting services) Up to 2000 devices 100 millions pages yearly (half printed, half scan and copy) Recommended hardware 8-core 2.6Ghz (for example Intel X5355) 16GB RAM recommended 200GB HDD (four years of statistics; default configuration when keeping cubes with detailed statistics for last three months and all basic statistics; enabled reporting services) Note: One-time cube processing in this configuration takes approx. three hours SOFTWARE REQUIREMENTS SUPPORTED OPERATING SYSTEMS Operating System CML ORS Mobile Print Server Microsoft Windows Server 2008 SP2 32bit/64bit all editions Microsoft Windows Server 2008 R2 SP1 64bit all editions Microsoft Windows Server bit all editions CRS Payment System YSoft SafeQ 5 229

4 Operating System CML ORS Mobile Print Server Microsoft Windows Server 2012 R2 64bit (Standard /Datacenter edition) Microsoft Windows Small Business Server 2011 Standard Microsoft Windows 7 SP1 32bit/64bit* Microsoft Windows 8 32bit/64bit CRS Payment System * Workstation operating system has limited number of incoming connections Notes When installing on Windows bit, please install standalone PostgreSQL bit. Installation of CML with embedded MS SQL database is not supported on server core editions. YSoft SafeQ CML supports Microsoft Server Cluster (MSCS). Using embedded terminals on YSoft SafeQ CML (embedded terminals connected to CML) always requires Microsoft.NET Note: If you do not install Terminal Server component, Microsoft.NET is not required; embedded features will not be available. Using embedded terminals on YSoft SafeQ ORS (embedded terminals connected to ORS) always requires Microsoft.NET See Installing YSoft SafeQ CRS for additional requirements of the YSoft SafeQ CRS. YSoft SafeQ 5 Server does not support Linux. SUPPORTED DATABASES Component YSoft SafeQ 5.0 ORS YSoft SafeQ 5.0 CML Server Supported data engine No database required (internal persistent cache). PostgreSQL 9.2 embedded* or standalone Microsoft SQL Server 2008/2012 Express edition (up to 10 devices per server) ** Microsoft SQL Server 2008/2008 R2/2012/2014 Standard or Enterprise Edition, 32-bit or 64-bit *When using Windows bit, install standalone PostgreSQL instead of embedded. **Not recommended for use with CML server cluster. YSoft SafeQ 5.0 CRS see CRS - Supported databases YSoft SafeQ 5 230

5 Component YSoft Payment System Supported data engine PostgreSQL 9.2 embedded* or standalone Microsoft SQL Server 2008/2012 Express edition Microsoft SQL Server 2008/2008 R2/2012/2014 Standard or Enterprise Edition, 32-bit or 64-bit *When using Windows bit, install standalone PostgreSQL instead of embedded. Microsoft SQL Server 2012/2014 offers AlwaysOn Availability Group. This functionality is not supported by SafeQ. DATABASE INSTANCES AND CONNECTION YSoft SafeQ CML requires a stable connection to the database server for its proper functionality. YSoft SafeQ CML server requires two databases: one is used for real-time access, configuration and active job data second is used as data archive, primarily for reporting and data audit YSoft SafeQ application level cluster requires two databases for each CML server. All databases can be on the same database server (high availability SQL server is mandatory in this case) Connection to the SQL server is realized on the Java level using secured JDBC connection (integral part of the application) Y Soft Corp. cannot guarantee proper functionality of YSoft SafeQ if the connection to the database server and its databases is not available. DATABASE SIZING Example based on real customer data (10 million pages per month): CML Database: 16 GB per SafeQ server CRS Database SQL: 100 GB aggregated DB (after 3 years) CRS Database OLAP: 100 GB aggregated DB (after 3 years) DATABASE SETTINGS AND CONFIGURATION YSoft SafeQ 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 YSoft SafeQ access, with ownership rights to its database Collation case-insensitive Reliable low-latency network connection (if the DB server is on another server) YSoft SafeQ 5 231

6 Microsoft SQL Server configuration: Correct collation: Case-Insensitive and Accent-Sensitive (language_ci_as) where applicable The user that YSoft SafeQ 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 YSoft SafeQ 5.0 the following database role is required: db_owner. To update/upgrade YSoft SafeQ 5.0 the following database role is required: db_owner. To run YSoft SafeQ 5.0 the following database roles are required: db_datareader, db_datawriter, db_ddladmin. For the installation to an MS SQL server, there must be two accounts created. One can be named in any way, name of second account is " sync" and this name is mandatory. In case of installation to a named instance of the external MS SQL server, the service "SQL Server Browser" must be configured and running on the SQL Server. In case that you are going to use the following to be allowed between SafeQ server and MS SQL server: external MS SQL server with named instance, you will need 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 ( /cc aspx). PostgreSQL configuration: UTF-8 collation 9.2 version only Non-local-admin account for running PostgreSQL system service (Windows OS) To install, update or run YSoft SafeQ 5.0 CML Server database user postgres and sync must have superadmin role NETWORK COMMUNICATION OVERVIEW This page provides a complete list of ports and protocols that must be enabled on firewalls in order to ensure YSoft SafeQ system functionality. NETWORK COMMUNICATION OVERVIEW WORKSTATION TO SERVER COMMUNICATION (SERVER INBOUND RULES) Description (communication from the user) Mandatory TCP 80 /443 HTTP/HTTPS for access to YSoft SafeQ administration /reporting web interface YSoft SafeQ 5 232

7 Description (communication from the user) TCP 8005 server shutdown port listener for tomcat (if using workstation client) (if using workstation client) (if using workstation client) (if using payment system) TCP 9100 proprietary compressed 10kB - 1GB per print job TCP 515 LPR 10kB - 1GB per print job TCP 4097 proprietary SSL 100kB per print job TCP 4098 proprietary SSL 100kB per access job reception from client workstations (YSoft SafeQ Client Protocol) job reception from client workstations (LPR) Access verification with job print from client workstations (YSoft SafeQ Port Protocol) YSoft SafeQ Payment Machine application (attended); Requires Pay For Print support; TCP 2382 OLAP for access to Central Reporting Services (if using central reporting) / kB-10MB per access OLAP interface (MS SQL Analysis service) / Recommended from Localhost TCP 9000 JMX CML/ORS/CRS system health monitoring via JConsole (monitoring only) / Recommended from Localhost TCP JMX CML/ORS system health monitoring (monitoring only) / Recommended from Localhost TCP 9898 JMX CRS system health monitoring (monitoring only) / Recommended from Localhost TCP 9999 JMX ORS system health monitoring YSoft SafeQ 5 233

8 Description (communication from the user) (monitoring only) / Recommended from Localhost TCP 9005 JMX DBSync system health monitoring via JConsole (monitoring only) / Recommended from Localhost TCP 9797 JMX DBSync system health monitoring via JConsole (monitoring only) / Recommended from Localhost TCP JMX ORSWeb system health monitoring via JConsole (monitoring only) (if using workstation client) TCP 4096 proprietary 1kB - per request Information regarding queues for YSoft SafeQ Client configuration Mandatory TCP 4110 Ricoh Embedded Terminal - accounting SERVER TO PRINTER COMMUNICATION (SERVER OUTBOUND RULES) Mandatory TCP 9100 proprietary 10kB - 1GB per print job Mandatory TCP 515 LPR 10kB - 1GB per print job Description (communication from the user) Job data delivery to printer (Raw TCP) Job data delivery to printer (LPR) (if using print data encryption) (if using print data encryption) TCP 80/443 IPP/SSL 10kB - 1GB per print job TCP 9100 proprietary SSL 10kB - 1GB per print job Job data delivery to printer (IPP over SSL) Job data delivery to printer (compressed via Terminal Professional) YSoft SafeQ 5 234

9 UDP proprietary broadcast (only within one subnet) Description (communication from the user) Terminal Professional/UltraLight discovery TCP 4095 proprietary Terminal Professional/UltraLight remote configuration embedded TCP proprietary WS Embedded (KM, Xerox, Sharp) terminals /50003 SSL remote configuration TCP 8080, proprietary YSoft SafeQ Embedded Embedded Terminal for Ricoh Terminal for Ricoh ESA ESA installation, manual terminal configuration, manual downloading logs YSoft SafeQ Embedded Terminal for Ricoh ESA automatic configuration online print/copy tracking UDP 161 SNMP Online accounting of network printer MFP TCP 49629, HTTP/HTTPS YSoft SafeQ Embedded Embedded Terminal for Toshiba Terminal for Toshiba installation TCP 80, HTTP/HTTPS YSoft SafeQ Embedded Embedded Terminal for Xerox 443 Terminal for Xerox/Fuji-Xerox /Fuji-Xerox installation TCP 80, HTTP, YSoft SafeQ Embedded Embedded Terminal for Konica proprietary WS Terminal for Konica Minolta Minolta SSL installation Embedded Terminal for Sharp YSoft SafeQ Embedded Terminal installation TCP 80 HTTP YSoft SafeQ Embedded Terminal for Sharp installation UDP 161 SNMP YSoft SafeQ Embedded Terminal installation MFP check PRINTER TO SERVER COMMUNICATION (SERVER INBOUND RULES) Description (communication from the user) TCP 4096 Proprietary SSL YSoft SafeQ 5 235

10 Description (communication from the user) Mandatory with Terminal low volume, low Terminal Professional/UltraLight Professional latency authentication and session control TCP 4096, Proprietary YSoft SafeQ Embedded Terminal Embedded Terminal for Rico 5012 low volume, low latency (Ricoh authentication and session control) YSoft SafeQ Embedded Terminal (Accounting and charging) TCP 5011, HTTP/HTTPS YSoft SafeQ Embedded Terminal Embedded Terminal for 5012, browser communication Browser 5013 TCP WS SSL YSoft SafeQ Embedded Terminal Embedded Terminal for KM 5019 low volume, low latency (KM) authentication and session control Embedded Terminal for Toshiba TCP 389 LDAP Internal LDAP for YSoft SafeQ Embedded Terminal for Toshiba When 389 is blocked (by already running AD on a domain controller), SafeQ 5 GUI installer will display warning and use 390 port instead Mandatory with Network TCP 5011 Proprietary SSL Network Card Reader Card Reader /5012 authentication (if using preview on Terminal Professional) (if using scan via SMTP) TCP 5020 Proprietary Preview provider for Terminal Professional (optional, depending on SafeQ setting, configurable by preview-provider-port) TCP 25 SMTP Scanning from MFPs via (optional, depending on MFP capabilities) WebDAV scanning TCP 443 Secured WebDAV /HTTPS Scanning from MFPs via scan workflow (optional, depending on MFP capabilities) (if using scan via SMB) TCP 139 SMB Scanning from MFPs via scan to folder (optional, depending on MFP capabilities) TCP 21 FTP YSoft SafeQ 5 236

11 embedded terminal scanning Description (communication from the user) Scanning from MFPs via scan to folder (optional, depending on MFP capabilities) - Passive FTP transfers (for embedded terminal scanning) TCP >1023 FTP Range of ports for passive FTP transfers (optional, depending on SafeQ setting, configurable by ftppassiveports) INTER-SERVER COMMUNICATION (INBOUND AND OUTBOUND RULES) data path Description (communication from the user) cluster TCP 4099 CML > CML proprietary ~1kB per print job Application-level cluster synchronization TCP 4111, CML > CML Application-level cluster DB cluster 4101 proprietary synchronization ~1kB per print job ORS Central Reporting TCP 6010 ORS > CML proprietary ~40-60 kb per print job TCP 4139 CML > CRS proprietary ~1kB per print job ORS-to-CML communication and synchronization Reporting data collection Mandatory TCP 5556 TS > server (CML/ORS) (localhost) Terminalserver (TS) component (required for YSoft SafeQ embedded terminal support), communication with server application YSoft SafeQ 5 237

12 data path Description (communication from the user) proprietary job roaming load balancing TCP 8000 ORS > ORS Job data transfer for roaming jobs (uncompressed) TCP 6020 CML > CML Internal communication between CMLs near job roaming UDP Multicast configurable ORS > ORS Near Roaming Group synchronization. roaming groups with 10+ ORS servers. near job roaming web status information web status information web status information web status information TCP 7800 ORS > ORS Near Roaming Group synchronization. Required for roaming groups up to 10 ORS servers. TCP CML > CML Node communication - service status TCP CML > CML Node communication - service status TCP CML > CML Node communication - service status TCP CML > CML Node communication - service status OTHER COMMUNICATION data path Description (communication from the user) LDAP synchronization TCP 686 CML > LDAP LDAP integration (server > LDAP controller) secured over SSL TCP 389 CML > LDAP LDAP integration (server > LDAP controller) TCP 3268 CML > LDAP LDAP integration (server > LDAP controller) (global catalogue) YSoft SafeQ 5 238

13 data path Description (communication from the user) (if using Payment system) (if using firmware updates of HW terminals) (if using Payment system) (if using Payment system) (if using Payment system) TCP 4098 Rech. Station > CML Proprietary encrypted TCP 4100 Terminal > SafeQ TCP 4444 Rech. Station > CML TCP 4197 YSoft SafeQ Payment Machine > CML TCP 4199 YSoft SafeQ Payment Machine > CML YSoft SafeQ Payment Machine; not supported by YSoft SafeQ5 Port where the terminal update service is running (configurable by rs-terminal-update-port) YSoft SafeQ Payment Machine (QuickChip); not supported by YSoft SafeQ5 Management connection over SSL - this port is needed to setup in SPM service menu during configuring of Payment System server address Main connection over SSL TCP 25 SMTP (as per scan size) SMTP (Scan job delivery, notifications to administrator and users) (if using workstation client) TCP 80 SafeQ Client -> ORS web ORS web communication with client (billing codes etc.) Mandatory (if using external MS SQL server with named instance) UDP 1434 CML > DB This communication is used to query the SQL server browser service. SQL browser service will respond with the TCP port number that shall be used for the rest of communication. Mandatory TCP see CML > DB The port number is dynamically (if using external MS SQL description assigned by SQL browser service, server with named see instance) us/library/cc aspx for more information. YSoft SafeQ 5 239

14 CLUSTER INSTALLATION Required Type Port Communication data path Description (communication from the user) Mandatory TCP 4111 CML > CML Proprietary DB Sync Mandatory TCP 6020 CML > CML Inter node communication TYPICAL COMMUNICATION OVERVIEW The following diagram is for reference only and does not show all possible options. YSoft SafeQ 5 240

15 TERMINAL COMMUNICATION OVERVIEW The HW terminals communicate with the YSoft SafeQ server over an Ethernet network (default communication port 4096). RJ45 connectors connect the terminal to the network. MFPs and printers communicate with the SafeQ server via the terminal. Each terminal has a MAC address allocated by Y Soft. DHCP SUPPORT Terminals can be configured in static IP or dynamic IP (DHCP) mode. YSoft SafeQ 5 241