To install a utility machine
The Installation Type screen opens.
The CA DataMinder server installation wizard starts in a separate window.
To install these components to a different location, click Change.
To check whether the target volumes have sufficient free disk space for the selected components, click Disk Space.
Important! If you install to a different location, the target path must not include folders whose names contain Far Eastern characters. The CA DataMinder infrastructure cannot handle these paths.
This folder contains all the configuration data and captured data associated with the current server. You can accept the default location or specify a different location.
Note: See the recommendation to disable 8.3 file names.
Go to step 9.
Click Change to specify a different location. Remote data folders are described below.
Important! Do not install the data folder to an encrypted folder or file system! Also, do not compress the data folder if you are using SQL Server.
You can specify a network file share, using the universal naming convention (UNC) or mapped network drive. For example:
\\MyMachine\share_name\target_folder
\\NAS_device\share_name\target_folder
Sharing and Security settings for the remote folder must allow Full Control for both the user running the installation wizard and the machine running the CA DataMinder Enterprise Server software.
Note: For SQL Server users, you cannot specify a network file share. This is a known issue. See the Database Guide; search the index for ‘Data folder: remote, and SQL Server’.
If you select Microsoft Jet, no further database configuration is needed. Go directly to step 18.
if you select Oracle or SQL Server, go to step 12.
Note: Regardless of the type of database engine, if the installation wizard is unable to validate the host server, for example because it is not switched on, the wizard adds a Bypass Database Validation check box to the screen. You can select this check box to skip the validation, but verify the spelling of the server name, otherwise the installation fails.
You must provide an appropriate service identifier (SID) to identify the correct database. The SID corresponds to the SID_NAME value in the listener.ora file on the Oracle host server. The installation wizard attempts to validate this SID if you chose the current machine as the host server.
Now go to step 15.
Select the host server. The IP port and database name are set automatically, though you can change both.
To set up your SQL Server database:
<machine name>\<Instance name>
Where <machine name> is the name of the server on which SQL Server is running, and <Instance name> is the name of the SQL Server instance. For example:
MyDBServer\Instance_1
WGN_<local machine name>
Where <local machine name> is the name of the server on which you are installing the CMS. For example, if this server is named CMS-HARDY:
WGN_CMS-HARDY
If you have already created a database for CA DataMinder, change the default name to the name used in SQL Server.
This is the main CA DataMinder database account. The infrastructure uses this account to access the CMS database. For SQL Server databases, the primary user owns the schema.
(Only available for Oracle CMSs) 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.
In all cases, you can specify existing database accounts or instruct the wizard to create new ones. If you specify existing accounts, verify that they have appropriate roles and privileges. The requirements for your Oracle users or SQL Server logins are provided in the Database Guide.
To specify the database user credentials:
button. In the resulting User Credentials dialog, specify the username and password for the database account. If this is a new account, select the Create User check box.
Important! All SQL Server accounts—for the Primary User, Search User, and even the database administrator in step 16—must use SQL Server Authentication! You specify the authentication method in the Login Properties dialog in SQL Server Enterprise Manager.
Note: The installation wizard does not try to validate these account details. Verify that you have entered them correctly, otherwise the installation fails.
If all the specified accounts are existing database user accounts, go directly to step 18.
button. In the resulting User Credentials dialog, specify the username and password for the database administrator account (but see the SQL Server warning in step 15.a).
By default, Oracle creates all new databases in the ‘Users’ tablespace, but we strongly recommend that you create separate tablespaces for the CA DataMinder database accounts. This has several advantages. For example, it allows precise monitoring of the CMS database and also permits off-line maintenance of the tablespace without disrupting other products that may be sharing your Oracle server.
Important! If you chose to specify a remote data folder in step 8, you will need to change the credentials of the infrastructure service.
Important! If you change any service logon account to a named user, you must manually assign the ‘Log on as a service’ security privilege to this account. See the next section.
|
Copyright © 2014 CA.
All rights reserved.
|
|