Database users
The Datacap applications access the Administration and Engine databases and can optionally include Fingerprint databases. You must grant access rights to the Datacap components for the databases that they use.
Datacap applications can also include access to external databases that are used for lookups (Lookup) and to which data is exported (Export).
When all of these databases (Administration, Engine, Fingerprint, Lookup, Export) are used by a Datacap application, each Datacap component must be granted specific access rights to the appropriate databases.
| Datacap component | Access these databases |
|---|---|
| Datacap Server | Administration, Engine, Fingerprint, Lookup |
| Rulerunner | Fingerprint, Lookup, Export |
| Datacap Web Client, Datacap Desktop | Fingerprint and Lookup - when you run actions, such as validation task profiles, that use these databases |
| FastDoc | Lookup - when you run actions, such as validation task profiles, that use this database |
When Microsoft SQL Server, Oracle, or DB2® authentication is used for the database connection strings, then a single database account can be used for connections to each database. Create these credentials for this account (user ID and password) in the Datacap Application Manager.
When Windows authentication is used with SQL Server, then there must be one SQL Server account for each Windows account that is used by a Datacap component. Alternatively, Windows groups can be used to authenticate the Datacap component Windows account to SQL Server.
When you are using an authentication system that does not require users to be set up in your Datacap application, you must set up Datacap users for Datacap components for database authentication purposes.
For more information about database rights that need to be granted, see Database security permissions.