Register an instance with the same server and instance name

10/10/2018 2:39 AM

10/10/2018 2:39 AM

There are times when the same machine and instance names are used and need to be registered in DPA because they are physically different machines. For example, your company has several different networks that have the exact same machine and instance name combinations. Currently, DPA will not allow this because it has a check for the same machine and instance so duplicate registrations are not accidentally done. Below is a procedure that will help workaround this problem.

Database Performance Analyzer

Modify a system property to allow DPA to register an instance with the same machine and instance name more than once. This is a one-time configuration and SolarWinds suggests setting this parameter back to False after registering an instance multiple times. This will prevent accidental registration of the same instance more than once when it is not wanted.

1. Open the system.properties file in a text editor. This file is located on the DPA server in C:\Program Files\SolarWinds\DPA\iwc\tomcat\ignite_config\idc.
2. Add the following parameter:

   # Allow instance to be registered more than once. This is good if someone wants
   # to register one database at a time in the same instance
   com.confio.idc.wizard.allowDuplicateDatabaseRegistration=true

3. Restart the Ignite PI Server service
4. Register the Instance. Now that DPA will allow for mutiple registrations, the second instance can be registered. However, both instances will have the same display name in the DPA interface and will be hard to tell apart.
    
5. Update the display name for one of the instances by running SQL statements similar to the following:

   select id, name from cond order by name;

   Find the instances, the one registered last will have a higher ID

   update cond set name = 'newDisplayName' where id = databaseID;

   The DPA home page displays the new name in approximately 10 seconds or at the next refresh.