After installing the SQL scripts, you can install the CA DataMinder central management server (CMS) using the server installation wizard. For details, see 'Installing a CMS' in the Platform Deployment Guide.
In particular, note the following wizard screens:
Specify the SID or service identifier (for Oracle) or the database name (for SQL Server).
Enter the name and password for the various CA DataMinder database accounts: the primary user, search user and, optionally for Oracle CMSs, the schema owner.
(Oracle CMSs only) This optional account owns the database schema. Some organizations choose to have separate accounts for the primary user and the database owner. This is typically for security reasons, for example, to ensure that employees cannot connect to the CMS database as the primary user and delete sensitive data or drop the underlying database objects.
This is the main CA DataMinder database account. The infrastructure uses this account to access the CMS database. By default, this user also ‘owns’ the database schema unless a Schema Owner is specified.
CA DataMinder consoles use this database account when searching the CMS database for events. This is a secure account that is subject to row level security (RLS) when searching the database for events. This ensures that reviewers cannot see events that they are not permitted to see when they run a search. If multiple database security models are enabled on your CMS, specify a separate Search User database account for each security model.
You created the primary user and (optionally) schema owner accounts when you prepared the database, so you do not need to create these accounts now. But you may need to create the Search User account.
Note: For details about the requirements for your Oracle users or SQL Server logins, see the references at the end of this section.
Specify whether to enable data warehousing and whether to collect event participant data.
The iConsole dashboard and BusinessObjects reports for CA DataMinder require the data warehouse. If you want to run reports or dashboards that show results broken down by user group, you must also collect event participant data.
For full details about these deploymet options, see the Data Warehouse chapter in the Platform Deployment Guide.
(Required only you enable the data warehouse.) Enter the name and password for the following database accounts:
External reporting applications (such as BusinessObjects Enterprise) use this database account to connect to the Data Warehouse and CMS database.
This database account corresponds to the 'Unrestricted' security model. CA DataMinder consoles and external reporting tools can use this database account when searching the CA DataMinder Data Warehouse and CMS database for events. Unlike normal Search User database accounts, the Unrestricted Search User is not subject to row level security (RLS) when searching the database. If a reviewer has 'Unrestricted' security model, the reviewer can see any events when they run a search or report. Search results or reports are not restricted by policy class or the reviewer’s management group.
|
Copyright © 2014 CA.
All rights reserved.
|
|