Creating the configuration database and customer databases
|Article:HOWTO58527|||||Created: 2011-08-01|||||Updated: 2013-07-12|||||Article URL http://www.symantec.com/docs/HOWTO58527|
The configuration database specifies the locations of the customer databases, and it stores details of the SQL Server, database files, and log files to use. Each customer database stores details of departments, user roles, search results, and more.
You can set up one configuration database only, but you can set up multiple customer databases. The configuration database can reside on one SQL Server, and the customer databases can reside on a different SQL Server. You may find it useful to set up multiple customer databases if, for example, you want to separate the groups who are to perform searches in Compliance Accelerator. Suppose that your legal department and human resources department both need to perform searches. These two departments may not be able to share roles in a Compliance Accelerator system. Setting up two customers lets both departments use Compliance Accelerator without needing access to the same Compliance Accelerator setup.
Before you proceed, note the following:
To create the configuration database
If you have yet to display the Accelerator Manager website, start Internet Explorer and browse to the following location:
where server_name is the name of the server on which you installed the Compliance Accelerator server software.
In the Configuration Database Details page, enter your preferred details, and then click OK.
When Compliance Accelerator prompts you to do so, restart the Enterprise Vault Accelerator Manager service by using the Services snap-in to Microsoft Management Console.
In the left pane of the Accelerator Manager website, right-click the server node, and then click New Customer.
Complete the details in the Create Customer page, and then click OK.
Indicates that this database is a customer database for Compliance Accelerator.
Specifies a unique name for the customer. The name cannot contain any of the following characters:
\ / : * ? " < > | '
Identifies the journal mailbox that the customer uses. You can obtain the ID by looking at the property page for the journal vault in the Vault Administration Console.
One customer only must have a blank VaultID(s) field to designate that it is the default customer. All other customers must have a unique entry in the field, such as the required journal vault ID or a statement such as "Do Not Use".
If you type anything other than a valid journal vault ID in this field, Compliance Accelerator's Journaling Connector cannot apply any department ID tags for any monitored employees of the customer. As a result, the random sampling feature of Compliance Accelerator does not work for the customer, and you cannot use the department ID tags in searches. Random sampling and department tagging only work properly for the default Compliance Accelerator customer and those customers that have a valid journal vault ID in this field.
Directory DNS aliases
Specifies the DNS alias, server name, or IP address of the Enterprise Vault Directory service computer. You can specify IP addresses in either IPv4 or IPv6 format.
Take care to specify the correct DNS alias information. If the information is wrong, no vault stores will be visible in any area of the Compliance Accelerator client.
Administrator User or Group
Optionally nominates an Active Directory user account or group account as an administrator for the Compliance Accelerator customer database. This user or group has full administrative permissions in the customer database and typically assigns application-wide roles to other users. Specify the account details in the form domain\user_or_group_name; for example, "OurDomain\Marie.Lopez".
Note that the Vault Service account already has full administrative permissions in the customer database, so there is usually no need to nominate another user or group. However, you may want to do this if your company policy restricts the use of service accounts.
Enable Customer's tasks
Enables users to perform activities in the Compliance Accelerator client. If you uncheck this option, only automatic tasks like scheduled searches are permissible.
Specifies the name of the IIS virtual directory for the Legacy Reports website. This site lets you view reports in Crystal Reports (
.rpt) format that you created with Compliance Accelerator 2007 or earlier.
No two customers can share the same virtual directory name. The directory name must not include space characters or any of the following characters:
* ? \ / % ' "
Note that you cannot name the virtual directory for any Compliance Accelerator customer as "EVBAAdmin", because this name is reserved for the Accelerator Manager website.
Specifies the name or IP address of the IIS server that is to host the Compliance Accelerator site. You can type the IP address in either IPv4 or IPv6 format. However, you cannot type an IPv6 address that includes colons (:) or is enclosed in square brackets ().
The default entry for this field is the server on which you are running the Accelerator Manager website.
Manage Virtual Directory
Lets you administer the virtual directory by using the Compliance Accelerator client. By default, the option is checked.
Database Details section
Specifies the name or IP address of the SQL Server on which the customer database is to reside. You can specify the IP address in either IPv4 or IPv6 format. The default entry for this field is the server on which you are running the Accelerator Manager website.
Specifies the name of the customer database. The name cannot contain any of the following characters:
\ / : * ? " < > | '
Use Existing Database
Instructs Compliance Accelerator to use the specified existing database instead of creating a new one. If you check this option, many of the remaining boxes in the page become unavailable. By default, the option is not checked.
Data File Folder
Specifies a location for the customer database file. This location should be a valid, existing path on the SQL Server computer, and it must be a local path (not a network share path). For example, you might specify the path as
Log File Folder
Specifies a location for the database log files. This location should be a valid, existing path on the SQL Server computer, and it must be a local path (not a network share path). For example, you might specify the path as
Initial Database Size
Sets the initial size in megabytes of the customer database file. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to the file each time more is needed.
Initial Log Size
Sets the initial size in megabytes of the database log files. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to a file each time more is needed.
Specifies whether to use a Microsoft Windows user account to connect to the customer database. If you uncheck this option, you must set the SQL logon name and password to use for the database connection.
Connection Time Out
Specifies the amount of time in seconds to wait for connections to the customer database to complete before terminating the attempt and generating an error.
Connection Life Time
Specifies the time in seconds that a connection to the customer database is considered valid. When the time has elapsed, the connection is disposed of.
Max Pool Size
Specifies the maximum number of database connections that can be simultaneously opened to the customer database.
Specifies the full connection string, or Data Source Name (DSN), to use when connecting to the customer database. The process of creating and connecting to the database automatically fills in this field. Do not modify the details unless Symantec Support advises you to do so.
Wait for Compliance Accelerator to create the customer database. This process can take several minutes to complete.
Article URL http://www.symantec.com/docs/HOWTO58527