Preparing the primary computer for installation

When you are ready to install RICOH ProcessDirector, use this procedure to make final configuration updates and verify that the system configured correctly.
    Note:
  • If you are using a copy of DB2 installed on a different computer instead of the version of DB2 that is included with RICOH ProcessDirector, make sure that you complete Installing and configuring your own copy of DB2 on a different computer before you start this procedure.
  • If you are using a copy of PostgreSQL installed on the local computer or on a different computer instead of the PostgreSQL version included with RICOH ProcessDirector, make sure that you complete Configuring your own PostgreSQL database before you start this procedure.
  • Setting the umask to use strict permissions might cause read or write issues on the installation folder. Therefore we recommend setting umax to 022, the default set of permissions.
To prepare the primary computer:
  1. Make sure that the planning checklist is complete and the required hardware and software are available and installed. See Planning for installation.
  2. Make sure that /etc/hosts on this computer has an entry for its IP address and the fully qualified host name.
  3. Log in as the root user.
      Important:
    • You must log in as a user with UID 0. If you must log in as a different user, you can use sudo su - or su - to become the root user. However, do not use sudo or the su command in any other way to become the root user.
  4. We recommend that you set user resource limits for the maximum number of open files, number of processes, and stack size.
    All systems perform better with the new settings. Systems with areas of high volume require the settings.
    1. Edit the /etc/security/limits.conf file with a text editor to set these limits:
      * soft nofile 16384
* hard nofile 32768
* soft nproc 16384
* hard nproc 65536
* soft stack 16384
* hard stack 32768
    2. Save the file and exit the editor.

      The new limits do not take effect until you log out and log back in.

  5. Optional: If you plan to use IBM DB2 as the RICOH ProcessDirector database, check to see whether DB2 or a DB2 client is installed on this computer. Enter this command to see if a separate copy of DB2 or a DB2 client is installed:
    • db2ls
    The results show whether DB2 is installed and the level of that installation. If there are no results, DB2 is not installed outside of RICOH ProcessDirector. If DB2 is installed, take one of the following actions to use either the installed copy or the RICOH ProcessDirector version.
    • If DB2 11.5.8 or higher is installed, continue installing RICOH ProcessDirector.
    • If there is a DB2 version lower than 11.5.8, update to DB2 version 11.5.8 or higher.
  6. Optional: If you plan to use an instance of PostgreSQL installed on a different computer as the RICOH ProcessDirector database, verify that the PostgreSQL server or client is installed on the primary computer.
    The PostgreSQL server or client must be at the same level as the PostgreSQL database that you plan to use with RICOH ProcessDirector.
    • If neither the PostgreSQL server nor the client is installed, you must install one of them.
    • If a PostgreSQL server or client is already installed, check its version:
    1. Open a command line and change directories to where PostgreSQL is installed.
    2. Enter this command to view the client version:
      psql -v
    3. Enter this command to view the server version:
      postgres -V
    If both versions match, continue installing RICOH ProcessDirector. If the versions do not match, update PostgreSQL before you continue.
  7. Disable your antivirus software.
    During the install process, various archive files (ZIP, JAR, and EPK files) are copied to your server. Then, the contents are extracted and moved to the correct directories on your system. Antivirus tools usually lock and scan files extracted from archives.

    While the lock and scan process is generally fast, the installation program runs faster. If the installer tries to unpack and move files before the scan is complete, installation errors occur and can be difficult to recover from. Disabling your antivirus software during the install process prevents these types of errors.

  8. Set up exceptions within your antivirus software.

    If you cannot deactivate your antivirus software entirely, excluding some directories from scans can reduce the possibility of installation errors. In addition, most antivirus software affects the function of databases. The software sometimes quarantines files that databases use, causing operation errors. Setting up these exclusions now prevents those errors after RICOH ProcessDirector is installed.

    Set up exceptions for these paths:

    • /aiw/aiw1
    • /opt/infoprint/ippd
    • /var/psf
    • If you plan to use DB2 installed with RICOH ProcessDirector as your database:
      • /home/aiwinst/sqllib
    • If you plan to use PostgreSQL installed in a Docker or Podman container as your database:
      • /var/lib
    • If you use a custom feature that integrates BCC software running on a Windows application server with RICOH ProcessDirector, exclude this path on the Windows system that the BCC software runs on:
      • C:\BCC
  9. Disable Security Enhanced Linux (SELinux). Installation errors occur on Linux systems when you run the RICOH ProcessDirector installation program with SELinux enabled. To verify the SELinux mode and disable it:
    1. Open a command line and type this command to view the current SELinux mode: getenforce
    2. If the result of the command is Enforcing, disable SELinux. Open /etc/selinux/config in a text editor and find the SELINUX line. Change that line to:
      SELINUX=disabled

      Save and close the file.

    3. Run the getenforce command again to make sure SELinux is disabled.
Parent topic: Installing