Configure Database Connections
The purpose of this article is to illustrate how to successfully configure and establish the two database connections, the ‘Data’ database and the ‘Client’ database, in order to use the NSS Console and it’s file system analysis capabilities.
Before establishing the connections, please ensure that the requirements described in the Database Server, Data Database, and Client Database sections of the Deployment Topology and System Requirements article are fulfilled. It is mandatory that the databases and the database server logins are configured correctly before a valid connection can be established.
A successfully established connection to the two NSS Databases:
- The Data database, commonly named “Data”
- The main database of NSS.
- Holds data collected by file system scanning operations.
- Also holds quota summary information when quotas are configured and the NSS Quota Update Service is running.
- The database can be given any name, “Data” is used in Northern’s documentation.
- The Client database, commonly named “NSS Client”
- Holds NSS console view configuration information, including users’ customized views and View Profiles.
- The database can be given any name, “Client” is used in Northern’s documentation.
|1||Open the Console interface (http://your-console-server-name/nssconsole).
If you are connecting to a database that has previously been used with the Console interface, i.e. Access Rules have previously been configured and are stored in the database that you are planning to connect to, you must log in to the Console with an account that has an Access Rule with administrative rights. If you login with an account that does not have these rights, you will be denied access to configure the connection to the Client database – after completing the configuration of the Data database, NSS will read any Access Rules stored there, denying access to further settings for any non-admin accounts.
|2a||Skip straight to step 2b if this is the first time you configure the database connections via the Console.
If you are connecting to a database that has previously been used with the Console interface and you are re-establishing those connections for some reason (e.g. the databases have been moved to a new SQL server, the Console Server has been replaced, etc.), you will be able to access the configuration item via the left-hand menu.
Under Administration (1), click on Database Configuration (2)
|2b||Configuring the connection to the ‘Data’ Database.
Click on the Configure button (3) related to the ‘Data’ database.
NOTE: The screenshot shows how the interface is displayed when you’re setting the connections up for the first time, without a left-hand menu.
|3||Enter the name of your database server under Host (4).
Enter the name of your ‘Data’ database under Database Name (5). “NSS” is used in this example.
Specify if Windows Authentication should be used by checking/unckecing Use Windows Authentication (6).
After entering the necessary information, click OK (7) to apply the settings.
|4||Configure the connection to the NSS Client Database.
Click on the Configure button (8) related to the ‘Client’ Database.
Specify the name of the Client database (9). “nssclient2” is used in this example.
Click OK to apply the changes.
|5||The Database Configuration page of the console should now show ticks next to the NSS Data Database and NSS Client Database configuration items. It should also show the following text:
As an additional step, you can navigate to Dashboards via the left-hand menu and create a new Dashboard in ‘My Dashboards’ or in one of the View Profiles – ensure that the new dashboard can be saved as expected (thus verifying that settings can be stored in the Client database).
If you are unable to establish the database connection, please verify that the requirements described in the Database Server, Data Database, and Client Database sections of the Deployment Topology and System Requirements article are fulfilled. Missing database permissions are usually the culprit when the NSS Console fails to connect to the two databases. Also, make sure that the database server name and the database names are correctly spelled.
For advanced troubleshooting, please contact the Support team at Northern.