Вы находитесь на странице: 1из 4

7/18/2017 Knowledgebase | ImageNow: Import Agent Technical Overview

Print | Send Link | Close

Author: Naomi Housknecht


Document ID: 160353
First Published: 12/5/2013 8:52 AM
Last Modified: 2/9/2017 1:40 PM
Last Published: 11/22/2016 11:17 AM
Channels: Internal; Customer Portal; Partner Portal;

ImageNow: Import Agent Technical Overview

Table of Contents

Overview
Technical requirements
Questions to ask
Information to capture
Sample INI and configuration
Related articles

Overview

The Perceptive Content (previously ImageNow) Import Agent is responsible for handling all
automated import routines on the server. This generic import facility is part of the
Perceptive Content Server software (running as a background thread) and is controlled by
the Import Agent service. It is used to automatically import files directly into the Perceptive
Content Server object store. After the object is imported, it is treated like any other
Perceptive Content document.

Technical requirements

Perceptive Content or ImageNow Server


A working directory where files to be imported are stored and processed

Questions to ask

These are the basic questions to ask during any investigation of an Import Agent issue.

Question Reason

How many Import Agents are Multiple Import Agents can be


there? used concurrently. This is
necessary to identify which one
is having problems.

Has it ever worked? To pinpoint configuration or


environmental issues

Is the corresponding Import To ensure the Import Agent is


Agent service running? running, especially if there are
multiple agents set up
https://lexmark--c.na56.visual.force.com/apex/Knowledge_Technical_Overview_Internal?popup=true&id=kA5i0000000L4fK&lang=en_US&pubstatus=o 1/4
7/18/2017 Knowledgebase | ImageNow: Import Agent Technical Overview

Does the account running the Import Agent must have


Import Agent service have permissions to read, write, and
Read, Write, and Modify remove files in the defined
permissions on all defined import directories. If
import directories and the files permissions are missing, errors
within them? may occur.

Information to capture

Obtain copies of the following types of files. If logging is not turned on to capture a
particular file type, turn on logging.

File/Information Reason

inserverImp.ini Configuration file for Import


Agent. If multiple Import Agents
are in use, collect all INI files.

Files are located in


[drive]:\inserver\etc.

Note: In ImageNow 6.7 and


lower, this directory is
[drive]:\inserver6\etc.

Any logs with inserverImp as To gather information about the


part of the log file name issue

Note: General Import Agent logs will be written to [drive]:\inserver\log, while error logs
will be written to [drive]:\inserver\log\error_logs\<yyyymmdd>. (In ImageNow 6.7 and
lower, the inserver folder is named inserver6.)

Sample INI and configuration

File Name Path to File

inserverImp.ini [drive]:\inserver\etc

Note: In ImageNow 6.7 and


lower, this directory is
[drive]:\inserver6\etc.

Configuration of the Import Agent is handled by modifying the inserverImp.ini file. There
are seven different methods for importing files into Perceptive Content using Import Agent,
described as follows:

INDEX_FILE – Import Agent obtains document keys from a separate index file, and
the data file is available on the Perceptive Content application server. The file can be
single-line or multi-line.

Tips

The index file is formatted as follows (the default delimiter is ^):

Drawer^field1^field2^field3^field4^field5^doctype^page^path^

https://lexmark--c.na56.visual.force.com/apex/Knowledge_Technical_Overview_Internal?popup=true&id=kA5i0000000L4fK&lang=en_US&pubstatus=o 2/4
7/18/2017 Knowledgebase | ImageNow: Import Agent Technical Overview

Note: A delimiter needs to be added after the path if the file location in the
index file is different than the import.directory location listed in the
inserverIMP.ini.

The number of delimiters on each line should not change.

Each field in the index file must be typed correctly, or the import will fail.

In the inserverImp.ini file, under the Key Mapping section, use <<index
provided>> for any document keys that will be provided in the index file.

The index file cannot contain any empty line breaks.

Documents that are not defined in the Index File will be ignored. For example, if
there are 100 documents in the working directory but only 15 defined in the
Index File, the other 85 documents will remain in the working directory.

COMBO – The Import Agent obtains document keys from the first line of the file and
the remaining data in the file is imported.

KEYMAPPING – When the import objects are TIFF-based, Perceptive Content looks
to the configuration file to determine the TAG to use when assigning the index data.

A single TAG can hold more than one Perceptive Content index value. Additionally,
multiple TAGs can be used to define a single document index. A TAG reference in the
configuration file causes the import facility to treat the imported object as a TIFF file.

Note: Setting a TAG reference for an import object of type text will cause an import
error.

This mode can also be used when the import objects consist of data only, and no
indexing information is provided. The import process is responsible for supplying the
index values. These values are set in the inserverImp.ini file and can be either
literal or dynamic values.

TIFF_TEXT_COMBO – This mode is used to import TIFF objects that are


accompanied by a text file containing an OCR extraction of the TIFF file. The import
process is responsible for supplying the index values. Index values are extracted from
the text file based on the search criteria defined in the inserverImp.ini file. Typically
this method is used in conjunction with the ImageNow Printer.

FILENAME – This mode is used when the import objects are data only, with the index
values being the file name.

DATA_CAPTURE – Import Agent sends files to Data Capture for indexing. Key
mapping is not performed by this agent, because files will be indexed according to the
Data Capture template used. Each directory that is monitored by this agent can be
assigned a different Data Capture template.

CAPTURE_PROFILE – Import Agent uses server-side capture profiles to import files


and set document keys. This mode ignores the following general settings:

send.to.queue
delete.source.objects.after.import
submit.to.content.server

Updated 10/20/2016 by Gary Dennis (Added Info for the INDEX FILE Import
type)

Related articles

https://lexmark--c.na56.visual.force.com/apex/Knowledge_Technical_Overview_Internal?popup=true&id=kA5i0000000L4fK&lang=en_US&pubstatus=o 3/4
7/18/2017 Knowledgebase | ImageNow: Import Agent Technical Overview

Import Agent FAQ


How to set up multiple Import Agents in Perceptive Content
Import Agent Throughput Performance Best Practices
How to import documents as a multipage TIFF using Import Agent
Troubleshooting Import Agent INDEX_FILE mode

Julio dos Santos

Updated 2/9/2017 by Ashley Cole (Updated inserverImp.ini for clarity)


Updated 11/22/2016 by Jason Gourse (added question regarding file and
folder permissions)
Updated 07/13/2016 by Adam Witt (fixed broken link for multiple import
agent setup)
Updated 06/24/2016 by Gary Dennis (Note about Index Delimiters)

Additional updates:

Updated 2/8/2016 by JohnMark Jones (revised index file format in


the Sample INI section, edited to reflect current products, and changed all
formatting to match current KB standards)

Is this the topic you were looking for? Yes No

Comments:

Submit
©2017 Perceptive Software | Legal Terms and Privacy Policy

https://lexmark--c.na56.visual.force.com/apex/Knowledge_Technical_Overview_Internal?popup=true&id=kA5i0000000L4fK&lang=en_US&pubstatus=o 4/4