Installing server software and trial versions of features locally (unattended)

Use this procedure to install the InfoPrint Manager software unattended:

  1. Copy the InfoPrint Manager ISO file locally.
  2. To mount the ISO file, enter this command:
    mount /<iso_file_location>/media/<mount_point>
  3. Create a response file containing all the user input. A response file template named ipin_response is included in the media/<mount_point>/templates directory of the InfoPrint Manager for Linux ISO.
    There are notes in the response file to guide you with your answers. For more information about user input, see Preparing to use the InfoPrint Manager Installer.
  4. Copy the /media/<mount point>/templates/ipin_response file into a different directory (such as /tmp), using this command:
    cp/media/<mount point>templates/ipin_response/tmp/ipin_response

    The /media/<mount point>templates/ipin_response file contains all of the potential input variables. See Sample ipin_response file for an example of the ipin_response file.

  5. Use your Linux editor of choice to specify the install options you require in the /tmp/ipin_response file. Accept the acceptLicense, and set the psfVolumeGroup, pdVolumeGroup, and segmentsVolumeGroup to vg_<hostname> as a minimum requirement for the installation to be successful. Save the ipin_response file and exit.
  6. Specify this command to start the remote pull installation:
    /media/<mount_point>/remote_install -a /tmp/ipin_response -s /media/<mount_point>
The installation will begin by reading the values from the response file. You will not see the InfoPrint Manager Installer graphic user interface appear.
    Important:
  • This procedure only allows you to install features from the base InfoPrint Manager ISO. Any features requiring a separate media must be installed separately.
  • Sensitive information, such as principal passwords, might be included in your response file. To avoid potential security breaches, you should restrict access to the response file before saving any sensitive information in it. To begin with, you should save the response file in a directory with restricted access that is not NFS-exported to other systems. Modify the permissions and ownership of the response file to limit the users who can examine its contents. Assuming that /tmp is not NFS-exported, these commands would secure our example response file:
    chmod 600 /tmp/ipin_response
    chown root:sys /tmp/ipin_response

Note: For troubleshooting information about the installation process, refer to the specific /var/log/pd/install/*.wlog files.