Deployment Guide › iConsole Standard Searches, Reports and Policies › Requirements › Database Requirements › Primary User Requirements for Dashboard

Primary User Requirements for Dashboard

To ensure that the dashboard is correctly populated with data, your CA DLP primary user (or login) must be correctly configured to run data aggregation jobs. This is the account that you specify in the Database Accounts screen of the CMS installation wizard. It is the main account that CA DLP uses to access the CMS database.

Note: By default, the CA DLP primary login in is WGNUSER. If upgrading from version 6.0 or earlier (when the product was called Orchestria APM), be aware that the primary login name previously defaulted to APMUSER.

Oracle CMSs

Before you install the dashboard, ensure that your CA DLP primary user has been granted the CREATE JOB privilege (aggregation jobs must be owned by the primary user). To confirm that your primary user has this privilege, run this command:

SELECT * FROM DBA_SYS_PRIVS WHERE PRIVILEGE ='CREATE JOB';

If you primary user does not have this privilege, run the following command line as an Oracle SYS user:

GRANT CREATE JOB TO WGNUSER; COMMIT;

SQL Server CMSs

Before you install the dashboard, ensure that your CA DLP primary login (such as WGNUSER) has been added as a user in the msdb system database and has been already granted the msdb database role SQLAgentUserRole. For details, see 'SQL Server CMSs: SQLAgentUserRole role'.

Important! Do not confuse this WGNUSER database user in the msdb system database with the WGNUSER instance-level login!