Applications Systems

Change DPA from an AWS Subscription to SolarWinds Commercial Licenses (BYOL)

Follow the instructions in this article if you are running DPA in the in the AWS Marketplace using subscription licensing but want to use traditional licensing (also called Bring Your Own Licenses or BYOL). You will install DPA on a new EC2 instance, point it to the current DPA repository, and apply your licenses. Your configuration and history will be retained.

First published date

10/29/2018 9:39 PM

Last published date

10/29/2018 9:39 PM

Overview

Follow the instructions below if you are running DPA in the in the AWS Marketplace using subscription licensing but want to use traditional licensing (also called Bring Your Own Licenses or BYOL). You will install DPA on a new EC2 instance, point it to the current DPA repository, and apply your licenses. Your configuration and history will be retained.

You cannot convert a subscription-based instance of DPA running in an AMI to traditional licensing. You must install DPA on an EC2 instance.
For more information about launching DPA in subscription mode, see Launch SolarWinds DPA on Amazon Web Services (AWS) on a Linux AMI

Product section

Database Performance Analyzer

Resolution

Install DPA on the EC2 instance

Deploy the EC2 instance. See the DPA system requirements .
Download DPA from the Customer Portal.
Install DPA on the new EC2 instance.

When the installation is complete, the DPA opens in your browser and launches the Repository wizard.
Do not complete the Repository creation wizard. Instead, stop DPA on the EC2 instance.
Copy the following file from the original DPA installation:
<DPA_HOME>\iwc\tomcat\ignite_config\idc\repo.properties
Paste the file into the same directory on the new server. (This connects the new DPA instance to the existing repository.)
If you have changed the default values for system or server properties, edit the following files on the new server to preserve your changes:
- server.properties
- system.properties
  
  In the system.properties file, do not copy over this cloud-specific option: com.confio.cloud.subscription.license.
Stop the original subscription-based DPA instance via the EC2 console. (Only one DPA instance can access the DPA repository.)

Do not terminate your subscription until the new setup is complete in case you need to access it again.

Start DPA and apply licenses

Start DPA on the new server or EC2 instance. (If DPA was already started, restart it.)

If you see either of the following error messages, use this information to correct the issue:
- The license files do not match this DPA Repository.
  
  Cause: You completed the Repository wizard after installing DPA.
  
  Correction: Remove the \licensing directory located in <DPA_Home>\iwc\tomcat, and restart DPA.
- Another DPA Server process is now controlling this Repository. In this case, either use the new IP address '', or shutdown the other DPA Server process and try again. Contact your DPA Administrator if you have questions.
  
  Cause: The original subscription-based DPA instance is still running.
  
  Correction: Stop the original subscription-based instance via the EC2 console.
Log in and apply licenses obtained from the Customer Portal.
When your instance is successfully installed and connected to the repository, and you see the database instances you were monitoring with their history, you can terminate the original EC2 instance with DPA in subscription mode and release the storage associated with it.

(Optional) Migrate the DPA repository

If you want to migrate repository, follow the instructions for your repository type:

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.