Configure Epic

Give Epic print administrators control of their print environment inside and outside of Epic with Vasion Print (formerly PrinterLogic). Eliminate the need to install print queues on the Epic print servers altogether and move to a driver-less print model, reducing the work required to maintain the print environment.

There are two places you’ll need to configure settings for the Epic connector, in the Vasion Print (formerly PrinterLogic) Admin Console and inside Epic's administrative settings.

To use the Epic Connector functionality, contact your Vasion Print (formerly PrinterLogic) Customer Success Manager.

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.
  • Have a certificate signed by a Certificate of Authority (CA) trusted by your Epic instance.
  • Obtain an EMP record for use when configuring the Epic service that has system login access.

    Epic credentials are required to send detailed print job status updates back to the Epic server.

  • Collect the Epic Endpoint record (E0A) basic authentication username and password to use during the configuration.

Enable Epic Connector Service

  1. In the Admin Console, select the Service Client where you want to configure Epic.
  2. Select the Output Automation tab.
  3. Enter the DNS Name of the Service Client you are using for Output Automation.

    Output Automation tab showing the DNS Name section

    This DNS name must match the device certificate name. 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.

  4. Scroll down to the API & IPP Print Service section and select Enable API Print Service.

    1. If needed, change the port number to match your Epic settings. The Epic default is 31990.

      API Print Service section of the Output Automation tab

    2. Select Enable Basic Authentication.

      1. Highlight and delete the generated code.
      2. Enter in the Epic Endpoint record (E0A) basic authentication username and password.
      3. Format — username:password

      Authorization code section of the Output Automation tab

    3. Enter the information for your certificate using one of the following options:

      1. Path to Certificate — enter the file path to where your .pem and .key files are stored on the Service Client.

        Path to certificate option in the Output Automation tab

      2. Enter Certificate — paste the contents of the certificate and key files into the corresponding text boxes.

        Enter certificate opition in the Output Automation tab

  5. Enter the EMP Record credentials. These credentials must match the EMP credentials set inside Epic.

    API status update credentials section of the Output Mangement tab

  6. Select Save.

The Status section displays a Green circle and states the service is Online when everything is configured correctly.

Output Automation service status

API Print Service

For information on the API Services and print options, visit the Developer APIs documentation.

Optional Next Step

Troubleshooting Help