Configure Epic

Last Updated: July 10, 2026

Give Epic print administrators control of their print environment inside and outside of Epic with Virtual Appliance. 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 need to configure settings for the Epic connector, in the Virtual Appliance Admin Console and inside Epic's administrative settings.

To use the Epic Connector functionality, contact your Virtual Appliance representative.

Requirements

• You must have a functional Service Agent that meets the minimum required specifications. Refer to Service Agents.

  Running IPv6 on your Windows Service Agent may cause conflicts. You may need to disable IPv6 on the Service Agent's network adapter to resolve the conflict.

• Your Service Agent must be able to access https://agent-api.Instance FQDN/.
• Have a certificate signed by a certificate authority (CA) A trusted entity that issues and validates digital certificates. The primary purpose of a CA is to verify the authenticity and trustworthiness of a website, domain, and organization. trusted by your Epic instance.

• Obtain an Epic master file A subset of Epic's integrated production database. 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.

Endpoints

Here are the endpoints for this feature. The <ServiceAgentName> is the IP address or hostname of your Service Agent.

https://<ServiceAgentName>/ReceiveJob

https://<ServiceAgentName>/BatchOpen

https://<ServiceAgentName>/BatchClose

Ubuntu Service Agent

Customers with an Ubuntu (LTS) 22.04 Service Agent must run an additional command on the Service Agent after configuring the steps below. The command initializes the service.

sudo ln -s "$(cat /etc/pl_dir)/service_client/service-output-management/bin/libmako-adapter-lib.so" "$(cat /etc/pl_dir)/service_interface/lib/libmako-adapter-lib.so" 

Turn On the Epic Connector Service

1. In the Admin Console, select the Service Agent where you want to configure Epic.
2. Select the Output Automation tab.

3. Enter the Domain Name of the Service Agent machine.

   

   This Domain Name must match the device certificate name and the Service Agent must map this Domain Name to its local IP address. If this field is empty, the service will fail to start, and adds a "Failed to get host address" 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 port is 31990.

      

   2. Select Enable Basic Authentication.

      1. Select and delete the generated code.
      2. Enter the Epic endpoint record (E0A) basic authentication username and password.
      3. Use the format username:password

      

   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 Agent.

         

      2. Enter Certificate: Paste the contents of the certificate and key files into the corresponding fields.

         

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

   

6. Select Save.

The Status section shows a green circle and indicates the service is Online when everything is configured correctly.

API Print Service

For information on the API Services and print options, refer to API Print Service documentation.

Optional Next Step

• Configure High Availability.

Troubleshooting Help