Using Define Destination
- Date: Nov 02, 2015
Using Define Destination2 Nov, 2015
Destination management is one of the most used functions of OM Plus. New destinations can be added and existing destinations can be modified or deleted. To access this component, from the OM Plus Control Panel, click Destination, and then the following OM Plus Destination Configuration screen appears.
The Define Destination interface screen was created to allow quick and easy edition of OM Plus Destinations, even in large numbers.
Adding, Deleting, and Updating Destinations
Click the “New” button in the lower left corner of the screen. The Add New Destination screen will appear. Alternately, right click on “Destinations” beneath the host name and select “New” from the popup menu.
Input a name for this destination, then select the type for this destination. After clicking “Next” the window will change to ask for more specific information depending on the category.
The destinations name from previous screen will be brought over. The drop down menu for “Protocol” will display for network printers, but will display “Type” for other groups. Similarly, the device configuration fields will change depending on what is selected from the drop down. See “Device” below for more details on the options presented in each case.
Of note, though, is the “Poll Mode” option. This option, when configured, allows the printer to be configured to send jobs to a remote i-Sat print server. For more information on i-Sat and i-Sat Plus servers and devices, please see the i-Sat documentation.
Right click on the name of the destination to be deleted, then select “Delete.” A window will appear to confirm the deletion.
A destination can be copied or cloned. To do so, right click on the name of the destination, then select “Clone.” A window will appear asking for the name of the new destination.
Select the destination from the left hand side. The settings from that destination will load in the main panel.
To aid in defining destinations quickly and accurately in a distributed environment, OM Plus can save destinations to multiple OM Plus servers at the same time. To do so, select multiple hosts from the “Hosts” drop down menu in the upper left corner. Right click on each host name in the destination selection list and make sure “Save Host” is checked. A green Plus logo will appear on the icon for each Save Host enabled server. Now, any destinations created or edited here will be saved to all Save Hosts.
NETWORK DESTINATION MODES
These destinations require access to a network in order to function.
The destination takes data over a raw TCP connection. This can be used to communicate with terminal/printer servers or laser printers with network interfaces. This is the preferred mode for printing to a remote network device because of its simplicity and low overhead.
The address here should be the host name or ip address of the device. “Port” is the port number on which to communicate with the device. Most devices will use port number 9100.
This is also the Mode used for the Print Confirmation. Please see PJL / MPCL Job Confirmation Types.
The network destination uses the LPD/LPR Transfer Protocol. Most network print devices support the LPD/LPR Protocol. The device for this destination type can be the host name, for example, hpjet18. Some destinations also require a queue name. For the proper queue name, refer to the manufacturer’s documentation.
LOCAL DESTINATION MODES
Local modes are used for destinations that do not require a transfer to another system. These include locally attached printers, as well as processes.
The Destination Device field displays an existing directory for output. For example, a directory called /reports/save for saving output requests with OM Plus. A tilde (“~”) character in the directory path expands to the user ID of the submitting user, therefore, if the directory path is specified as /reports/~, requests that user Bob submits would be written to /reports/Bob and reports that user Tom submits would be sent to /reports/Tom. By default, the file name is the request name, RIDnnnnn. This may be overwritten by the -o file=filename request parameter. Permissions on the destination directories should be set to prevent unauthorized user access to the contents. The target directory must already exist; OM Plus will not create it.
This destination type is specifically designed to work with Bottomline’s eComIntegrate products. For more information on configuring this device, please contact Bottomline.
PIPE EVENT (WINDOWS ONLY)
This mode can be used for vendor-supplied software to route output requests. Some network terminal/print server vendors supply software filters for the delivery system to use. There is usually a better OM Plus mode to use instead of these filters. See Event Processing: Windows Events, pipe.bat.
A queue designed to hold bundled requests until they are to be released to another destination. Reports submitted to this type of destination will be saved and held until an acceptable trigger event causes them to be released.
The destination connects to the Report Distributor pseudo-printer. Reports submitted to this type of destination will be broken into sub-reports based on content. The sub-reports then spool as new OM Plus requests. The Destination Device field is the path to a working directory for temporary files (for example, /tmp). See the section on Report Distributor for more details.
This destination is generic process destination, used to provide an environment to a specific process. When a job is sent to this Destination Type, it is de-spooled into a ‘User Filter’ process that provides the data to a process (script / program / utility) and returns that process exit code back to the OM Plus system.
WINDOWS PRINT QUEUE (WINDOWS ONLY)
The Destination Device field should contain the name of the Windows-defined printer to where the request should be sent. For example, an HP LaserJet 4 printer connected to the parallel port of the Windows print server and defined to Windows as HPLJ4 would be configured in OM Plus using a windows mode and a device of “HPLJ4.”
PARALLEL (UNIX ONLY)
Used to connect to a destination attached to the local server through a parallel port.
SERIAL (UNIX ONLY)
A printer connected to the server by a serial line. The device field should be the location of the serial port (eg. /dev/term/tty006).
OM Plus will output the result of the print stream to standard out which can then be routed to an executable process for additional processing.
SERVER TO SERVER
These modes are used for connecting to remote systems, but not typically to print devices directly.
OM PLUS LPD
Mode used to connect with a legacy LP Plus server. The server address and queue name must be given.
OM PLUS SERVER
Windows and UNIX. The destination is on a remote host system running OM Plus. This mode is used for passing requests between OM Plus systems, features encrypted transport, End-To-End status, and status tracing. An address and queue name must be specified.
The destination is a directory on a remote system. FTP Protocol can be used for the transfer. By default, the file name for the transfer is the request name RIDnnnnn. This may be overwritten by the -o file=filename request parameter. Enter the address, the target directory and the user name to use when connecting to this server. A ~ character in remotedir expands to the user ID of the submitting user. If remotedir begins with a / it is treated as an absolute path on the remote computer. If it does not, it is treated as a path relative to the home directory for the login ID used for the transfer. If the user is not specified, it defaults to the ID used when submitting to OM Plus. The $LPHOME/security/remotelogins file contains a table of host, user, and passwords for the FTP mode transfers. On Unix, make sure this file has permissions set to 600 to avoid compromising the remote user IDs. For example, ftp.someplace.com, someuser will transfer to the home directory of someuser.
OTHER PRINT SERVER
The destination print queue on another host computer supports the LPD/LPR Protocol. The host can be a Windows computer, UNIX system, Novell server, mainframe, or any other system that supports LPD/LPR printing. This mode may also be appropriate for a network printer that spools to a disk before printing. The server address must be given along with a viable queue name on that device.
This set of modes is used to send documents and notifications through other electronic means.
The print requests are routed to an email server using Blat (Windows) or Sendmail (Unix).
The print requests are routed to a fax server such as RightFax or VisiFax.
The print requests are routed to a pager service.
Type is used to link a Windows Print driver with a OM Plus Destination. In a properly configured system, OM Plus will automatically create shared Windows print queues for devices defined with a type. For setting up types, see the Types configuration screen.
This is a collection of time outs and maximums for the destination. In all cases but purge delay a value of “0” means unlimited.
Amount of time, in seconds, for a job to remain in the queue after cancellation or completion.
Time, in seconds, OM Plus will wait on a write to the destination device.
The amount of time, in seconds, for OM Plus to open a connection to the destination.
The amount of time a connection is allowed to remain open after the close command has been sent.
In streaming mode, this is the maximum amount of time allowed between jobs before the connection to the destination is closed.
The amount of time, in seconds we will suspend waiting on a write.
The speed at which jobs will be transferred to a destination. Mostly useful for legacy dot matrix type devices or printers at remote sites with limited bandwidth.
MAXIMUM REQUEST SIZE IN PAGES
The maximum number of pages a document can have and still be printed on this device.
This allows for a failover destination to be designated for this device. To set a device to use the included failover logic, check the “Failover on Error” box. If desired, select an alternate failover destination from the drop down menu or select the original destination to retry jobs on this printer until successful.
Should the banner page be printed for requests spooled to this device?
ADD CARRIAGE RETURN TO LINE FEEDS
On some printers and for some print jobs a line feed will be indicated but not a carriage return, causing the job to appear to have a “stair step” line of text off the right side of the page. This setting, when enabled, changes plain line feeds into carriage return line feeds that will reset the text line to the left edge after each line.
FORM FEED AFTER EACH JOB
Inserts a form feed at the end of each job if one is not already present.
FORM FEED AFTER EACH COPY
Inserts a form feed at the end of each copy of a job if one is not already present.
Holds (does not print) all jobs sent to this destination.
Allows jobs printed on this destination to be purged.
The name of the form that, by default, is defined to this destination. For more information on forms, see Form Maintenance.
Default Print Control file for this destination.
CUSTOM DATA FILTER
The full path name to a custom script to be used by this destination. The print job is delivered to the filter on standard in and the job is returned using standard out. If the filter does not return anything on standard out, this is a valid condition and OM Plus will accept that there is nothing further to process.
FILTER CONTROL FILE
Determines whether the control file will be processed as part of the print job when the custom data filter is executed.
What user or group should be notified in case of an error with this device.
PRINT STREAMS ALLOWED
Useful for legacy devices that may not support all print streams, or for destinations that use scripting for processing only certain types of data.
Extensions can be used to configure custom parameters for a printer. These are used exclusively in custom implementations and should not be used without direction from Plus Technologies.
The advanced tab provides a centralized list of some advanced features. Most of these settings are intended for use by legacy or power users. In several places the functionality is duplicated in other screens (Mode, Device, PJL, SNMP, etc) but some are unique to this screen.
Models can be defined to provide additional functionality to the destination. This must be the name of an executable script located in the models directory.
A comment field that can be used to give the name or contact information for a support technician.
Translation tables are used to substitute characters in the print stream. The translation table must be a specially formatted file located in the “trans” folder.
This is a print control file that will be inserted at the beginning of a print job. While some users still use these, in most cases it is better and more efficient to use a different method.