Server Preparation

Installation Guide › Plan Your Installation › Prepare Servers

Prepare Servers

The servers that you select to host the CA Server Automation software must meet the system requirements specified in the Release Notes.

CA Server Automation Server

The wizard provides a centralized installation, with components installed on a single Windows server. If your site requires it, you can install some components (for example, AIMs and Autoshell) across multiple servers. However, the CA Server Automation components (core) are not distributable.

To distribute components across more than one server, verify the following conditions:

Open the communication ports if components are installed across firewalls.
Install the Microsoft SQL Management Tools (OSQL, BCP) on the Microsoft SQL server database (Management Database).
Use the same authentication (Windows or SQL) for the Management Database and the Performance Database.
Synchronize all server clocks.

Use the following table to prepare the server for installing CA Server Automation.

Server	Requirements
For installing CA Server Automation	Valid path for installing CA Server Automation is identified. Microsoft SQL Server is accessible and configured. CA EEM server (local or remote) and users are identified. Active Directory is configured (if applicable). Required network ports are identified and open. Additional runtime locales are identified (if applicable). Community strings are defined. DNS server is working properly. If you are using DHCP for the IP address assignment, DHCP is configured to update the DNS server dynamically. Java Quick Test Pro (QTP) plug-in is not installed. Antivirus programs are stopped before installation. All systems and databases are backed up.

Server

Requirements

For installing CA Server Automation

Valid path for installing CA Server Automation is identified.
Microsoft SQL Server is accessible and configured.
CA EEM server (local or remote) and users are identified.
Active Directory is configured (if applicable).
Required network ports are identified and open.
Additional runtime locales are identified (if applicable).
Community strings are defined.
DNS server is working properly.
If you are using DHCP for the IP address assignment, DHCP is configured to update the DNS server dynamically.
Java Quick Test Pro (QTP) plug-in is not installed.
Antivirus programs are stopped before installation.
All systems and databases are backed up.

Management Database Requirements

Use the following table to prepare the Management Database servers for installation.

Server	Other Requirements
Management Database Server	TCP/IP is enabled. Remote connections are enabled. Authentication mode is enabled (mixed mode or Windows mode). TCP/IP port for the instance is static (dynamic is not supported). No existing databases are named AOM2 or DPM. No IP address is used as the server name for the local database.
Clients	The system PATH must have an entry for the client (or CA Server Automation does not recognize that the SQL Server is installed). OSQL.EXE and SQLCMD.EXE are in one of the system PATH entries.

Database Sizes for Best Performance

During installation, select an initial size for the Management Database. Selecting an appropriate initial size can avoid incremental resizing that leads to data fragmentation and performance issues.

Review the following table to select the best initial size for the Management Database.

Initial Size	Number of Systems	Disk Space
Small	1,000	1 GB—core components 500 MB—log files
Medium	5,000	5 GB—core components 1 GB—log files
Large	10,000	10 GB—core components 5 GB—log files

Initial Size

Number of Systems

Disk Space

Small

1,000

1 GB—core components

500 MB—log files

Medium

5,000

5 GB—core components

1 GB—log files

Large

10,000

10 GB—core components

5 GB—log files

Note: The SQL Server databases are set to Full Recovery Model by default, so the transaction log grows until it is backed up. Regularly schedule database backups.

Note: The Performance database defaults to 500 MB and increases automatically as needed.