2.6 Configuring Security Manager Settings

To avoid an error message when running the Discovery_CallDataAnalysis script or the CallData_AddDataSource scripts, use AppManager Security Manager to store the SQL user name and password information for each SQL Server hosting a Call Data Analysis agent. You also need to create Security Manager entries for each SQL Server you are using, including the Data Source, Data Warehouse, and Data Mart.

Security Manager entries are only required if you add a name in the SQL username parameter in the Discovery_CallDataAnalysis script and the CallData_AddDataSource scripts. If you leave the SQL username parameter blank, Call Data Analysis will use Windows authorization, and you do not need to create Security Manager entries.

If the Data Warehouse and Data Mart are located in the same SQL Server instance, the Call Data Analysis agent can use the same SQL user name from the Security Manager settings to access both databases.

If the Data Warehouse, Data Mart, and Data Sources are on different SQL Servers, create separate Security Manager entries for the following:

  • The Data Warehouse

  • Every Data Mart, each of which may be on a different server

  • Every Data Source, each of which may be on a different server, and that server does not need to be the same server as the Data Mart server

On the Custom tab in Security Manager, complete the following fields for each SQL Server you are using for this module:




Specify the SQL Server name and the instance name of the SQL Server hosting the Call Data Analysis agent or the Data Warehouse, the Data Mart, or the Data Source database.

sql$<sql server virtual server or cluster name>

For example, type sql$HOUSERVER22\CLUSTER


Specify the SQL Server username.

Value 1

Specify the SQL Server password.

Value 2

Leave this field blank.

Value 3

Leave this field blank.

Extended application support

Select this option to encrypt the new password in Security Manager. This option is required.