Novell OPEN ENTERPRISE SERVER 2.0 SP2 - UPGRADING TO OES-PLANNING AND IMPLEMENTATION GUIDE 12-2009 Implementation Manual page 124

"Tips and Caveats" on page 124
"Transferring iPrint in a Cluster" on page 124
How Clustered iPrint Migration Works
The OES 2 SP2 Migration Tool (miggui) contains an NLM
the iPrint data from the cluster to an XML text file named
that you created in
the root of the volume.
The migration tool uses the information in
driver store, create printer agents, etc. The tool also changes the names of the old iPrint objects in
eDirectory by appending
objects. All changes are completely transparent to iPrint users.
Tips and Caveats
Legacy queue-based printing cannot be serviced by an OES 2 SP2 Printer Agent.
You can manage both OES iPrint and NetWare iPrint from NetWare, but you can only manage
OES iPrint from OES.
You must create the iPrint NSS pool and volume as instructed in
adding OES nodes to the cluster or running the migration.
Transferring iPrint in a Cluster
1 Download the
iprint_load.sh)
oes2/scripts/iprint_unload.sh)
2 Customize the iPrint load script for your iPrint pool resource by doing the following:
2a In iManager, access the load script for the destination iPrint pool resource.
2b Copy and paste the contents of the downloaded
of the current load script.
2c Using the information in the current script, replace each variable (indicated by <angle
brackets>) with the correct values for the cluster resource.
For example, if the first line in the current script reads
nss /poolactivate=POOLNAME
Modify the third line in the downloaded script to read
exit_on_error nss /poolact=POOLNAME
2d Remove all of the lines down to the first line you inserted.
2e Click Apply.
3 Customize the iPrint unload script for your iPrint pool resource by doing in the following:
3a In iManager, access the unload script for the destination iPrint pool resource.
3b Copy and paste the contents of the downloaded
line of the current unload script.
3c Using the information in the current script, replace each variable (indicated by <angle
brackets>) with the correct values for the cluster resource.
124 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide
Step 2 on page 120. The
psminfo.xml
to each name. The old names can then be applied to the new printer
_nw
script (http://www.novell.com/documentation/oes2/scripts/
iprint_load.sh
and the
iprint_unload.sh
from the OES 2 Documentation Web site.
named
TM PSMINFO.NLM
psminfo.xml
file is located in an
psminfo.xml
to create new printer objects, set up the
script (http://www.novell.com/documentation/
iprint_load.sh
iprint_unload.sh
that copies all of
on the iPrint NSS volume
directory at
/ndps
Step 2 on page 120 prior to
file below the last line
file below the last