Last updated: November 14, 2024
SAP Configuration
Once the LPD Service is configured and running on the Service Client, confirm the device settings with the SAP Business Client software.
Requirements
- LPD services running with at least one functional Service Client.
- If using high availability zones, ensure the Service Clients in the appropriate zones can communicate appropriately.
- Print queues configured Admin Console for each printer used to print from SAP. Ensure there are no spaces in the Printer Name and that each name is unique. See Require Unique TCP / IP Printer Names for details about the unique name setting.
- Port 515 is open from the SAP Spool Server(s) to the Service Client(s). You may change the port, but it needs to match on both SAP and the Service Client.
Definitions
- Spool Server
- An SAP application server that provides spool processing. It processes data to prepare it for transfer via the defined Access Method. At least one of these servers is required and is not replaced by the Vasion Print (formerly PrinterLogic) Output Automation solution.
- Device Type
- An option that is set on a printer object inside SAP that is SAPs version of a print driver.
- Access Method U
- The U refers to Unix Berkeley LPR, the original version of LPR used by SAP to forward jobs with this access method. This ties directly into Vasion Print (formerly PrinterLogic)'s LPD service.
Device Settings
Confirm the settings for the output device in SAP Business Client software.
- Access the Spool Administration: Initial Screen.
-
If updating an existing printer definition, enter the name of the printer in the Output Devices field and select Display. Otherwise, create a new Output Device.
- Ensure the Output Device has the following attributes in the Spool Administrator: Output Device (Display) window:
- Make sure the Device Type selected roughly matches the manufacturer and model for the destination printer.
- If the Device Type is set to SAPWIN, change to a device type that is appropriate for the printer. SAPWIN won't work with Access Method U.
- Select the Access Method tab.
- Ensure the Host Spool Access Method is set to U: Print Using Berkeley Protocol.
- In the Host Printer field, input the name of the host printer as its named in the Admin Console.
- In the Destination Host field, input the IP or hostname of the destination Service Client.
When using multiple Service Clients for load balance, input the Virtual IP Address configured for the Service Clients on the load balancer.
The load balancer for this traffic must be configured to use persistent or "sticky" connections so the initial acknowledgment messages and the print job themselves are forwarded to the same Service Client.
Test the Connection and Print Job
Check the Connection
Test that the port is open and traffic can flow to the configured destination.
On the Spool Administration: Output Device window, use the Check Connection button on the top menu bar. You can also use the Ctrl+4 keyboard shortcut. The resulting modal displays a success or failure message.
Sent a Test Print Job
- On the Spool Administration: Output Device (Display) window, use the Spool Requests button on the top menu bar. (To the right of the Check Connection button)
- In the Spool Requests for Device [device name] modal, select the Print button or use the Ctrl+P keyboard shortcut.
- In the Print Screen List modal do the following:
- Enter the name of your output device, or
- Select the button next to Output Device to search through the list of devices by name and select the device.
- In the Properties section, ensure the Print Time field is set to Immediately.
- Select the button with the green check to initiate the job.
Check the Print Job Status
Verify the print job was received by the LPD service.
- Return to the Spool Administration: Output Device (Display) window.
- Select the Output Requests button on the top menu bar. (To the right of the Spool Request button)
- In the Output Request for Device [device name] window confirm the status of the print job.
SAP only receives the status that communicates whether we successfully received a print job. The status does not indicate whether a job was then sent to the printer. Check the Admin Console to confirm the printer's print job status / history.
Troubleshooting Help
If the Output Automation logs have no activity from print jobs, make sure ports are open and the network traffic is flowing. You can use the Check Connection option of the Spool Administration: Output Device (Display) window to verify SAP is reaching the LPD service.
If the Output Automation logs show a error relating to an unsupported command, check the following:
- Make sure the Access Method for the output device is U.
- Make sure the Device Type for the output device matches the destination printer as closely as possible.
- If those look good, there may be a new message type that needs to be supported. Contact support.
In some setups, external applications may need to reach the Output Automation Service Client using a DNS name that resolves to an external IP address. However, this can cause issues the following issues:
- The Service Client cannot resolve the DNS name to its internal IP address.
- External DNS resolution conflicts with internal requirements.
Check if the Service Client can resolve the DNS name to its internal IP address. If the DNS name doesn't resolve correctly, you may need to modify the hosts file. See Troubleshoot DNS Resolution for Output Automation-Service Client
Ensure that the DNS name in the UI matches the one in the certificate used by the Service Client.
-
Week Ending In Nov 23rd, 2024
-
Output Automation IPP(S) Protocol
-
Released: November 12th, 2024
-
Android/iOS: November 11th, 2024
-
Released: November 11th, 2024