Installing on AIX systems

You can install the RICOH ProcessDirector Secondary Server feature on an AIX system in your network.
    Important:
  • Although the Secondary Server feature is not mandatory to be at the same code level as the base product, we recommend checking and upgrading the secondary server too when 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 from Preparing the primary computer.
    Note:
  • In addition to RICOH ProcessDirector, this software is installed or upgraded if it is not already present on the AIX system:
    • RPM installp package (Rpm.rte 3.0.5.52 or later)

To install the Secondary Server feature on an AIX 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. Open a command line and enter this command to make sure you are in the root directory:
    • cd /
  4. If you are installing on a server running in a double-byte language (such as Japanese), the server must be running in a UTF-8 language environment. To change the server to a UTF-8 language environment:
    1. Enter:
      export LANG=locale.UTF-8
      Replace locale with the locale identifier for a double-byte language (such as JA_JP).
  5. Insert the RICOH ProcessDirector Secondary Server feature DVD.
  6. If you already have a CD file system defined (named /cdrom, for example), you can insert the disk and enter:
    • mount /cdrom
    To determine whether or not you already have a file system defined, enter:
    • /usr/sbin/lsfs | grep cdrfs | awk ‘{print $3}’
  7. If you do not have a CD file system present, you can create one.
    1. Determine the name of the CD device by entering:
      lsdev -Cc cdrom
    2. Create the CD file system for device ‘cd0’ at mount point ‘/cdrom’ by entering:
      /usr/sbin/crfs -v cdrfs -p ro -d’cd0 -m’/cdrom’
  8. To start the installer, enter:
    • /cdrom/setup IPPDs

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

  9. 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.

  10. Review and accept the license and maintenance agreements.
  11. Type the host name or fully qualified IP address of the primary computer and verify it.
  12. Enter the name of the RICOH ProcessDirector system user that you used on the primary computer. The default system user is aiw1.
      Note:
    • All user IDs and group names must be 1-8 characters because of a restriction in DB2.

    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.

  13. 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.

      Note:
    • All user IDs and group names must be 1-8 characters because of a restriction in DB2.
    If you created the user and group before you started the installer, you are not asked for these values.
  14. 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.
  15. 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.
  16. 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
  17. Click Done to complete the installation.
    The secondary server starts automatically.
  18. 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.

  19. 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.