The administrative user has access to the following utilities.
To reinitialize the despooler on the EasySpooler server:
Click Admin in the main menu and select Reinitialize despooler from the menu options.
On the Confirmation click OK.
This utility exports the destination definitions to a script file. If necessary later, you can recreate the destinations, restoring the destination configuration to the time of the backup.
NOTE: In the case of a printer pool, the script backs up the destination, but not the pool members. If you have any printer pools, you may want to print a pool report for reference before you back up the destination database so that you have a record of the members in each pool.
NOTE: The backup can take a while to perform and it prevents you from making other requests.
To back up the destination database:
Click Admin in the main menu and select Backup destinations from the menu options.
On the Confirmation click OK.
EasySpooler backs up the destination database.
This utility runs the previously created backup script to restore the destination configuration. See Back up the Destination Database.
NOTE: In the case of a printer pool, the restoration recreates the destination, but does not add the members. You must restore the pool members manually.
NOTE: This operation can take several minutes to perform.
To restore the destination database:
Click Admin in the main menu and select Restore destinations from the menu options.
On the Confirmation click OK.
EasySpooler restores the destination database.
To display the system type and system ID for the EasySpooler server:
Click Admin in the main menu.
Select Server report from the menu options.
EasySpooler opens a new window and displays the system type and system ID for the EasySpooler server.
To display a list of all users that are currently logged in to EasySpooler:
Click Admin in the main menu.
Select User report from the menu options. The Logged in Users window opens.
Click Close.
The Web application automatically writes messages to the file webserver.log. If you installed the EasySpooler WebUI Service in the default directory, the file is in C:\Program Files\ROC\Output Management\webapp\logs on a Windows PC and in /usr/roc/om/web/logs on a UNIX system.
The Web application can also write debugging messages to webserver.log. ROC Software Technical Support may ask you to turn debugging on when assisting you in resolving a problem.
To view the Web application log:
Click Admin in the main menu and select Web application log from the menu options.
The current Web application log opens in a new window.
This utility breaks the connection between the Web UI and the EasySpooler server Then it reconnects the EasySpooler server and does an update.
To reset server updates:
Click Admin in the main menu and select Reset server updates from the menu options.
On the Confirmation click OK.
EasySpooler resets the server updates.
The EasySpooler process lpsqueue maintains and rebuilds the database files constantly based on the rebuild pctl and rebuild queue parameters defined on the Miscellaneous tab on the Global Tuning window. The parameters are:
rebuild_pctl_empty_ratio
rebuild_pctl_min_size
rebuild_queue_empty_ratio
rebuild_queue_min_size
Before the database files can be rebuilt, they must contain at least the number of entries defined in the minimum file size parameters, this value includes deleted entries.
The ratio of deleted entries to the file size determines when to rebuild the database files. The default values for the minimum file size parameters is 1000 entries and the default ratio is 0.60 (60 percent). If a queue or pctl file contains less than 1000 entries it will never be rebuilt even if all of the entries are deleted. However if there are 1000 or more entries in the files and 600 (60 percent) or more of them are deleted entries, then the files will be rebuilt such that all non-deleted entries are moved to the front of the file and the unused portion of the file is then truncated. This keeps the files from taking up too much disk space with nothing but deleted entries
Consider the parameter settings based on how busy your system is. On a busy system, where new documents are always being spooled, those documents will take up empty space and the rebuild may not need to happen often. However if a large number of documents are spooled in batch and then a long period of time passes where only a few documents are spooled, then it may be necessary to reclaim disk space.
Although it is not usually recommended, you can also perform file maintenance manually if needed. You may need to rebuild the database files manually if you have very long host names and/or user names and they change on a regular basis.
Rebuilding the database:
Creates a new queue file for the server and writes into it only the active documents and those that could be reactivated
Removes inactive documents.
Rebuilds the printer control (pctl) database
For more information, see the sections lpsqueue and queue in Chapter 2 of the ROC EasySpooler Developer’s Guide. Also see the addp maintenance option in Chapter 2 of the ROC EasySpooler Developer’s Guide.
CAUTION: The process of rebuilding the database may take a few minutes to complete. You must stop ALL processing. We recommend that you put all active documents on hold before continuing. If EasySpooler is currently processing documents, it waits until they are completed.
To manually perform file maintenance:
Click Admin in the main menu and select File maintenance from the menu options.
NOTE: This option is also available on the EasySpooler Server window. Select Admin from the main menu. Select EasySpooler server from the first drop-down menu options and select Server status from the second drop-down menu options. The File maintenance is under the Tools section of the window.
NOTE: For more information on maintaining the queue file, see the section lpsqueue in Chapter 2 of the ROC EasySpooler Developer’s Guide.