TACTIC Database Configuration

TACTIC Database Configuration

By default TACTIC will look at localhost to the database. This is the simplest implementation and most installations will have the database on the same physical server as the TACTIC application servers. However, in scaling up TACTIC, it may become necessary to separate the database server from the TACTIC applications servers.

TACTIC can be configured to look at an external database by connecting through sockets of TCP/IP. This can be set in the TACTIC configuration file.

While it is possible to edit this file manually, it is often simpler to use the provided utility found in: <TACTIC_INSTALL_DIR>/src/bin/util/change_db_info.py

This command line script will ask a series of questions and update the appropriate configuration file

Usage:

python change_db_info.py

When executing, the script will ask configuration questions and show a default value in brackets. If the default is sufficient, merely press enter without entering anything in will accept the default.

Below is a sample output where all the default values are accepted:

TACTIC Database Configuration

Please enter the database vendor (PostgreSQL or Oracle):

(PostgreSQL) ->

Please enter database server hostname or IP address:

(localhost) ->

Please enter user name accessing the database:

(postgres) ->

Please enter database password:

(ENTER to keep password, '__EMPTY__' for empty password)

Enter Password ->

Vendor: [PostgreSQL]

Server: [localhost]

User: [postgres]

Save to config (N/y) ->

Once the values have been saved, a restart of TACTIC is required to start using the new database configuration.