NetResident - Network Content Monitoring Tool

Prev Page Next Page
System Requirements
What Network Content NetResident Can Analyze
What’s New in NetResident 3.0
NetResident Architecture
Deploying the Application
Before You Begin: Network Visibility
Step 1: Deploying the NetResident Service and Console
Step 2: Deploying NetResident Agents
Ensuring Connectivity Between the System Components
Tips and Tricks
Setting Up the Database
Step 1: Creating a New Database and Configuration File
Step 2: Selecting an SQL Server
Step 3: Selecting a Database Location and Name
Step 4: Setting Database Access Token
Step 5: Summary
Working with NetResident
Understanding the Difference Between the Display and Capture Filters
Remote Connections
Adding Exceptions to NetResident Agents
Manual SQL Server Installation
Analyzing Imported Capture Files
Frequently Asked Questions
Sales and Support

Step 4: Setting Database Access Token

In order to access the database, the application needs an access token, which is basically an encrypted piece of information that contains all the necessary credentials. In this step, the wizard prompts you to do one of the following:

a) If this a new, clean installation, use the Generate Token button to generate a new access token.
b) If you have created a new database for an existing installation, you can use a previously saved token. Normally, it is automatically loaded for you from the database configuration file.

Note that the SQL credentials contained in the token override the existing SQL credentials, so an attempt to change existing SQL credentials will generate a warning. The access token entry dialog is illustrated below.


Important: Be sure to save the access token, as you might need it to access the database if the configuration file is lost. Normally, the access token is stored in the encrypted configuration file, and you do not need to reenter it.

c) If you are creating a new configuration file for an existing database, enter the access token that you generated in the past, when you were creating the database. Note that you will be prompted to enter the access token only if no configuration file exists. Otherwise, the access token will be automatically read from the configuration file. Automatic loading of the access token from the configuration file is always a better option. The access token entry dialog is illustrated below.