EBS does not have any OS requirements for local or remote printers. How printing is accomplished at the Operating System level is indiscernible to EBS; that is to say, whether the printer is: local, remote, using a print server, using TCP/IP printing, CUPS, or a printer with a HP JetDirect card and an IP address, EBS simply uses the command or program placed within the Apps driver.
The printer's OS communication path needs to be established by your OS / Network Administrator. At this level, the Administrator will need to contact the vendor of the third party software product or utility being used at the OS level to communicate with the printer for assistance. Also keep in mind if the printer will be printing reports other than the Text format, such as Postscript; if so, ensure that the OS print queue has the correct settings--such as the RAW setting in Unix--or the correct printer drivers--such as a Postscript printer driver in Windows.
The only EBS requirement is that the communication path must be established at the OS level of the Concurrent Processing (CP) server. Whatever command is used at the OS level (lp, lpr, print, etc), the same command must be used within the Apps printer driver and/or any EBS printing tools, such as Pasta.
On the CP server, as the applmgr, open a command window and verify that printing is possible. Check with your OS / Network Administrator for the appropriate print command and syntax.
On Unix:
lp -d <printer_name> -n<copies> <file_name>
lpr -P<printer_name> -#<copies> -T<"title"> <file_name>
On Windows:
print /D:\\<server_name>\<printer_name> <file_name>
print <file_name>
Note: Printers on the Windows platform with shared and/or networked printers may need to be registered with the Windows Universal Naming Convention (UNC) of \\Server_Name\Printer_Name, according to the print command that works form a DOS / Command window. When using the UNC to register the printer in the Apps form, include the slashes with the names.