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 Datacap for a DB2, Microsoft SQL Server, or Oracle database, you can put the Administration, Engine, and Fingerprint schemas for the same application in a single database. You cannot put schemas for different applications in the same database.

For Oracle, each computer that accesses the database must have the Oracle 32-bit client software installed. A net service name must be created on that computer as well.

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.