To edit the configuration file(s) for your database

You must edit the configuration file(s) for your database. Some edits are required, and some are optional.

1.	Locate the default config file for your database in the librarymanager/conffolder.

You can make as many versions of the config file as you need. For example, if you have multiple databases for Detect (such as one each for development, quality assurance, and production), you can use a different configuration file for each of them. As a best practice, give the file a name that identifies the database to which it refers. For example, you could name a file that refers to your dev database as Detect_dev.config.

2.	Edit the configuration file(s) so that the jdbcDatabaseURL setting identifies the database to which to connect.

Although the examples shown here wrap onto multiple lines, in the configuration file each must be on one line.

For Oracle, modify it so that it identifies your database server’s name (or IP address), its port, and the name of the database.

jdbcDatabaseURL=<Detect Database Server name or IP Address>:<port>:<database name>

By default the port is 1521. If the default port is not used, you can find it in the tnsnames.ora file under the Oracle directory in NETWORK\ADMIN. It will also give the fully-qualified path required to reach the Oracle server. To test that it is a fully-qualified path, ping it.

For SQLServer,

jdbcDatabaseURL=//<Detect Database Server name or IP Address>:<port>;database=<database name>

If you intend to use the Library Manager to move just a few workspaces, then you can skip this step and instead create empty target workspaces using the Detect user interface before you import the workspaces. However, if you intend to move many workspaces you may find it too labor intensive to create them individually. In that case, use this step to set up the Library Manager to create them for you.

If you did not install Detect to the default path, or your database is on another machine, modify the following line in this file so that it points to your Detect database directory.

This setting identifies where the database scripts are stored. If they are on a remote machine, you must be able to reference the directory, or the files can be copied locally.

db.home.dir=c:/Program Files/Unica/AffiniumDetect/Application/Database

You must use forward slashes, as shown in the default path. Also, although this example wraps onto multiple lines, in the configuration file it must be on one line.

4.	Determine how you want to manage your database password. You have these options:

To allow the Library Manager to connect to the database automatically, modify the following line to replace CEE4 with the correct password.

jdbcPassword=CEE4

If, for security reasons, you do not want to store an un-encrypted password in a text file, you can copy the encrypted database password from the registry, or use the Password Encryption tool (PasswordEncryption.exe).

To have the Library Manager tool prompt you for the password, delete the line or comment it out by prefixing it with the hash mark ( # ).

5.	If you want to change the default directory for log files, modify the following line to specify the correct log file directory. Otherwise, skip this step.

logfile.home=C:/TEMP

You must use forward slashes, as shown in the default path.

6.	You may have more than one configuration file in the conf directory so that each configuration file points to a different database. To create multiple configuration files, you can optionally rename detect.config when you save changes to this file.