Configuring an application to use the database

You use the Datacap Application Manager to configure the application to use the database. Datacap Application Manager works well with separate Test and Production environments because it stores the information that is specific to the Datacap application environment such as database locations and physical paths.

In a Test and Production paradigm, the physical applications are identical. The rules, workflows, page types, and other components, are identical, except for the *.app file. The difference between the environments is what the Datacap Application Manager stores. In the Test environment, the Datacap Application Manager stores the Test environment details while the Production system has its own unique environmental settings.

When you configure a Datacap application for a DB2 , Microsoft SQL Server, or Oracle database, you can use a single schema name for all the Administration, Engine, and Fingerprint tables and indexes. (To do so, copy and edit the table and index SQL DDL in the ...Datacap\support\DBscript directory, then add the correct schema and tablespace name for the right SQL database type creating a new template.) You can also have multiple Datacap applications in the same database depending on volume of batches processed. However, you must use a different schema and tablespace name for each Datacap application. NOTE: It is harder to create a “tablespace” equivalent in SQL Server (file group) than on DB2 or Oracle server, which is the standard practice.

For any SQL database like DB2 , Oracle or SQL Server, each computer that accesses the database, for example TMS and RR servers, must have the correct 32-bit database client software installed. An Oracle Net Service Name must be created on that computer to connect to the Oracle databases.

For DB2 , if the user ID that created the database tables is different from user ID that is used in the connection string, you must also specify the user ID that created the database tables as the schema. To specify the correct schema, use the user ID in the connection string. Use CurrentSchema=user ID that created the tables.