6.3 Creating and Configuring a Broker and Print Manager

Before running iPrint in a cluster environment, you must create a Broker and Print Manager on the cluster-enabled volume. You should dedicate a volume for printing.

To create a Broker and Print Manager, use iManager.

To prepare the print shared disk partition for a print broker:

  1. Using Windows* Explorer, browse and select the Print volume in the eDirectory™ tree.

    This creates a client connection to the server currently hosting the volume.

  2. From a server's local volume, copy the sys:\ndps directory and subdirectories to the root directory of the shared cluster volume created for printing.

    Ensure that \ndps is the top -level directory at the root of the Print volume.

To create a Broker using iManager:

  1. From iManager, click iPrint Management > Create Broker.

  2. Fill in the fields.

    For the RMS Volume, select the shared cluster volume created for printing.

    NOTE:You cannot create a Broker object until you have copied the resource directory as explained in Step 2 in the above instructions for preparing the print volume for a print broker.

    For more information, see "Creating a Broker" in the OES iPrint Administration Guide for NetWare.

To create a Print Manager:

  1. From iManager, click iPrint Management > Create Print Manager.

  2. Fill in the fields.

    For the Database Volume select the shared cluster volume created for printing.

    For more information, see"Creating a Print Manager" in the OES iPrint Administration Guide for NetWare.

IMPORTANT:While you can have more than one Print Manager running in a cluster, only one Print Manager can run on a cluster resource node. For example, if you have a four node cluster with serverA, serverB, serverC, and serverD, you can have two print managers: one running on serverA and one on serverB and then assign them to failover to different servers: serverC and serverD. If you assign the print managers to failover to the same cluster resource node, the Print Managers will collide and not failover.