Complete the following steps to configure the required Scan Acquisition Server settings in EpicIntegrations.config.
These steps describe required settings only. For information about all settings, both required and optional, see OBEpicScanControl.
- Open EpicIntegrations.config.
-
In the <OBEpicScanControl> element, under <Init>, set the GeneralHKCU setting to 0 or 1. For example:
<GeneralHKCU>0</GeneralHKCU>
This setting specifies whether general registry settings (i.e., thumbnail settings) should be read from the HKEY_CURRENT_USER hive or the HKEY_LOCAL_MACHINE hive.
-
Set to 0 if general settings should be stored and read from HKEY_LOCAL_MACHINE .
-
Set to 1 if general settings should be stored and read from HKEY_CURRENT_USER .
For more information, see Choosing Where Registry Settings Are Stored.
-
-
Under <Init>, set the ScanHKCU setting to 0 or 1. This setting specifies whether scan registry settings should be read from the
HKEY_CURRENT_USER
hive or the
HKEY_LOCAL_MACHINE
hive.
-
Set to 0 if scan settings should be stored and read from HKEY_LOCAL_MACHINE .
-
Set to 1 if scan settings should be stored and read from HKEY_CURRENT_USER .
For more information, see Choosing Where Registry Settings Are Stored.
-
-
Specify the ServiceURL. This setting specifies the default Application Server.
Within the <![CDATA[ ]]> tag, enter the URL to the default Application Server. If the environment ID that Epic passes to OnBase is blank or invalid, the server specified here is used. For example:
<ServiceURL><![CDATA[http://server1/AppServer]]></ServiceURL>
-
Specify the ServiceDatasource. This setting specifies the default data source, which must be configured on the Application Server.
Within the <![CDATA[ ]]> tag, enter the name of the data source to be used if Epic passes in an environment ID that is blank, invalid, or not mapped to a data source (as described later in this procedure). If the ServiceDatasource is blank in this situation, the Scan Acquisition Server uses the data source configured in the Application Server's Web.config file.
<ServiceDatasource><![CDATA[dmdatasource]]></ServiceDatasource>
If a valid environment ID is passed in, then the data source mapped to the ID is used.
-
Under <Diskgroup>, set the Path value to the temporary storage directory for scanned images and documents. The directory should be defined in a local temporary location to which the workstation user has read and write access.
Note:
This directory must be unique for each scanning user. If users have unique user names, include the %username% variable to ensure the directory is unique for each user.
Note:Do not use the installation files directory as the Path.
-
Within the <![CDATA[ ]]> tag, enter the temporary storage directory for scanned images and documents. For example:
<![CDATA[C:\SAS\%username%]]>
-
The Path value can include the following environment variables:
Variable
Location
%systemdrive%
The drive where the operating system is installed (e.g., C:\).
%systemroot%
The drive and path to the Windows installation (e.g., C:\WINDOWS).
%temp%
The current user's temp folder (e.g., C:\DOCUME~1\JDOE\LOCALS~1\Temp).
%username%
The current user name (e.g., JDOE).
%userprofile%
The current user's profile path (e.g., C:\Documents and Settings\JDOE).
Note:If you use the %userprofile% variable, the value must point to another folder within that location, such as %userprofile%\SAS; it cannot be directly mapped to the root of %userprofile%.
%appdata%
The path to the current user's application data folder (e.g., C:\Documents and Settings\JDOE\Application Data).
Tip:Use the %username% variable to represent the scanning user's user name. When images are scanned, Scan Acquisition Server dynamically replaces the variable with the user name of the currently logged in user. For example, if the path is C:\SAS\%username%, when a user who's logged on to the workstation as JDOE scans images, the images are temporarily stored in C:\SAS\JDOE. This feature is particularly helpful in Citrix deployments.
-
-
If a keyword mapping file is configured, update the FilePath setting. Under <Mapping>, set the FilePath to the full path to the keyword mapping file (e.g., \\server\SAS\Mappingfile\epickeywords.txt).
Note:
It is highly recommended that this path be a shared network path. It points to the epickeywords.txt file.
- Save the EpicIntegrations.config file.
- Continue to Mapping Environment IDs in the Configuration File.