PaperCut Print Management on UNIX and Enterprise Systems (tracking)

KB Home   |   PaperCut Print Management on UNIX and Enterprise Systems (tracking)

Main.PrintManagementOnUnix History

Hide minor edits - Show changes to output

July 16, 2018, at 05:52 AM by 139.130.165.134 - Remove reference to "follow me" printing
Changed line 8 from:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms running CUPS to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizations have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
to:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms running CUPS to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizations have taken this further to cover other areas of print management including secure print release (pull printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
July 16, 2018, at 05:48 AM by 139.130.165.134 - Remove reference to "follow me" printing
Changed line 39 from:
[-* VPSX and LRS is a registered trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSX filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* VPSX and LRS is a registered trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSX filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (pull printing).-]
June 20, 2017, at 08:46 PM by priyanka - Updated the section in the manual. Old link no longer pointed to the correct chapter
Changed line 22 from:
PaperCut has a number of features to help with identifying the user of a document from an enterprise product such as JD Edwards, SAP, Oracle Financial, etc. This functionality is discussed in detail in the PaperCut Manual under [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-external-usernames.html|Advanced Print Management - Username Extraction]].
to:
PaperCut has a number of features to help with identifying the user of a document from an enterprise product such as JD Edwards, SAP, Oracle Financial, etc. This functionality is discussed in detail in the PaperCut Manual under [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-external-usernames.html|Advanced Print Management - Username Extraction]].
April 28, 2016, at 03:47 PM by timg - Removed AS400 formatting
Changed line 4 from:
''[-(also applies to other systems like `AS400, iSeries, etc.)-]''
to:
''[-(also applies to other systems like [=AS400=], iSeries, etc.)-]''
Changed lines 13-14 from:
Some sites have chosen to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server). A detailed example of queue forwarding exists in this [[https://www.papercut.com/kb/Main/QueueRedirectionLinuxExample|article]].
to:
Some sites have chosen to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server).
Added lines 17-18:
A detailed example of queue forwarding exists in this [[https://www.papercut.com/kb/Main/QueueRedirectionLinuxExample|article]].
Changed lines 13-14 from:
Some sites have chosen to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server).
to:
Some sites have chosen to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server). A detailed example of queue forwarding exists in this [[https://www.papercut.com/kb/Main/QueueRedirectionLinuxExample|article]].
Changed lines 6-7 from:
A: PaperCut will run on Linux out of the box and this is a standard supported platform.  Other UNIX systems are however less popular and hence treated as custom environments, however they must be running the [[http://www.cups.org/ CUPS]] printing system.  Each implementation is approached differently depending on requirements, architecture, and level of tracking required.
to:
A: PaperCut will run on Linux out of the box and this is a standard supported platform.  Other UNIX systems are however less popular and hence treated as custom environments, however they must be running the [[http://www.cups.org/|CUPS]] printing system.  Each implementation is approached differently depending on requirements, architecture, and level of tracking required.
September 13, 2013, at 05:05 AM by Alec - Added some wiggle by adding need for CUPS on UNIX
Changed lines 6-9 from:
A: PaperCut will run on Linux out of the box and this is a standard supported platform.  Other UNIX systems are however less popular and hence treated as custom environments.  Each implementation is approached differently depending on requirements, architecture, and level of tracking required.

We encourage organizations considering implementing print control or [[https://www
.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizations have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
to:
A: PaperCut will run on Linux out of the box and this is a standard supported platform.  Other UNIX systems are however less popular and hence treated as custom environments, however they must be running the [[http://www.cups.org/ CUPS]] printing system.  Each implementation is approached differently depending on requirements, architecture, and level of tracking required.

We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms running CUPS
to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizations have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
Changed lines 13-14 from:
Some sites have choose to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server).
to:
Some sites have chosen to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server).
October 07, 2012, at 11:21 PM by ian - Added erp keyword
Changed line 42 from:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing, iseries, SAP -]
to:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400, as400 printing, iseries, SAP, erp -]
Changed lines 20-21 from:
PaperCut has a number of features to help with identifying the user of a document from an enterprise product such as JD Edwards, SAP, Oracle Financial, etc. This functionality is discussed in detail in the PaperCut Manual under [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-external-usernames.html|Advanced Print Management]]
to:
PaperCut has a number of features to help with identifying the user of a document from an enterprise product such as JD Edwards, SAP, Oracle Financial, etc. This functionality is discussed in detail in the PaperCut Manual under [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-external-usernames.html|Advanced Print Management - Username Extraction]].
Added lines 19-21:
!!Username Extraction
PaperCut has a number of features to help with identifying the user of a document from an enterprise product such as JD Edwards, SAP, Oracle Financial, etc. This functionality is discussed in detail in the PaperCut Manual under [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-external-usernames.html|Advanced Print Management]]

Changed line 42 from:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing, iseries, SAP -]
to:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing, iseries, SAP -]
Changed lines 10-11 from:
Here is a summary of integration methods used:
to:
The general approach to monitor these queues is to forward the jobs to another server running PaperCut.
Changed lines 17-21 from:
!!LPR Alias/Wrapping
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc
.gnu.org/|GCC]] is available.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.

This custom compile/build will require you to engage PaperCut on a consulting basis to compile this special and configure this integration.  The development team will also usually require remote access to the system and GCC compiler tools to compile the program for your platform
.
to:
NOTE: When jobs are sent via Unix or forwarded the information about the originating username and workstation is not known (e.g. the IP address of the workstation the user printed from).  For this reason, some user client that rely on this information may not be possible to use (e.g. client popup authentication, account selection, etc).
Deleted lines 21-23:
!!Native CUPS
If the system is configured to run [[http://cups.org/|CUPS]], PaperCut's CUPS integration can be leveraged.  Again, this will require a special build for the given architecture and the development team will usually request remote access and GCC to compile this up.

Deleted lines 11-13:
!!LPR Alias/Wrapping
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc.gnu.org/|GCC]] is available.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.

Added lines 15-21:
This is the best option for sites running on these systems, as it allows PaperCut to run on one of the standard/supported operating systems, and also allows tracking of jobs from this other UNIX system.

!!LPR Alias/Wrapping
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc.gnu.org/|GCC]] is available.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.

This custom compile/build will require you to engage PaperCut on a consulting basis to compile this special and configure this integration.  The development team will also usually require remote access to the system and GCC compiler tools to compile the program for your platform.

Changed lines 23-24 from:
If the system is configured to run [[http://cups.org/|CUPS]], PaperCut's CUPS integration can be leveraged.  Again, this will require a build for the given architecture and the development team will usually request remote access and GCC to compile this up.
to:
If the system is configured to run [[http://cups.org/|CUPS]], PaperCut's CUPS integration can be leveraged.  Again, this will require a special build for the given architecture and the development team will usually request remote access and GCC to compile this up.
Changed lines 36-37 from:
[-* VPSX and LRS is a registered trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* VPSX and LRS is a registered trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSX filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
Changed lines 13-14 from:
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc.gnu.org/|GCC]] is avlaiable.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.
to:
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc.gnu.org/|GCC]] is available.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.
Changed lines 1-2 from:
(:title PaperCut Print Management on UNIX and Enterprise Systems:)
to:
(:title PaperCut Print Management on UNIX and Enterprise Systems (tracking) :)
Changed lines 22-24 from:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  This has been done in the past using various methods such as:

-->'''Integration with special spooler systems such as VPSX'''
to:
In many cases, PaperCut can track configured from special Unix software or enterprise applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  This has been done in the past using various methods including:

-->'''Integration with special spooler sub-systems such as VPSX'''
Changed lines 28-29 from:
-->PaperCut may be configured to retrospectively loading print jobs.  See [[https://www.papercut.com/products/ng/manual/apdx-tools-importing-jobs.html|importing print job details]] for more information.
to:
-->PaperCut may be configured to retrospectively loading print jobs. For example, SAP print event logs.  See [[https://www.papercut.com/products/ng/manual/apdx-tools-importing-jobs.html|importing print job details]] for more information.  This approach has been taken at a number of sites who require consolidated [[https://www.papercut.com/solutions/print-audit-for-business/|print audit]] reports.
Changed lines 8-9 from:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizaitons have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
to:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizations have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.
Changed line 41 from:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing -]
to:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing, iseries, SAP -]
Changed lines 4-5 from:
''[-(also applies to other systems like `AS400)-]''
to:
''[-(also applies to other systems like `AS400, iSeries, etc.)-]''
Changed lines 1-2 from:
(:title PaperCut Print Management on UNIX systems:)
to:
(:title PaperCut Print Management on UNIX and Enterprise Systems:)
Changed lines 21-23 from:
!!Special Systems
In
many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx* from [[http://www.lrs.com/|LRS]], retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
to:
!!Special System Integration
In
many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  This has been done in the past using various methods such as:

-->'''Integration with special spooler systems such as VPSX'''
-->PaperCut has been integrated with special print spooling systems such as VPSX* from [[http://www.lrs.com/|LRS]] (see [[PaperCutInstallationOnVPSX|+]] for more details).  In some cases this process has involved working with report developers
on the site to ensure job owner ID's are embedded in the spool content.

-->'''Post processing of print event logs'''
-->PaperCut may be configured to retrospectively loading print jobs.  See [[https://www.papercut.com/products/ng/manual/apdx-tools-importing-jobs.html|importing print job details]] for more information.

We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.  All successful projects need good resources dedicated to the project management.


Changed lines 36-37 from:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* VPSX and LRS is a registered trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
Changed lines 4-5 from:
to:
''[-(also applies to other systems like `AS400)-]''
Changed line 32 from:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing -]
to:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing, AS 400. as400 printing -]
Changed lines 26-27 from:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality (Windows, Linux, Mainframe) to implement print tracking, accounting and secure print release (follow me printing).-]
Changed lines 7-8 from:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Here is a summary of integration methods used:
to:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Historically print management on UNIX system has been limited to logging and auditing, however some organizaitons have taken this further to cover other areas of print management including secure print release (follow me printing), account allocation via popup client software, print routing, and printer error tracking. These are regarded as more advanced topics and often require planning.

