Print server on Windows

This document describes the minimum configuration requirements when installing a SAFE X3 print server on a Microsoft Windows server.

Category	Configuration requirements
Operating system	Microsoft Windows Server 2008 R2 x64. Microsoft Windows Server 2012 R2 x64. Microsoft Windows Server 2016.
Computer	Industry-standard server or virtual machine. Processor Intel Xeon Quad Core E544 2.3GHz or above recommended.
RAM memory	1 GB or above based on the number of concurrent print processes.
Disk space	90 MB: Sage X3 Print server. 180 MB: Crystal Report 2016 client (under \Program Files). Plan an additional 20 MB per SAFE X3 solution associated with a SAFE X3 Print server.
Database access	By default, the SAFE X3 Print server uses the ODBC SQL Server Native Client or CR Oracle Wire Protocol ODBC Driver, installed by its own setup. The use of these drivers does not require to install the SQL Server or Oracle client part. In case of a forced use of a CR Oracle ODBC Driver (for a SAFE X3 solution that uses an Oracle database), the presence of an Oracle Net 11 client on the server is mandatory. In this case, the SAFE X3 Print server takes into account the Oracle environment variable "TNS_ADMIN" during the automatic "creation/update" procedure of an ODBC data source. If this variable is present and properly valued, the "tnsames.ora" file located in the location indicated by the contents of this variable is updated by the SAFE X3 Print server during an automatic "creation/ update" procedure of an ODBC data source.
User account	If the print server must be launched in "Windows Service" mode, it is highly recommended not to use the "Local System" login account. The user account with which the print server has been launched (in "Console" or "Windows service" mode) must have at least one printer set up. The Windows user account used to launch the print server must have sufficient rights to: create system ODBC data sources; modify the "%Windir%\system32\drivers\etc\services" file; create global objects ("Create global objects" local security attribute); when using a CR Oracle ODBC driver, access the OracleNet alias descriptions ("tnsames.ora" file located in the location specified by the Oracle environment variable "TNS_ADMIN") in read/write mode. Thus, it is highly recommended that the Windows user account used to launch the print server be the Local administrator of the computer. However, if the security rules do not allow to use an Administrator account and if the user account used does not have sufficient rights to access the resources mentioned above, you could apply one of these 2 strategies: using a print server version EDT.208 or upper, add the following registry key (REG_DWORD) with the numerical value 3, after the installation and before to configure the print server using the console : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ADONIX\SRVIMP\0,1,5,0\GENERAL\AdvancedSrvOpt whatever the print server version, apply these 2 rules : a record must be manually added to the "%Windir%\system32\drivers\etc\services" file to declare the print server listening port. The port number that must be entered is the one declared in the SAFE X3 configuration console during the component configuration. The port alias must comply with the following convention: "adonix_numport" The Oracle or SQLServer data sources must be manually created on the computer. In the case of a CR Oracle ODBC Driver data source, do not forget to also create the OracleNet alias (use for this the Oracle "Net configuration" wizard). The configuration parameters to use for the manual creation of ODBC data sources can be accessed via the SAFE X3 solution definition available from the SAFE X3 configuration console. Finally, in this case, the print server must be started using the "/noodbc" option in order to deactivate the automatic creation of ODBC data sources. If you want more details on these matters, consult the print server presentation and operation guide.
E-mail software	A MAPI compatible e-mail system is necessary in case the e-mail will be used to distribute the results of a print request. This software must be active in such a way that a MAPI session can be established without it being necessary to previously carry out a connection.
Others	A SAFE X3 ADXADMIN administration runtime must be installed on the server. A JDK or Java Runtime Environment (version 7 or later) must be installed.

Index Home