Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Database Performance Analyzer (DPA) > DPA Documentation > DPA 12.1 Administrator Guide > Link together separate DPA servers > Set up a Central Server and add remote DPA servers

Set up a Central Server and add remote DPA servers

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 15, 2016

Views: 909 Votes: 0 Revisions: 4

Use Central Server mode to link separate SolarWinds DPA servers together. This is useful if:

  • You want to monitor more than 250 database instances. You can divide monitoring tasks between different DPA servers.
  • Your monitored databases are distributed geographically. You can install separate DPA servers in each location.

The Central Server collects  information from your remote servers and consolidates the data into a single interface. The Central Server has low overhead and no additional information is added to its repository database.

Set up a Central Server

  1. Install SolarWinds DPA on a server. This will be your Central Server.
  2. Log in to that instance as an administrator.
  3. On the DPA menu bar, click Options.
  4. Under Administration > Display, click Manage Central.

    Your SolarWinds DPA server should be listed as the Central DPA Server in the list of Registered Servers.

Add remote DPA servers

The user credentials for the Central and remote DPA servers must match. See Configure authentication for Central Server for more information.

  1. On the DPA menu bar, click Options.
  2. Under Administration > Display, click Manage Central.
  3. Click Add Server.
  4. Enter information about the remote SolarWinds DPA server.
  5. Click Test connection, and click Save.

    A successful test indicates that SolarWinds DPA can communicate with the remote server through the provider host and port. It does not indicate that DPA can authenticate users.

    If the test fails, check the host name in the Server Name field. Does it contain an underscore (_) character? An underscore is not valid for host names. If you cannot rename the host, enter the IP address.

  6. Repeat steps 1 - 4 for the remaining remote SolarWinds DPA servers.

The details of your remote SolarWinds DPA servers are not stored in the repository, but in a file on your Central Server, located here:

<DPA_Home>/iwc/tomcat/ignite_config/iwc/central/RemoteRepositories.json

This is a plain-text JavaScript Object Notation (JSON) file. No sensitive data is stored in this file.

Last modified

Tags

Classifications

Public