Requirements
- JDK 1.5+
- Apache ant 1.7+
- CUPS 1.3.2+
- Samba 3.0.24+
First install
Download
Download the latest version of the package esup-cupsbackend from http://sourcesup.cru.fr/frs/?group_id=319
Uncompress
Unzip the distribution files somewhere in your source hierarchy (something like /usr/local/src/esup-backend).
This will create a foder like /usr/local/src/esup-cupsbackend/esup-cupsbackend-x.y.z.
Configure
Edit the following configuration files to fit to your environment (examples are provided):
- /build.properties: tell the application where and how to install.
- /properties/config.properties: configure the application runtime.
- /properties/logging/log4j.properties: configure the logs of the backend.
- /properties/logging/log4j-batch.properties: configure the logs of the batch commands. The folder tmpDir set in /properties/config.properties should be writable by the CUPS user (usually lp) as it used by esup-cupsbackend to store the states of the queues. The folder that contains the logs (see /properties/logging/log4j.properties) should also be writable by the CUPS user (the folder and not just the file, to allow log4j rotations).
Deploy
Simply run:
ant deploy
Use
When modifying a printer through the CUPS web interface, CUPS should now show a new backend named ESUP-Portail.
Use a URI of one of the following forms:
esup://address?backend=socket&port=xxx[&accounting=xxx] esup://address?backend=ipp[&port=xxx]&path=xxx[&accounting=xxx] esup://address?backend=lpd&path=xxx[&accounting=xxx]
Parameter backend is the real backend used by esup-cupsbackend to effectively print the job, other parameters are backend-dependent.
Possible accounting implementations are defined in /properties/domain/domain.xml. A common URI when using the ESUP-Portail CUPS backend is:
esup://printer.domain.edu?backend=socket&port=9100&accounting=hp
Upgrades
Download the latest version of your package and install beside your previous installation at the same filesystem level (/usr/local/src/esup-cupsbackend in our example).
unzip the package.
go to the newly created directory.
Recover your previous configuration files by running:
ant recover-config
Deploy:
ant deploy