Installing the Secondary Server feature

You can install the RICOH ProcessDirector Secondary Server feature on a Linux system in your network.
    Important:
  • Secondary Server features are not required to have the same level of code as the base product. However, we recommend checking and upgrading the secondary server whenever the primary server is upgraded. To determine the level of code that is installed on either computer, enter this command:
    • echo $AIW_VERSION
  • Before you begin this procedure, make sure that you followed the steps in Preparing the primary computer.

To install the Secondary Server feature on a Linux system:

  1. 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.
  2. Make sure that /etc/hosts on this computer has an entry for its IP address and the fully qualified host name.
  3. Disable any antivirus software running on the system.

    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.

  4. 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
  5. Open a command line and enter this command to make sure you are in the root directory:
    • cd /
  6. Insert the RICOH ProcessDirector Secondary Server feature DVD.
  7. To determine the name of the mount point, enter:
    • ls /media
    On some systems, the name of the mount point is the same as the name of the DVD.
      Note:
    • If you are using a Red Hat Linux system, the drive might mount automatically. However, drives that are mounted automatically on those systems are set up so that you cannot run programs from the media. You must unmount the drive and mount it again with the exec option before you can continue. You can use this command:
      • mount -t iso9660 -o remount, exec <mount_point>
      You must remount the drive for every DVD that you insert.
  8. Mount the drive, if necessary. Enter:
    • mount /media/mount_point
  9. Change directories so you can see the contents of the DVD. Enter these commands:
    • cd /media/mount_point
    • ls
    You see several scripts and directories, including a script called setup.
  10. To start the installer, enter: ./setup IPPDs

    The installer starts and displays the Introduction screen. Select the appropriate language for the installer to use and then click OK.

      Note:
    • If the computer's operating system is a supported Red Hat-derived operating system and its language is Japanese, Simplified Chinese, or Traditional Chinese, choose English on the dropdown language menu. Japanese, Simplified Chinese, and Traditional Chinese characters do not display properly during a Red Hat installation of RICOH ProcessDirector.
  11. Follow the instructions in the installer.

    The installer verifies many of the prerequisites for the system. If it finds any problems, it lists them for you. You cannot proceed until you correct them. After you fix the issues, verify the prerequisites again by returning to the Prerequisite Verification window. Click Previous in the installer or type back in console mode, then continue with the installer.

      Important:
    • After you verify all the prerequisites, click Cancel to change a previous entry and begin the installation process again. Clicking the Previous button sometimes causes problems.

  12. Review and accept the license and maintenance agreements.
  13. Type the host name or fully qualified IP address of the primary computer and verify it.
  14. Enter the name of the RICOH ProcessDirector system user that you used on the primary computer. The default system user is aiw1.
      Note:
    • All Linux operating system user IDs and group names must be 1-8 characters because of a restriction in DB2. You cannot create a user ID that includes international characters (such as á, É, î, ñ, ô, ß) or double-byte characters. This limitation only applies if you use DB2 as your database.

    If the installer finds that the user already exists on the system, it asks if you want to use that user. If you did not create the user, choose No and enter a different name. If the installer does not find the user on the system, the installer creates it.

    Do not select the check box for Use system update file from another computer.

  15. Enter the values that you used on the primary computer for:
    • The security group to use as the primary group for the system user
    • The UID number for the user
    • The GID number for the group
    • The home directory for the system user

    The default values are shown in the installer.

    If you created the user and group before you started the installer, you are not asked for these values.

  16. Enter the same password that you used for the system user on the primary computer twice. Remember this password; you need it later when you have to log in as the system user. If you created the user before you started the installer, you are not asked for the password.
  17. Choose the language that you want the system user to use. This language determines the language used for some messages, even if you set the browser for the user interface to a different language.
  18. Review the pre-installation summary and click Install to start installing.
    The final window displays the URL for accessing the user interface in this format, where hostname is the host name of the primary computer:
    • http://hostname:15080/pd
  19. Click Done to complete the installation.
    The secondary server starts automatically.
  20. On the command line, type this command to return to the root directory:
    • cd /
  21. If you installed from a DVD, eject the disc.
  22. Reboot the system.
      Note:
    • If you have an automated recovery mechanism for system outages, disable it before rebooting.
  23. To verify that the secondary server is running, enter this command on the command line:
    • ps -ef | grep Instance
    You should see an instance statement such as:
    • java com.ibm.aiw.instance.SecondaryInstance hostname

    If the software is not running, view the installation logs in the /opt/infoprint/ippd/logs directory. If this does not solve the problem, contact customer support.

  24. To make sure that the secondary server is connected to the primary server, log in to the RICOH ProcessDirector user interface and click Administration Objects Servers to verify that the Connection status column contains Connected.
After your secondary server is running, you must determine how it is used and change the properties of some objects accordingly. For example:
  • What printers and input devices do you want the secondary server to manage?

    Create or modify those devices so this secondary server is listed as their Parent server.

  • What step templates can run on this secondary server?

    Tune those step templates so that they can run on this secondary server.

  • What external programs on this secondary computer can be accessed using an external step?

    Set up the external program and configure a step based on the RunExternalProgram step template so it uses that program.