Environment
Situation
This TID shows how to overcome the above described limitation.
Resolution
This TID won't attempt to document how to configure an iPrint cluster. However, it is important to note that the iprint_nss_relocate script must be run on every node which intends to host an iPrint resource.
While following this TID allows any iPrint resource to load to any cluster node, these steps will not allow multiple Print Managers or Driver Stores to run on the same node at the same time. You must use RME Groups to define sets of resources which will not run at the same node at the same time.
3. Modify the iPrint resource cluster load script
a. iManager -> Cluster Manager -> Select the Cluster -> click the iPrint resource link -> Scripts
ignore_error rm /etc/opt/novell/iprint/conf
ignore_error ln -s /media/nss/<VolumeName>/etc/opt/novell/iprint/conf /etc/opt/novell/iprint/conf
ignore_error rm /var/opt/novell/iprint
ignore_error ln -s /media/nss/<VolumeName>/var/opt/novell/iprint /var/opt/novell/iprint
ignore_error rm /var/opt/novell/log/iprint
ignore_error ln -s /media/nss/<VolumeName>/var/opt/novell/log/iprint /var/opt/novell/log/iprint
sed -i s:/media/nss/[A-Za-z0-9]*:/media/nss/<VolumeName>:g /etc/opt/novell/iprint/httpd/conf/iprint_g.conf
ignore_error mv /media/nss/<VolumeName>/var/opt/novell/iprint/iprintgw.lpr /media/nss/<VolumeName>/var/opt/novell/iprint/iprintgw.lpr.bak
exit_on_error rcnovell-idsd start
exit_on_error rcnovell-ipsmd start
/etc/init.d/apache2 reload
exit 0
Click Apply