Planning for configuration

Destination configuration models show the relationships among logical destinations, job- and document-attribute defaults, queues, and actual destinations. Your standard InfoPrint destination configuration, the one created during installation, has a one-to-one relationship between a logical destination and an actual destination, and provides minimal job- and document-attribute default setting. As you customize your InfoPrint environment to support your printing needs, you might want to consider a more complex destination configuration model.

For any of the configuration models, while the logical destination and the queue that it sends jobs to must reside in the same InfoPrint server, the actual destination can be running in a different InfoPrint server running on a different AIX, Linux, or Windows system. However, to submit jobs directly to the actual destination, the actual destination must reside in the same server as the logical destination and queue.

In this section:

  1. Default model
  2. Desktop destination configuration model
  3. Pool destination configuration model
  4. Funnel destination configuration model
  5. Hourglass destination configuration model
  6. Recommended distributed configuration model
  7. Cloud considerations
  8. Running InfoPrint Manager for Linux in a Docker container
Parent topic: Planning Guide