Multiple databases and their licenses need to be installed on one server.
KM7: All Versions
KM7 Premium only
When you one two or more KM7 licenses and want them hosted on a single server some additional configurations are required.
Determine the databases you want and some logical names. Note in the examples the consistence between names and where the KM7 prefix is used.
e.g.
¶ Database 1
Business unit = “Watercare Services”
DatabaseName = KM7Watercare.fdb
Environment = Watercare
Alias = KM7Watercare
¶ Database 2
Business unit = “Social Development Services”
DatabaseName = KM7SocialDevelopment.fdb
Environment = Social Development
Alias = KM7SocialDevelopment
Normally during the installation, the database configuration tool is run to create the database and is then removed from the file system at the completion of the installation.
For multiple databases, the database configuration tool is required to be run multiple times.
Open a command line prompt and run the installer with:
KM7Setup.exe /V LEAVEDBCFG 1
Running the setup this way will preserve some temporary files used by the installation so they can be used for multiple databases.
Open the aliases.conf
file in notepad.
The location of this file is:
C:\Program Files(x86)\WH Software\KM7\FB\aliases.conf
Or for 32bit Windows:
C:\Program Files\WH Software\KM7\FB\aliases.conf
Notepad must run as administrator in order to save your changes
There will be a single line
KM7=C:\ProgramData\WH Software\KM7\Database\KM7.FDB
Based on our examples above, we want to change this file to have just the following two lines:
KM7Watercare=C:\ProgramData\WH Software\KM7\Database\KM7Watercare.fdb
KM7SocialDevelopment=C:\ProgramData\WH Software\KM7\Database\KM7SocialDevelopment.fdb
This file is used by the database engine to associate a name (KM7WaterCare) with a database file (KM7Watercare.fdb)
If you wish to store the databases in a different local location this is where you define that location.
On the server (but the same changes will need to be applied to each workstation), edit the following file:
C:\ProgramData\WH Software\KM7\KM7.ini
In that file there will be two sections that look like this (likely the blank lines will be missing but you may make blank lines to make the file more readable):
[Environments]
Default=Environment-Default
[Environment-Default]
ServerName=localhost:KM7
Based on our examples above, we want to change this part if the file the following:
[Environments]
Watercare=Environment-Watercare
Social Development=Environment-SocialDevelopment
[Environment-Watercare]
ServerName=localhost:KM7Watercare
[Environment-SocialDevelopment]
ServerName=localhost:KM7SocialDevelopment
This change is making two “Environments” each of which point to another section in the same ini file, which in turn specifies the server (localhost) and alias (as we set earlier in aliases.conf)
Later, the same change needs to be made to all workstations (but possibly not all environments on each workstation), but on the workstations, the reference to
localhost
will be the name of the server on which the databases are hosted.
During the installation, the database C:\ProgramData\WH Software\KM7\Database\KM7.fdb
was created. We have changed all references so they are specific to each database, so this database (it may have been a blank one or may have been your KM7 database upgraded depending on the choices you made) must be renamed.
Change its name from KM7.fdb
to KM7Watercare.fdb
(or whatever name you have chosen)
We now need to make the other databases (only 'Social Development' in this example as we did the other database with the initial installation)
Run the program KM7DbCfg.exe
The location of this file is:
C:\Program Files(x86)\WH Software\KM7\Bin\KM7DbCfg.exe
Or for 32bit Windows:
C:\Program Files\WH Software\KM7\Bin\KM7DbCfg.exe
Social Development
Re-run KM7DbCfg.exe
for any other databases that need to be created.
Still on the server, for each environment one at a time do:
Still on the server, run KM7Back.exe
, click the configure button and ensure that all environments are selected for backup and ensure that the Windows Scheduled Task is created and active. See the article Overview of backups
Do not do anything that directly accesses the FDB database files such as your own backup processes or even anti-virus software. Read the documentation about this as it is very important.