Installing InfoPrint Manager for Linux on a Linux HA server

Once you have verified the failover of your Linux HA system, you can use the following procedure to install InfoPrint Manager for Linux.

1. Mount all the filesystems on the primary server but not on the secondary or backup server.
   Note: /var/psf/segments filesystem must be a local filesystem that must not be mirrored on a shared Storage Across Network (SAN).
2. Run the InfoPrint Manager Installer on both the primary and the backup server. When installing on the primary server, use the -V flag. When installing on the secondary or backup server, use the -v flag.
3. Stop and disable the following InfoPrint Manager services by running the following commands:

   InfoPrint Manager Web Server

   systemctl is-active --quiet ipm-ws.service && systemctl stop ipm-ws.service
   systemctl disable ipm-ws.service
   

   InfoPrint Manager IPPGW

   systemctl is-active --quiet ipm-ippgw.service && systemctl stop ipm-ippgw.service 
   systemctl disable ipm-ippgw.service
   

   InfoPrint Manager MVS Download

   systemctl is-active --quiet ipm-mvsd.service && systemctl stop ipm-mvsd.service 
   systemctl disable ipm-mvsd.service

   InfoPrint Manager LPD

   systemctl is-active --quiet ipm-lpd.service && systemctl stop ipm-lpd.service 
   systemctl disable ipm-lpd.service
   

   InfoPrint Manager SAP

   systemctl is-active --quiet ipm-sapcbd.service && systemctl stop ipm-sapcbd.service 
   systemctl disable ipm-sapcbd.service
   

   InfoPrint Manager PDServers

   systemctl is-active --quiet ipm-pdservers.service && systemctl stop ipm-pdservers.service 
   systemctl disable ipm-pdservers.service

   InfoPrint Manager Notification

   systemctl is-active --quiet ipm-notifyd.service && systemctl stop ipm-notifyd.service 
   systemctl disable ipm-notifyd.service

   InfoPrint Manager LDAP Cache

   systemctl is-active --quiet ipm-lcd.service && systemctl stop ipm-lcd.service 
   systemctl disable ipm-lcd.service

   InfoPrint Manager Licensing

   systemctl is-active --quiet ipm-licverd.service && systemctl stop ipm-licverd.service 
   systemctl disable ipm-licverd.service

4. Configure the ipmha service using the web interface. You can find more information about accessing the web interface and configuring the service in the Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, or the SUSE Linux Enterprise.
   Note: InfoPrint Manager for Linux Support does not support user modification of this script.

5. When InfoPrint Manager is not running as user root, allow the user running InfoPrint Manager to restart cups service on all your cluster nodes:

   1. Copy the /usr/lpp/pd/polkit/10-ipm-cups-restart.rules file to the /etc/polkit-1/rules.d directory.
   2. If the user running InfoPrint Manager is not ipm1, edit the /etc/polkit-1/rules.d/10-ipm-cups-restart.rules file and change the following line:

      var IPM_USER = "ipm1".

      Replace ipm1 with the actual user running InfoPrint Manager.

6. Specify the appropriate server names that must be started or stopped on one of the cluster nodes when the ipmha script runs.
   Important: Make sure that you synchronize these files on all your cluster nodes:

   • rc.pd.servers
   • rc.ippgw.daemons
   • rc.lpd.daemons
   • rc.mvsd.daemons
   • rc.ipmws.daemons
   • rc.iprsap.daemons (if available)

   These files can be found in the /etc folder.

   Note: This step needs to be performed manually on all cluster nodes.
7. Run both the InfoPrint Manager Administration GUI and the InfoPrint Manager Operations GUI on the primary node.

   Ricoh recommends against running either GUI on the backup node.

8. Once InfoPrint Manager for Linux has been installed, ensure that you synchronize cluster resources across the installation.
9. Test to make sure that your server can failover to the backup node. Check to ensure the InfoPrint system is operational by verifying standard functions, including:
   • If you are performing a manual failover event, Ricoh recommends you shut down both the InfoPrint Manager Administration GUI and the InfoPrint Manager Operations GUI on the primary node. When the file systems are moved to the backup node on a failover, both GUIs are brought down.