Last updated: December 11, 2024
Configure IPP
Some cloud-enabled ERP / MRP solutions print via the IPP protocol. Our Output Automation solution supports the ingestion of print jobs into Output Automation using the IPP or IPPS protocols.
Requirements
-
You must have a functional Service Client that meets the minimum required specifications. See Service Client.
Running IPv6 on your Windows Service Client may cause conflicts. You may need to disable IPv6 on the Service Client's network adapter to resolve the conflict.
-
Your Service Client must be able to access
https://agent-api.app.printercloud.com/
.- If you are also using Off-Network Print, your service client must be able to access the following:
ofn.app.printercloud.com
ofn-gw.app.printercloud.com
Ensure you add the region code after printercloud, if applicable. Example: For Canada, add a 15 after printercloud:https://agent-api.app.printercloud15.com/
, EMEA add a 5, APAC add a 10, Singapore add a 20. - If you are also using Off-Network Print, your service client must be able to access the following:
- Have a certificate signed by a Certificate of Authority (CA) trusted by the source application submitting the job via IPP / IPPS.
- Source application must be able to reach the Service Client over its assigned IPP port; the default is 631.
Enable IPP(S) Service
- In the Admin Console, select the Service Client where you want to configure IPP / IPPS.
- Select the Output Automation tab.
-
Enter the DNS Name of the Service Client you are using for Output Automation.
This DNS name must match the device certificate name if using IPPS. The Service Client must map this DNS name to its local IP address. If this field is empty, the service will fail to start, and a "Failed to get host address" error is added to the log.
-
Scroll down to the API & IPP Print Service section and select Enable IPP(S) Service.
- Select Save.
Certificate
You only need to employ a certificate trusted by the source application if you use IPPS. Follow the steps below:
-
Select Enable TLS on IPP(S) Service.
-
Enter the information for your certificate using one of the following options:
The Status section displays a green circle and states the service is Online when everything is configured correctly.
Optional Next Step
Troubleshooting Help
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 Dec 14th, 2024
-
Released: Dec 12th, 2024
-
Released: Dec 9th, 2024
-
Output Automation IPP(S) Protocol
-
Android/iOS: Nov 11th, 2024