Setting up Print Daemons in Aleph 15

Setting up print daemons in Aleph 15.n Based on Documentation from Anne Bressler, [email protected], modified by David Wuolu [email protected] 20041102

Note: these instructions will guide you to set up a method of emailing notices. The reason we use the print daemon is so that it gives a subject heading in the email message. Most of this stuff is actually controlled by the individual client installation.

1. Overview / 2. Not covered here / 3. Server setup / 4. Client setup / 5. Admin permissions

1. Overview: run the printd client executable (C:\AL500\JOBMGR\BIN\PRINTD.EXE) to print all files on the server with a specified filename extension (Aleph calls this a "Print ID"). If left running, the print daemon check at set intervals and print all new files with that Print ID as they are created. Note: Print IDs should be in lower case.

The print daemon copies each file to the local workstation's C:\AL500\JOBMGR\files\xxx50\print\history directory, creating a subfolder for each day, and within that subfolders for each hour. Notices/printouts are broken up into individual files.

On the server side, the files are moved to a subdirectory of the print directory, using the naming convention save-yyyy-mm-dd/ so that the files will not print again if the daemon is not deactivated.

2. Not covered here: print templates; running jobs in batch mode. To customize your templates, use the Ex Libris documentation:

Customizing Printouts - XML and XSL - 15.pdf

N.B. The email letters/orders will always have the html attachment. In order for the information to also print in the body of the email message, you must have a corresponding plain-.xsl template. For a courtesy notice (loan-notice-letter.xsl), you must also create a plain-loan-notice-letter.xsl with the third line of the xsl changed from to . 3. Server setup: edit xxx50/tab/tab_file_aut, which associates Aleph usernames with Print IDs. Caveat: once you have an entry in this table ALL files with extensions will be hidden from ALL users, EXCEPT when associated in the table. All files without extensions will be visible to all users. Sample tab_file_aut setup:

!======! tab_file_aut !Authorization for report printing !======! ! 1 2 3 ...... !!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!! csb DWUOLU JENN BONNIE TESS NICOLE sju DWUOLU BETTY BONNIE TESS BEV

With this setup, when JENN opens the task manager, any files in the selected library's print directory which end in .csb will be displayed in the Remote file list. BETTY will see files ending in .sju. No other users than the ones explicitly listed here will see these files.

4. Client setup: edit the following client files (assuming your clients are in C:\AL500)

C:\AL500\JOBMGR\TAB\JOBMGR.INI C:\AL500\JOBMGR\TAB\PER_LIB.INI C:\AL500\JOBMGR\TAB\PRINT.INI C:\AL500\JOBMGR\TAB\ENG\print.dat C:\AL500\ALEPHCOM\TAB\ALEPHCOM.INI

C:\AL500\JOBMGR\TAB\JOBMGR.INI: relevant lines are:

[General] Targets=csb,sju /*these print IDs will be displayed in the "Print Daemon -- Set Up Print Daemon" window PrintdAutoActivate=N /*determines whether print daemon is activated when Task Manager is opened PrintdAutoDeactivate=N /*determines whether print daemon is deactivated after last qualifying file is printed

[PrintDaemon] SleepTime=120 /*Interval at which printd will check server for files Libraries=SBJ50 /*Client connects to this library by default Targets=csb /*Print ID selected in "Print Daemon -- Set Up Print Daemon" window is stored here C:\AL500\JOBMGR\TAB\PER_LIB.INI: add all libraries whose print directories you wish to access

!------! ! List of permitted libraries ! !----> SBJ50 SBJ30

C:\AL500\JOBMGR\TAB\PRINT.INI: this is where you specify whether the file is printed, mailed, or both. In this example, orders will be printed to the pc's default printer, and overdues will be emailed. ("filename.prn" is a litteral ... it doesn't seem to apply to processing server files)

!------! ! 1 - function name ! 2 - version ID (00-99) ! 3 - display Print Setup window (Y/N) ! 4 - mail default (M-Email/P-Print/B-Both) ! 5 - local filename ! 6.1-6.10 - print ID (off-line printing/printer dispatching) - optional ! ! 1 2 3 4 5 6.1 6.2 6.3 ... !------+--+-+-+------+------+------+------... sju 00 N P filename.prn csb 00 N M filename.prn

C:\AL500\JOBMGR\TAB\ENG\print.dat: this is where you get subject lines for your email. Consequently, you must have a separate print ID for each subject line you wish to use.

!------! ! Printout Texts ! ! ID Data ! 40 255 !------!------> sju -SJU Circulation: return or renew materials csb -CSB Circulation: return or renew materials C:\AL500\ALEPHCOM\TAB\ALEPHCOM.INI: very important! The following lines must be filled in (without a mail server or return address, email will NOT go out, though you won't get any error to tell you it failed!) Another thing to verify with your email server administrator is that email originating from the PCs you are setting up needs to be allowed through and NOT be placed in a junk email folder. This is typically controlled via IP address, so be prepared to provide your IP addresses to the clients sending the notices. Also, we had some difficulty with Symantec antivirus scanning the outbound email and hanging for an extended period of time. We needed to turn off outbound scanning on the computers running these notices.

[Print] SaveHistoryNumberOfDays=nn [Mail] MailServer=exchange.csbsju.edu [email protected] MailerName=Clemens Library Circulation

5. Admin. permissions: users must have the following access rights for each library from which they print:

Task Manager -- All Task Manager functions Get html package -- Get html package