Creating an installer response file

To install RICOH ProcessDirector in automated mode, create an installer response file. This file includes the answers that you would provide in the installation wizard in the in interactive mode, so the installer can retrieve the answers autonomously.

The RICOH ProcessDirector installation media provides these sample installer response files. Choose the correct sample file to start with, based on the database you plan to use and whether you install it with RICOH ProcessDirector or install your own version.

The sample files are:

Embedded_PostgreSQL.properties
Use with the default database configuration: PostgreSQL installed at the same time as RICOH ProcessDirector.
Embedded_DB2.properties
Use with IBM DB2 provided with RICOH ProcessDirector.
External_PostgreSQL.properties
Use with a PostgreSQL database installed separately from RICOH ProcessDirector, either on the same server or a different server.
External_DB2.properties
Use with IBM DB2 installed separately from RICOH ProcessDirector, but on the same server.
Remote_DB2.properties
Use with IBM DB2 installed on a different server.

If you are familiar with Red Hat®Ansible® Automation Platform, we also provide a sample Ansible playbook called InstallRicohProcessDirector.yaml. You can customize and use it with the appropriate response file.

To create an installer response file:

  1. Mount the RICOH ProcessDirector base product DVD or ISO file. Open scripts/sample-response-files and find the sample file that matches your database configuration. Save the file to your system.
  2. Open the sample file in a text editor and review the contents.
  3. Do not change the settings in the first section (INSTALLER_UI and DB_TYPE).
    These settings configure the installer to run in "silent" mode and specifies the database configuration to use.
  4. Update the next two settings to accept the license and maintenance agreements.

    Review the agreements here:

    Remove the # sign at the beginning of these lines to indicate acceptance:

    #LICENSE_AGREEMENT=ACCEPT
#MAINTENANCE_AGREEMENT=ACCEPT

  5. For USER, enter the ID for the system user, the user ID that RICOH ProcessDirector runs under.
    You can choose the name that you want to use for the RICOH ProcessDirector system user or you can use the default name. 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.

    For additional information about the system user and groups, see Creating system groups and users.

  6. Enter additional information for the system user. Default values are shown in the file.
    GROUP
    The security group to use as the primary group for the system user.
    UID
    The UID for the system user.
    GID
    The GID for the primary group in GROUP.
    HOMEDIR
    The home directory for the system user.
    PW
    The password for the system user.

    Remember this password; you need it later when you have to log in as the system user.

  7. For SYSTEM_LANGUAGE, choose the language that you want the system user to use.
    This setting determines the language used for some messages, even if you set the browser for the user interface to a different language. Copy and paste the appropriate language value. Values are case-sensitive.
  8. Continue editing based on your database type:
    1. PostgreSQL installed with RICOH ProcessDirector: File is complete. Continue with step .
    2. PostgreSQL installed separately: Continue with step .
    3. DB2 installed with RICOH ProcessDirector: Continue with step .
    4. DB2 installed separately on the same server: Continue with step .
    5. DB2 installed on a different server: Continue with step
  9. If you choose PostgreSQL installed separately, set up the remote PostgreSQL database server connection:
    1. If you have not completed the procedure in Configuring your own PostgreSQL database, do that procedure now.
    2. After you complete that procedure, enter values for these fields:
      PGSQL_TOOLS
      The location of the PostgreSQL bin directory. The default binary path is /usr/<version_number>/bin, where <version_number> is the PostgreSQL database version installed.
      PGSQL_SERVER
      The IP address or host name of the server where PostgreSQL is installed.
      PGSQL_PORT
      The port number used to communicate with the PostgreSQL database.
      PGSQL_USER
      The user name for the owner of the PostgreSQL database.
      PGSQL_PASSWORD
      The password for the owner of the PostgreSQL database.
    3. Continue with step .
  10. If you use IBM DB2 included with RICOH ProcessDirector or a separate DB2 on the same server, both configurations require an instance user, a fenced user, and their corresponding groups. Information about these values is available in Creating system groups and users.
    1. Set these values:
      DB2_INSTANCE_USER
      The user ID that the RICOH ProcessDirector DB2 database instance runs under.
      DB_INSTANCE_DIR
      The home directory for the DB2 instance user on the primary server.
      DB_INSTANCE_GROUP
      The group used to give members DB2 sysadm authority for database operation.
      DB_FENCED_USER
      A second user ID that DB2 requires when you create an instance.
      DB_FENCED_DIR
      The home directory for the DB2 fenced user on the primary server.
      DB_FENCED_GROUP
      The internal group required by DB2; the default or primary group for the fenced user.
    2. For the RICOH ProcessDirector version of DB2, set DB2_INSTALLER_FOLDER to the installation media location (mount point) for the DB2 install ISO or DVD.
    3. For a separate DB2 on the same server, set DB2_INSTALL_PATH to the base directory where DB2 is installed.
    4. Continue with step .
  11. If you use DB2 installed on a different computer, the configuration requires an instance user and group for the DB2 client on the primary computer. It also requires an instance user, a fenced user, and their corresponding groups for the DB2 server on the other computer.

    You created these users and groups when you installed and configured the DB2 client and server in Installing and configuring your own copy of DB2 on a different computer. If you have not completed that procedure, do it now.

      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.
    1. For DB2_INSTALL_PATH, enter the full path to the install location for the DB2 client on the primary server.
    2. Enter values for the users and groups that you created in the previous procedure.
      DB2_INSTANCE_USER
      The instance user for the DB2 client on the primary server.
      DB_INSTANCE_DIR
      The home directory for the DB2 instance user on the primary server.
      DB_INSTANCE_GROUP
      The DB2 instance group on the primary server.
      DB_REMOTE_HOST
      The host name or IP address of the server that DB2 is installed on.
      DB_REMOTE_PORT
      The port that you want DB2 to listen on to communicate with the primary server.
      DB_REMOTE_USERID
      The DB2 user on the remote server.
      DB_REMOTE_DIR
      The home directory for the DB2 user on the remote server.
      DB_REMOTE_PASSWD
      The password for the DB2 user on the remote server.
    3. Continue with step .
  12. Save the file and copy it to a location on the primary computer. When you run the installer, you provide the path to this file. The file must be stored in a location that is accessible to the installer.
Now you're ready to run the installation program in automated mode. Choose your next step based on how you plan to run the install media:
Parent topic: Installing