Here is a summary of integration methods used:
Changed lines 24-25 from:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with `VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]
Changed lines 24-25 from:
[-* VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]
to:
[-* `VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]
Changed lines 19-20 from:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from [[http://www.lrs.com/|LRS]], retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
to:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx* from [[http://www.lrs.com/|LRS]], retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
Added lines 23-25:

[-* VPSx is a trademark of Levi, Ray & Shoup, Inc.  PaperCut has conducted integration with VPSx filter functionality to implement print tracking, accounting and secure print release (follow me printing).-]

Changed lines 19-20 from:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
to:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from [[http://www.lrs.com/|LRS]], retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
Changed lines 19-20 from:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, P`eopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
to:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, `PeopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
Changed lines 19-20 from:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, PeopleSoft, Oracle Financial, JDEdwards, etc.  In some cases this is done by integrating with special print spooling systems such as VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
to:
In many cases, PaperCut can track configured from special Unix software applications such as SAP, P`eopleSoft, Oracle Financial, JD Edwards, etc.  In some cases this is done by integrating with special print spooling systems such as `VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.
Added lines 18-20:
!!Special Systems
In many cases, PaperCut can track configured from special Unix software applications such as SAP, PeopleSoft, Oracle Financial, JDEdwards, etc.  In some cases this is done by integrating with special print spooling systems such as VPSx from LRP, retrospectively loading print jobs, or working with report developers to ensure job owner ID's are embedded.  We find that these types of applications are heavily customized for site specific requirements and hence integration is considered on an implementation by implementation basis.

Changed line 23 from:
[-keywords: sun, HP, IBM Unix, Legacy Unix, lpd printing -]
to:
[-keywords: sun, HP-UX, IBM Unix, Legacy Unix, lpd printing -]
Changed lines 10-11 from:
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where GCC is avlaiable.  A command-line tool is avlaible and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.
to:
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where [[http://gcc.gnu.org/|GCC]] is avlaiable.  A command-line tool is available and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.
Changed lines 7-9 from:
We encourage organizations considering implementing print control or print management on UNIX platforms to open dialog with our development/support team. Here is a summary of integration methods used:

!!LPR Prox/Wrapping
to:
We encourage organizations considering implementing print control or [[https://www.papercut.com/|print management software]] on UNIX platforms to open dialog with our development/support team. Here is a summary of integration methods used:

!!LPR Alias/Wrapping
Changed lines 16-17 from:
If the system is configured to run CUPS, PaperCut's CUPS integration can be leveraged.  Again, this will require a build for the given architecture and the development team will usually request remote access and GCC to compile this up.
to:
If the system is configured to run [[http://cups.org/|CUPS]], PaperCut's CUPS integration can be leveraged.  Again, this will require a build for the given architecture and the development team will usually request remote access and GCC to compile this up.
Changed lines 7-8 from:
We encourage organizations considering implementing print control or print management on UNIX platforms to open dialog with our development/support team.  Here is a summary of integration methods used:
to:
We encourage organizations considering implementing print control or print management on UNIX platforms to open dialog with our development/support team. Here is a summary of integration methods used:
Added lines 18-19:
In conclusion, UNIX printing is potentially a complex topic and needs to be carefully reviewed and considered. Implementation should also be approach pragmatically and cooperation is required by all parties (Unix system administrations, application manages, and PaperCut).  A budget for PaperCut consulting is advised to ensure a supported implementation.
Added lines 18-21:
----
''Categories:'' [[!Implementation]]
----
[-keywords: sun, HP, IBM Unix, Legacy Unix, lpd printing -]
Added lines 1-17:
(:title PaperCut Print Management on UNIX systems:)

Q: What options does PaperCut provide to run on AIX/HPUX/Solaris?

A: PaperCut will run on Linux out of the box and this is a standard supported platform.  Other UNIX systems are however less popular and hence treated as custom environments.  Each implementation is approached differently depending on requirements, architecture, and level of tracking required.

We encourage organizations considering implementing print control or print management on UNIX platforms to open dialog with our development/support team.  Here is a summary of integration methods used:

!!LPR Prox/Wrapping
PaperCut's ''print provider'' code (native C) can be compiled on all major Unix platforms/architectures where GCC is avlaiable.  A command-line tool is avlaible and this, along with some shell scripting, can be used to alias, proxy or wrap the [@lp@] or [@lpr@] commands to intercept and track jobs.

!!Queue Forwarding
Some sites have choose to avoid native code and instead forward the UNIX queues through to say a Linux CUPS server.  The jobs spool via the Linux system before being passed through to the physical printer.  PaperCut is installed on the Linux system (usually as a secondary server reporting to say a Windows server).

!!Native CUPS
If the system is configured to run CUPS, PaperCut's CUPS integration can be leveraged.  Again, this will require a build for the given architecture and the development team will usually request remote access and GCC to compile this up.

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on July 16, 2018, at 05:52 AM
Printable View   |   Article History   |   Edit Article