Configure your database and verify that computer name resolution is operating correctly on your network before you install a CA DataMinder server.
When you deploy CA DataMinder to client systems, identify its parent server (the CMS or gateway) by name or IP address. If you specify the CMS or gateway by its name, verify that the client systems can resolve this name. If they cannot do so, they cannot locate it. Choose a method of computer name resolution that suits the needs of your organization, for example, DNS or a WINS server.
Before installing a CMS or gateway server, your chosen database engine must already be installed and correctly configured on the target computer. For Oracle and SQL Server configuration guidelines, see the Database Guide.
For NTFS file systems, we recommend that you disable creation of 8.3 file names on the system hosting the CA DataMinder data folder. If 8.3 file creation remains enabled, performance can be adversely affected. To disable 8.3 file creation, you set the NtfsDisable8dot3NameCreation registry value to 1 (one) and reboot; for further details, search for this registry value on www.support.microsoft.com.
To simplify mass deployments, you can bulk create new gateway accounts and assign gateways to parent servers in advance of the CA DataMinder rollout. This enables you to deploy multiple gateways using a single source image (which identifies a single parent server) while ensuring that each gateway automatically connects to its 'correct' parent server immediately after installation. To bulk create new accounts, you use the Account Import feature.
Note: If you install Event Import or Import Policy on a gateway, the target server must meet the email archive integration requirements.
Utility machines inherit the common client system policy. For Content Proxy servers and iConsole application servers, the Communications Encryption policy setting (in the Security folder) and settings in the Logging folder are relevant.
|
Copyright © 2014 CA.
All rights reserved.
|
|