Database Utility - Database - System Database Tab
Use this tab to select your database configuration.
You cannot change the export properties for batches stored in SQL Server, Oracle, or IBM DB2. In this case, the Batch Information Editor tab is not available.
Use this tab to switch between the databases supported by Kofax Capture. You can switch databases as often as you like. You cannot switch databases if there are existing batches in the system. The default setting is Standard and uses the Microsoft SQL Server Express database (included and installed with Kofax Capture).
Use the SQL Server option to specify a SQL Server database. Selecting this option requires that you also supply the SQL Server database server name and the name of the database.
Use the Oracle option to specify an Oracle database. Selecting this option requires that you also supply the Oracle database service name.
Use the IBM DB2 option to specify an IBM DB2 database. Selecting this option requires that you also supply the IBM DB2 database server name and the name of the database.
In addition, when switching databases:
-
No Kofax Capture services or applications, including RSA, (other than the Database Utility) can be running on any client.
-
You must be logged in to Windows with administrative privileges.
-
If you select SQL Server, Oracle, or IBM DB2, you must have already installed your own licensed version of the selected database. Each workstation must also have the data provider installed. For Oracle and IBM DB2, the DB client .NET provider must be installed.
-
If you select SQL Server (with Store Batches in SQL Server selected), Oracle, or IBM DB2, you cannot switch databases back to Standard or SQL Server (without Store Batches in SQL Server selected) if there are existing batches in the system.
When you change databases, a message box displays the progress of the conversion. You can cancel at any time. If you cancel, your system is left in its original state.
If you switch to an SQL Server database, there is no need to change back to the Standard database before reinstalling or upgrading Kofax Capture.
The following restrictions apply to pre-existing SQL Server, Oracle, and IBM DB2 databases:
-
The default logon schema must be empty, with no predefined tables, stored procedures, views, etc. The schema objects are created by Kofax Capture.
-
The user must have rights to create the schema objects.
-
Two different Kofax Capture installations cannot use the same database schema.
Standard
Select this option to use the standard database that is included with Kofax Capture.
SQL Server
Select this option to use an SQL Server database. If you are using SQL Server Enterprise Edition, it is required that you have a Kofax Capture Evaluation or Enterprise license. If you are using SQL Server Standard Edition, a Kofax Capture Enterprise license is not required.
Server name
Enter or select the name of the SQL Server to which the Batch Catalog database is to be moved. The drop-down list
contains the names of all SQL Server visible to the workstation, except for any server with a name ending in
\Kofax Capture
(which indicates a standard
Kofax Capture
database).
A name of an SQL Server may not display if it is not consistently broadcasting its existence. You are free to enter a name not shown in the drop-down list.
If the Database Utility is run from a workstation that does not have SQL Server client installed, the drop-down list may be empty.
Database name
Enter the name of the database to be used or created on the target SQL Server system.
Create new database
Select this option to create a new database. The new database is created on the target SQL Server system. You may want to alter the resulting database using SQL Server commands to increase the size of the database, or change other options. Refer to your SQL Server documentation for additional information.
Authentication
This area contains the authentication options for your database.
Kofax Capture creates a special SQL Server application role, ACSystemRole, in the newly created database that automatically grants all needed privileges. Whenever Kofax Capture connects to the database, the ACSystemRole receives the needed permissions to run Kofax Capture. Users who might manage to get to the database through other means (such as SQL Server interactive utilities) cannot view or modify Kofax Capture data. However, be aware that system administrators have full access to the database tables.
- SQL-Server authentication - Login ID
-
Enter a login ID for the SQL Server. This login ID is used for converting the database and for authentication during processing. A default login ID is shown but you should change it as appropriate for your system.
The login ID must be a user that has Create Database privileges on the SQL Server. Once this login ID is used to create the database, it becomes the ID for the database owner, which gives it full permissions for the database. The login ID that is used to create the database is also used for all logins during Kofax Capture processing. Therefore, this login ID must retain the full permissions of a database owner.
- SQL-Server authentication - Password
- If required, provide a password for SQL Server authentication. By default, the password field is blank.
- Windows authentication using the network login ID
-
When selected, this option specifies that authentication is to be performed using the login ID of the currently logged in Windows user. This login ID is used for moving the database and for authentication during processing. All users require database owner permissions.
If you select this method of authentication, you need to enable all your Windows users and groups within SQL Server. Refer to your SQL Server documentation for additional information.
If you enable SecurityBoost, you cannot use the Windows authentication using the network login ID option.
Store Batches in SQL Server
By default, batch information is stored in Access databases. When selected, this option specifies that all new batches are stored in your SQL Server database instead.
When this option is selected, the Batch Information Editor tab on this window is disabled, because the export properties for batches that are stored in SQL cannot be changed.
This option can be applied only if there are no batches in the system. If there are batches in the system, an error message appears when the Apply button is clicked. If this happens, you can finish the batches and try again.
Oracle
These are the statuses associated with the respective batches. All possible statuses are displayed (Completed, Ready, In Progress, Suspended, Error, and Reserved); however, you cannot edit batches if the status is In Progress.
You cannot change the status of a batch from this tab.
Service name
Enter the name of the Oracle Net Service to which the Batch Catalog database is to be moved. The service name, used to identify Oracle Net server, is mapped to a port number and protocol.
User ID
Enter a login ID for the Oracle Net Server. This login ID is used for converting the database and for authentication during processing. The user must have privileges to create the schema objects.
The login ID must be a user that has user rights to create schema objects on the Oracle Net Server.
Password
Enter the assigned user password.
IBM DB2
Select this option to use an IBM DB2 database. This option is enabled only if the IBM DB2 .NET provider exists on the workstation, and the Kofax Capture installation has an Evaluation or Enterprise license. You must create an empty schema prior to installing Kofax Capture.
When this option is selected, the Batch Information Editor on this window is disabled, because the export properties for batches stored in IBM DB2 cannot be changed.
Server name
Enter the name of the IBM DB2 Server to which the Batch Catalog database is to be moved.
Database name
Enter the name of the database to be created on the target IBM DB2 Server.
Password
Enter the assigned user password.