Installing the SLES operating system
- See the SLES documentation to install SUSE Linux Enterprise Server (SLES) 12.0 with Service Pack 4 or above for x86_64 or SUSE Linux Enterprise Server (SLES) 15.0 with Service Pack 1 or above for x86_64.
- Make sure that these components are installed on the secondary computer:
- Korn shell (
mksh
) - binutils
insserv-compat
packagelibX11.so.6
and its dependent libraries- Perl interpreter (Perl.rte 5.8.8 or later)
- Zip and unzip utilities
- The
fontconfig
andfreetype
librariesWe also strongly recommend installing DejaVu Fonts. OpenJDK requires these libraries to identify available fonts on the system.
- Korn shell (
- Make sure that these components are installed on the secondary computer:
- Create Linux partitions and file systems. See Planning for file systems for recommendations and considerations.
- Run these commands and look for the expected results to verify that you installed
SLES correctly:
SLES commands and expected results
Command Expected result To check the SLES release: cat /etc/os-release
Returns the operating system version and patch level. To verify that the operating system is 64-bit: uname -a
A response that includes: x86_64 To check for Korn shell (mksh): rpm -q mksh
Response similar to: mksh-50-2.13.x86_64
To check for binutils: rpm -q binutils
Results resemble this example: binutils-2.31-9.26.1.z86_64
To check for insserv-compat: rpm -qa | grep insserv-compat
Results resemble this example: insserv-compat-0.1-4.3.1.noarch
If no results are returned, you must install the missing package.
To install the serving-compat package, type:
zypper install insserv-compat
To check for libX11.so.6: rpm -qa |grep -i X11
ls -l /usr/lib*/libX11*
Results include a collection of libraries with the text X11 in the name, such as: libX11-6-1.6.2-12.5.1.x86_64 libX11-data-1.6.5-1.41.noarch libxkbcommon-x11-0-0.8.0-1.17.x86_64 ghostscript-x11-9.25-23.13.1.x86_64 xorg-x11-essentials-7.6_1-1.22.noarch
If fewer than five results are returned, not all of the dependencies are installed. Install the libX11 libraries again, making sure to install all of the dependencies.
To check the version of Perl that is installed: rpm -q perl
A response that resembles: perl-5.8.8-14.10 To verify that the libraries for font support are installed: - rpm -qa | grep fontconfig
- rpm -qa | grep freetype
- rpm -qa | grep -i dejavu
Results resemble these examples: - fontconfig-2.13.0-4.3.el7.x86_64
- freetype-2.8-14.el7.x86_64
- dejavu-fonts-common-2.35-7.el8.noarch
If no results are returned, you must install the missing library or fonts.
To install all three, type:
zypper install libfreetype6 fontconfig dejavu-fonts
To check the versions of zip and unzip that are installed: rpm -q zip
rpm -q unzip
zip-3.0-1.el6.x86_64 (typical) unzip-6.0-1.el6.x86_64 (typical)
getconf GNU_LIBPTHREAD_VERSION NPTL 2.19 To verify that the rpcbind service is running: rpcinfo
A response that includes system information indicates that the rpcbind service is running. If the responses is an error message, the rpcbind service is not running. Type this command to start the rpcbind service: /sbin/rpcbind If you are going to print with AFP printers whose parent server is a SLES Linux server, the portmap utility must be installed and running. rpcinfo -p
This command only returns results if the rpcbind service is running.
A response that includes portmap, such as: program vers proto port service 100000 4 tcp 111 portmapper
To check the status for SELinux: getenforce
Disabled - Note:
- If you have installed a later version of a prerequisite, the version number returned varies.
If the command results are not as you expect, use YaST to make sure you have installed the required components (see step ). In YaST, click .
- Verify date, time, and time zone settings through YaST, and correct if necessary:
Click. If you change the date, time, or zone, you might have to reboot the system for your changes to take effect.
- Set up networking based on system networking information:
- Make sure that RICOH ProcessDirector has access to a Domain Name System (DNS) server. The DNS server must have correct
entries for the host name and IP address of each RICOH ProcessDirector primary computer and application/secondary computer on the network.
- Note:
- RICOH ProcessDirector supports both IPv4 and IPv6 protocols. If you use IPv4, IP addresses can be expressed using dotted-decimal addresses or the fully qualified host name. If you use IPv6, you must use the fully qualified host name of the server.
- If you use an IPv6 address, you must complete additional configuration steps after you install RICOH ProcessDirector. See Configuring to use IPv6 addresses.
- Make sure that
/etc/hosts
on the primary computer has an entry for its IP address and the fully qualified host name. - In your firewall, open any ports that RICOH ProcessDirector uses. Depending on your configuration, you might need these ports:
Ports to open on the RICOH ProcessDirector primary server
Port Source system Description 15080 User workstation Access to the RICOH ProcessDirector user interface if not using TLS. 15090 Administrator workstation Access to the RICOH ProcessDirector Feature Manager interface if not using TLS. 15443 User workstation Access to the RICOH ProcessDirector user interface if using TLS. 15453 Administrator workstation Access to the RICOH ProcessDirector Feature Manager user interface if using TLS. 515 Customer application Required when sending jobs to RICOH ProcessDirector using LPR. 5001-65535 Customer mainframe Required when sending jobs to RICOH ProcessDirector using Download for z/OS or AFP Download Plus. The port numbers defined in RICOH ProcessDirector must match the port numbers defined as printers on the mainframe. 55555 RICOH ProcessDirector secondary server Required if you use secondary servers that are not defined on the same system as the primary server. Allows communication between the secondary server and the primary server. 15080 or 15443 RICOH TotalFlow Print server Used to send printing status to RICOH ProcessDirector. Ports to open on RICOH ProcessDirector primary and secondary server
Port Source system Description 15081 Administrator workstation Used to import the custom PDF printer definition to the RICOH ProcessDirector server that will be communicating with the printer Only necessary when using custom PDF printers. Most systems do not use custom PDF printers.
15081 Ricoh PDF printer The job ticket contains reference to a PDF file that the printer retrieves. Ports to open on the NFS server
Port Source system Description 111 RICOH ProcessDirector primary and secondary server Used by the NFS server and User Name Mapping function when sharing data from the primary server to secondary servers or other systems using NFS. 2049 RICOH ProcessDirector primary and secondary server Used by the NFS server when sharing data from the primary server to secondary servers or other systems using NFS. Ports to open on printers
Port Source system Description 161 RICOH ProcessDirector primary and secondary server Required when RICOH ProcessDirector gets printer status and information using SNMP. 8010 RICOH ProcessDirector primary and secondary server Required when RICOH ProcessDirector gets printer status and information using SNMP. 9100-9103 RICOH ProcessDirector primary and secondary server Required when sending jobs to a printer with a EFI Fiery controller using Postscript job tickets. Ports to open on LDAP server
Port Source system Description 389, 636, or other port as configured. RICOH ProcessDirector primary server Required when RICOH ProcessDirector is using LDAP to authenticate users. Ports to open on printers that support JMF interfaces 1
Port Source system Description 80 RICOH ProcessDirector primary and secondary server Required when RICOH ProcessDirector sends IMSS queries using the HTTP protocol. 8010 RICOH ProcessDirector primary and secondary server Required when sending JMF files to EFI Fiery controllers. 9100 (default) - 9103 RICOH ProcessDirector primary and secondary server Required when sending jobs to a printer with a EFI Fiery controller using Postscript job tickets. 9100 is the default port. EFI printers use port 9102.
Ports to open on Passthrough printers
Port Source system Description 515 RICOH ProcessDirector primary server Required when receiving jobs from RICOH ProcessDirector using LPR. Ports to open on IPDS printers
Port Source system Description 5001-65535 RICOH ProcessDirector primary server Required when sending files to RICOH ProcessDirector using Download for z/OS or AFP Download Plus. These port numbers are configured when you create the input devices that receive these jobs. Open these ports after you define the input devices.
Ports to open on a transform server
Port Source system Description 6984-6992 RICOH ProcessDirector primary server Required if you use any of the RICOH Transforms and they are not installed on the primary server. These transforms are not the same as the RICOH ProcessDirector Advanced Transform feature. 16080 Administrator workstation Access to the Transform Features user interface if using any of the RICOH Transforms. Ports to open on a PostgreSQL server
Port Source system Description 5432 RICOH ProcessDirector primary server and any system accessing RICOH ProcessDirector reports data Access to PostgreSQL database. By default, the PostgreSQL database is installed on the RICOH ProcessDirector primary computer. Required when using the RICOH ProcessDirector Reports feature.
Ports to open on a DB2 server
Port Source system Description DB2 prior to 11.5.6: 50000 DB2 11.5.6 and higher: 25000
RICOH ProcessDirector primary server Required when RICOH ProcessDirector uses a DB2 database installed on a different server. These are the default ports used by DB2; the default value changed in Version 11.5.6. If your installation of DB2 uses a different port, open the port you use.
- Make sure that RICOH ProcessDirector has access to a Domain Name System (DNS) server. The DNS server must have correct
entries for the host name and IP address of each RICOH ProcessDirector primary computer and application/secondary computer on the network.
- Verify network connectivity:
- To verify that host name resolution is working, enter this command:host localhost
If you can access the DNS server, the response includes the host name localhost or loopback and the address 127.0.0.1. For example:
localhost.mycompany.com is 127.0.0.1
- From all secondary computers (if any), ping the primary computer.
- From the primary computer, ping all secondary computers (if any).
- Contact the network administrator if you are not successful with any of these verifications.
- To verify that host name resolution is working, enter this command: