Configuring Anyplace Print Queues

In addition to creating Pull Print actual destinations, you can create special queues to hold jobs that you want your LDAP authenticated users to be able to pull to any Pull Print printer or Anyplace printer. These Anyplace queues have no actual destinations associated with them and can only accept LDAP authenticated jobs. Authenticated user's jobs in Anyplace queues appear on all Pull Print and Anyplace printers.

To create an Anyplace queue, set the initially settable queue-type attribute to anyplace-queue when you create it. The queue-type attribute cannot be changed once a queue is created.

Note: An Anyplace queue and an Anyplace logical destination can be created from the command line or from the Administration GUI.

Anyplace queues support a subset of the standard queue attributes and queue operations. For more information, see the RICOH InfoPrint Manager: Reference publication.

Configuration considerations for Anyplace Print queues

Like standard queues, logical destinations can be created and associated with Anyplace queues. This allows job and document defaults to be applied to Anyplace jobs just like other jobs. These are the only job and document attribute defaults that are applied to the job.

Whether a particular Pull Print actual destination can support the job and document attributes of a job cannot be determined until a print request is made from the printer. This means Anyplace jobs can appear on the Anyplace tab on the printer console that cannot be printed on that printer. An error is returned when the attempt to print the job is made at the console. If an error is returned, the job remains in the Anyplace queue. If the print request is successful, the job is moved to the Pull Print actual destination's queue and behaves like a released Pull Print job. It cannot be pulled to another Pull Print printer even if it does not print for a while.

Required logical destination configuration for Anyplace queues when printing to a StreamlineNX server (Anyplace printer)

When jobs are submitted to a logical destination that routes into an Anyplace queue, InfoPrint Manager must be able to determine which logical destination is allowed to process the job after it is released at an Anyplace printer. To enable this routing, the logical destination must specify a processing logical destination that is associated with an Anyplace actual destination.

Setting the processing-logical-destination-requested attribute

In the initial-value-job configuration of the logical destination that receives submissions from the Anyplace queue, you must set processing-logical-destination-requested to a logical destination that is assigned to an actual destination configured as an Anyplace printer. You must configure this attribute when a logical destination is used as the submission point for Anyplace jobs, and when jobs are expected to be released at StreamlineNX printers.

This attribute ensures that InfoPrint Manager can:

  • Identify which logical destinations are eligible to process the job after the Pull Print release
  • Map the job to the correct Anyplace actual destination
  • Make the job available for authenticated retrieval at StreamlineNX printers
Without this setting, jobs submitted to the logical destination may:
  • Remain in the Anyplace queue without routing
  • Be rejected at release time

From an operational viewpoint, a correct configuration ensures that:

  • Jobs submitted from desktops or applications into an Anyplace workflow are properly routed
  • StreamlineNX printers can retrieve and print the job after user authentication
  • Pull Print behavior is consistent across all StreamlineNX devices

Configuring additional Anyplace InfoPrint Manager systems

To configure additional Anyplace InfoPrint Manager systems:

  1. Identify the additional Anyplace InfoPrint Manager systems to the Pull Print Web application and make sure these are not command processors in the primary system.

    Add the additional Anyplace InfoPrint Manager systems by using the InfoPrint Manager SMIT (AIX), IPMMI (Linux), or IPMMC (Windows) interface.

    To configure the Pull Print Feature setting with additional Anyplace command processors of remote InfoPrint Manager systems, you must set the Additional Anyplace systems field.

    This field specifies the list of the IP addresses and ports of the Anyplace systems that the Web application can use in order to pull jobs.

    Note: The InfoPrint Manager SMIT (AIX) interface allows you to add only two additional Anyplace InfoPrint Manager systems. If you need to add more additional Anyplace InfoPrint Manager systems, call support for assistance on how to do this.

    See Configuring the Pull Print Feature Web Application to Work with the InfoPrint Manager System, for more information about how to use these interfaces.

  2. On the additional servers, if you do not have the Pull Print Feature installed on the remote InfoPrint Manager systems, you must set the proper InfoPrint Manager Security that allows the Web application to perform the required operations.

    Use the instructions from Managing InfoPrint Manager Security for the Pull Print Feature to set the InfoPrint Manager Security for the Anyplace InfoPrint Manager systems.

  3. On each additional system, you must create Anyplace queues.

    Use the InfoPrint Manager Java GUI or the command line, to create the Anyplace queues.

Parent topic: Configuring InfoPrint Manager Server Software