SimpleIndex lets you run any SimpleIndex job as a Windows service for fully unattended processing. This is particularly useful for high-volume, high-demand applications where scanned images are coming from many remote workstations, as well as small and large implementations utilizing network scanners or digital copiers. In server mode, images are saved to a “hot folder” on the server where they are processed automatically. SimpleIndex performs barcode recognition, OCR and other indexing tasks and exports formatted files to storage and database servers.
Server processing licenses may be added to any version of SimpleIndex. Unattended processing is possible without a server license, but a user must be logged on to the workstation for it to execute. Windows services run automatically when the computer is booted up, even if nobody is logged on. You must have a Server license to run SimpleIndex on Windows Server operating systems.
SimpleIndex Servers can run multiple jobs on different schedules on the same server, or run multiple instances of the same job simultaneously to take advantage of multiple CPUs.
- Run multiple jobs on different schedules
- Run multiple copies of the same job for parallel processing and increased throughput
- Server licenses can be purchased in 1 Million Page per Year increments as an add-on to any workstation license
- Unlimited page barcode processing license available with Advanced Barcode Server
- Server processing compatible with Windows 7 or above and all Windows Server versions
You can find sample formats of the command lines for Simple Software products below.
“C:\Program Files (x86)\SimpleIndex\SimpleIndex.exe” /c:”Path to job file”
“C:\Program Files (x86)\SimpleIndex\SimpleSend.exe” “Path to job file” /hide /run
“C:\Program Files (x86)\SimpleIndex\qb\SimpleQB.exe” “Path to job file” /hide /run
This is used to closed SimpleIndex after the job has been completed automatically.
Put this in the Post-Proc field under the Batch tab in the Job Options:
taskkill -f -im simpleindex.exe
In SQL Server, Oracle and MySQL (among others) user logons are associated with a default “schema” that determines which tables and views they can see.
Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.
To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.
You can also change the user’s default schema on the server to the one matching the table.
A third option is to create a view under the user’s default schema that selects the necessary records.
At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.
The paths to the configuration files that are stored in the list in the Service Control and Options panel is located in the registry here:
If your Job Settings Wizard configuration’s of Database mode setting is set to “Update Existing Records”, the database record and the image will be deleted when you delete an image from a batch. The Table Name must be an updateable query or table and you must have sufficient permissions for both the database record and the file.
You cannot delete files with SimpleSearch. To enable retrieval users to change indexes, rename or delete files, use a SimpleIndex Standard license.
There are a variety of ways to connect to your database. Detailed instructions are provided in the Manual (check the Help menu). Here is a brief overview of the steps involved: -Create a job configuration to scan and index files -On the database tab, set the “Database Mode” to “Insert New Records” -To use ODBC, enter the data source name or file in Data Source -To connect directly, select your database type under “Select a Data Source” and click Start. A series of dialogs will prompt you for database connection information. -Select destination Table or View and click Reload -For each index field, select the corresponding database field that will receive that field value -The “Output File Field” will receive the path to the exported file Once you have created records in your database in “Insert” mode, you can change to “Retrieve and View Records” and use SimpleIndex or SimpleSearch to search and view the files.
Yes. Image files can be inserted into binary fields in Access, SQL Server, Oracle, MySQL and other databases.
Check the “Store files as binary objects” option on the Database tab and the “Output File Field” setting can be mapped to a binary field.
If using PDF, MS Office or other non-image files, use the File Type Field to store the file extension of the stored file.
SimpleSearch mode will let you view files stored using this method as well.
If the database you use to store index information has security access features, you can use these to manage access to documents with SimpleIndex retrieval mode.
In your database, create user accounts and groups and assign them the appropriate permissions to records in your document database.
In SimpleIndex, check the “Require Logon” option on the Logging tab to force the user to logon to the database using the accounts you created. When they search and view documents, they will only be able to access records that the corresponding database user has been assigned access to.
On the Database tab there dropdown in the lower portion of the panel for Full Text OCR Field. Put the name of the field that will store the full-text data there. This must be configured both for Insert and Retrieval mode configurations. The database field needs to be sufficient length to store the entire text of your document. Of course, the Insert Mode configuration must have “Enable Full Page OCR” checked to generate full text data from images. Text from MS Office documents, PDF files and existing OCR text files can be used without setting this option. When designing your Retrieval Mode configuration, create a Text field to use for full text search queries. On the Database tab, set the corresponding “Database Field Name” to the full text database field. When searching on your full text field, SimpleIndex finds the text you enter no matter where it appears in the document. It is able to match partial words. It does not perform boolean or natural language search
Yes! We’ve made it simple to create a database that you can use to store index information and perform searches with SimpleIndex Retrieval Mode. Once you have configured a SimpleIndex job to scan and store documents on your network, use these steps to create a database to store index information for searching: 1. On the database tab, make sure “Create Generic Access DB” is selected in the drop-down and click “Start”. 2. Save the Access database in a location accessible to all SimpleIndex users. All the settings on this form will be filled in automatically after you save the database. 3. Change the “Database Mode” to “Insert New Records”. This means that when the job is run, new records will be added to the database as new files are processed. 4. Save the this configuration. 5. To create a configuration for searching and viewing, simply change the “Database Mode” setting to “Retrieve and View Records”. You may