Installation Guide › Installing CA Virtual Assurance › Installation on Multiple Servers › Guidelines for an Installation on Multiple Servers

Guidelines for an Installation on Multiple Servers

To install CA Virtual Assurance components on different servers you must run the installation on each server. Select the appropriate components from the components tree during installation respectively. Due to dependencies between components, consider the following guidelines:

• If an installation ranges across firewalls, open the corresponding communication ports between the affected components.
• For seamless timezone operation, verify that your distributed computing environment is synchronized to a common time source (for example, NTP server, GPS).
• Verify that the SQL Management Tools (OSQL, BCP) are available on the server on which the Automation Management Framework runs. The SQL Management Tools (OSQL, BCP) are part of the SQL Server installation and required to access a local or remote SQL Server. The Automation Management Framework and all CA Virtual Assurance manager components which access the Management Database and Performance Database reside on one server.
• Verify that TCP is enabled for SQL Server and a static port (default: 1433) has been set. If you connect to a remote SQL Server, allow Remote Access in SQL Server. CA Virtual Assurance allows Windows or SQL Server authentication to access the Management Database and the Performance Database.
• If you use Windows authentication for a remote SQL Server, verify the following requirements: CA SM Domain Server, Apache HTTP Server, and Apache Tomcat services have to run under a nonlocal system account. The nonlocal system account (domain user account) must have the required access privileges for the manager server and the database server. If you use Windows authentication for a remote SQL Server, the installation program automatically prompts you for that user.

  These conditions are not required for SQL Server authentication.

• When you install the Distribution Server on a remote system, configure the Distribution Server to connect to the associated CA SM Domain Server.

Follow these steps:

1. Open the Services dialog from the Control Panel, Administrative Tools.

   The list of available services appears.

2. Open the Properties dialog for the CA SM Distribution Server.
3. Stop the service
4. Add the following parameter into the Start parameters field:

   -m <name of the system on which the CA SM Domain Server service runs>

5. Start the service and click OK.

Scenario: Maximal Distributed Installation

This scenario lists all those CA Virtual Assurance components that you can install on separate servers.

Server 1

CA Virtual Assurance manager components
SQL Server Management Tools (OSQL, BCP)

Server 2

CA EEM

Server 3

Management Database

Server 4

Performance Database

Server 5

Distribution Server

Server 6

SystemEDGE and AIMs

Depending on your implementation, a smaller number of servers can be sufficient.

Example

Remote databases on one server, remote Distribution Server, local CA EEM, SystemEDGE, and AIMs:

Server 1

CA Virtual Assurance manager components
SQL Server Management Tools (OSQL, BCP)
CA EEM
SystemEDGE and AIMs

Server 2

Management Database
Performance Database

Server 3

Distribution Server

More Information

Communication Ports