Manual Configuration of the EpicIntegrations Configuration File - Integration for Epic - English - Foundation 22.1 - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential

Integration for Epic

Platform
OnBase
Product
Integration for Epic
Release
Foundation 22.1
License
Premier
Standard
Essential

Scan Aquisition Server and Front Office Scanning settings are maintained in EpicIntegrations.config. This file was provided with the Integration for Epic installation files; it resides in the location of the Epic executables.

The following procedure describe how to configure the Scan Aquisition Server and Front Office Scanning settings in EpicIntegrations.config. Alternately, you can use EpicIntegrations Configuration to configure the file, as described under Creating a New EpicIntegrations.config File.

To manually configure settings:

  1. Open EpicIntegrations.config from the Epic executables directory.
  2. Locate the <servers> element under <OBEpicViewer>.
  3. Within the first <server> element, modify the following to map the Epic environment ID to the corresponding OnBase Web or Application Server.

    Element

    Description

    environmentID

    The Epic environment ID you want to map.

    url

    The Application Server URL to connect to for the specified environment ID. Both HTTP and HTTPS are allowed. You can use the server's hostname or IP address. The following formats are acceptable:

    • http://server/AppServer/service.asmx

    • http://server/AppServer/

    • http://server/AppServer

    dataresource

    The OnBase data source the scanning integration will use for the specified environment ID. This data source must be configured on the associated Application Server.

    For example, if the environment ID is PRD, the section might look like this:

    The environmentID, url, and datasource elements must be provided in the order shown. Make sure environmentID is first, url is second, and datasource is third.

    Note:

    If the environment ID contains a <, >, or &, then the value must be enclosed in a CDATA section. For example, if the environment ID is X&Y, then the environmentID element would use the following format: <environmentID><![CDATA[ X&Y ]]></environmentID>. If you use EpicConfigFileCreator.exe, this formatting is applied automatically as needed.

  4. Repeat for each environment ID. When you are finished, the file might resemble the following:
  5. Ensure all <server> elements reside between the <servers> opening tag and the </servers> closing tag. Each <server> element must have an opening tag and a closing tag.
  6. Save the EpicIntegrations.config file.